From: Toby Speight <streapadair@gmx.net>
Subject: Re: Mail from multiple lists...
Date: 07 Nov 2000 11:21:15 +0000 [thread overview]
Message-ID: <8766m02fkk.fsf@delivery.cam.eu.citrix.com> (raw)
In-Reply-To: Norman Walsh's message of "06 Nov 2000 16:51:55 -0500"
0> In article <87g0l4kbus.fsf@nwalsh.com>,
0> Norman D. Walsh <URL:mailto:ndw@nwalsh.com> ("Norman") wrote:
Norman> Unfortunately, my
Norman>
Norman> (setq nnmail-split-fancy
Norman> ...
Norman> (any "list1@.*example\.com" "example.list1")
Norman> (any "list2@.*example\.com" "example.list2")
Norman> ...)
Norman>
Norman> puts two copies of this message in nnml:example.list1 instead of
Norman> putting one copy in example.list1 and another in
Norman> example.list2.
I assume you have (| ) around those two rules; maybe (& ) is what
you're looking for. Split to all matches, not just the first. That
does mean that both copies will be split to both groups - that's not
a problem for me, as I use duplicate suppression, but you may have
different circumstances.
Norman> On close inspection, I do see that one of the received headers
Norman> offers a clue:
Norman>
Norman> Received: from eastmail1.example.com (eastmail1.example.com [129.148.1.240])
Norman> by mail1.example.com (8.9.1b+Sun/8.9.1/ENSMAIL,v1.6.1-mail1) with ESMTP id NAA19369
Norman> for <list1@example.com>; Mon, 6 Nov 2000 13:02:24 -0800 (PST)
Norman>
Norman> I suppose I could filter on that, though I feel a little
Norman> uncomfortable filtering on received: headers. Is my
Norman> discomfort unfounded?
I feel a bit uncomfortable, too, if I do that, because you don't know
when the site will change mailer (or reconfigure their mailer) and
lose the vital bit.
But you could use it, with fallback to considering explicit recipients:
(|
(|
(received "for\\s-+list1@.*example\\.com" "example.list1")
(received "for\\s-+list2@.*example\\.com" "example.list2"))
(&
(to "\\<list1@.*example\\.com" "example.list1")
(to "\\<list2@.*example\\.com" "example.list2")))
Or even
(|
(received "for\\s-+\\(list[12]\\)@.*\\<example\\.com" "example.\\1")
(&
(to "\\<list1@.*example\\.com" "example.list1")
(to "\\<list2@.*example\\.com" "example.list2")))
I agree that lists should set the envelope from address, and also the
Sender header...
prev parent reply other threads:[~2000-11-07 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-06 21:51 Norman Walsh
2000-11-07 11:21 ` Toby Speight [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=8766m02fkk.fsf@delivery.cam.eu.citrix.com \
--to=streapadair@gmx.net \
/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;
as well as URLs for NNTP newsgroup(s).