Problem solved. Turns out, we were using a DNS provider that was having issues. Changed to another DNS provider primary and secondary, and slowness issues stopped.
As for the corrupted messages showing up, I will let you know. Jeff > On Nov 4, 2014, at 12:45 PM, Wietse Venema <wie...@porcupine.org> wrote: > > SH Development: >>>> I use postsuper -d to delete them, but they keep coming back. >>> >>> What command did you use? Normally postsuper does not >>> remove files from the "corrupt" directory. >> >> postsuper -d AE7E42857D76 >> >> and so forth for each message. > > Hmm. The "postsuper -d" command will not complain when a file is > not found, otherwise you would have noticed that it does not look > in the "corrupt" directory. > > When a file ends up in the corrupt directory, basically Postfix has > given up on it. The file is no longer accessible with the postsuper > command - it looks only in places that contain "good" files. So, do > with the files as you please. Postfix no longer cares. Sniff! > > As for slow logins, that can have many causes, starting with delays > while looking up the client hostname (for example, there is no > in-addr.arpa mapping for your local network, or the name from > that mapping does not resolve in DNS). > > Wietse >
