5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Adding/subtracting he...
FromSent OnAttachments
Sean KennedyFeb 5, 2004 4:27 pm 
Thorsten HaudeFeb 5, 2004 4:59 pm 
Sean KennedyFeb 5, 2004 5:14 pm 
Thorsten HaudeFeb 5, 2004 11:08 pm 
Sean KennedyFeb 6, 2004 8:49 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Adding/subtracting headersActions...
From:Sean Kennedy (sken@tpno.org)
Date:Feb 6, 2004 8:49:51 am
List:net.sourceforge.lists.courier-maildrop

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Thorsten Haude wrote:

| Hi, | | * Sean Kennedy wrote (2004-02-06 02:14): | |> | You should be careful to change this header, as you might | |> information required to reach the sender. At least check wheter |> the | header is already set before munging it. |> |> Ah, good point. On the other hand, for me at least, I keep the |> messages in a mailing list ( my own searchable archive, as it |> were ), so if I wanted to respond to someone, I'm sure i could |> find the original email in the list. | | | That might not be sufficient. I work with email accounts accessed | through mobiles. A lot of customers set their Reply-To to some | other address and do not want to receive email with their mobile | because they have to pay for every byte. Others may not be able to | receive mail through the address in the From header. | | | This has been discussed a lot of times before. Ask Google for | 'Reply-To munging', though a lot of things do not apply to you if | you munge the headers yourself with appropriate care. | | | Thorsten

Thank you, you make a good point.

Per your suggestion, I checked into reformail. I found the option -i, which,

| Appends a custom header to the message. If this header already | exists it is renamed by prepending "Old-" to the name of the header.

I think that's a fairly neat solution. And given my specific setup, I think will be sufficient.

Thanks again!

iD8DBQFAI8WHIjyA6vwcN38RAsTbAJ4kxfBYzojTRKUdCYayc6xMAZfrpwCggHa0 4So3tInP46YNXMmhp85nkqs= =jMrJ -----END PGP SIGNATURE-----