Thanks again. I will do so as soon as the problem recurs. On 1/18/2018 3:46 PM, Viktor Dukhovni wrote: > >> On Jan 18, 2018, at 3:26 PM, Dennis Putnam <d...@bellsouth.net> wrote: >> >>>> The messages show in mailq as having timed >>>> out and are a few days old. >>> They've probably maxed out the maximal_backoff_time and are tried >>> infrequently, but are not forgotten. >> The default is 4000 seconds according to the docs. Since I don't >> specifically set it in main.cf that is a little over an hour. In the 2-3 >> days they have been sitting in the queue there should have been numerous >> retries. During which time other message were going through. Why did >> they not time out as well? It is too coincidental that the destination >> server times out every time just those messages are retried while others >> do not. > Are any such messages still present? What is the mtime of their queue files? > What is the current time at the time you noted the file mtimes? Are the > files open in some delivery agent (use lsof)? > >>>> In the mean time other messages are going through just fine. >>> That's normal. >> I wouldn't think so if the maximal_backoff_time has expired many times >> during that period. > Postfix scans the deferred queue periodically. Your logs should show > evidence of the messages entering the active queue multiple times. > What does your master.cf entry for "qmgr" look like? > >>>> Can someone tell me how I might trouble shoot this problem? >>> First post evidence of a problem (logs and configuration details). >>> >> Nothing of note in the logs ever shows up. All the retry timeout config >> stuff is default. I don't set any of that in main.cf. > Post *all* log entries for one of the problem queue files. Post > the "qmgr" master.cf entry. Post any timer overrides from main.cf. > Post any warnings or errors logged by "qmgr". >
signature.asc
Description: OpenPGP digital signature
