Mailman 3 May 2010 - Mailman-Users

Re: [Mailman-Users] bounces
by b19141＠anl.gov May 5, 2010

May 5, 2010

>In SMTP 4.y.z DSNs are "temporary" errors. They could be caused by a >spam filter over loaded, or the system shutting down, or... > >> i'm assuming it's retried by the mta. the settings in mailman clearly >> state that it should be discarded right away... > >The 4.y.z should be seen as an invitation for the SMTP server to try >sending the message again at a later time. > >The MTA will eventually time out the message and generate a permanent error. I … [View More]

2 1

bounces
by kalin m May 4, 2010

May 4, 2010

hi there... wondering if fake email addresses in a mailman list can get cleaned up with the bounces options. just testing with one and the mail log says (correctly) it could not resolve the host. is this considered a hard bounce by mailman?! i have enabled the bounce processing, the maximum bounce score is 1.0, the bounce_you_are_disabled_warnings are set to 0 expecting immediate removal. now that i sent a couple of test messages out that fake address is still in the members list. what … [View More]

3 4

Re: [Mailman-Users] Changing host names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?
by Tanstaafl May 3, 2010

May 3, 2010

On 2010-05-03 5:05 PM, mailman-users-request(a)python.org wrote: > May 3 13:17:46 myhost postfix/qmgr[3930]: 265E36285BC: > from=<listname-bounces(a)myhost.example.com>, size=1334, nrcpt=4 (queue > active) > ^^^^^^ > NOTE: ^^^^^^ where did that come from? Sorry, that wrapped weird... May 3 13:17:46 myhost postfix/qmgr[3930]: 265E36285BC: from=<listname-bounces(a)myhost.example.com>, size=1334, ^^^^^^ NOTE: ^^^^^^ … [View More]

1 0

Proper names
by Hicks, Robert CTR May 3, 2010

May 3, 2010

I have some account that have the proper name and the email address of the user. I would like all my lists to only have the email address of the users. Is there a way to remove all the "Joe Public" proper names? Bob

2 1

Re: [Mailman-Users] ****SPAM**** Re: Block reply to all
by rpschwar＠knology.net May 3, 2010

May 3, 2010

Let me give further explanation of why I need this. The site I support is a community band. When there is an email set to everyone from the director about something, we do not want each person to reply to all. They should only be replying back to the person who sent the email (the director). That is why we want to limit the reply to all. Robert On Sun 02/05/10 7:01 PM , Grant Taylor gtaylor(a)riverviewtech.net sent: > Geoff Shang wrote: > > Frankly, I think the best approach … [View More]

4 4

Limitations on the subscriptions
by Nicolas Seichepine May 2, 2010

May 2, 2010

Hello, I take care of a server with mailman 2.1.5 and numerous lists, but I administer only a small part of them. Besides, my SMTP relay allows me to send e-mails only on a particular domain (university addresses). The problem is that no matter how many times I repeat to administrators and users to use only these addresses, subscriptions are regularly made with other addresses, which are rejected and generate a lot of bounces. I would like to know if there is a mean to verify automatically … [View More]

2 1

Nonexistent user receiving a monthly password reminder
by Pat Plummer May 2, 2010

May 2, 2010

I have an interesting problem. I have been reading google hits and mailman archives for the last several hours and have not been able to find anything that addresses the above problem. Here's the deal: A few months ago, I had to restore my server from back up due to catastrophic drive failure. Since then I have had a single user that was deleted over 3 years ago that has begun to get monthly password reminders for a list she no longer belongs to. Her name does not show up in any list member … [View More]

2 1

Re: [Mailman-Users] Block reply to all
by Mark Sapiro May 2, 2010

May 2, 2010

On 5/2/2010 12:10 PM, rpschwar(a)knology.net wrote: > > This is what I'm trying to do. User x sends a post to listy. User z > receives the post from the list. > > I want user Z only to be able to reply to user x and otherwise to be > required to send a new, origional, not-preply message to the list. Thanks for the explanation. The short answer is you can't remove the list posting address from all the headers. Normally it will be in the To: header or Cc: header and 'reply-… [View More]all' will include the list. If the personalization options are available to you, you can set the list(s) to Full Personalization which will replace the To: header with one that is To: the recipient of the message, but this will not help because Mailman will in this case add a Cc: to the list posting address in order to facilitate including the list in replies. Mailman works this way because it is designed mainly for discussion lists where people carry out a multi-way conversation on the list. Thus, the only thing you can do is as has been suggested, apply header_filter_rules to not accept posts that contain In-Reply-To: and/or References: headers, or use max_num_recipients = 2 to hold all posts with more than one recipient. To this latter suggestion, you replied: > That didn't work because the first message sent will go to yourself > and the mailing list which will be blocked. If you tell it not to send > it to yourself, the first message will send. If you try to reply to all > to this message it will also be sent because the reply to will only have > the member list. This reply raises other questions. The first sentence seems to indicate you want to send to the list with Cc: to yourself, and yes, such a post would be held as it would have 2 recipients. However, the last sentence indicates you are concerned about people replying-all to their own posts. Is this a real concern, or is it just something you encountered in testing with replying to your own post? I.e., normally, a reply-all would include the list and the poster and would be held for 2 recipients. Only in the case where you are replying-all to your own post and not editing the recipients, would the post have only one recipient. Of course with a recipient limit, the user could still do a reply-all and then remove all but the list address from the addressees before sending, and this reply would go to the list if you were only checking the number of recipients, so it seems if you want to block all non-original messages, header_filter_rules would be the way to go. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan [View Less]

3 2

Changing host names, revisited... DEFAULT_EMAIL_HOST
by Tanstaafl May 2, 2010

May 2, 2010

The second question I have is about the DEFAULT_EMAIL_HOST setting... Currently, people send to my lists using listname(a)example.com and everything is working fine. But, while prepping for this change I found this commented section from someone's mm_cfg.py (these comments aren't in mine for some reason): # For example, if people visit your Mailman system with # "http://www.dom.ain/mailman" then your url fqdn is "www.dom.ain", # and if people send mail to your system via "yourlist(a)dom.ain" … [View More]

2 2

Changing host names, revisited... final steps...
by Tanstaafl May 2, 2010

May 2, 2010

Lastly... Is there any special order for making these changes, or just: 1. Make the changes to mm_cfg.py per below 2. Restart mailman 3. Run $prefix/bin/withlist -l -a -r fix_url to fix all existing lists 4. Restart mailman 5. Done...? Thanks again, Charles ******************* My current and proposed new settings: Defaults.py currently contains > DEFAULT_EMAIL_HOST = 'myhost.example.com' > DEFAULT_URL_HOST = 'myhost.example.com' > DEFAULT_URL_PATTERN = 'http://%s/mailman/' … [View More]

2 1