On Tue, May 07, 2013 at 01:58:57PM +0200, Suvayu Ali wrote: > Hello Patrick and others, > > First, apologies for the delayed response. > > On Fri, May 03, 2013 at 08:08:48AM -0400, Patrick Shanahan wrote: > > > > Try the following: > > set reverse_name > > add as the very first send-hook: send-hook . "" > > comment out or remove subject reply-hooks > > > > Make sure that all of the required "reverse_name"s are defined in > > "alternates" > > This is what I did: > > 1. I removed all reply and send-hooks, `set reverse_name' (not > reverse_name=yes), and then I set an empty default send-hook as you > show above. I also made sure all my addresses are matched with > alternates. > > The above allows me to respond to my own responses in a thread > correctly, i.e. my email address from my response is picked as from. > > However, I cannot respond to mailing list emails delivered to any of > these alternate email addresses with the correct email address (I use > <reply> or <list-reply>). Responding to messages addressed directly > to any of the alternates work well. > > 2. To solve this, I added send-hooks for mailing lists delivered to my > alternates. > > send-hook "%C work-lists" my_hdr From: wor...@domain.com > send-hook "%C foss-lists" my_hdr From: l...@gmail.com > > Note work-lists and foss-lists are groups with mailing list > addresses, and I still have the default empty send-hook. > > After this change, <reply> and <list-reply> works correctly again. > But now, I have a problem with composing new messages. The new > message has the from address of the last email I started to compose > (it does not matter if I aborted the message or sent it). I guess > this means the last my_hdr command "persists" through the rest of the > session. > > 3. To solve this problem, I now change the default send-hook to > something like this: > > send-hook . my_hdr From: prim...@gmail.com > > And of course this last change then breaks $reverse_name, and > <reply>; <list-reply> still works because of (2). > > 4. Now to solve this issue, I re-introduce the old reply-hooks. > > reply-hook '~h "Delivered-To: +list@gmail\\.com"' my_hdr From: > l...@gmail.com > reply-hook '~h "Delivered-To: +wor...@domain.com"' my_hdr From: > wor...@domain.com > > This does not work right away because of (3). So I remove (3), set > the default send-hook back to empty, as in (1), and introduce a > default reply-hook as below: > > reply-hook . my_hdr From: prim...@gmail.com > > This fixes reply, but $reverse_name is still broken.
I forgot to mention, this last step reintroduces the problem with composing new messages I mentioned in (2). This stands to reason since I removed the `my_hdr From: ...' command from the default send-hook. -- Suvayu Open source is the future. It sets us free.
