These headers were introduced with 2,8 I believe and are added to mails sent via the mailing list support.

It has resulted in two issues:

Firstly: frequently people reply to me direct when they intended to reply to the mailing list, I'm posting to. As far as I can tell they are simply replying to the mail, so at some level the Mail-Reply-To: must be overriding the list set Reply-To:

There doesn't seem to be anyway for me to control these headers, either to suppress them or to modify their content.

Ideally I would suppress the Mail-Reply-To: as I generally always expect ,mailing list replies to go to list.

Secondly:

When I receive a mail with the Mail-Reply-To: and try to reply to it, my reply will always go to the Mail-Reply-To: and not the lists Reply-To: address (this assumes I've switched off mailing list support for the mail dir in question).

A 'normal' mail from a mailing list ie one without the Mail-Reply-To: shows a requester witha From / replyTo choice. No requester is offered if Mail-Reply-To: is present.
I'm not aware of any "followup" rather than reply option in Yam, so this seems like a bug to me. (I can transfer it to the bug tracker if you agree).

There you would find some quite verbose information on the general purpose of these header files. Nevertheless, to identify if there is really a missbehaviour in how YAM is using/creating these header files we would requite a much more verbose step-by-step explaination on what exactly is happening on your end. Which mailing list are you talking about? How did you setup the mailing list support of the folder where you put these mails into and how are the Mail-Reply-To and Mail-Followup-To headers are actually set when you use YAM? We really need to get here some examples to better understand and able to track what is happening and if this is really a missbhaviour in how YAM is using the headers or perhaps just a missconfiguration on your end.

Jens Maus

Apr 30, 2013, 8:45:23 PM (5 years ago)

Message #383

Thanks for the link, I had allready read the proposl linked to, to find what these headers were about before posting

I was looking for an associated RFC but that was all I could find on a quick search.

He seems to be proposing a solution to an issue that doesn't exist ie that the OP of an email sent to a mailing list gets two copies. I wont say it doesn't happen but it's usuallu solved by omiting the Reply-To: header if the address would be the same as the From: address, perhaps he doeb't have access to apowerful email client like YAM

The problem it causes me, is that I end up with a reply and the list doesn't which is not what is wanted 95% of the time.

It happens with on two mailing list whoch I have currently active both closed beta lists.

I set them up in YAM buit filtering incoming mails to a specific folder then enabling mailing list support on them.

Here the typical settings for one with the projectname replaced for security as this list is not closed (paranoid me?) :

So that's the set up. The presence of these extra headers causes some email client s to reply direct to me rather than to the list so it would useful to be able to switch them off, so as to be compatable with older clients /mailing setups etc.

The clients are obviously following the

Mail-Reply-To: / Reply-To: / From heirarchy as described in the document you linked to.

As regards YAM when I switch off mailing list support so that the To: address of the new mail is no lonmger set by those options and try to reply the mail the same issue occurs my new mail is created with the address from the Mail-Reply-To:

In contrast to the case where there is a Reply-To: and From: that differ when there is a Mail-Reply-To: Replty-To: and from: I get no requester to make a choice.