| |||||||||||||||||||||||||||||||
|
> Stop speculating, start doing real measurements. > Send mail to the exchange box that pretends to come from such a domain. > > $ sendmail -f user@suspect-domain recipient... < inputfile > > where inputfile contains some text. Joey: > This was a good test, if I use the sender domain of the messages I am saying > are spam because they are the messages that lock up in the queue and remain > there: > sendmail -f colvdiyfq testaccount < > testfile > > This times out sending to the exchange server. Now we're getting somewhere. So this means exchange can't handle domains that have "many" MX records. > If I take the same exact entry but put my domain as the sender like so: > sendmail -f colvdiyfq testaccount < > testfile > > It works perfectly with NO hung connections on either side. > > I tried this with 2 different domains that were from messages that were > locked up in the queue on the postfix side with the same results. So all we need to do is to configure Postfix to stop mail from domains with more than some number of MX records. DNS lookups like this don't work over UDP. They require DNS over TCP. This can break in several ways: - Perhaps Exchange can't handle DNS replies that exceed the size of an UDP response (i.e. it can't do DNS lookup over TCP). - Perhaps the Exchange server is behind a broken firewall that blocks DNS lookups over TCP. - Or perhaps Exchange can't handle large DNS replies with 100+ MX records. Postfix currently has no feature built-in that disallows DNS replies with "many" MX records. Wietse
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com