Joey Hess wrote: > Joey Hess wrote: > > Joey Hess wrote: > > > Oho. I just noticed I have a third MX that is not currently available. > > > Could master's reverse delivery check somehow be trying to check that > > > MX, old.kitenet.net, which is a level 20 MX? I'll update my zone file > > > and we'll see I suppose. > > > > Now that the MX fix has propigated, master seems to be accepting new > > mail from me, but continues to re-defer all the old mail it deferred > > before. > > Update -- master is *still* deferring new mail from me. It did let a > couple through, but I just noticed several bugs I reported yesterday are > still stuck in the queue. Getting very old indeed. Update again -- the problem turned out to be that I relay mail through kitenet.net from a system behind a firewall, which thinks its name is dragon.kitenet.net, but was not in the DNS. Master's paranoid setup looked at the Sender: and found a host not in the dns there, and deferred the mail with a very confusing message that didn't mention dragon at all. Oh well, fixed now for me anyway. -- see shy jo
Attachment:
pgpiIF6bL7BNK.pgp
Description: PGP signature