At 9:56 AM -0500 12/02/2003, Bill Cole modified the matrix with:
Not exactly the log pieces I was hoping for, but at least I understand the SIMS flaw involved now: SIMS does not see the 450 it gets from Verizon as a temporary failure, and bounces the message instead of requeueing it for later.
Bill, these are the only log lines connected with that SMTP session. Actually SIMS is treating the 450 as a temp but Verizon keeps sending the 450 forever.
That's interesting. I was certain that at one point SIMS was mishandling 450 responses...
[...]
The fact that the Verizon server accepted the message that was sent using a domain not hosted by us makes me think that Verizon is maybe doing some sort of checking with regards to the DNS for the domain name in the return address. Can someone take a look at our DNS and see if there is something obvious that could be causing Verizon to reject email from our domain 3-rivers.com and/or our primary server mail.3-rivers.com (63.95.200.5) but it will accept from the bentonrea.com domain.
I see nothing wrong there now, but it does look like you did some changes today. (SOA serial 2003120204)
I have changed the email addresses to helpfully protect them, but here is the log (logging set to ALL INFO in the SMTP settings) from the SMTP session with the GTE server:
[SNIP]
You need to do the same thing but looking for the 'callback' from the GTE machine shortly after you give it the MAIL FROM. If there is no callback session, that would explain the problem: they can't do the validation for some reason.
There is no call back from the Verizon server other than the responses I already included in the log I send.
That's VERY strange, because I trigger that callback every time I try sending to a Verizon address. It's a connection coming from sc###pub.verizon.net and it goes through the motions of trying to send mail from '[EMAIL PROTECTED]' to the address used in the MAIL FROM I offered. I do not get a response to my MAIL FROM until the Verizon machine has tested to see if I might be mailable. Your getting a 450 (i.e. a temporary failure) would be a reasonable result of the Verizon machine being unable to connect to you at all.
On another thought, could the blacklists we utilize be causing any problem with the Verizon servers accepting email?
They definitely will make your ability to send to Verizon dependent on Verizon's mail servers not being listed in the lists you use: if you shun the test, your MAIL FROM gets a 550 response instead of a 450.
However, that would not be the problem in your case, since you are neither seeing the callback connection nor are you getting a 550. If your router had the relevant Verizon space blocked (206.46.170.* holds some of their machines) then that would explain the issue.
--
Bill Cole [EMAIL PROTECTED]
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
