[Mailman-Users] Displaying the sender email
Hello, Is there a way to configure Mailman lists so the From: line can say: From listn...@mymanserver.com [On Behalf of john@yahoo.com] We are using a 3rd-party SMTP relay for all outbound mail, so we need to approve all senders for the service to allow the email to go through. This poses a problem with the dozens of mailing lists we host, since it is not practical to approve hundreds (if not thousands) of members. So what we are doing is configuring the mailman lists to Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) , setting it to Yes. So now all members of the list will see posts as: From: listn...@mymailmanserver.com Instead of the address of the poster. This is actually a good thing for us, and we actually prefer this behavior to ensure that discussions will stay on the lists, but also this solves the problem of the SMTP relay service, since now we only need to approve the wildcard for *@mymailmanserver.com so the service will relay the email. The problem is that posters don't always include signatures, and we need to know who sent them, but by stripping out the original sender, unless they do include a signature in the body, members might not always be able to tell who posted to the list. Thanks in advance. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Displaying the sender email
On 3/8/2012 8:39 AM, Duane Winner wrote: Is there a way to configure Mailman lists so the From: line can say: From listn...@mymanserver.com [On Behalf of john@yahoo.com] First, please see the FAQ at http://wiki.list.org/x/RoA9. Hopefully, this will explain what MS Outlook is actually displaying as the From: of the message. T answer your question, no there is not, at least not as a standard configuration. This could be done by setting the Sender: to listn...@mymanserver.com instead of listname-boun...@mymanserver.com, but this would not be desirable as it could result in bounces being returned to the list instead of to bounce processing. We are using a 3rd-party SMTP relay for all outbound mail, so we need to approve all senders for the service to allow the email to go through. Are you sure the relay is not looking at the envelope sender rather than any From: or Sender: header in the message. I would expect that it is, in which case, the addresses you need to 'whitelist' are the listname-boun...@mymanserver.com addresses regardless of any From: in the message. This poses a problem with the dozens of mailing lists we host, since it is not practical to approve hundreds (if not thousands) of members. So what we are doing is configuring the mailman lists to Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) , setting it to Yes. So now all members of the list will see posts as: From: listn...@mymailmanserver.com Instead of the address of the poster. This is actually a good thing for us, and we actually prefer this behavior to ensure that discussions will stay on the lists, but also this solves the problem of the SMTP relay service, since now we only need to approve the wildcard for *@mymailmanserver.com so the service will relay the email. I suspect the above will work regardless of any list settings. The problem is that posters don't always include signatures, and we need to know who sent them, but by stripping out the original sender, unless they do include a signature in the body, members might not always be able to tell who posted to the list. Try setting anonymous_list back to No, and if you want to ensure that discussions will stay on the lists, set reply_goes_to_list to This list. I suspect that together with whitelisting *@mymailmanserver.com will do what you want. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
Hi all,
I've had this parameter defined in my postfix ever since it was first
set up (not by me), and most everything I read online says it should be
there.
But, the newer versions of postfix now provide warnings for unused
parameters, and that is what I'm getting for this one parameter:
myhost : Fri Mar 09, 13:16:12 : ~
# postconf -n | grep mailman
alias_maps = hash:/etc/mail/aliases, hash:/var/lib/mailman/data/aliases
virtual_alias_maps = ${mysql}/vam.cf,
hash:/var/lib/mailman/data/virtual-mailman
postconf: warning: /etc/postfix/main.cf: unused parameter:
mailman_destination_recipient_limit=1
myhost : Fri Mar 09, 13:16:26 : ~
#
Anyone have any idea why? Am I indeed not using it? I'd rather not just
comment it out and test without some confirmation first, since this is a
production box.
Thanks...
Charles
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
On Fri, 9 Mar 2012, Tanstaafl wrote:
Hi all,
I've had this parameter defined in my postfix ever since it was first set up
(not by me), and most everything I read online says it should be there.
But, the newer versions of postfix now provide warnings for unused
parameters, and that is what I'm getting for this one parameter:
myhost : Fri Mar 09, 13:16:12 : ~
# postconf -n | grep mailman
alias_maps = hash:/etc/mail/aliases, hash:/var/lib/mailman/data/aliases
virtual_alias_maps = ${mysql}/vam.cf,
hash:/var/lib/mailman/data/virtual-mailman
postconf: warning: /etc/postfix/main.cf: unused parameter:
mailman_destination_recipient_limit=1
myhost : Fri Mar 09, 13:16:26 : ~
#
Anyone have any idea why? Am I indeed not using it? I'd rather not just
comment it out and test without some confirmation first, since this is a
production box.
transport_destination_recipient_limit is a Postfix parameter that is
specific to the named transport. If you don't have a transport named
mailman, then mailman_transport_destination_recipient is indeed unused.
-- Larry Stone
lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] MAIL FROM envelope header query.
Hi, I have a Mailman 2.1.14 *moderated* list that goes to Gmane for newsgroup access. The other day a post was made from someone who didn't appear to be on my list. I wasn't sure whether this was due to an error at my end, or at Gmane's. So I queried them. The problem however is that I didn't understand their reply but more importantlyhow to fix things so it doesn't happen again ! Can someone here read the following and tell me if/how I can put a stop to people not on my mailing list, posting please ? When Gmane sends messages (posted through the news-to-mail gateway) to the mailing lists, it uses the subscribed email address as the MAIL FROM envelope header. If your mailing list software discriminates based on the MAIL FROM instead of the From: header (the latter is more usual), then you may see stuff like that... I have been using Mailman for a time, but still consider myself a newbie, so any help on this would be appreciated. Regards, John. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] MAIL FROM envelope header query.
John Fitzsimons wrote:
When Gmane sends messages (posted through the news-to-mail gateway)
to
the mailing lists, it uses the subscribed email address as the MAIL
FROM
envelope header. If your mailing list software discriminates based
on
the MAIL FROM instead of the From: header (the latter is more usual),
then you may see stuff like that...
They are telling you that there is a Gmane address which is a member of
your list that is how gmane receives messages posted to your list.
When someone posts to your list on Gmane, Gmane sends that post to
your list with the envelope sender (SMTP MAIL FROM address) equal to
the Gmane address that's a member of your list.
Mailman in turn checks every address found in any of the places listed
in the Defaults.py/mm_cfg.py setting SENDER_HEADERS, and if any of
these is a list member, the is considered to be from first member
address found.
It is not clear to me whether this post was held as a post from a
moderated member or just went to the list. If it just went to the list
and you want it to be held, just set the mod flag on the subscribed
Gmane address and it will be held as a post from a moderated member.
If, on the other hand, you want it treated as a non-member post, you
have to override SENDER_HEADERS in mm_cfg.py. The default setting is
SENDER_HEADERS = ('from', None, 'reply-to', 'sender')
which says places checked in order are the From: header, the envelope
sender, the Reply-To: header and the Sender: header. The None entry in
the above list refers to the envelope sender. If you just want to stop
considering the envelope sender and keep all the others, you would set
SENDER_HEADERS = ('from', 'reply-to', 'sender')
in mm_cfg.py. If you wanted to consider only the From: header, you
could set
SENDER_HEADERS = ('from', )
in mm_cfg.py (the comma and parens are significant here).
Note that this is a global setting and affects all lists in the
installation.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Newer postfix: unused parameter:mailman_destination_recipient_limit=1
Larry Stone wrote: On Fri, 9 Mar 2012, Tanstaafl wrote: Anyone have any idea why? Am I indeed not using it? I'd rather not just comment it out and test without some confirmation first, since this is a production box. transport_destination_recipient_limit is a Postfix parameter that is specific to the named transport. If you don't have a transport named mailman, then mailman_transport_destination_recipient is indeed unused. And in case you're wondering why this may have gotten put there, if you are using (the officially unsupported) postfix_to_mailman.py as a 'mailman' transport, that transport doesn't handle a single message with more than one list recipient (i.e. a post addressed to multiple lists) unless it is delivered to the transport separately for each list. Thus the requirement in that case for mailman_destination_recipient_limit=1. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
