All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Potential mail loss in postfix?
Date: Thu, 11 Nov 2010 04:55:06 +0000	[thread overview]
Message-ID: <4CDB772A.9000201@yahoo.com.au> (raw)
In-Reply-To: <robbat2-20100928T230341-934503680Z@orbis-terrarum.net>

On 11/11/10 2:58 PM, Ben Schmidt wrote:
> I might have found this bug.
>
> If init_sockfd() fails (e.g. because Postfix has shut down so there is no smtpd
> listening) it calls exit(). Mail would then fail to be archived or requeued. It
> will be in a queue file only until mlmmj-maintd cleans it up (which it will do as
> soon as it finds it, as it won't have accompanying .mailfrom etc. files).
>
> Do you have logs from when this happened? Do you see "Could not get socket" or
> "Could not connect to %s, exiting..." (%s probably is 127.0.0.1) in them?

"Could not connect to %s, exiting ..."

Omitted a space before. Correcting myself, just in case you search for
that part of the string and don't find it because of my error. :-)

> Ben.
>
>
>
> On 29/09/10 9:21 AM, Robin H. Johnson wrote:
>> Hi
>>
>> Noticed something, and I don't have a testcase for it yet unfortunately
>> or a suitable setup to re-test on. Instead I've got my analysis of the
>> problem how it's occurred twice now.
>>
>> - Using verp and postfix together first of all (string 'postfix' in the
>> verp file, '100' in maxverprecips).
>> - Pick a list with a lot of subscribers.
>> - This leads to a case where the mlmmj-send invocation takes several
>> minutes to complete for a normal list mail.
>> - (optional) set postfix to hold incoming mail, and you can release it
>> just at the right moment to see it be mlmmj-recieve.
>> - The postfix log will show delivery to mlmmj-recieve.
>> - mlmmj.operation.log will contain a line from mlmmj-process stating
>> that the message was allowed (by your access rules).
>> - Now, while mlmmj-send is running, you're going to execute a normal
>> shutdown of postfix: 'postfix stop' [1]
>> - The mail will be lost completely now. There is no record of it in
>> archive, or any of the queues :-(.
>>
>> [1] The description for 'postfix stop': Stop the Postfix mail system in
>> an orderly fashion. If possible, running processes are allowed to
>> terminate at their earliest convenience.
>>
>
>
>


  parent reply	other threads:[~2010-11-11  4:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 23:21 [mlmmj] Potential mail loss in postfix? Robin H. Johnson
2010-11-11  3:58 ` Ben Schmidt
2010-11-11  4:55 ` Ben Schmidt [this message]
2010-11-11  5:12 ` Robin H. Johnson
2010-11-11 12:15 ` Ben Schmidt
2010-11-11 21:13 ` Robin H. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CDB772A.9000201@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.