From: Joel Aelwyn <joel@lightbearer.com>
To: mlmmj@mlmmj.org
Subject: Re: alternate value for RECIPDELIM
Date: Thu, 22 Sep 2005 01:29:55 +0000 [thread overview]
Message-ID: <43320913.3060308@lightbearer.com> (raw)
In-Reply-To: <43316167.4010700@woozle.org>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Neale Pickett wrote:
> I've got a mail server that's been using '-' instead of '+' for a long,
> long time now, and I can't switch it over to '+' without breaking a
> billion email addresses. I patched the source code (patch at bottom) to
> let me use '+', and let anyone else #define a new RECIPDELIM (and have
> it work), but I don't like the patch.
>
> It seems like the *right* thing to do would be to use something like my
> patch, where people could configure it at compile-time, but to maybe
> read /etc/mlmmj/recipdelim (if it exists) to get the RECIPDELIM. This
> would let me go back to using the debian package with its default '+'.
This looks awfully familiar. I swear I developed mine separately. But it's
clearly a feature in fairly high demand...
The two differences are that I set it up to read an optional list delimiter on
a per-list basis, and that my patch supports multi-character delimiters (not
that this is probably a generally-sane idea to do with most servers, but...
why make things difficult? It's not really any more effort to support it, or
any slower in practice).
As soon as I can pare out the last nits, I'll post it (it's getting copies of
real list emails from my production server right now to excercise it some, and
there are a couple of things still being odd).
--
Joel Aelwyn <joel@lightbearer.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2005-09-22 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 13:34 alternate value for RECIPDELIM Neale Pickett
2005-09-21 13:39 ` Neale Pickett
2005-09-22 1:29 ` Joel Aelwyn [this message]
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=43320913.3060308@lightbearer.com \
--to=joel@lightbearer.com \
--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