Apache OpenOffice (AOO) Bugzilla – Issue 62001
my mails don't get thorough to the mailinglists [post mortem]
Last modified: 2007-04-06 18:20:32 UTC
Mails I send don't appear in the mailinglists. I still retrieve mails from other users (= I am still subscribed). Mails are sent successfully from my end, and so far I did not retrieve any failure notice or similar. My email is "Christian Lohmaier <cloph@openoffice.org>" The last mail that was delivered was http://www.mail-archive.com/dev@de.openoffice.org/msg10432.html From: Christian Lohmaier <cloph@openoffice.org> Subject: Re: [de-dev] Zeilenende in den html-Dateien To: dev@de.openoffice.org Date: Fri, 10 Feb 2006 21:18:04 +0100 Mail-Followup-To: dev@de.openoffice.org In-Reply-To: <43ECBA18.4060500@t-online.de> User-Agent: Mutt/1.4.1i All mails sent after that do not show up in archives and were not delivered either. The next one was sent From: Christian Lohmaier <cloph@openoffice.org> Subject: Re: [de-dev] Zeilenende in den html-Dateien To: dev@de.openoffice.org Date: Sun, 12 Feb 2006 00:42:52 +0100 Mail-Followup-To: dev@de.openoffice.org In-Reply-To: <6.2.3.4.0.20060211002234.01caa030@imap.uni-koeln.de> User-Agent: Mutt/1.4.1i it should have been a reply to http://www.mail-archive.com/dev@de.openoffice.org/msg10435.html but it doesn't show up. None of the messages sent after that show up. The mentioned thread in OOo's mail-archive: http://de.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=1278824 But note: All mailing-lists I'm subscribed to are affected, not only dev@de. ######## quick summary: mails worked until Date: Fri, 10 Feb 2006 21:18:04 +0100 after that, no mails were delivered
Created attachment 34165 [details] msg silently dropped
Created attachment 34166 [details] msg silently dropped
Please find attached two messages which didn't make it to the @openoffice.org address but were received successfully at the @yahoo.com resp. @sun.com account.
The mails hit the lists. For those where I did put Stefan in CC, I now as well recieved mail-delivery warnings (I didn't get any for the previous mails) ### the usual "This is a warning-only text" Your message could not be delivered for 4 hour(s). It will be retried until it is 5 day(s) old. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the attached returned message. The Postfix program <dev@de.openoffice.org>: connect to cylon2.sjc.collab.net[204.16.104.18]: Connection timed out <st@openoffice.org>: connect to cylon2.sjc.collab.net[204.16.104.18]: Connection timed out Reporting-MTA: dns; mail-in.m-online.net X-Postfix-Queue-ID: 5B1A170413 X-Postfix-Sender: rfc822; cloph@openoffice.org Arrival-Date: Tue, 14 Feb 2006 20:58:04 +0100 (CET) Final-Recipient: rfc822; dev@de.openoffice.org Original-Recipient: rfc822;dev@de.openoffice.org Action: delayed Status: 4.4.1 Diagnostic-Code: smtp; 420 Unable to connect to server Will-Retry-Until: Sun, 19 Feb 2006 20:58:04 +0100 (CET) Final-Recipient: rfc822; st@openoffice.org Original-Recipient: rfc822;st@openoffice.org Action: delayed Status: 4.4.1 Diagnostic-Code: smtp; 420 Unable to connect to server Will-Retry-Until: Sun, 19 Feb 2006 20:58:04 +0100 (CET) ######################### One other warning-report includes the other mail-server as well: The Postfix program <dev@de.openoffice.org>: delivery temporarily suspended: connect to cylon2.sjc.collab.net[204.16.104.18]: Connection timed out <st@openoffice.org>: connect to cylon1.sjc.collab.net[204.16.104.10]: Connection timed out Reporting-MTA: dns; mail-in.m-online.net X-Postfix-Queue-ID: 5726270692 X-Postfix-Sender: rfc822; cloph@openoffice.org Arrival-Date: Tue, 14 Feb 2006 20:56:18 +0100 (CET) Final-Recipient: rfc822; dev@de.openoffice.org Original-Recipient: rfc822;dev@de.openoffice.org Action: delayed Status: 4.4.1 Diagnostic-Code: smtp; 420 Unable to connect to server Will-Retry-Until: Sun, 19 Feb 2006 20:56:18 +0100 (CET) Final-Recipient: rfc822; st@openoffice.org Original-Recipient: rfc822;st@openoffice.org Action: delayed Status: 4.4.1 Diagnostic-Code: smtp; 420 Unable to connect to server Will-Retry-Until: Sun, 19 Feb 2006 20:56:18 +0100 (CET) ############################ The only warning for one of the mails directly to a list (without putting anybody in CC), was for a mail sent today night <qa@de.openoffice.org>: connect to cylon2.sjc.collab.net[204.16.104.18]: Connection timed out Reporting-MTA: dns; mail-in.m-online.net X-Postfix-Queue-ID: BD9BE73BAE X-Postfix-Sender: rfc822; cloph@openoffice.org Arrival-Date: Wed, 15 Feb 2006 01:34:07 +0100 (CET) Final-Recipient: rfc822; qa@de.openoffice.org Original-Recipient: rfc822;qa@de.openoffice.org Action: delayed Status: 4.4.1 Diagnostic-Code: smtp; 420 Unable to connect to server Will-Retry-Until: Mon, 20 Feb 2006 01:34:07 +0100 (CET) ############################ So still the question is: Why were the first mails not delivered (although other, newer ones/ones written in the same timeframe from others were delivered without problems) and if there were server-problems, why didn't it report an error-status?
We will take a close look of this issue.
may I ask when you will have a look? The last comment is almost two months old now.
Hi Cloph, Sorry for not updating this earlier. I had actually asked our operations team to check for any abnormalities, but they could not find any. They had asked us to gather more details; obviously we did not do that. There is another related issue 63493 (more around SPAM/VIRUS filtering) that is also open. It is possible that there could have been glitches while trying to setup that configuration. However, please let us know if you are still running into this. In the meantime we will check if from the old log files we can find any other details.
please have a look at issue 64090 as well. Although my mails recently did make it to the mailinglist, a mail sent to a mailing-list where I'm subscribed with another address has not been approved or rejected. (I'm not sure whether it was delivered to the moderators and simply overlooked, or whether it was dropped, as described in issue 64090)
Cloph, Issue 64090 is now closed since it was problem on the user's end. Are you still seeing the same issue? Please let us know. Thanks
No, I'm not currently seing the problem. If you can assure that future mails won't be silently dropped again, feel free to close this issue. I'd prefer if you could give a reason why the mails in question were dropped at all.
Hi Cloph, It is possible that there were some mail integrity issues. For Issue 65396 we are running some scripts to fix these. However, I will keep this issue open for now to see if we are getting reports from other users around this. Thanks
Closing this for now after the scripts were run to fix any mail integity. Please reopen should this happen again. For what it's worth, mails should not be dropped silently on the CEE end. Since we did not find any evidence yet, I am closing this issue. Any trace that leads to the fact that the mail reached the OOO MX on the CN end (*and* then was discarded without notice), will be immediately looked into.
closing, since it is now covered by issue 65953 PS: great to see that you did not get my comment to issue 65953 wrong :-)
reopen issue. I'm having the same problem again. Mails from me are not delivered to the mailinglists.
Last mail that made it through was on april 4 I got no bounce/failure notice so far, but the mails don't show up in the archives and were not delivered either. I still recieve mails from the lists.. Again I demand that mails must not be dropped silently. The last mail that made it through was http://de.openoffice.org/servlets/ReadMsg?list=users&msgNo=64536 The first that is dropped silently is: From: Christian Lohmaier <cloph@openoffice.org> Subject: Re: [de-users] Tabellenfehler To: users@de.openoffice.org Date: Thu, 5 Apr 2007 20:14:02 +0200 Mail-Followup-To: users@de.openoffice.org In-Reply-To: <4615005C.4010609@t-online.de>
Hi, Thank you for contacting CollabNet customer support. Will initiate our research based on the provided details & provide you an update once we have adequate information. Regards, Jeeva Support Operations
This time I feel like a fool, because the problem was at my end this time. (openssl incompatibility) Sorry for the inconvenience, restoring fixed issue-state.
closing. "false alert"/my fault.