Re: [Mailman-Users] can I resend new list creation welcome message?
Ralf Hildebrandt wrote: * Steve Lindemann st...@marmot.org: I've had several occasions where list admins have lost the initial welcome message they received when I created a new list for them. Is there a way to resend that new list created message? Welcome to the club. Awaiting the answer :) Ironically, I've never had this problem. I didn't even know it was a problem you could have. I've had listowners forget their password and ask for a reset, which I did and gave the new password to them and told them to change it ASAP, but that's different. It never once occurred to me that someone might want to re-send that original list creation message. -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] can I resend new list creation welcome message?
Mark Sapiro wrote: Steve Lindemann wrote: I've had several occasions where list admins have lost the initial welcome message they received when I created a new list for them. Is there a way to resend that new list created message? Mailman can't resend the list created email with the password. You can recreate the mail or even make a script to do it from the newlist.txt template, but you can't get the password because it's encrypted. Thank you Mark! I don't really need the password in the message (nice to have, but not needed). I can always deal with that separately if I have to. Since most of the lists on my server only have one admin the other limitation shouldn't be an issue and I can always change which email address is listed first for the admin. This will also be handy when the admin role for a list changes hands. -- Steve Lindemann __ Network Administrator //\\ ASCII Ribbon Campaign Marmot Library Network, Inc. \\// against HTML/RTF email, http://www.marmot.org //\\ vCards M$ attachments +1.970.242.3331 x116 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Bounce Score..
hello .. how can I know what the current bouce score is for each of my members?? Thanks.. _ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] mailman installation and domains - confused
Hello, at first: sorry for my bad English, German is my preferred language and I'm not a Linux guru. I'm not sure about my malman installation. I will show at first some facts: - LAN: our LAN domain is intern.company.de - the mail server in the LAN: mail.intern.company.de - on mail.intern.company.de is running open xchange on an UCS (unvention corporate server, a debian) - our external domain is: company.com - an email address is name@company.com and @company.de on the same server. - the internal open xchange has so three mail domains : intern.company.de, company.com and company.de - fetchmail is polling the emails from the external mail server - mailman is installed on the open xchange server 'mail.intern.company.de' My first mailing list is (after mailman) 'about-dummy'. And /etc/postfix/virtual contains: about-du...@company.com about-dummy about-du...@company.de about-dummy about-du...@intern.company.de about-dummy My first try to receive an email from an external address to this list is failed, because I have to add 'about-du...@localhost' in virtual. After this entry, the email was received. But why @localhost? I saw this in the log file, unknown mailbox about-du...@localhost. For mailman I have no Idea about virtual_alias or virtual domains. Only these two lines IMAGE_LOGOS = '/icons/' MTA = 'Postfix' I have added to mm_cfg.py. Is this ok? And in postfix? Here a short cutout from main.cf: ---snip--- myhostname = mail.intern.company.de mydomain = intern.company.de myorigin = /etc/mailname smtp_helo_name = mail.intern.company.de append_dot_mydomain = no masquerade_domains = $mydomain masquerade_exceptions = root transport_maps = hash:/etc/postfix/transport, ldap:ldaptransport mydestination = $myhostname.$mydomain, localhost.$mydomain, $mydomain, localhost, $transport_maps mynetworks = 127.0.0.0/8 relay_domains = $mydestination relayhost = www.company.de canonical_maps = hash:/etc/postfix/canonical virtual_maps = hash:/etc/postfix/virtual, ldap:ldapgroups, ldap:ldapdistlist, ldap:ldapvirtual, ldap:ldapsharedfolderlocal relocated_maps = hash:/etc/postfix/relocated alias_maps = hash:/etc/aliases,hash:/usr/local/mailman/data/aliases alias_database = hash:/etc/aliases ---snap--- and many LDAP entries from the open xchange installation. Is main.cf ok? I'm not sure. How looks the right configuration files? Many thanks and greeting Oliver from Germany -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Why host_name and not domain?
Hello, why I get as a subscriber a hostname and not an right email address? I think, it is not good to answer with e.g. Willkommen auf der Mailingliste %(real_name)s...@%(host_name)s! Why host_name??? host_name is not the domain! host_name is only the FQDN of the Server, but no domain. This welcome email to the subscriber is going out of our LAN and the subscriber see the internal server name of mailman!! And a mailing list isn't a 'name -at- Servername' but 'name -at- domain' !! Not: n...@mail.intern.company.de Right: n...@company.com !! How can I configure mailman??? I need help. Thanks a lot, Oliver -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Backscatter spam via the -request address
Recently I've noticed spammers have started spamming the -request address on a couple of mailing lists I host. I don't know if this is deliberate or just they've somehow picked up the -request addresses via address collection mechanisms. Anyway the result is The results of your email commands mails going to people who never sent a message to the list with a copy of the original spam attached. From looking at the code I see that newer versions of mailman than the one I'm running don't include the original message in the response to help the backscatter problem (so I've hacked the code on the copy I've got to do the same). The lists I run aren't open to people subscribing themselves - they have to be added by the list administrator. To that end there's no need on my server for the -request auto responder to reply to non-members. So to my mind the following two options on a per-list basis would be useful to me: 1) Be able to configure the -request auto responder to not reply if there were no valid commands included in the message (the spammers aren't spamming with valid commands at the moment) 2) Be able to configure the -request auto responder to not reply to non-members There may be reasons why both those options are a bad idea or are unworkable, but I thought I'd punt them out there in case anyone else found them useful :). Regards, Matt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Bounce messages to list moderator?
We have an announce-only list (all members are moderated, moderated postings are rejected). There is a single list moderator and a single list administrator. For an unknown reason, bounce messages are being sent to both the administrator and moderator e-mail addresses. This is not typical behavior for any of our other lists. I've attached headers from a recent bounce below. Any advice on why this is happening is much appreciated. -Rob Return-Path: mailman-boun...@acvr.org Received: from murder ([unix socket]) by acvr.org (Cyrus v2.3.8-OS X Server 10.5:9C31) with LMTPA; Tue, 24 Feb 2009 11:09:31 -0500 X-Sieve: CMU Sieve 2.3 Received: from localhost (localhost [127.0.0.1]) by acvr.org (Postfix) with ESMTP id E4ED890212A for treasu...@acvr.org; Tue, 24 Feb 2009 11:09:30 -0500 (EST) X-Virus-Scanned: amavisd-new at acvr.org Received: from acvr.org ([127.0.0.1]) by localhost (xserve.petrad.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3oNS6-ofbrCr for treasu...@acvr.org; Tue, 24 Feb 2009 11:09:30 -0500 (EST) Received: from xserve.petrad.com (localhost [127.0.0.1]) by acvr.org (Postfix) with ESMTP id A0B38902093 for treasu...@acvr.org; Tue, 24 Feb 2009 11:09:27 -0500 (EST) X-Original-To: announcements-ow...@acvr.org Delivered-To: announcements-ow...@acvr.org Received: from localhost (localhost [127.0.0.1]) by acvr.org (Postfix) with ESMTP id 422F6902049 for announcements-ow...@acvr.org; Tue, 24 Feb 2009 11:09:26 -0500 (EST) X-Virus-Scanned: amavisd-new at acvr.org Received: from acvr.org ([127.0.0.1]) by localhost (xserve.petrad.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2+levVjTjgSk for announcements-ow...@acvr.org; Tue, 24 Feb 2009 11:09:23 -0500 (EST) Received: from xserve.petrad.com (localhost [127.0.0.1]) by acvr.org (Postfix) with ESMTP id A97A4901EC2 for announcements-ow...@acvr.org; Tue, 24 Feb 2009 11:09:14 -0500 (EST) Subject: Bounce action notification From: mail...@acvr.org To: announcements-ow...@acvr.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary1347886839== Message-ID: mailman.17.1235491751.325.announceme...@acvr.org Date: Tue, 24 Feb 2009 11:09:11 -0500 Precedence: bulk X-BeenThere: announceme...@acvr.org X-Mailman-Version: 2.1.9 List-Id: ACVR Announcements \(moderated\) announcements.acvr.org X-List-Administrivia: yes Sender: mailman-boun...@acvr.org Errors-To: mailman-boun...@acvr.org --===1347886839== Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit This is a Mailman mailing list bounce action notice: List: Announcements Member: axon...@rad.usuhs.mil Action: Subscription disabled. Reason: Excessive or fatal bounces. The triggering bounce notice is attached below. Questions? Contact the Mailman site administrator at mail...@acvr.org. --===1347886839== Content-Type: message/rfc822 MIME-Version: 1.0 Return-Path: X-Original-To: announcements-boun...@acvr.org Delivered-To: announcements-boun...@acvr.org Received: by acvr.org (Postfix) id 11000901DF6; Tue, 24 Feb 2009 11:06:16 -0500 (EST) Date: Tue, 24 Feb 2009 11:06:16 -0500 (EST) From: mailer-dae...@acvr.org (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: announcements-boun...@acvr.org Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=DC6F7901D92.1235491576/acvr.org Content-Transfer-Encoding: 7bit Message-Id: 20090224160616.11000901...@acvr.org This is a MIME-encapsulated message. --DC6F7901D92.1235491576/acvr.org Content-Description: Notification Content-Type: text/plain; charset=us-ascii This is the mail system at host acvr.org. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system axon...@rad.usuhs.mil: host rad.usuhs.edu[151.200.170.182] said: 554 5.7.1 axon...@rad.usuhs.mil: Relay access denied (in reply to RCPT TO command) --DC6F7901D92.1235491576/acvr.org Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; acvr.org X-Postfix-Queue-ID: DC6F7901D92 X-Postfix-Sender: rfc822; announcements-boun...@acvr.org Arrival-Date: Tue, 24 Feb 2009 10:54:09 -0500 (EST) Final-Recipient: rfc822; axon...@rad.usuhs.mil Original-Recipient: rfc822;axon...@rad.usuhs.mil Action: failed Status: 5.7.1 Remote-MTA: dns; rad.usuhs.edu Diagnostic-Code: smtp; 554 5.7.1 axon...@rad.usuhs.mil: Relay access denied -- Mailman-Users mailing list
[Mailman-Users] Unable to open list admin page
Greetings, I've been using mailman since about 2004; currently, I am running version 2.1.5. We have about ten different lists on our server. Everything has been functioning well until today (quite a record). We have one list with several thousand emails. We wanted to see if we could find and remove those email addresses that have gotten stale or invalid. Consequently, we adjusted the bounce processing settings. Now, we can't log in to that particular list's admin page (all other lists do no have this problem). After typing the password and hitting enter, the web browser appears to be authenticating, but after an extensive period shows a message to the effect Internal Server Error. It seems that this would indicate some sort of corrupted file or data. Any suggestions on how to remedy this? Much thanks. Max Pyziur p...@brama.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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman 2.1.12 final released.
Champagne! * * * * [] _**_ || |*||*| |* | |_||_| |__| \*/\*/ | *| _|__|_ |__| Mark Sapiro a écrit : I am happy to announce the final release of Mailman 2.1.12. Since 2.1.12rc2 there have been a few bug fixes, the Polish translation has been updated and a couple of items have been added to the contrib directory. Mailman 2.1.12 is a minor bug fix and Python 2.6 compatibility release. The minimum Python for this release is Python 2.4 and it is compatible with Python through 2.6. The previous Mailman releases are not compatible with Python 2.6. See the release notes at https://sourceforge.net/project/shownotes.php?release_id=653108group_id=103 for more details. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. For more information, including download links, please see: http://www.list.org http://mailman.sf.net http://www.gnu.org/software/mailman -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/s.u.n%40free.fr Security Policy: http://wiki.list.org/x/QIA9 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce Score..
Khalil Abbas wrote: how can I know what the current bouce score is for each of my members?? See http://www.msapiro.net/scripts/get_bounce_info.py (mirrored at http://fog.ccsf.edu/~msapiro/scripts/get_bounce_info.py). -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce messages to list moderator?
Rob wrote: For an unknown reason, bounce messages are being sent to both the administrator and moderator e-mail addresses. This is not typical behavior for any of our other lists. I've attached headers from a recent bounce below. Any advice on why this is happening is much appreciated. The message is the notification to the owners/moderators of a member who's delivery is disabled by bounce. This notice is sent becaues bounce_notify_owner_on_disable is set to Yes. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Backscatter spam via the -request address
Matt Hoskins wrote: Recently I've noticed spammers have started spamming the -request address on a couple of mailing lists I host. I don't know if this is deliberate or just they've somehow picked up the -request addresses via address collection mechanisms. They send lots of spam ot *-owner, *-request, postmaster, webmaster, etc They know that these addresses exist on most sites, and will accept mail from most any address. This drives up their deliverability numbers, so that they can claim that they deliver to billions of addresses per second, and sell their services to people than want to send spam. It's a known problem, and it's never going to go away. It's only ever going to get worse. 1) Be able to configure the -request auto responder to not reply if there were no valid commands included in the message (the spammers aren't spamming with valid commands at the moment) That sounds like a really good idea. 2) Be able to configure the -request auto responder to not reply to non-members Not so sure about this one, but it might also be an idea to consider. However, I'm not a Mailman developer, so I can't really speak to how easy it would be to add such features. That might be a discussion to have over on the mailman-developers list. -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Unable to open list admin page
Max Pyziur wrote: We have one list with several thousand emails. We wanted to see if we could find and remove those email addresses that have gotten stale or invalid. Consequently, we adjusted the bounce processing settings. Now, we can't log in to that particular list's admin page (all other lists do no have this problem). After typing the password and hitting enter, the web browser appears to be authenticating, but after an extensive period shows a message to the effect Internal Server Error. It seems that this would indicate some sort of corrupted file or data. Can you go to the listinfo page for the list, or do you get the came error? What is the error message in the web server logs. If it is premature end of script headers, the CGI is timing out before issuing any output. The issue could be a corrupt lists/LISTNAME/config.pck, but I think it is more likely a stale lock. See the FAQ at http://wiki.list.org/x/noA9. If you find a stale lock, check Mailman's locks and error logs for clues as to what may have caused this. Note that in 2.1.5, there is a potential issue with reducing bounce_score_threshold in that cron/disabled doesn't check if bounce info is stale so, e.g, if a member has stale bounce info with a score of 3.0 and you reduce bounce_score_threshold from something greater than 3 to something = 3, the next time cron/disabled runs, that member's delivery will be disabled. This was fixed in 2.1.10. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman 2.1.12 final released.
S/U/N wrote: Champagne! I prefer Château d'Yquem. Vintage 1811, SVP. -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Backscatter spam via the -request address
Brad Knowles wrote: Matt Hoskins wrote: 1) Be able to configure the -request auto responder to not reply if there were no valid commands included in the message (the spammers aren't spamming with valid commands at the moment) That sounds like a really good idea. 2) Be able to configure the -request auto responder to not reply to non-members Not so sure about this one, but it might also be an idea to consider. However, I'm not a Mailman developer, so I can't really speak to how easy it would be to add such features. That might be a discussion to have over on the mailman-developers list. Speaking as a developer, we are aware of the spam reflection/backscatter issues with Mailman, and we want to address them. Steps will be taken in Mailman 2.2 to at least reduce this problem. Thanks for your ideas, and as Brad suggests, if you want to follow up on mailman-develop...@python.org or submit further suggestions, we'd be happy to get them. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Why host_name and not domain?
Oliver Glueck wrote: why I get as a subscriber a hostname and not an right email address? Because your Mailman installation is misconfigured. I think, it is not good to answer with e.g. Willkommen auf der Mailingliste %(real_name)s...@%(host_name)s! Why host_name??? host_name is not the domain! host_name is only the FQDN of the Server, but no domain. host_name should be the email domain for this list. If it isn't, then at least when the list was created, things like DEFAULT_EMAIL_HOST and/or the VIRTUAL_HOSTS dictionary were not properly configured. This welcome email to the subscriber is going out of our LAN and the subscriber see the internal server name of mailman!! And a mailing list isn't a 'name -at- Servername' but 'name -at- domain' !! Not: n...@mail.intern.company.de Right: n...@company.com !! How can I configure mailman??? DEFAULT_URL_HOST = 'the domain you want the world to see in web URLs' DEFAULT_EMAIL_HOST = 'company.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) in mm_cfg.py. Then restart mailman and run bin/withlist -a -l -r fix_url to fix your lists. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman installation and domains - confused
Oliver Glueck wrote: I'm not sure about my malman installation. I will show at first some facts: - LAN: our LAN domain is intern.company.de - the mail server in the LAN: mail.intern.company.de - on mail.intern.company.de is running open xchange on an UCS (unvention corporate server, a debian) - our external domain is: company.com - an email address is name@company.com and @company.de on the same server. - the internal open xchange has so three mail domains : intern.company.de, company.com and company.de - fetchmail is polling the emails from the external mail server - mailman is installed on the open xchange server 'mail.intern.company.de' My first mailing list is (after mailman) 'about-dummy'. And /etc/postfix/virtual contains: about-du...@company.com about-dummy about-du...@company.de about-dummy about-du...@intern.company.de about-dummy These things shouldn't be in /etc/postfix/virtual. My first try to receive an email from an external address to this list is failed, because I have to add 'about-du...@localhost' in virtual. After this entry, the email was received. But why @localhost? I saw this in the log file, unknown mailbox about-du...@localhost. This is not a Mailman issue. This is probably fetchmail that is delivering the message to about-du...@localhost. For mailman I have no Idea about virtual_alias or virtual domains. Only these two lines IMAGE_LOGOS = '/icons/' MTA = 'Postfix' I have added to mm_cfg.py. Is this ok? With MTA = 'Postfix'. Mailman will maintain both aliases in /usr/local/mailman/data/aliases and virtual maps (if necessary?) in /usr/local/mailman/data/virtual-mailman, but you have issues that will probably preclude this from working. If fetchmail is going to deliver to addresses like listn...@localhost listname-boun...@localhost etc, and localhost is in mydestination as it appears to be, you only need aliases and not virtual maps. Thus both what you have in mm_cfg.py and what you have in main.cf looks OK. If you have mail being given to Postfix for listn...@company.com, you can add POSTFIX_STYLE_VIRTUAL_DOMAINS = ['company.com'] in mm_cfg.py and, assuming the list's email domain is company.com (see my reply to your other post), Mailman will generate virtual maps like listn...@company.com LISTNAME listname-boun...@company.com LISTNAME-bounces etc, in /usr/local/mailman/data/virtual-mailman and you need to add hash:/usr/local/mailman/data/virtual-mailman to virtual_maps in main.cf. If you actually need multiple domains for the same list in the virtual maps, Mailman won't do that automatically. And in postfix? Here a short cutout from main.cf: ---snip--- myhostname = mail.intern.company.de mydomain = intern.company.de myorigin = /etc/mailname smtp_helo_name = mail.intern.company.de append_dot_mydomain = no masquerade_domains = $mydomain masquerade_exceptions = root transport_maps = hash:/etc/postfix/transport, ldap:ldaptransport mydestination = $myhostname.$mydomain, localhost.$mydomain, $mydomain, localhost, $transport_maps mynetworks = 127.0.0.0/8 relay_domains = $mydestination relayhost = www.company.de canonical_maps = hash:/etc/postfix/canonical virtual_maps = hash:/etc/postfix/virtual, ldap:ldapgroups, ldap:ldapdistlist, ldap:ldapvirtual, ldap:ldapsharedfolderlocal relocated_maps = hash:/etc/postfix/relocated alias_maps = hash:/etc/aliases,hash:/usr/local/mailman/data/aliases alias_database = hash:/etc/aliases ---snap--- and many LDAP entries from the open xchange 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman 2.1.12 final released.
S/U/N wrote: Champagne! * * * * [] _**_ || |*||*| |* | |_||_| |__| \*/\*/ | *| _|__|_ |__| Merci! -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce messages to list moderator?
Rob wrote: So, owner = administrator(s) moderators? Can bounces be sent only to the administrator? My list moderators don't need to get bounce notices. The list has attributes 'owner' and 'moderator', each of which is a list of zero or more addresses, although having zero addresses in 'owner' is not a good idea. Most owner notifications are actually sent to LISTNAME-owner which in turn is resent to all the owner AND moderator addresses. Some notices use the Message.OwnerNotification class directly which has the ability to exclude moderators, but I think the only notice that goes to owners only and not moderators is the forward of an unrecognized bounce. So the answer is if bounce_unrecognized_goes_to_list_owner is Yes, those notices go only to the 'owner' addresses and not to 'moderator' addresses, but the bounce_notify_owner_on_disable notices and the bounce_notify_owner_on_removal notices go to both 'owner' and 'moderator' addresses and changing this would require source code modifications. Granted, the terminology, documentation and results are not consistent, but that's the way it works. -- 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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Setting a bind address for SMTP delivery
Hi, I'm wondering if there's a way to set the address that mailman binds to when sending SMTP. Here's the background: I'm using postfix as a MTA. When postfix receives mail containing addresses that have no @domain part, and the mail is sent from the local box, it automatically adds @whateverthelocaldomainis to the end of all header and envelope addresses. This causes a problem with mailman, because mailman is sending mail from the local box any addresses that come in without @domain on the end (for whatever reason) gets rewritten when mailman re-sends the mail to the list. There's various ways around the problem, ways to keep postfix from re-writing the addresses. I think the simplest would be if I could control the address from which mailman sends it's mail, say if mailman binds to 127.0.0.2 instead of 127.0.0.1 when it sends it's mail. But I don't see a knob I can frob to control this. (Postfix seems to prefer to base it's address re-writing decision on the IP of the SMTP client.) At the moment I happen to be running Debian etch, which has a 2.1 based mailman version. I soon hope to be running something newer. Thanks. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Setting a bind address for SMTP delivery
on 2/25/09 10:28 PM, Karl O. Pinc said: This causes a problem with mailman, because mailman is sending mail from the local box any addresses that come in without @domain on the end (for whatever reason) gets rewritten when mailman re-sends the mail to the list. This is a problem to fix in your MTA, before the message ever gets to Mailman. Your MTA should be ensuring that all addresses are properly fully qualified, either when it reads the message from the sender, or after the sender has sent the message and it does internal processing. This really isn't a problem that can be solved from within Mailman. -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Setting a bind address for SMTP delivery
On 02/25/2009 11:07:46 PM, Brad Knowles wrote: on 2/25/09 10:28 PM, Karl O. Pinc said: This causes a problem with mailman, because mailman is sending mail from the local box any addresses that come in without @domain on the end (for whatever reason) gets rewritten when mailman re-sends the mail to the list. This is a problem to fix in your MTA, before the message ever gets to Mailman. Your MTA should be ensuring that all addresses are properly fully qualified, either when it reads the message from the sender, or after the sender has sent the message and it does internal processing. This really isn't a problem that can be solved from within Mailman. I agree, but the problem is that an MTA shouldn't be re-writing addresses in mail that it receives from external sources, that is, the Internet. Mail sent from a _local_ source should be re-written by the MTA to be properly fully qualified. So, I need to figure out how to pretend that mail re-sent by Mailman is mail that is, effectively, from an external source. That means Mailman needs to do something different so the MTA can distinguish the mail Mailman sends from regular mail sent locally from the box. Or do you think that an MTA should re-write all addresses and fully qualify them with the local domain, regardless of whether the mail was received from the Internet for delivery to a local user? I don't mean to put words in your mouth but that seems to be the only alternative. Somebody else out there is mis-behaving and I've got to deal with the consequences. It would be easiest to tell the Postfix MTA that the mail that Mailman sends is not of local origin if Mailman could be set to bind to a particular IP when sending mail via SMTP. Thanks for the reply. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Setting a bind address for SMTP delivery
on 2/25/09 11:53 PM, Karl O. Pinc said: Or do you think that an MTA should re-write all addresses and fully qualify them with the local domain, regardless of whether the mail was received from the Internet for delivery to a local user? I don't mean to put words in your mouth but that seems to be the only alternative. That's not the only solution to this problem, but most of the time it is the simplest and easiest to implement. If you always use fully-qualified names across the board, then there can't ever be any question of whether or not something belongs in one place or another. -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Setting a bind address for SMTP delivery
On 02/26/2009 12:29:33 AM, Brad Knowles wrote: on 2/25/09 11:53 PM, Karl O. Pinc said: Or do you think that an MTA should re-write all addresses and fully qualify them with the local domain, regardless of whether the mail was received from the Internet for delivery to a local user? I don't mean to put words in your mouth but that seems to be the only alternative. That's not the only solution to this problem, but most of the time it is the simplest and easiest to implement. If you always use fully-qualified names across the board, then there can't ever be any question of whether or not something belongs in one place or another. Tacking my domain name on somebody else's email address puts it in the wrong place. Better to leave it alone. The Postfix author seem to agree. Postfix has changed so that the default is to rewrites only the mail sent by local users. For the rationale and further detail see: http://www.postfix.org/ADDRESS_REWRITING_README.html#william You are correct, there is no right answer. I am able to configure Postfis so that Mailman mail is not rewritten, but it would be more straightforward if Mailman had another knob to frob. I will see what happens and if there are too many problems then I'll change the rewriting rules. (I'd tend to favor bouncing such incoming email. But given the application that's not an option.) Thank you for the input. It has been helpful. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein P.S. FYI. I'm pretty confidant it's Microsoft software that's causing this headache, although I couldn't say whether it's Outlook or Exchange. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
