From: Mads Martin Joergensen <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Re: lists.gentoo.org powered by mlmmj - bugs and a feature request
Date: Wed, 11 Apr 2007 12:08:24 +0000 [thread overview]
Message-ID: <20070411120824.GC69191@mmj.dk> (raw)
In-Reply-To: <20070411095339.GE4502@curie-int.orbis-terrarum.net>
* Robin H. Johnson <robbat2@gentoo.org> [Apr 11. 2007 11:53]:
> Hi,
>
> I've taken over maintenance of lists.gentoo.org (all powered by mlmmj
> :-), some 32k unique recipients!) from the previous maintainer, and
> there's a few things we're working at. First of all, two bug reports,
> then a feature request.
>
> 1.
> There is occasionally some mail loss that we haven't gotten to
> the bottom of. I can confirm 100% that Sendmail (not my choice, trust
> me) definitely piped the email to mlmmj-recieve. There should have been
> some 1900 emails that went out from the input, but a lot less than that
> did go out.
>
> The splitting in the sendmail logs appear that it only got some 800
> recipients from mlmmj-send, but I cannot confirm that.
>
> All suggestions on tracing this are welcome, losing mail sucks.
If sendmail is not your choice, why not switch to Postfix which performs
wonderfully. SuSE is running lists.opensuse.org without a hitch with
mlmmj + postfix.
> 2.
> This was reported by one of our users:
> https://bugs.gentoo.org/show_bug.cgi?id\x173159
>
> mlmmj appends the footer, without being aware of the encoding of the
> email. It is not safe to just directly append the footer if the mail has
> Content-Transfer-Encoding: base64!
There's a patch from Jakob Hirsch for handling this.
> 3.
> Now the feature request.
>
> Without going into all of the details, I need a sane way to have
> mlmmj-process to call a different application (procmail for the moment)
> where it would call mlmmj-send to send out the mass email to all list
> recipients (so mlmmj-process has already completed all of it's
> processing at this point).
> Then I also need a way to call mlmmj-send in the same way later on.
>
> We're working on some asynchronous processing stuff, so breaking the
> chain between mlmmj-process and mlmmj-send is the only sane way of
> handling large quantities of messages.
You can always just replace any mlmmj binary with one of your choice.
For instance mlmmj-process (yours) doing stuff and finally invokes the
mlmmj binaries the same way as the original one would.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
next prev parent reply other threads:[~2007-04-11 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 9:53 lists.gentoo.org powered by mlmmj - bugs and a feature request Robin H. Johnson
2007-04-11 12:08 ` Mads Martin Joergensen [this message]
2007-04-11 12:12 ` Andrea Barisani
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=20070411120824.GC69191@mmj.dk \
--to=mmj@mmj.dk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox