On Sat 06/21/08 at 10:11 AM -0400, Sahil Tandon [EMAIL PROTECTED] wrote:
Why not place all email addressed to mutt-users@ (regardless of the domain
name) in your mutt mailbox?
Great idea, and I think this is my preferred solution. Thanks for the tip.
--
// [EMAIL
A few years ago messages to the mutt-users list (from Germany?) were
occasionally ending up in my inbox because they had been sent to what was
apparently some sort of alternative address for the list:
[EMAIL PROTECTED]
Is anyone aware if this address is still in any way active for the
On Sat 06/21/08 at 02:12 AM -0500, David Champion [EMAIL PROTECTED] wrote:
If it is not, I'd like to remove the following from my .procmailrc:
:0
* ^Delivered-To:[EMAIL PROTECTED]
$HOME/Mail/m/
Just use a List-* header instead:
List-Post: mailto:mutt-users@mutt.org
It's too bad
David Champion [EMAIL PROTECTED] wrote:
A few years ago messages to the mutt-users list (from Germany?) were
occasionally ending up in my inbox because they had been sent to what was
apparently some sort of alternative address for the list:
[EMAIL PROTECTED]
Is anyone aware if
Russell Hoover [EMAIL PROTECTED] wrote:
On Sat 06/21/08 at 02:12 AM -0500, David Champion [EMAIL PROTECTED] wrote:
If it is not, I'd like to remove the following from my .procmailrc:
:0
* ^Delivered-To:[EMAIL PROTECTED]
$HOME/Mail/m/
Just use a List-* header instead:
Not sure what you mean by use a List-* header -- I'm trying to clean out
Several RFCs (e.g., 2369, 2919) specify mail headers beginning with
List-. These culminate (I guess) with inclusion in RFC 4021.
Most modern mailing list managers support one or both of List-ID or
List-Post. You can
A few years ago messages to the mutt-users list (from Germany?) were
occasionally ending up in my inbox because they had been sent to what was
apparently some sort of alternative address for the list:
[EMAIL PROTECTED]
Is anyone aware if this address is still in any way active for the list?
If
