Issue 652 - Message not send to subscriber
Summary: Message not send to subscriber
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: http://www.openoffice.org/www-release...
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-05 13:41 UTC by stx123
Modified: 2007-09-23 15:38 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2001-04-05 13:41:14 UTC 
message http://www.openoffice.org/www-releases/msg00342.html was sent by Martin
Hollmichel as a news postings to releases@ooo. It was received and archived, but
didn't make it to the subscriber
openoffice-releases@staroffice-news.germany.sun.com.

Log Entries for the outgoing mail:
Apr  4 14:36:25 staroffice-news sendmail[6077]: OAA06077: from=news, size=1272,
class=0, pri=31272, nrcpts=1, msgid=<20010404.12362758@p0i8f5.Germany.Sun.COM>,
relay=news@localhost
Apr  4 14:36:25 staroffice-news sendmail[6079]: OAA06077:
to=releases@openoffice.org, ctladdr=news (9/13), delay=00:00:00,
xdelay=00:00:00, mailer=smtp, stat=Sent (OAA20589 Message accepted for delivery)
Comment 1 stx123 2001-04-06 21:30:26 UTC 
Please have a look at your logfiles before they are expired...
Comment 2 Unknown 2001-04-07 19:06:24 UTC 
I'm looking at the logs now.  There are entries which look problematic; I'm
doing research right now.  Unfortunately, I don't know if there will be
sufficient information to resurrect dead messages.
Comment 3 Unknown 2001-04-18 23:35:57 UTC 
Taking issue
Comment 4 Unknown 2001-04-19 00:22:08 UTC 
emailing edk for status report
Comment 5 Unknown 2001-04-20 21:08:45 UTC 
What happened is this : transient problems with lack of system resources started
on Mar 30th.  This seemed to be caused by problems with the tunnel connections
(Niels has some ideas as to what needs to be fixed on the Sun side) ... anyway,
the problem gradually got worse until Apr 5th, when it was resolved.  We're now
watching more carefully for it.

A significant number of outgoing messages were dropped during this period;
generally subscribers to mailing lists got a message from ezmlm about how one or
more messages from the resp mailing lists had bounced.  I believe there is no
way to recreate those messages, unfortunately; but this shouldn't happen again.

In addition to watching for tunnel processes hanging around, I'm looking into
changing qmail so that -- should this sort of thing happen again -- it'd attempt
retry, instead of dying with a complain about how qmail-remote was unable to
run.
Comment 6 Unknown 2001-04-20 21:14:43 UTC 
Ed, 

What needs to happen so that we can close this issue?  

Also, since you say the problem was resolved Apr 5, does that mean that
  a) this issue is resolved
  b) this issue is not resolved, but is no longer a P2
  c) this issues is resolved, but we should create another issue for the 
changes in qmail that you mention

Or something else?
Comment 7 Unknown 2001-04-25 00:57:02 UTC 
Issue resolved, per edk
Comment 8 Raphael Bircher 2007-09-23 15:38:46 UTC 
I close this issue