Website link for 207.173.187.220
"Leisher, Doug" <[email protected]> Thu, 7 Dec 2006 09:18:02 -0500
| Newsgroups | gmane.mail.spam.dsbl.admin |
|---|---|
| Message-ID | <[email protected]> |
It's been 7 days since I last tried to remove my server from the blacklist. So, I initiated another removal request. This time, I made sure all necessary logging on my Exchange 2000 server was activated. The second request is the same as the first - my postmaster email account did not receive DSBL's email. The status on DSBL's site shows "Remote host said: 250 2.6.0 <[email protected]> Queued mail for delivery" If I look at message tracking on my Exchange server, there is no mail message from DSBL. Also, there is nothing in my BadMail folder or my Spam blocker (SMSMSE) showing that the message was either bad or blocked. In my Exchange log, here's all I see: 2006-12-07 13:07:22 205.231.149.48 ares.penguinhosting.net SMTPSVC1 WEB 207.173.187.220 0 HELO - +ares.penguinhosting.net 250 0 48 28 2172 SMTP - - - - 2006-12-07 13:07:22 205.231.149.48 ares.penguinhosting.net SMTPSVC1 WEB 207.173.187.220 0 MAIL - +FROM:<> 250 0 27 12 0 SMTP - - - - 2006-12-07 13:07:22 85.202.158.144 ip.85.202.158.144.dyn.sub-4.broadband.voliacable.com SMTPSVC1 WEB 207.173.187.220 0 QUIT - ip.85.202.158.144.dyn.sub-4.broadband.voliacable.com 240 1563 68 4 0 SMTP - - - - 2006-12-07 13:07:22 205.231.149.48 ares.penguinhosting.net SMTPSVC1 WEB 207.173.187.220 0 RCPT - +TO:<[email protected]> 250 0 38 35 0 SMTP - - - - 2006-12-07 13:07:22 205.231.149.48 ares.penguinhosting.net SMTPSVC1 WEB 207.173.187.220 0 DATA - +<[email protected]> 250 0 119 674 157 SMTP - - - - 2006-12-07 13:07:22 205.231.149.48 ares.penguinhosting.net SMTPSVC1 WEB 207.173.187.220 0 QUIT - ares.penguinhosting.net 240 2563 68 4 0 SMTP - - - - One thing I did notice is that the first line has "HELO". Test messages I sent from outside email accounts to my postmaster account I see has "EHLO" instead. From what I've read, this shouldn't matter. So, it appears that the DSBL message is not being delivered for some reason. Evidently, it's being held up before Exchange's message tracking sees it. Can anyone out there shed some light on this so I can get this fixed? Thanks! Doug Leisher Technology Coordinator Southern Fulton School District