Issue 419 - Errors during delivery to subscribers are sent to author
Summary: Errors during delivery to subscribers are sent to author
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-02-12 14:34 UTC by stx123
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Error Message (1.57 KB, text/plain)
2001-08-03 08:16 UTC, stx123
no flags Details
full error message (3.43 KB, text/plain)
2001-08-03 08:16 UTC, stx123
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2001-02-12 14:34:41 UTC
Shouldn't error messages from "openoffice.org" about not being able to deliver
messages to subscribers go to the list owner?
PLease find attached the example from interface-announce, where HTML messages
can't be delivered to asmith@14inverleith.freeserve.co.uk
Comment 1 stx123 2001-02-12 14:38:06 UTC
Created attachment 70 [details]
Error Message
Comment 2 Unknown 2001-02-12 16:56:40 UTC
If the client's MTA wasn't seriously broken, you would never have seen the
bounce message. The message which was delivered to
asmith@14inverleith.freeserver.co.uk had a return path which should have sent
the message back to EZMLM (which handles these things internally):

interface-announce-return-48-asmith=14inverleith.freeserve.co.uk@openoffice.org

In the attachment, you didn't include the message headers for the message which
you recieved (it appears to be only the bounced message contents) -- I would
guess that if you look at that, you'll find freeserve either sending it directly
to you (which would be wrong) or sending it to OOo with a bogus envelope-to.

I could say this with more certainty if I could see those headers, but I'm of
the opinion that there is literally no technical solution possible, and the
proper course of action is to unsubscribe this recipient (after sending them a
message explaining that their server's MTA is broken).

If you can provide the entire message which you recieved (raw) I'll verify the
problem and forward it to the people who run freeserve to see if they can be
convinced to fix it.
Comment 3 Unknown 2001-02-13 07:23:39 UTC
Stefan, 

Would you please provide the complete email message (including headers)? 
Comment 4 stx123 2001-02-14 11:20:29 UTC
Created attachment 72 [details]
full error message
Comment 5 stx123 2001-02-15 13:42:57 UTC
sorry, forgot to reassign
Comment 6 Unknown 2001-03-06 08:26:16 UTC
As this relates to mailing lists, 
reassigning to goolie 
for ownership 
(to coordinate technical support as required toward resolution). 

Please Accept Issue 
and follow-up with edk. 
Comment 7 Unknown 2001-03-08 01:08:32 UTC
Accepting issue and emailing edk
Comment 8 Unknown 2001-07-13 18:51:35 UTC
Goolie's technical bugs go to David.

-jh-
Comment 9 Unknown 2001-07-16 15:38:03 UTC
i accept this issue and will follow up with edk to find out what the status is. 
from edk's earlier comments this looks like it might have been a unique issue
with one user.  has anyone else seen anything similar to this since this issue
has been created?
Comment 10 stx123 2001-07-17 12:12:51 UTC
I never heard complains again from our developers here in Hamburg.
Comment 11 Unknown 2001-11-08 23:14:01 UTC
changing QA contact from bugs@ to issues@
Comment 12 Unknown 2002-03-08 21:45:25 UTC
Closing this.  Please reopen if this resurfaces.
Comment 13 michael.bemmer 2003-03-12 14:25:50 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 14 michael.bemmer 2003-03-12 14:26:18 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 15 michael.bemmer 2003-03-12 14:26:20 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for
details. First step in IssueZilla is unfortunately to set them to verified.
Comment 16 michael.bemmer 2003-03-12 14:43:20 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. 
Comment 17 michael.bemmer 2003-03-12 14:43:39 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. 
Comment 18 michael.bemmer 2003-03-12 14:43:45 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.