-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, October 5 at 11:42 AM, quoth Breen Mullins:
> After more digging, I understand a bit more about what's going on.
>
> ChangeLog:
> 2004-07-20 08:17:21 Thomas Roessler <[EMAIL PROTECTED]>
> (roessler)
>
> * imap/message.c, mutt.h, parse.c, send.c, url.c: Use List-Post
> headers when doing list-reply.
Ah, I thought that might be happening.
> And indeed, there's a List-Post header present that specifies
> [EMAIL PROTECTED]
> I've changed my .muttrc as you suggested, to delimit the subscribed
> address properly.
> But the list-reply still picks up both versions of the list address when I
> try to reply. (The 'normal' one is in the address used by the
> person I was replying to.) There are no followup headers in the message.
So, have you tried making it this:
subscribe '[EMAIL PROTECTED]'
That way the only address that is recognized as a list is the one the
list specifies in the List-Post header. Unless something else is going
on, that should prevent you from replying to [EMAIL PROTECTED]
Of course, you could always *force* the issue, by adding a send2-hook:
send2-hook '~C [EMAIL PROTECTED] ~C [EMAIL PROTECTED]' \
'push <edit-to><kill-line>[EMAIL PROTECTED]<enter>'
;)
> This looks like a bug: mutt usually gives us the flexibility to work
> around eccentric configurations by a listowner, but it doesn't seem to
> work here.
Oh, I don't doubt that we can work around this eccentricity, and
except for the fact that the use of List-Post isn't documented, things
don't appear to be behaving other than as advertised, so... but you
have a point that this could probably be done better. The question is,
what's the best way to work around it in a generic way?
I'm assuming the List-Post header was used for cases when a person is
too lazy to add that mailing list to their list of mailing lists (e.g.
with the subscribe or list commands). Perhaps a variable could be
added to turn that off? Or change the behavior to only use the
List-Post header when no other mailing list addresses have been found?
~Kyle
P.S. I've often thought something like an addr-hook, that forces
specific addresses to be treated as something else (akin to a
charset-hook, kinda) would be pretty useful, and such a thing would
solve the problem here, as long as mutt eliminates duplicate
recipients. For example:
addr-hook [EMAIL PROTECTED] [EMAIL PROTECTED]
- --
The price of freedom of religion, or of speech, or of the press, is
that we must put up with a good deal of rubbish.
-- Robert Jackson
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFHBowUBkIOoMqOI14RAmvrAKCvEpyBotQ7NURl4J8iK1sWGa65fgCgg16h
BJnmg+VeI7apP8iczaIqoXk=
=IW9F
-----END PGP SIGNATURE-----
