Yes, I admit there is much to learn. I have much to learn about DNS. Just when you think you've got it, an RFC change (in March) throws everyone, and expecially me for a loop.
I just got off the phone with Eric S and he was kind enough to let me point Imail to one of his DNS servers until tommorrow. Here is a successful email as reported in the syslog: 20021205 135425 127.0.0.1 SMTP (1856) Connect hotmail.com [65.54.254.151:25] (1) 20021205 135425 127.0.0.1 SMTP (1856) 220 mc4-f27.law16.hotmail.com Microsoft ESMTP MAIL Service, Version: 5.0.2195.5600 ready at Thu, 5 Dec 2002 14:02:55 -0800 20021205 135425 127.0.0.1 SMTP (1856) >EHLO telesite.com 20021205 135425 127.0.0.1 SMTP (1856) 250-mc4-f27.law16.hotmail.com (02.00.05.0005) Hello [209.55.118.2] 20021205 135425 127.0.0.1 SMTP (1856) 250-SIZE 3565158 20021205 135425 127.0.0.1 SMTP (1856) 250-PIPELINING 20021205 135425 127.0.0.1 SMTP (1856) 250-8bitmime 20021205 135425 127.0.0.1 SMTP (1856) 250-BINARYMIME 20021205 135425 127.0.0.1 SMTP (1856) 250-CHUNKING 20021205 135425 127.0.0.1 SMTP (1856) 250-VRFY 20021205 135425 127.0.0.1 SMTP (1856) 250-AUTH LOGIN 20021205 135425 127.0.0.1 SMTP (1856) 250-AUTH=LOGIN 20021205 135425 127.0.0.1 SMTP (1856) 250-X-HMAUTH 20021205 135425 127.0.0.1 SMTP (1856) 250 OK 20021205 135425 127.0.0.1 SMTP (1856) >MAIL FROM:<[EMAIL PROTECTED]> 20021205 135425 127.0.0.1 SMTP (1856) 250 [EMAIL PROTECTED] OK 20021205 135425 127.0.0.1 SMTP (1856) >RCPT To:<[EMAIL PROTECTED]> 20021205 135425 127.0.0.1 SMTP (1856) 250 [EMAIL PROTECTED] 20021205 135425 127.0.0.1 SMTP (1856) >DATA 20021205 135425 127.0.0.1 SMTP (1856) 354 Start mail input; end with <CRLF>.<CRLF> 20021205 135425 127.0.0.1 SMTP (1856) >. 20021205 135426 127.0.0.1 SMTP (1856) 250 <[EMAIL PROTECTED]> Queued mail for delivery 20021205 135426 127.0.0.1 SMTP (1856) rdeliver hotmail.com [EMAIL PROTECTED] (1) [EMAIL PROTECTED] 2480 20021205 135426 127.0.0.1 SMTP (1856) >QUIT 20021205 135426 127.0.0.1 SMTP (1856) 221 mc4-f27.law16.hotmail.com Service closing transmission channel 20021205 135426 127.0.0.1 SMTP (1856) finished d:\IMAIL\spool\Q0d1f78609a8.GSC status=1 20021205 135426 127.0.0.1 SMTP (1856) d:\IMAIL\spool\Q6d4a0014023eabdd.SMD 20021205 135426 127.0.0.1 SMTP (1856) processing d:\IMAIL\spool\Q6d4a0014023eabdd.SMD 20021205 135426 127.0.0.1 SMTP (1856) Trying hotmail.com (0) 20021205 135426 127.0.0.1 SMTP (1856) Connect hotmail.com [65.54.254.140:25] (1) 20021205 135426 127.0.0.1 SMTP (1856) 220 mc3-f23.law16.hotmail.com Microsoft ESMTP MAIL Service, Version: 5.0.2195.5600 ready at Thu, 5 Dec 2002 14:02:55 -0800 20021205 135426 127.0.0.1 SMTP (1856) >EHLO commandline.net 20021205 135426 127.0.0.1 SMTP (1856) 250-mc3-f23.law16.hotmail.com (02.00.05.0005) Hello [209.55.118.2] 20021205 135426 127.0.0.1 SMTP (1856) 250-SIZE 3565158 20021205 135426 127.0.0.1 SMTP (1856) 250-PIPELINING 20021205 135426 127.0.0.1 SMTP (1856) 250-8bitmime 20021205 135426 127.0.0.1 SMTP (1856) 250-BINARYMIME 20021205 135426 127.0.0.1 SMTP (1856) 250-CHUNKING 20021205 135426 127.0.0.1 SMTP (1856) 250-VRFY 20021205 135426 127.0.0.1 SMTP (1856) 250-AUTH LOGIN 20021205 135426 127.0.0.1 SMTP (1856) 250-AUTH=LOGIN 20021205 135426 127.0.0.1 SMTP (1856) 250-X-HMAUTH 20021205 135426 127.0.0.1 SMTP (1856) 250 OK 20021205 135426 127.0.0.1 SMTP (1856) >MAIL FROM:<[EMAIL PROTECTED]> 20021205 135426 127.0.0.1 SMTP (1856) 250 [EMAIL PROTECTED] OK 20021205 135426 127.0.0.1 SMTP (1856) >RCPT To:<[EMAIL PROTECTED]> 20021205 135426 127.0.0.1 SMTP (1856) 250 [EMAIL PROTECTED] 20021205 135426 127.0.0.1 SMTP (1856) >DATA 20021205 135426 127.0.0.1 SMTP (1856) 354 Start mail input; end with <CRLF>.<CRLF> 20021205 135426 127.0.0.1 SMTP (1856) >. 20021205 135426 127.0.0.1 SMTP (1856) 250 <002501c29c8d$513d5150$6b01a8c0@pc> Queued mail for delivery 20021205 135426 127.0.0.1 SMTP (1856) rdeliver hotmail.com [EMAIL PROTECTED] (1) <[EMAIL PROTECTED]> 6111 20021205 135426 127.0.0.1 SMTP (1856) >QUIT 20021205 135426 127.0.0.1 SMTP (1856) 221 mc3-f23.law16.hotmail.com Service closing transmission The problem seems to be pointing to Hotmail. Eric S also found out that their TTL's are not as short as everyone thinks. And Julie, I think your issue might have been a badly implemented virtual host, and it is likely that the default key change/fix you mentioned is not going to affect Imail and Hotmail exchanges. It could have been a resolved DNS issue by your upstream provider (by chance). J.J. Beatrice, President Commandline Media, LLC http://www.commandlinemedia.com/ 877-306-8777 TF California 310-306-8777 T 310-306-0887 F Ohio 440-684-0483 T/F -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Julie Silverman Sent: Thursday, December 05, 2002 12:50 PM To: [EMAIL PROTECTED] Subject: RE: [IMail Forum] hotmail rejection??? Hi Guys, We had a similar problem earlier this week with MSN.com SMTP server rejecting connections from our IMail Server (running 7.13 HF1). Another related thread here in the forum described not being able to send mail to a certain domain. Here's what happened and how we fixed it... Problem: We noticed on a Monday that approx 1500 messages per day were piling up on our spool directory destined for msn.com email addresses. Our mail server would make 96 attempts to deliver each message (every 30 minutes for 48 hours). We could send mail to all other domains except this one. The log entries looked like this: 12:01 01:15 SMTP-(00000168) processing G:\IMAIL\spool\Q0fb5ee6.FWD 12:01 01:15 SMTP-(00000168) Trying msn.com (0) 12:01 01:15 SMTP-(00000168) Connect msn.com [207.46.181.13:25] (1) 12:01 01:15 SMTP-(00000168) 12:01 01:15 SMTP-(00000168) SMTP_DELIV_FAILED 12:01 01:15 SMTP-(00000168) >QUIT 12:01 01:15 SMTP-(00000168) 12:01 01:15 SMTP-(00000168) requeuing G:\IMAIL\spool\Q0fb5ee6.FWD R0 T14 12:01 01:15 SMTP-(00000168) finished G:\IMAIL\spool\Q0fb5ee6.FWD status=3 Not very descriptive. No error code or nothing. Checked all of these things: DNSReport.com said we looked good. Our DNS servers do allow recursive lookup for IPs in our network. We *could* Telnet to MSN's SMTP servers from the mail server machine. NIC settings, TCP/IP settings and MTU looked okay. It's a 3Com NIC that's been working fine for more than a year. Read every IMail KB article and Forum message that was remotely related - no luck. Finally in desperation I cracked open the system registry and started going through every setting under HKLM->Software->Ipswitch->IMAIL one-by-one and compared them to the registry of one of our customer's machines that's running IMail. Under each IP address key there are three values: (Default) Aliases Official Here's a picture from the IMail site that shows this: http://support.ipswitch.com/kb/IMAGES/1.gif The IP key for the main host for the entire mail server had the following entries/values: (Default) = mail.domain.com Aliases = domain.com (in hex, if I remember right) Official = mail.domain.com I cleared the entry mail.domain.com from the (Default) key and *poof* like magic! MSN.com started accepting our mail immediately (no reboot required). Apparently that one little reg key affected how (or if) MSN's SMTP servers determined our official hostname, did a reverse dns lookup or whatever other checks their SMTP servers are doing this week. Geez! Hotmail, Yahoo, AOL or any other SMTP server on the 'net didn't seem to have a problem with the previous registry settings and would allow us to connect with no problem. So, what's up with MSN anyway? Regards, Julie Silverman Microsoft Certified Systems Engineer, Network Geek ---------------------------------------------------------- Acme Internet http://www.acmeinternet.com voice: 952-928-8828 Microsoft Certified Partner ---------------------------------------------------------- ---------- Original Message ---------------------------------- From: Len Conrad <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Thu, 05 Dec 2002 03:25:51 -0600 > >>If it was a DNS problem on our end, what would you guess it might be? > >commandline.net has no DNS errors, so Hotmail shouldn't be having any >problem validating you in DNS. > >>The TTL on our end? Meaning we have updates, albeit old data, still in >>our nameserver, which might be the reason that the IP's are not valid on >>the Hotmail side...? I am not sure. > >easy to fix, just stop and start your NS, which zeroes the cache of stale >or poisoned data. > >> I did a DNS report at >>http://www.dnsreport.com/ and got good scores for commandline.net, >>however, when I did it the first time it recommended that I set my SOA >>to expire after 14 days, do you think that could have anything to do >>with the Hotmail rejecetions? > >no. Hotmail isn't "rejecting" SMTP-lyyou via a policy. You have tcp/ip >"stack connect" failures trying to establish TCP/SMTP with ip's that your >DNS is telling Imail are the Hotmail MX hostname ip's. > >Can you have IMail use another recursive DNS? > >Can you take the list of ip's and from another machine telnet to port 25 of >each one and get an SMTP welcome banner from Hotmail MX? > >Len To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
