On Dec 16, jhenders@??? (Me) wrote:
>
> After adding sender_verify and sender_verify_fixup to the configure
> file, the following message was rejected.
> 154P Received: from ns.web2010.com [208.14.1.1] (nobody)
After doing some more digging (literally) I've found that the problem
here seems to be in this case attempting to get an MX record for
ns.web2010.com leads to a timeout for some reason. From the SOA record
returned for the domain it is probably a database config error. However,
it would seem to me that if sender_verify_fixup is defined, then it
might be a more preferable strategy to fall through to it rather than
defering on the timed out MX lookup on the envelope From line. Is this
possible? Would it be a good idea?
--
Artificial Intelligence stands no chance against Natural Stupidity.
GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
