Lyris ListManager 10.2 blocked domain troubleshooting
According to a posting I found online: “In Lyris 10.x and higher an unfortunate bug exists where if mail gets rejected even once from any email address from a particular mailhost, any domain and email address that MX host services gets permanently blocked without a retry.”
So I opened up and scanned through the delivery history for all 57 subscribers to our e-newsletter at that domain. What I noticed is that the software seems to attempt them alphabetically. E-mail addresses starting at the beginning of the alphabet had no delivery problems, while people towards the end experienced issues. I opened up the log messages for those that failed, and found this entry for [email protected]:
Tue, 14 Aug 2012 18:15:49 Sending email to: [email protected] <-- DNS info available for: xxxx.edu --> Attempting to connect to: xxxx.edu (000.000.00.000 25) <-- Connected to: xxxx.edu (000.000.00.000 25) <-- 220 yyyyyyyy2.xxxx.edu Microsoft ESMTP MAIL Service ready at Tue, 14 Aug 2012 18:15:49 -0500 --> HELO zzzzzzzzzzz.zzzz.zzz <-- 250 yyyyyyyy2.xxxx.edu Hello [111.111.111.111] --> MAIL FROM: [email protected] <-- 250 2.1.0 Sender OK --> RCPT TO:<[email protected]> <-- 250 2.1.5 Recipient OK --> DATA <-- 354 Start mail input; end with <CRLF>.<CRLF> --> (message body) --> [sent entire message body] <-- 554 5.1.0 Sender denied --> QUIT --> Mail stream '---------' is blocked by domain 'xxxx.edu' in step CONNECT.
Wed, 15 Aug 2012 19:20:34 - Mail stream '---------' is blocked by domain 'xxxx.edu'.
Everyone (alphabetically) before this address had no problems with delivery. Addresses after this one did, but their log messages just had a single line stating that the mailstream was blocked without the mailing ever being attempted. I’m pretty confident that this email address is the one sending the block signal back to our server which is then causing problems for other recipients at the domain.
To fix the problem I unsubscribed the email address in question, so that we no longer attempt delivery to it. Our e-news goes out each Tuesday, so next week we’ll know for sure whether this solved the problem.
Edit: Long after initially writing this blog I found a nifty little shortcut to troubleshooting the cause of a mailstream block by using the following URL:Â http://xxxxxxxxx.xxxx.xxx/utilities/administration/mailstreams/TopDomainDrillDown.tml?domain=xxxx.xxx¤t_list=xxxx











