On some mailman lists I receive messages in which Thunderbird displays a "Reply to List" button. However, on my own lists that does not happen. What header is TB relying on to get that and what setting do I need to change my mailman for that to happen? TIA.
On 01/09/2016 06:14 AM, Dennis Putnam wrote:
Thunderbird and many other MUAs rely on the RFC 2369 List-Post: header for "reply to list". There are six RFC 2369 List-* headers; List-Id:, List-Unsubscribe:, List-Archive:, List-Post:, List-Help: and List-Subscribe:. Mailman's adding of these headers is controlled by the lists General Options include_rfc2369_headers and include_list_post_header settings.
If include_rfc2369_headers is No, none of these headers will be added. If include_rfc2369_headers is Yes, List-Post: will be added only if include_list_post_header is Yes, List-Archive will be added only if the list is archiving and the other four will be added.
So to ensure posts received from the list have a List-Post header, both include_rfc2369_headers and include_list_post_header must be Yes.
Also note that if your "Avoid duplicate copies of messages?" setting on a list is Yes and you are directly addressed in a reply, the copy you receive doesn't come from the list and won't have any Mailman headers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 01/09/2016 01:10 PM, Dennis Putnam wrote:
Are there other Mailman headers such as X-BeenThere: and X-Mailman-Version: in the messages?
Do you have any local modifications to Mailman/Handlers/CookHeaders.py?
How do messages get from Mailman to you?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/9/2016 4:43 PM, Mark Sapiro wrote:
Thanks for the reply. Unfortunately I don't recall but I don't think so. I am currently unable to test it to see as imap.gmail.com seems to be down and has been for a while. The messages go from mailman on my Postfix server to JetMail, to the subscriber's ISP (AT&T in my case).
On 01/10/2016 06:29 AM, Dennis Putnam wrote:
I use imap.googlemail.com for my gmail imap server, but that won't make any difference. I've just tested, and it appears that gmail/googlemail is now forcing SSL. I.e., neither imap.gmail.com nor imap.googlemail.com is answering port 143 connects, but both work with SSL on port 993.
The messages go from mailman on my Postfix server to JetMail, to the subscriber's ISP (AT&T in my case).
The next time you receive a post from the list in question, view the source (More -> View Source in Thunderbird). If you don't see the List-* headers, copy ALL of the headers and post them here. You can munge any personal info if you like.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/10/2016 1:57 PM, Mark Sapiro wrote:
Google is back up. I guess I was wrong in my original assessment. The headers are indeed there including List-Post. The reply to list button is displayed (I don't know why I sometimes don't get that but I will have to look closer next time it happens). Anyway, I now see the problem, but I don't know how/where to fix it. The address in the List-Post is wrong. I can see how to turn it off/on in the documentation but not how to customize it?
On 01/10/2016 03:07 PM, Dennis Putnam wrote:
It is the list posting address, i.e. listname@host_name, the same as the address in "To post a message to all the list members, send email to ..." on the list's listinfo page.
If the local part in the List-Post: header is not the list name, something is seriously wrong, but I don't know what. If the domain is not what you think it should be, the list's host_name (on the General Options page) is wrong. You can change it there, although that may indicate issues with add_virtualhost and DEFAULT_*_HOST in mm_cfg.py.
As I said before, if you sometimes don't see it, it might be because you are looking at a reply sent to you directly (To: or Cc:) and not from the list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 01/14/2016 04:02 AM, Dennis Putnam wrote:
Got it. I guess the "Preferred Hostname" in the settings is somewhat of a misnomer. It is really the preferred email hostname.
Where are you seeing "Preferred Hostname"?
Mailman's General Options page says
Host name this list prefers for email. (Details for host_name)
which seems clear enough. I can't find the regexp 'preferred.?host' case insensitively anywhere in the GNU Mailman distribution.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/14/2016 1:38 PM, Mark Sapiro wrote:
Sorry, I guess I should not have put it in quotes. That title is not at all clear to me that it means the domain name (not host name) for replying email. I had that set to my email domain (bellsouth.net). Changing it to the reply email domain (gmail.com) worked. I tried the host name 'pop.gmail.com' and that did not.
On 01/14/2016 11:58 AM, Dennis Putnam wrote:
OK. Now I understand the confusion. We use 'host' in a number of places where we really mean 'domain' and it can be particularly confusing for email addresses where the 'domain' may just have an MX record and not be a 'machine' at all.
However, this terminology is deeply embedded and affects translations if it were to be changed, so I don't propose to actually change it at this point.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 01/09/2016 06:14 AM, Dennis Putnam wrote:
Thunderbird and many other MUAs rely on the RFC 2369 List-Post: header for "reply to list". There are six RFC 2369 List-* headers; List-Id:, List-Unsubscribe:, List-Archive:, List-Post:, List-Help: and List-Subscribe:. Mailman's adding of these headers is controlled by the lists General Options include_rfc2369_headers and include_list_post_header settings.
If include_rfc2369_headers is No, none of these headers will be added. If include_rfc2369_headers is Yes, List-Post: will be added only if include_list_post_header is Yes, List-Archive will be added only if the list is archiving and the other four will be added.
So to ensure posts received from the list have a List-Post header, both include_rfc2369_headers and include_list_post_header must be Yes.
Also note that if your "Avoid duplicate copies of messages?" setting on a list is Yes and you are directly addressed in a reply, the copy you receive doesn't come from the list and won't have any Mailman headers.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 01/09/2016 01:10 PM, Dennis Putnam wrote:
Are there other Mailman headers such as X-BeenThere: and X-Mailman-Version: in the messages?
Do you have any local modifications to Mailman/Handlers/CookHeaders.py?
How do messages get from Mailman to you?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/9/2016 4:43 PM, Mark Sapiro wrote:
Thanks for the reply. Unfortunately I don't recall but I don't think so. I am currently unable to test it to see as imap.gmail.com seems to be down and has been for a while. The messages go from mailman on my Postfix server to JetMail, to the subscriber's ISP (AT&T in my case).
On 01/10/2016 06:29 AM, Dennis Putnam wrote:
I use imap.googlemail.com for my gmail imap server, but that won't make any difference. I've just tested, and it appears that gmail/googlemail is now forcing SSL. I.e., neither imap.gmail.com nor imap.googlemail.com is answering port 143 connects, but both work with SSL on port 993.
The messages go from mailman on my Postfix server to JetMail, to the subscriber's ISP (AT&T in my case).
The next time you receive a post from the list in question, view the source (More -> View Source in Thunderbird). If you don't see the List-* headers, copy ALL of the headers and post them here. You can munge any personal info if you like.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/10/2016 1:57 PM, Mark Sapiro wrote:
Google is back up. I guess I was wrong in my original assessment. The headers are indeed there including List-Post. The reply to list button is displayed (I don't know why I sometimes don't get that but I will have to look closer next time it happens). Anyway, I now see the problem, but I don't know how/where to fix it. The address in the List-Post is wrong. I can see how to turn it off/on in the documentation but not how to customize it?
On 01/10/2016 03:07 PM, Dennis Putnam wrote:
It is the list posting address, i.e. listname@host_name, the same as the address in "To post a message to all the list members, send email to ..." on the list's listinfo page.
If the local part in the List-Post: header is not the list name, something is seriously wrong, but I don't know what. If the domain is not what you think it should be, the list's host_name (on the General Options page) is wrong. You can change it there, although that may indicate issues with add_virtualhost and DEFAULT_*_HOST in mm_cfg.py.
As I said before, if you sometimes don't see it, it might be because you are looking at a reply sent to you directly (To: or Cc:) and not from the list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 01/14/2016 04:02 AM, Dennis Putnam wrote:
Got it. I guess the "Preferred Hostname" in the settings is somewhat of a misnomer. It is really the preferred email hostname.
Where are you seeing "Preferred Hostname"?
Mailman's General Options page says
Host name this list prefers for email. (Details for host_name)
which seems clear enough. I can't find the regexp 'preferred.?host' case insensitively anywhere in the GNU Mailman distribution.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/14/2016 1:38 PM, Mark Sapiro wrote:
Sorry, I guess I should not have put it in quotes. That title is not at all clear to me that it means the domain name (not host name) for replying email. I had that set to my email domain (bellsouth.net). Changing it to the reply email domain (gmail.com) worked. I tried the host name 'pop.gmail.com' and that did not.
On 01/14/2016 11:58 AM, Dennis Putnam wrote:
OK. Now I understand the confusion. We use 'host' in a number of places where we really mean 'domain' and it can be particularly confusing for email addresses where the 'domain' may just have an MX record and not be a 'machine' at all.
However, this terminology is deeply embedded and affects translations if it were to be changed, so I don't propose to actually change it at this point.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dennis Putnam -
Mark Sapiro