Found nn messages in the processing-messages database
mark at msapiro.net
Fri Apr 17 17:19:51 IST 2009
On Fri, Apr 17, 2009 at 05:24:14PM +0200, Kai Schaetzl wrote:
> Mark, grep the mailscanner log for the first part of the MS id. If you
> archive, you may see two hits as I see here. If you don't archive there
> might not be any trace of the first processing in the log.
> As I understand, though, it happens for you in the middle of operation and
> not on MS refresh.
> Which MTA produces those completely random number-only ids?
This is not the same issue as in your case. Here's an example grep (with
Apr 17 05:24:19 sbh16 postfix/smtpd: 84250690369: client=localhost.localdomain[127.0.0.1]
Apr 17 05:24:19 sbh16 postfix/cleanup: 84250690369: hold: header Received: from sbh16.songbird.com (localhost.localdomain [127.0.0.1])??by sbh16.songbird.com (Postfix) with ESMTP id 84250690369??for <u at example.com>; Fri, 17 Apr 2009 05:24:19 -0700 (PDT) from localhost.localdomain[127.0.0.1]; from=<gpc-talk-bounces+u=example.com> to=<u at example.com> proto=ESMTP helo=<sbh16.songbird.com>
Apr 17 05:24:19 sbh16 postfix/cleanup: 84250690369: message-id=<1ACE54F6-7ABD-4188-B051-5807DD1B2213 at lmi.net>
Apr 17 05:24:25 sbh16 MailScanner: Requeue: 84250690369.89777 to 09D3A69017C
These are the only occurrences of 84250690369 in the log.
You may have hit on a clue. This is Postfix and all-numeric queue-ids are
rare, but every one of the ones left in the processing-messages database
is all-numeric. It doesn't happen to every all-numeric id, but it certainly
seems significant that all the problem ones are.
Mark Sapiro mark at msapiro net The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the MailScanner