Issue 106447 - Can't send emails to @openoffice.org addresses
Summary: Can't send emails to @openoffice.org addresses
Status: CONFIRMED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: Unknown All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-29 17:54 UTC by john.mccreesh
Modified: 2013-02-07 21:42 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description john.mccreesh 2009-10-29 17:54:29 UTC
This seems to have started sometime yesterday evening UTC:

Oct 29 16:28:56 jpmcc-1 postfix/smtp[15868]: 076432794412:
to=<floeff@openoffice.org>, relay=cylon1.sjc.collab.net[204.16.104.10]:25,
delay=12907, delays=12905/0/1.9/0, dsn=4.0.0, status=deferred (host
cylon1.sjc.collab.net[204.16.104.10] refused to talk to me: 554
cylon1.sjc.collab.net)

Thanks

John
Comment 1 john.mccreesh 2009-10-29 20:11:41 UTC
Checked my IP 89.238.172.89 against the usual spam blacklists and that doesn't
seem to be the problem.
Comment 2 stx123 2009-10-30 08:40:52 UTC
Support, any idea about the reason for the rejection?
Comment 3 john.mccreesh 2009-10-30 12:42:36 UTC
Is there any update on this? I'm now building up an email backlog, and some of 
the emails are quite urgent - concerning next week's conference.

Thanks - John
Comment 4 john.mccreesh 2009-11-01 09:51:54 UTC
My email backlog started being accepted at Oct 31 20:15:38 UTC and now
everything appears to be ok:

Nov  1 09:43:04 jpmcc-1 postfix/smtp[30452]: 5571D2794409:
to=<floeff@openoffice.org>, relay=cylon1.sjc.collab.net[204.16.104.10]:25,
delay=2.1, delays=0.06/0.21/0.88/0.97, dsn=2.0.0, status=sent (250 ok:  Message
32242877 accepted)
Nov  1 09:43:04 jpmcc-1 postfix/qmgr[30329]: 5571D2794409: removed

Please tell me what you changed and close the issue.
Comment 5 stx123 2011-03-23 16:22:31 UTC
Reset QA Contact to new default