Issue 36067 - asmx1 defers mail since 2004-10-25 6AM GMT
Summary: asmx1 defers mail since 2004-10-25 6AM GMT
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Mailing lists (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-25 10:12 UTC by stx123
Modified: 2006-09-28 15:37 UTC (History)
3 users (show)

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

Attachments
How to verify if SMPT server accepts mails (50.84 KB, image/png)
2004-10-25 12:01 UTC, pavel 		no flags Details
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 2004-10-25 10:12:29 UTC 
Our mail exchange host asmx1 defers mail since 2004-10-25 6AM GMT with the 
return message
(Deferred: 451 4.7.1 Please try again later)
Comment 1 Unknown 2004-10-25 11:33:42 UTC 
Accepting the issue , I have a internal issue PCN 32338  to the operations and 
they are working on this issue right now .

Jobin.
Comment 2 Unknown 2004-10-25 11:50:55 UTC 
The operations has worked on the issue and the issue has been solved  please 
verify and confirm that the  issue has been solved .

Jobin.
Comment 3 stx123 2004-10-25 11:58:33 UTC 
Sorry, but the issue still exists.
Comment 4 pavel 2004-10-25 12:01:15 UTC 
The attached screenshot shows you, how to test this yourself.

Please try it before saying it is fixed.
Comment 5 pavel 2004-10-25 12:01:58 UTC 
Created attachment 18643 [details]
How to verify if SMPT server accepts mails
Comment 6 Unknown 2004-10-25 12:53:15 UTC 
Our operations has found the root cause for the problem and it was due to  a 
component being down , it would take a few hours for all the mails to be 
restored . We would also be sending out a incident report with the information 
of why the mails were been deferred.

Jobin.
Comment 7 stx123 2004-10-25 18:45:36 UTC 
Please make sure that the report also contains why the issue incorrectly was
reported as fixed in the first instance.
Thanks for taking care of the issue, it's fixed.
Stefan
Comment 8 Unknown 2004-10-27 01:28:34 UTC 
According to the internal ticket, our operations engineer had to restart the 
mail component and successfully sent himself a test message.  At that time he 
saw a lot of mail delivering correctly in the maillog.  Sure, some mails did 
get deferred, but others injected both locally and remotely-- delivered
without problems.

At that point in his communication with the Support engineer he mentioned that 
it looked like the problem is under control. It took some time for the mail 
system to fully come up to speed on the queued up messages.
Comment 9 stx123 2004-10-27 09:24:04 UTC 
If you think the issue is fixed, please mark it as RESOLVED.
I don't see any need for further action. I reset the prio to it's intial value
for  tracking purposes.
Comment 10 Unknown 2004-10-27 10:57:51 UTC 
This is now RESOLVED.
Comment 11 Unknown 2006-09-28 10:36:42 UTC 
Could we close this issue .
Comment 12 stx123 2006-09-28 15:37:32 UTC 
Yes, closing. Feel free to reopen as necessary.