Mailing List SIMS@mail.stalker.com Message #15107
From: Bill Cole <listbill@scconsult.com>
Subject: Re: Why not receiving mail from this server?
Date: Sat, 10 Sep 2005 01:23:45 -0400
To: SIMS Discussions <SIMS@mail.stalker.com>
At 10:03 AM -0400 9/9/05, Linda Pautsch  imposed structure on a stream of electrons, yielding:
Hi,

I've got a couple people (maybe more) who are having trouble sending to my mail server. I'm running SIMS v 1.8b9d14 on OS 8.6. Here's an example of someone using a gmail.com email address that is failing:

09:42:14 4 SMTP(tcp) Connection request from [64.233.184.207:39066],seq=3506, 7/8
09:42:14 4 SMTP Line 3643 created for answering
09:42:14 4 SMTP-643() Got connection from [64.233.184.207:39066]
09:42:14 4 SMTP(tcp) Connection accepted from [64.233.184.207:39066], seq=3506, 7/8
09:42:14 4 SMTP-643([64.233.184.207]) Sending 220-realimagesdesign.com Stalker Internet Mail Server V.1.8b9d14 is ready.\r\n220 ESMTP is spoken here. You are welcome\r\n
09:42:14 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.relays.visi.com
09:42:14 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.sbl.spamhaus.org
09:42:14 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.koea.services.net
09:42:14 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.cbl.abuseat.org
09:42:15 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.opm.blitzed.org
09:42:15 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.cn-kr.blackholes.us
09:42:50 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.singapore.blackholes.us
09:43:25 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.nigeria.blackholes.us
09:43:59 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.malaysia.blackholes.us
09:44:34 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.brazil.blackholes.us
09:45:09 4 SMTP-643([64.233.184.207]) Looking for 207.184.233.64.relays.ordb.org
09:45:09 4 SMTP-643([64.233.184.207]) Input Line: EHLO wproxy.gmail.com\r
09:45:09 4 SMTP-643(wproxy.gmail.com) Looking for wproxy.gmail.com
09:45:09 4 SMTP-643(wproxy.gmail.com) Sending 250-realimagesdesign.com is pleased to meet you\r\n250-HELP\r\n250-ETRN\r\n250 EHLO\r\n
09:45:09 3 SMTP-643(wproxy.gmail.com) Abort Received, reason=54
09:45:09 3 SMTP-643(wproxy.gmail.com) Reading Failed. Error Code=-25010. Read:
09:45:09 4 SMTP disposing line 3643

Any idea of what I can do about this?

Stop taking three minutes to run all of your blacklist checks. That's not hard to do, since one that you are checking has been dead for a very long time (relay.visi.com) 5 others have been intermittently down for a few weeks (a VERY BAD SIGN) and remain painfully slow when they do answer, and one is misspelled (Korea has an r in it...). You could also check sbl-xbl.spamhaus.org  and get a composite of the SBL, CBL, OPM, and a 'fresh meat' subset of the NJABL proxies list, all with one query.

Fix those problems and SIMS will notice and respond to the gmail EHLO command faster.

Is it a gmail.com problem? There's another domain that I know of that is having trouble, but since I increased the log detail they haven't sent another test message, so I don't have any data on it.

Arguably it is a gmail.com (Google) problem. They should not be giving up so fast. The relevant RFC's say that, but Google is Google and suffers from a severe case of believing that they know best because, well, they are Google. Note that Google is very new to the business of running a very big mail system, and so probably lacks the internal experience to understand why 5 minutes was a good idea 20 years ago and remains a good idea today.

That said, you will find a lot of high-volume email senders and more than a few desktop clients timing out in less than 5 minutes, and 2 minutes seems to be a popular choice. If you see more than 2 minutes between 'Sending 220' and 'Sending 250' in many cases, you need to try to fix it or resign yourself to mail that doesn't get through.


--
Bill Cole                                  bill@scconsult.com

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster