[Mailman-Users] Problem with mailman-loop address
On 6/8/19 9:58 AM, ratatouille wrote: > Hello! > > Mark Sapiro schrieb am 08.06.19 um 08:13:24 Uhr: > >> On 6/8/19 3:29 AM, ratatouille wrote: >>> >>> In /var/lib/mailman/data/aliases there is no alias like mailman-loop. >>> >>> What's wrong here and how do I fix this? >> >> >> There should be. If Mailman is generating this file, it should contain >> >> # The ultimate loop stopper address >> mailman-loop: /var/lib/mailman/data/owner-bounces.mbox >> >> Try running Mailman's bin/genaliases > > I did this already, it is not there. > > # STANZA START: mailman > # CREATED: Sat Jun 8 11:43:23 2019 > mailman: "|/usr/lib/mailman/mail/mailman post mailman" > mailman-admin: "|/usr/lib/mailman/mail/mailman admin mailman" > mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman" > mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman" > mailman-join:"|/usr/lib/mailman/mail/mailman join mailman" > mailman-leave: "|/usr/lib/mailman/mail/mailman leave mailman" > mailman-owner: "|/usr/lib/mailman/mail/mailman owner mailman" > mailman-request: "|/usr/lib/mailman/mail/mailman request mailman" > mailman-subscribe: "|/usr/lib/mailman/mail/mailman subscribe mailman" > mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman" > # STANZA END: mailman It's not in that stanza. The beginning of the aliases file, even in 2.1.17 should be > # This file is generated by Mailman, and is kept in sync with the > # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE > # unless you know what you're doing, and can keep the two files properly > # in sync. If you screw it up, you're on your own. > > # The ultimate loop stopper address > mailman-loop: /var/lib/mailman/data/owner-bounces.mbox If this is not the case, what Mailman package is this? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailman-loop address
Hello! Mark Sapiro schrieb am 08.06.19 um 08:13:24 Uhr: > On 6/8/19 3:29 AM, ratatouille wrote: > > > > In /var/lib/mailman/data/aliases there is no alias like mailman-loop. > > > > What's wrong here and how do I fix this? > > > There should be. If Mailman is generating this file, it should contain > > # The ultimate loop stopper address > mailman-loop: /var/lib/mailman/data/owner-bounces.mbox > > Try running Mailman's bin/genaliases I did this already, it is not there. # STANZA START: mailman # CREATED: Sat Jun 8 11:43:23 2019 mailman: "|/usr/lib/mailman/mail/mailman post mailman" mailman-admin: "|/usr/lib/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/lib/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/lib/mailman/mail/mailman confirm mailman" mailman-join:"|/usr/lib/mailman/mail/mailman join mailman" mailman-leave: "|/usr/lib/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/lib/mailman/mail/mailman owner mailman" mailman-request: "|/usr/lib/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/lib/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman Andreas -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailman-loop address
On 6/8/19 3:29 AM, ratatouille wrote: > > In /var/lib/mailman/data/aliases there is no alias like mailman-loop. > > What's wrong here and how do I fix this? There should be. If Mailman is generating this file, it should contain # The ultimate loop stopper address mailman-loop: /var/lib/mailman/data/owner-bounces.mbox Try running Mailman's bin/genaliases -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem with mailman-loop address
Hello! Using mailman 2.1.17 Today I found this in the logfile: Jun 1 05:16:16 bitmachine1 postfix/qmgr[4215]: 3070F181214: from=, size=6027, nrcpt=1 (queue active) Jun 1 05:16:16 bitmachine1 postfix/smtpd[3659]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 3070F181214; from= to= proto=ESMTP helo= Jun 1 05:16:16 bitmachine1 postfix/lmtp[3687]: 599AE1811EF: to=, relay=mail.bitcorner.de[private/dovecot-lmtp], delay=0.05, delays=0.02/0/0.03/0.01, dsn=5.1.1, status=bounced (host mail.bitcorner.de[private/dovecot-lmtp] said: 550 5.1.1 User doesn't exist: mailman-l...@listen.bitcorner.de (in reply to RCPT TO command) In /var/lib/mailman/data/aliases there is no alias like mailman-loop. What's wrong here and how do I fix this? Kind regards Andreas -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem with mailman web interface on Debian/Apache
Hello, I just setup mailman on Debian and created the first list mailman. I receive a new mailing list email, with the link: http://mysite/cgi-bin/mailman/admin/mailman Unfortunately when opening this URL I get: 404: The requested URL /cgi-bin/mailman/admin/mailman was not found on this server. I used the following tutorial: http://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze /usr/lib/cgi-bin/mailman/ seems to contain the proper contents, whereas /var/www/lists is empty. Can anyone help me? Kind regards, Sascha. -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailman web interface on Debian/Apache
On 10/20/2013 06:26 AM, Sascha Rissel wrote: I just setup mailman on Debian and created the first list mailman. ... I used the following tutorial: http://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze Please see the FAQ at http://wiki.list.org/x/OIDD. Can anyone help me? See http://www.list.org/mailman-install/node10.html. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailman and outlook.com
On 07-10-13 04:36, Mark Sapiro wrote: On 10/04/2013 05:51 AM, Tim Sterk wrote: Hi All, I'm having a problem with outlook.com and mailman. When I'm trying to send a message through Outlook.com marks it as spam, but when I'm sending a message from the same domain (and IP address), it is accepted without a hitch. Underneath the headers of a message that is rejected at outlook.com: Rejected or marked as spam? They are not the same. And if it was rejected, where did you find the headers? They are moved into the unwanted box, so I was able to view the message and headers from there. *Is there anybody who can help me solving this problem? Probably only Microsoft, but the FAQ at http://wiki.list.org/x/4oA9 may help. The interesting part for me is that this problem only applies to mail sent through mailman, if I'm sending an email to the same address from the same domain name it is accepted without a problem, so I'm thinking that there is something in the headers that triggers this reaction at outlook.com. p.s. the messages are accepted without a problem at gmail.com (I haven't tried any other major mail providers). Greetings, Tim Sterk -- Mailman-Users mailing list Mailman-Users@python.org https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailman and outlook.com
On 10/09/2013 12:45 AM, Tim Sterk wrote: They are moved into the unwanted box, so I was able to view the message and headers from there. So they were not rejected but rather marked as spam and put in a spam box rather than the inbox. Had they been rejected, you wouldn't have seen them at all, and they would have been recorded as a bounce by Mailman. The interesting part for me is that this problem only applies to mail sent through mailman, if I'm sending an email to the same address from the same domain name it is accepted without a problem, so I'm thinking that there is something in the headers that triggers this reaction at outlook.com. Exactly. It could be the 'Precedence: list' header or some other header or combination of headers, but only Microsoft knows for sure, and they won't tell you because they consider it proprietary information which would be useful to spammers. Since you apparently use Mutt and have your own server, you could experiment by resending the message directly with all Mailman's added headers and delete headers one by one to find the header(s) that trigger it, but it is possible that this is a more complex situation than that which depends on the presence of certain headers in combination together with body contents. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailman and outlook.com
On 10/04/2013 05:51 AM, Tim Sterk wrote: Hi All, I'm having a problem with outlook.com and mailman. When I'm trying to send a message through Outlook.com marks it as spam, but when I'm sending a message from the same domain (and IP address), it is accepted without a hitch. Underneath the headers of a message that is rejected at outlook.com: Rejected or marked as spam? They are not the same. And if it was rejected, where did you find the headers? *Is there anybody who can help me solving this problem? Probably only Microsoft, but the FAQ at http://wiki.list.org/x/4oA9 may help. -- 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 https://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: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem with mailman and outlook.com
Hi All, I'm having a problem with outlook.com and mailman. When I'm trying to send a message through Outlook.com marks it as spam, but when I'm sending a message from the same domain (and IP address), it is accepted without a hitch. Underneath the headers of a message that is rejected at outlook.com: *x-store-info:4r51+eLowCe79NzwdU2kRyU+pBy2R9QCDI9u8Kc1JelXzetVs2jxqzkjAYPLy37kFX3uWvhbpReT+kd3FNPdHDodYhyNaiuBe10IjgJ9uVS+uLoSKBU3VnG6jNOpx113ilW3cGTstfg=** **Authentication-Results: hotmail.com; spf=pass (sender IP is 5.100.228.36) smtp.mailfrom=multimedia-boun...@timsterk.nl; dkim=none header.d=omroep.nl; x-hmca=pass header.id=multimedia-boun...@timsterk.nl** **X-SID-PRA: multimedia-boun...@timsterk.nl** **X-AUTH-Result: PASS** **X-SID-Result: PASS** **X-Message-Status: n:n** **X-Message-Delivery: Vj0xLjE7dXM9MDtsPTA7YT0wO0Q9MjtHRD0yO1NDTD00** **X-Message-Info: 11chDOWqoTn8iE/ukSoV1IKf/+tjujgtcofeWcH8mN5+omgSD1AOLsWpxZfkXjbeki+FAFVuODCkKqQlTLEmbqmxAv6EBb8AU1OosBVIDZg0IwMEF5IBFbQ8d8fDABaP5BwS6e8fEhibyMgyZZVlOMsuLjg68zz52a+xOkOOje76eIAVTHAuFzBzttwS/avJZnMVYx8SqqkNx/IDKm+v0k83Kfw0rshe** **Received: from hosting.timsterk.nl ([5.100.228.36]) by COL0-MC3-F48.Col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4900);** ** Fri, 4 Oct 2013 01:38:14 -0700** **Received: from localhost (localhost.localdomain [127.0.0.1])** **by hosting.timsterk.nl (Postfix) with ESMTP id 8619B20147B** **for rswg...@hotmail.com; Fri, 4 Oct 2013 09:38:13 +0100 (WEST)** **X-Virus-Scanned: Debian amavisd-new at hosting.timsterk.nl** **Received: from hosting.timsterk.nl ([127.0.0.1])** **by localhost (hosting.timsterk.nl [127.0.0.1]) (amavisd-new, port 10024)** **with ESMTP id m-as2VKnalxb for rswg...@hotmail.com;** **Fri, 4 Oct 2013 09:38:12 +0100 (WEST)** **Received: from hosting.timsterk.nl (localhost.localdomain [127.0.0.1])** **by hosting.timsterk.nl (Postfix) with ESMTP id C48DD2012C8;** **Fri, 4 Oct 2013 09:38:09 +0100 (WEST)** **Received: from localhost (localhost.localdomain [127.0.0.1])** ** by hosting.timsterk.nl (Postfix) with ESMTP id 9397C201472** ** for multime...@lists.timsterk.nl; Fri, 4 Oct 2013 09:37:25 +0100 (WEST)** **X-Virus-Scanned: Debian amavisd-new at hosting.timsterk.nl** **Received: from hosting.timsterk.nl ([127.0.0.1])** ** by localhost (hosting.timsterk.nl [127.0.0.1]) (amavisd-new, port 10024)** ** with ESMTP id e2U_TLa8kIQS for multime...@lists.timsterk.nl;** ** Fri, 4 Oct 2013 09:37:25 +0100 (WEST)** **Received: from out1b.mail.omroep.nl (out1b.mail.omroep.nl [145.58.30.185])** ** by hosting.timsterk.nl (Postfix) with ESMTP id 107E9201471** ** for multime...@timsterk.nl; Fri, 4 Oct 2013 09:37:23 +0100 (WEST)** **Received: from localhost (ou1bclean [10.10.30.159])** ** by out1b.mail.omroep.nl (Postfix MTA - NPO ICT) with ESMTP id 1D6AE8016C2** ** for multime...@timsterk.nl; Fri, 4 Oct 2013 10:37:24 +0200 (CEST)** **X-Virus-Scanned: NPO ICT** **Received: from tech1a.mail.omroep.nl (tech1a.mail.omroep.nl [145.58.71.108])** ** by out1b.mail.omroep.nl (Postfix MTA - NPO ICT) with ESMTP id 0D44A8016C0** ** for multime...@timsterk.nl; Fri, 4 Oct 2013 10:37:24 +0200 (CEST)** **Received: from localhost (unknown [IPv6:2a02:458:101:13:21f:d0ff:fe46:e9c1])** ** by tech1a.mail.omroep.nl (Postfix MTA - NPO ICT) with ESMTPSA id D6EBB201270F** ** for multime...@timsterk.nl; Fri, 4 Oct 2013 10:37:23 +0200 (CEST)** **Date: Fri, 4 Oct 2013 10:37:23 +0200** **From: Tim Sterk tim.st...@omroep.nl** **To: multime...@timsterk.nl** **Message-ID: 20131004083723.gg12...@omroep.nl** **MIME-Version: 1.0** **Content-Disposition: inline** **X-Clue: no** **X-Disclaimer: Geregistreerd bij de Kamer van Koophandel Gooi Eemland onder** ** nummer 32043579 // Registered at the Chamber of Commerce** **User-Agent: Mutt/1.5.21 (2010-09-15)** **X-Mailman-Approved-At: Fri, 04 Oct 2013 09:38:09 +0100** **Subject: [Multimedia] test** **X-BeenThere: multime...@timsterk.nl** **X-Mailman-Version: 2.1.15** **Precedence: list** **List-Id: multimedia.timsterk.nl** **List-Unsubscribe: http://lists.timsterk.nl/options/multimedia,** ** mailto:multimedia-requ...@timsterk.nl?subject=unsubscribe** **List-Archive: http://lists.timsterk.nl/pipermail/multimedia/** **List-Post: mailto:multime...@timsterk.nl** **List-Help: mailto:multimedia-requ...@timsterk.nl?subject=help** **List-Subscribe: http://lists.timsterk.nl/listinfo/multimedia,** ** mailto:multimedia-requ...@timsterk.nl?subject=subscribe** **Content-Type: text/plain; charset=us-ascii** **Content-Transfer-Encoding: 7bit** **Errors-To: multimedia-boun...@timsterk.nl** **Sender: Multimedia multimedia-boun...@timsterk.nl** **Return-Path: multimedia-boun...@timsterk.nl** **X-OriginalArrivalTime: 04 Oct 2013 08:38:14.0931 (UTC) FILETIME=[1134EE30:01CEC0DD]* And here are the headers of a mail that is accepted at outlook.com (same domain and IP address, different mailbox): * *
Re: [Mailman-Users] problem with mailman not working...
Thanks again. Observations: Somehow the stale lock was stopping all emails from going out and secondly, /var/lock/mailman is where the lock was. I'm not sure how I happened to figure that lock location out as it isn't ~mailman/locks. Perhaps my config is non-standard. Troy This email was created using 100% recycled organic free range electrons. On 1/13/2012 4:11 PM, Mark Sapiro wrote: Troy Campbell wrote: It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! I'm glad things are again working well for you, but deleting and recreating the list was probably overkill. The FAQ at http://wiki.list.org/x/noA9 gives information about clearing stale/orphaned locks. I have now added a pointer to this FAQ from section 7 of the FAQ athttp://wiki.list.org/x/A4E9. -- 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] problem with mailman not working...
Troy Campbell wrote: Thanks again. Observations: Somehow the stale lock was stopping all emails from going out and secondly, /var/lock/mailman is where the lock was. I'm not sure how I happened to figure that lock location out as it isn't ~mailman/locks. Perhaps my config is non-standard. Is this a RedHat RPM installation? See http://wiki.list.org/x/KYCB. -- 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] problem with mailman not working...
It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! Troy This email was created using 100% recycled organic free range electrons. On 1/12/2012 8:05 PM, Mark Sapiro wrote: On 1/12/2012 6:09 PM, Troy Campbell wrote: It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878: to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23, delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post troytest) No email is coming out though? It should be expanding to my email address? OK. The mail was piped to the wrapper to be posted to the list, so now it's getting to Mailman. See the FAQ athttp://wiki.list.org/x/A4E9, particularly sections 2b, 6b, 7, 8, 9 and 13. -- 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] problem with mailman not working...
Troy Campbell wrote: It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! I'm glad things are again working well for you, but deleting and recreating the list was probably overkill. The FAQ at http://wiki.list.org/x/noA9 gives information about clearing stale/orphaned locks. I have now added a pointer to this FAQ from section 7 of the FAQ at http://wiki.list.org/x/A4E9. -- 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] problem with mailman not working...
For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? Regards, -- Troy 719-484-2300 This email was created using 100% recycled organic free range electrons. -- 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] problem with mailman not working...
Troy Campbell wrote: For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Yes, it sounds like a Postfix issue, but in order to say anything, we'd need to see postconf -n and some relevant Postfix log messages. Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. Which one? (ps -fw) I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? The command is postalias, not postmap, and it's unlikely to help unless perhaps you previously ran 'postmap /etc/mailman/aliases', but it couldn't hurt to run 'postalias /etc/mailman/aliases'. -- 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] problem with mailman not working...
Thanks so much Mark...see inline replies below Troy This email was created using 100% recycled organic free range electrons. On 1/12/2012 5:48 PM, Mark Sapiro wrote: Troy Campbell wrote: For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Yes, it sounds like a Postfix issue, but in order to say anything, we'd need to see postconf -n and some relevant Postfix log messages. # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliaseshash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 html_directory = no inet_interfaces = all local_recipient_maps = mail_owner = postfix mailbox_size_limit = 0 mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname localhost.$mydomainlocalhost localhost.localdomainrequest1.localdomain request2.localdomain request1.rmtc.fedex.com request2.rmtc.fedex.com mailman.rmtc.fedex.commailman2.rmtc.fedex.com mynetworks = 127.0.0.1/32146.18.0.0/16 155.161.0.0/16161.135.0.0/16 165.150.0.0/16170.5.0.0/16 170.86.0.0/16172.18.64.0/18 192.189.184.0/22198.140.0.0/22 199.81.0.0/16199.82.0.0/16 204.135.100.0/23204.135.106.0/23 204.135.108.0/23204.135.92.0/23 204.135.94.0/23204.135.96.0/23 204.135.97.0/23172.31.248.0/23 172.31.252.0/23 newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no permit_mx_backup_networks = $mynetworks queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES recipient_delimiter = + relay_domains = cosd.fedex.comrmtc.fedex.com relayhost = mapper.mail.fedex.com sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_authorized_verp_clients = localhost smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/accesspermit_mynetworks reject_unauth_destination transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. Which one? (ps -fw) mailman 21869 21862 92 16:16 ?02:24:52 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? The command is postalias, not postmap, and it's unlikely to help unless perhaps you previously ran 'postmap /etc/mailman/aliases', but it couldn't hurt to run 'postalias /etc/mailman/aliases'. It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1
Re: [Mailman-Users] problem with mailman not working...
On 1/12/2012 6:09 PM, Troy Campbell wrote: It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878: to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23, delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post troytest) No email is coming out though? It should be expanding to my email address? OK. The mail was piped to the wrapper to be posted to the list, so now it's getting to Mailman. See the FAQ at http://wiki.list.org/x/A4E9, particularly sections 2b, 6b, 7, 8, 9 and 13. -- 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] problem with Mailman on Mac OS X Snow Leopard client
Mail generated by Mailman hangs in my dedicated, on-board MTA's queue unless I remove a certain bit of custom Postfix configuration that I entered following instructions kindly posted here by one Larry Stone. The instruction in question are those for building Mailman on above platform directly from code downloaded from a source referenced on list.org and the configuration in question is one involving alias maps. Everything about this build of Mailman seems to be working fine. I can create lists and add or remove members. New members receive the expected mail--but here's the catch: only if I remove the above mentioned bit of custom Postscript configuration. I came to suspect this bit of custom Postscript configuration exactly because Postfix reported an error involving it. Therefore I removed the bit of custom Postscript configuration to see if the queue would clear and it did. Everyone got their mail. However and of course, I question whether I can just remove this bit of custom Postscript configuration without consequences. Mailman-users may seem unlikely as a place to inquire about this; but, again, the instruction to use this bit of custom Postfix configuration came from a poster to this list whose particular posting is cited on list.org as authoritative. I am running Mailman on an Intel Mac mini with the client version of Mac OS X Snow Leopard installed. I will gladly post more details about my platform although I am not sure what might be needed. The bit of custom Postfix configuration that I've experimented with removing is exactly as follows: hash:/etc/postfix/aliases The context in which this bit is supposed to appear is as follows: alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases. I just remove the bit, leaving: alias_maps = hash:/usr/local/mailman/data/aliases. Again, with just this as remnant of my custom Postscript configuration, Mailman-generated mail gets sent. The error message that Postfix repeatedly issues when I don't have the suspect portion of this bit of custom Postscript configuration removed is as follows: Oct 10 21:10:05 email postfix/local[75578]: fatal: open database /etc/postfix/aliases.db: No such file or directory Oct 10 21:10:06 email postfix/master[141]: warning: process /usr/libexec/postfix/local pid 75578 exit status 1 Oct 10 21:10:06 email postfix/master[141]: warning: /usr/libexec/postfix/local: bad command startup -- throttling Oct 10 21:11:06 email postfix/local[75583]: fatal: open database /etc/postfix/aliases.db: No such file or directory Oct 10 21:11:07 email postfix/master[141]: warning: process /usr/libexec/postfix/local pid 75583 exit status 1 Oct 10 21:11:07 email postfix/master[141]: warning: /usr/libexec/postfix/local: bad command startup -- throttling Oct 10 21:12:07 email postfix/local[75584]: fatal: open database /etc/postfix/aliases.db: No such file or directory Oct 10 21:12:08 email postfix/master[141]: warning: process /usr/libexec/postfix/local pid 75584 exit status 1 Oct 10 21:12:08 email postfix/master[141]: warning: /usr/libexec/postfix/local: bad command startup -- throttling Oct 10 21:13:08 email postfix/local[75593]: fatal: open database /etc/postfix/aliases.db: No such file or directory Oct 10 21:13:09 email postfix/master[141]: warning: process /usr/libexec/postfix/local pid 75593 exit status 1 Oct 10 21:13:09 email postfix/master[141]: warning: /usr/libexec/postfix/local: bad command startup -- throttling One can see why I investigated Postscript alias maps upon seeing these log entries. I obviously don't understand them, though. Finally, inasmuch as it may be relevant, I next post feedback that I get from a certain postconf command, specifically postconf alias_maps: alias_maps = hash:/etc/aliases Seeing this as the feedback to said command, makes we wonder: Wouldn't the correct feedback here include reference to Mailman's own aliases file given what remains of my custom Postscript configuration? Anyway, something is certainly wrong. Assistance, if offered, will be much appreciated. Indeed thanks for even reading this since its the first thing I hope for that people read about my problem. Hopefully, I have posted well for starters but i am more than happy to take hints about what else I need to submit. I am a first time poster. Graham -- 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] problem with Mailman on Mac OS X Snow Leopard client
On Mon, 10 Oct 2011, Graham Young wrote: Mail generated by Mailman hangs in my dedicated, on-board MTA's queue unless I remove a certain bit of custom Postfix configuration that I entered following instructions kindly posted here by one Larry Stone. I guess I'm best to answer this. The bit of custom Postfix configuration that I've experimented with removing is exactly as follows: hash:/etc/postfix/aliases The context in which this bit is supposed to appear is as follows: alias_maps = hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases. I just remove the bit, leaving: alias_maps = hash:/usr/local/mailman/data/aliases. Again, with just this as remnant of my custom Postscript configuration, Mailman-generated mail gets sent. alias_maps is this list of aliases, local addresses which do not get delivered locally but rather get sent elsewhere. That could be another address (for instance, on my system, postmaster is an alias for me so I get all postmaster mail) or for Mailman, a pipe to the Mailman mail input script. The error message that Postfix repeatedly issues when I don't have the suspect portion of this bit of custom Postscript configuration removed is as follows: Oct 10 21:10:05 email postfix/local[75578]: fatal: open database /etc/postfix/aliases.db: No such file or directory It means exactly what it says. /etc/postfix/aliases.db does not exist. Finally, inasmuch as it may be relevant, I next post feedback that I get from a certain postconf command, specifically postconf alias_maps: alias_maps = hash:/etc/aliases That should be the outpust of postconf -d alias_maps. -d means the default value. On my system (and I have never touched this part), /etc/aliases is a softlink to /etc/postfix/aliases (in other words, just a pointer to that file). So the real is why does /etc/postfix/aliases.db not exist. It's not really required and it isn't part of Mailman. I had assumed it was past of the standard Postfix installation on OS X client but perhaps not (or maybe it was and no longer is but I didn't realize that because I've been upgrading or moving all the way from 10.3. (a digression as to how aliases.db is created. aliases is a text file in a prescribed format. To turn it into the hash table Postfix wants to use, it's run through postmap. postmap hash:aliases created aliases.db) The purpose of that customization is to append Mailman's alias file to the existing alias file. If you don't have /etc/postfix/aliases.db, then don't include it in alias_maps. It's that simple. If you have a different aliases file, use that in place of /etc/postfix/aliases in alias_maps. The best way to do this is to look in your Postfix main.cf for an earlier definition of alias_maps. So if you find alias_maps = hash:foo, then replace my instructions with alias_maps = hash:foo, hash:/usr/local/mailman/data/aliases If there is no prior definition of alias_maps in main.cf, then do postconf -d alias_maps and then: alias_maps = (whatever postconf -d alias_maps returned), hash:/usr/local/mailman/data/aliases However, please note that my instructions assume and expect familiarity with Postfix. If you don't understand Postfix, you will almost certainly have other problems in the future. -- 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] Problem with Mailman+Postfix
Hi there.
I´m using Postfix + Dovevot + Mailman on Debian Lenny with ISPConfig3 Setup.
I´ve installed Mailman seperate from ISPConfig via apt-get,
administrating lists works fine but there is one problem: Postfix does
not accept incoming mails to the mailing list.
mail.info:
Jul 22 10:53:13 atom-29 postfix/smtpd[12620]: NOQUEUE: reject: RCPT from
mailout-de.gmx.net[213.165.64.22]: 550 5.1.1 t...@xyz.net: Recipient
address rejected: User unknown in virtual mailbox table;
from=a...@gmx.de to=t...@xyz.net proto=SMTP helo=mailout-de.gmx.net
main.cf of Postfix:
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.
myorigin = /etc/mailname
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
# Uncomment the next line to generate delayed mail warnings
#delay_warning_time = 4h
readme_directory = /usr/share/doc/postfix
# TLS parameters
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_use_tls = yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.
myhostname = atom-29.ip-projects.de
alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
myorigin = /etc/mailname
mydestination = atom-29.ip-projects.de, localhost, localhost.localdomain
relayhost =
mynetworks = 127.0.0.0/8 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
html_directory = /usr/share/doc/postfix/html
virtual_alias_domains =
virtual_alias_maps =
proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf,
mysql:/etc/postfix/mysql-virtual_email2email.cf
virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
virtual_mailbox_base = /var/vmail
virtual_uid_maps = static:5000
virtual_gid_maps = static:5000
smtpd_sasl_auth_enable = yes
broken_sasl_auth_clients = yes
smtpd_sasl_authenticated_header = yes
smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, check_recipient_access
mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination
smtpd_tls_security_level = may
transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
relay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cf
relay_recipient_maps =
mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
proxy_read_maps = $local_recipient_maps $mydestination
$virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps
$virtual_mailbox_domains $relay_recipient_maps $relay_domains
$canonical_maps $sender_canonical_maps $recipient_canonical_maps
$relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps
smtpd_sender_restrictions = check_sender_access
mysql:/etc/postfix/mysql-virtual_sender.cf
smtpd_client_restrictions = check_client_access
mysql:/etc/postfix/mysql-virtual_client.cf
maildrop_destination_concurrency_limit = 1
maildrop_destination_recipient_limit = 1
virtual_transport = dovecot
header_checks = regexp:/etc/postfix/header_checks
mime_header_checks = regexp:/etc/postfix/mime_header_checks
nested_header_checks = regexp:/etc/postfix/nested_header_checks
body_checks = regexp:/etc/postfix/body_checks
dovecot_destination_recipient_limit = 1
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
content_filter = amavis:[127.0.0.1]:10024
receive_override_options = no_address_mappings
message_size_limit = 0
#Mailman
owner_request_special = no
What am I doing wrong?
--
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] Problem with Mailman+Postfix
On 7/22/2011 4:32 AM, gigahe...@fettabernett.de wrote: Hi there. I´m using Postfix + Dovevot + Mailman on Debian Lenny with ISPConfig3 Setup. I´ve installed Mailman seperate from ISPConfig via apt-get, administrating lists works fine but there is one problem: Postfix does not accept incoming mails to the mailing list. mail.info: Jul 22 10:53:13 atom-29 postfix/smtpd[12620]: NOQUEUE: reject: RCPT from mailout-de.gmx.net[213.165.64.22]: 550 5.1.1 t...@xyz.net: Recipient address rejected: User unknown in virtual mailbox table; from=a...@gmx.de to=t...@xyz.net proto=SMTP helo=mailout-de.gmx.net main.cf of Postfix: [...] alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases [...] virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf [...] What am I doing wrong? 'postconf -n' is generally more useful than main.cf. It appears the problem is that your list domain is a virtual mailbox domain, but you have no virtual mapping for the list addresses. If that is indeed the problem, you need to add hash:/var/lib/mailman/data/virtual-mailman to virtual_alias_maps in main.cf. You also need to put your list domaian (xyz.net) in POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py as in POSTFIX_STYLE_VIRTUAL_DOMAINS = ['xyz.net'] and run Mailman's bin/genaliases to generate virtual-mailman. Also, you should not have hash:/var/lib/mailman/data/aliases because it will cause Postfix's newaliases command to rebuild hash:/var/lib/mailman/data/aliases.db which may adversely affect the owner:group of this file. -- 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] problem with mailman handling incomming mail
Mark Sapiro a écrit : On 6/2/11 8:13 AM, Maxime Longuepee wrote: Here is the output of postconf -n: [...] virtual_alias_maps = mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/aliases This is wrong. You need to add hash:/usr/local/mailman/data/aliases to alias_maps, not to virtual_alias_maps. Probably something like alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases Then you need virtual_alias_maps = mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/virtual-mailman and if it isn't already there, you need POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org'] in mm_cfg.py, and if that wasn't already there, you need to run Mailman's bin/genaliases to create the virtual-mailman* files. Hi Mark, Thanks a lot, it's working perfectly!!! Now, if I want to add a mailing list with another domain name i own (it's hosted on the same machine), what should i do? I tryed to add a new mailing list specifying the domain name with /usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org I can access the administration page over the web interface but when i send an email to that address, i get an error (here is the postfix log): postfix/smtpd[94206]: NOQUEUE: reject: RCPT from myhome.org[MY.IP]: 550 5.1.1 name-of-the-list @myotherdomain.org: Recipient address rejected: User unknown in virtual mailbox table; from=m...@email.com to=name-of-the-list??@myotherdomain.org proto=ESMTP helo=[MY.IP] Thanks a lot in advance for helping me! -- Maxime Longuepee -- 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] problem with mailman handling incomming mail
On 6/4/11 6:30 AM, Maxime Longuepee wrote:
Now, if I want to add a mailing list with another domain name i own
(it's hosted on the same machine), what should i do? I tryed to add a
new mailing list specifying the domain name with
/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org
I can access the administration page over the web interface but when i
send an email to that address, i get an error (here is the postfix log):
postfix/smtpd[94206]: NOQUEUE: reject: RCPT from myhome.org[MY.IP]: 550
5.1.1 name-of-the-list @myotherdomain.org: Recipient address
rejected: User unknown in virtual mailbox table; from=m...@email.com
to=name-of-the-list??@myotherdomain.org proto=ESMTP helo=[MY.IP]
You need to add
add_virtualhost('myotherdomain.org', 'myotherdomain.org')
to mm_cfg.py and add the domain to POSTFIX_STYLE_VIRTUAL_DOMAINS as in
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']
This assumes the web domain is the same myotherdomain.org as the email
domain. If not, the only difference is add_virtualhost is
add_virtualhost('myotherwebdomain.org', 'myotherdomain.org')
After adding 'myotherdomain.org' to POSTFIX_STYLE_VIRTUAL_DOMAINS, run
bin/genaliases to update data/virtual-mailman*
Also not that the notation
/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org
is deprecated and doesn't do the intuitive thing (but does the right
thing if the web domain and email domain are the same). See
/usr/local/mailman/bin/newlist --help
--
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] problem with mailman handling incomming mail
Mark Sapiro a écrit :
On 6/4/11 6:30 AM, Maxime Longuepee wrote:
Now, if I want to add a mailing list with another domain name i own
(it's hosted on the same machine), what should i do? I tryed to add a
new mailing list specifying the domain name with
/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org
I can access the administration page over the web interface but when i
send an email to that address, i get an error (here is the postfix log):
postfix/smtpd[94206]: NOQUEUE: reject: RCPT from myhome.org[MY.IP]: 550
5.1.1 name-of-the-list @myotherdomain.org: Recipient address
rejected: User unknown in virtual mailbox table; from=m...@email.com
to=name-of-the-list??@myotherdomain.org proto=ESMTP helo=[MY.IP]
You need to add
add_virtualhost('myotherdomain.org', 'myotherdomain.org')
to mm_cfg.py and add the domain to POSTFIX_STYLE_VIRTUAL_DOMAINS as in
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']
This assumes the web domain is the same myotherdomain.org as the email
domain. If not, the only difference is add_virtualhost is
add_virtualhost('myotherwebdomain.org', 'myotherdomain.org')
After adding 'myotherdomain.org' to POSTFIX_STYLE_VIRTUAL_DOMAINS, run
bin/genaliases to update data/virtual-mailman*
Also not that the notation
/usr/local/mailman/bin/newlist name-of-the-l...@myotherdomain.org
is deprecated and doesn't do the intuitive thing (but does the right
thing if the web domain and email domain are the same). See
/usr/local/mailman/bin/newlist --help
Hi Mark!
I tryed what you said and it's not working.. I have this error:
postfix/smtpd[99110]: NOQUEUE: reject: RCPT from myhome.org[MY.HOME.IP]:
550 5.1.1 test-l...@myotherdomain.org: Recipient address rejected:
User unknown in virtual mailbox table; from=m...@email.com
to=test-l...@myotherdomain.org proto=ESMTP helo=[MY.HOME.IP]
Mailman was originally configured with mydomain.org which still works
well. The web domain i use to manage mailman is webmail.mydomain.org.
The other domain i'm trying to add is myotherdomain.org and following
your advices it didn't worked.
So, I did that in mm_cfg.py:
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']
add_virtualhost('myotherdomain.org')
Then, I ran genaliases and also restarted mailman. I added the list
test-list for myotherdomain.org with: /usr/local/mailman/bin/newlist
--urlhost=webmail.mydomain.org --emailhost=myotherdomain.org test-list
and it doesn't work :|
What did I do wrong?
--
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] problem with mailman handling incomming mail
Maxime Longuepee wrote:
I tryed what you said and it's not working.. I have this error:
postfix/smtpd[99110]: NOQUEUE: reject: RCPT from myhome.org[MY.HOME.IP]:
550 5.1.1 test-l...@myotherdomain.org: Recipient address rejected:
User unknown in virtual mailbox table; from=m...@email.com
to=test-l...@myotherdomain.org proto=ESMTP helo=[MY.HOME.IP]
Mailman was originally configured with mydomain.org which still works
well. The web domain i use to manage mailman is webmail.mydomain.org.
The other domain i'm trying to add is myotherdomain.org and following
your advices it didn't worked.
So, I did that in mm_cfg.py:
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org', 'myotherdomain.org']
add_virtualhost('myotherdomain.org')
Then, I ran genaliases and also restarted mailman. I added the list
test-list for myotherdomain.org with: /usr/local/mailman/bin/newlist
--urlhost=webmail.mydomain.org --emailhost=myotherdomain.org test-list
If you want all lists to use the same web host (webmail.mydomain.org)
and only different email domains, you do not want an add_virtualhost()
for the other domains.
You want
DEFAULT_URL_HOST = 'webmail.mydomain.org'
DEFAULT_EMAIL_HOST = 'mail.mydomain.org'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org',
'myotherdomain.org']
However, the
add_virtualhost('myotherdomain.org')
doesn't really do any harm. So I don't understand what the problem is.
The newlist command you gave should have created the list with a
host_name attribute (visible on the list's General Options page) of
myotherdomain.org, and if that domain was in
POSTFIX_STYLE_VIRTUAL_DOMAINS when the list was created, the required
virtual maps should have been added to data/virtual-mailman.
So, what is the host_name for test-list?
Does it match exactly a domain in POSTFIX_STYLE_VIRTUAL_DOMAINS in
mm_cfg.py?
Is there only one POSTFIX_STYLE_VIRTUAL_DOMAINS assignment in mm_cfg.py?
What's in data/virtual-mailman?
is the time stamp of data/virtual-mailman.db the same or more recent
than that of data/virtual-mailman?
--
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] problem with mailman handling incomming mail
Hi! I have mailman installed on my freebsd server. I am running postfix+dovecot with mysql support for my mail server. Everything is working perfectly except mailman gives error on incomming mail. Here is the error (I replaced my real domain name in the error message with mydomain.org): *This is the mail system at host mail.mydomain.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 |/usr/local/mailman/mail/mailman post mailman@mail.mydomain.org (expanded from mail...@mail.mydomain.org): unknown user: |/usr/local/mailman/mail/mailman post mailman* Can someone help me please!! -- Maxime Longuepee -- 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] problem with mailman handling incomming mail
On 6/1/11 6:50 AM, Maxime Longuepee wrote: The mail system |/usr/local/mailman/mail/mailman post mailman@mail.mydomain.org (expanded from mail...@mail.mydomain.org): unknown user: |/usr/local/mailman/mail/mailman post mailman* Postfix is apparently trying to deliver to the alias via a transport that doesn't do pipe delivery, i.e. some transport other than 'local'. We need to see the output from 'postconf -n' to say more. -- 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] problem with mailman handling incomming mail
Hi Mark! Thanks for your reply! Here is the output of postconf -n: address_verify_map = btree:/var/spool/postfix/address_verify broken_sasl_auth_clients = yes command_directory = /usr/local/sbin config_directory = /usr/local/etc/postfix daemon_directory = /usr/local/libexec/postfix data_directory = /var/spool/postfix debug_peer_level = 2 disable_vrfy_command = yes html_directory = no inet_interfaces = $myhostname, localhost invalid_hostname_reject_code = 450 mail_owner = postfix mailq_path = /usr/local/bin/mailq manpage_directory = /usr/local/man maps_rbl_reject_code = 450 mydestination = mail.mydomain.org, localhost.mydomain.org, localhost, mail myhostname = mail.mydomain.org mynetworks = 127.0.0.1, mail.mydomain.org mynetworks_style = host myorigin = mail.mydomain.org newaliases_path = /usr/local/bin/newaliases non_fqdn_reject_code = 450 owner_request_special = no queue_directory = /var/spool/postfix readme_directory = no recipient_delimiter = + sample_directory = /usr/local/etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = maildrop smtp_tls_cert_file = /etc/ssl/server.crt smtp_tls_key_file = /etc/ssl/server.key smtp_tls_security_level = may smtp_tls_session_cache_database = btree:/var/spool/postfix/smtp_tls_session_cache smtpd_data_restrictions = reject_unauth_pipelining, reject_multi_recipient_bounce,permit smtpd_helo_required = yes smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticatedpermit_tls_clientcerts reject_unauth_destinationreject_invalid_helo_hostname reject_non_fqdn_senderreject_non_fqdn_recipient reject_rbl_client cbl.abuseat.orgreject_rbl_client list.dsbl.org reject_rbl_client opm.blitzed.orgreject_rbl_client sbl.spamhaus.orgreject_rbl_client bl.spamcop.net reject_rbl_client dnsbl.sorbs.net=127.0.0.2reject_rbl_client dnsbl.sorbs.net=127.0.0.3reject_rbl_client dnsbl.sorbs.net=127.0.0.4reject_rbl_client dnsbl.sorbs.net=127.0.0.5reject_rbl_client dnsbl.sorbs.net=127.0.0.7reject_rbl_client dnsbl.sorbs.net=127.0.0.9reject_rbl_client dnsbl.sorbs.net=127.0.0.11reject_rbl_client dnsbl.sorbs.net=127.0.0.12 smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_ask_ccert = yes smtpd_tls_cert_file = /etc/ssl/server.crt smtpd_tls_key_file = /etc/ssl/server.key smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_security_level = may smtpd_tls_session_cache_database = btree:/var/spool/postfix/smtpd_tls_session_cache tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/aliases virtual_gid_maps = static:6 virtual_mailbox_base = /usr/vmail virtual_mailbox_domains = mysql:$config_directory/mysql_virtual_domains_maps.cf virtual_mailbox_maps = mysql:$config_directory/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 143 virtual_transport = dovecot virtual_uid_maps = static:143 On Thu, 02 Jun 2011 07:40:43 -0700, Mark Sapiro m...@msapiro.net wrote: On 6/1/11 6:50 AM, Maxime Longuepee wrote: The mail system |/usr/local/mailman/mail/mailman post mailman@mail.mydomain.org (expanded from mail...@mail.mydomain.org): unknown user: |/usr/local/mailman/mail/mailman post mailman* Postfix is apparently trying to deliver to the alias via a transport that doesn't do pipe delivery, i.e. some transport other than 'local'. We need to see the output from 'postconf -n' to say more. -- 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] problem with mailman handling incomming mail
On 6/2/11 8:13 AM, Maxime Longuepee wrote: Here is the output of postconf -n: [...] virtual_alias_maps = mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/aliases This is wrong. You need to add hash:/usr/local/mailman/data/aliases to alias_maps, not to virtual_alias_maps. Probably something like alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases Then you need virtual_alias_maps = mysql:$config_directory/mysql_virtual_alias_maps.cf,hash:/usr/local/mailman/data/virtual-mailman and if it isn't already there, you need POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.mydomain.org'] in mm_cfg.py, and if that wasn't already there, you need to run Mailman's bin/genaliases to create the virtual-mailman* files. -- 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] Problem migration mailman
Hi I am configuring migrating from one server postfix with courier to a server with postfix and dovecot. I'm also trying to migrate the mailman who currently works in the postfix server I have the following configuration: myhostname = mail.dominio.com mydomain = dominio.com myorigin = $mydomain mydestination = localhost, $myhostname relayhost = mynetworks = 127.0.0.0/8, 192.168.0.0/16 10.1.4.0/24 201.90.175.48/28, 10.0.0.0/24 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all # for mailman owner_request_special = no recipient_delimiter = + alias_maps = hash:/var/lib/mailman/data/aliases virtual_alias_maps = mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf, hash:/var/lib/mailman/data/virtual-mailman virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_transport = dovecot virtual_mailbox_base = /mnt/maildir virtual_uid_maps = static:1001 virtual_gid_maps = static:1001 I copied the directories of the mailman date, archives and lists the current server to the new facility and issued the following commands # cd /var/lib/mailman # bin/genaliases # bin/withlist -a -l -r fix_url with that lists the current server appear in the web interface and command execution bin/list_lists but when I try to send an email to the list in the logs of postfix and get a bounce message user unknown Att. __ Faça ligações para outros computadores com o novo Yahoo! Messenger http://br.beta.messenger.yahoo.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
Re: [Mailman-Users] Problem migration mailman
Ricardo Barbosa wrote: I am configuring migrating from one server postfix with courier to a server with postfix and dovecot. I'm also trying to migrate the mailman who currently works in the postfix server I have the following configuration: courier/dovecot should make no difference: [...] alias_maps = hash:/var/lib/mailman/data/aliases virtual_alias_maps = mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf, hash:/var/lib/mailman/data/virtual-mailman virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_transport = dovecot virtual_mailbox_base = /mnt/maildir virtual_uid_maps = static:1001 virtual_gid_maps = static:1001 Did this configuration work on the old server? It appears to be missing virtual_alias_domains for the Mailman domains. I copied the directories of the mailman date, archives and lists the current server to the new facility and issued the following commands # cd /var/lib/mailman # bin/genaliases # bin/withlist -a -l -r fix_url If you have multiple virtual hosts, the above withlist/fix_url is not appropriate as it will put every list in the DEFAULT_URL_HOST/DEFAULT_EMAIL_HOST domain. Also, whatever fix_url is necessary needs to be done before genaliases. with that lists the current server appear in the web interface and command execution bin/list_lists but when I try to send an email to the list in the logs of postfix and get a bounce message user unknown If you need more help, post the contents of mm_cfg.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 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] Problem migration mailman
following my main.cf file server in production --- main.cf -- myorigin = /etc/mailname myhostname = mail.dominio.com mydestination = localhost, localhost.localdomain, mail.dominio.com, dominio.com best_mx_transport = virtual relayhost = mynetworks = 127.0.0.0/8, 192.168.0.0/16 10.1.4.0/24 smtpd_banner = $myhostname ESMTP $mail_name bounce_template_file = /etc/postfix/bounce.cf biff = no append_dot_mydomain = no smtpd_use_tls = no inet_interfaces = all alias_maps = hash:/var/lib/mailman/data/aliases alias_database = # Para mailman owner_request_special = no virtual_alias_domains = virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf, hash:/var/lib/mailman/data/virtual-mailman virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf virtual_mailbox_limit_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailbox_limit_maps.cf virtual_mailbox_base = /mnt/maildir virtual_uid_maps = static:1000 virtual_gid_maps = static:1000 virtual_create_maildirsize = yes virtual_mailbox_extended = yes virtual_mailbox_limit_override = yes virtual_mailbox_limit_inbox = yes virtual_mailbox_lock = fcntl, dotlock virtual_maildir_limit_message = Caixa de e-mail lotada. virtual_overquota_bounce = yes home_mailbox = Maildir/ message_size_limit =500 recipient_delimiter = + maildrop_destination_recipient_limit = 1 smtpd_sasl_local_domain = $mydomain smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtp_destination_recipient_limit = 100 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, permit smtp_generic_maps = hash:/etc/postfix/generic --- mm_cfg.py This is the module which takes your site-specific settings. From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example. from Defaults import * MAILMAN_SITE_LIST = 'mailman' DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/' PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private' IMAGE_LOGOS = '/images/mailman/' DEFAULT_EMAIL_HOST = 'dominio.com' DEFAULT_URL_HOST = 'mail.dominio.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_SERVER_LANGUAGE = 'pt_BR' USE_ENVELOPE_SENDER = 0 # Still used? DEFAULT_SEND_REMINDERS = 0 MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dominio.com'] OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes DEFAULT_ARCHIVE = Off Att. Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.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
Re: [Mailman-Users] Problem migration mailman
On 3/25/2010 12:30 PM, Ricardo Barbosa wrote: following my main.cf file server in production Generally, the output from postconf -n is preferable to posting the entire main.cf. [...] virtual_alias_domains = This needs to be virtual_alias_domains = dominio.com If that conflicts with virtual_mailbox_domains, you'll have to find some other way to handle this, perhaps by taking this question to one of the lists at http://www.postfix.org/lists.html, possibly http://listas.softwarelivre.org/mailman/listinfo/postfix-br/ [...] DEFAULT_EMAIL_HOST = 'dominio.com' DEFAULT_URL_HOST = 'mail.dominio.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) [...] MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dominio.com'] These settings look good. -- 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] problem with mailman list
Hello, We have a problem with our 'mailman' list http://listserv.enar-eu.org/mailman/admindb/board+subs I would like to accept for the mailing list that are still pending but every time I want to do so, I come onto a page which says: Bug in Mailman version 2.1.8b1 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Could you please solve the problem? Thanks in advance for your help. Best regards, Georgina Siklossy Communication and Press Officer ENAR, European Network Against Racism 43 Rue de la Charité B-1210 Brussels Tel: +32 (0)2 229 35 77 Fax: +32 (0)2 229 35 75 Email: georg...@enar-eu.org mailto:georg...@enar-eu.org Visit ENAR's website @ www.enar-eu.org http://www.enar-eu.org/ -- 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] problem with mailman list
Georgina Siklossy wrote: We have a problem with our 'mailman' list http://listserv.enar-eu.org/mailman/admindb/board+subs I would like to accept for the mailing list that are still pending but every time I want to do so, I come onto a page which says: Bug in Mailman version 2.1.8b1 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. Could you please solve the problem? First of all, this is the first beta release of Mailman 2.1.8. It would be advisable to update to a final release. The current release is 2.1.12. As far as the Bug is concerned, we need to see the full traceback from Mailman's error log to be able to help. -- 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] problem with mailman list
On Fri, May 29, 2009 at 02:35:07PM +0200, Georgina Siklossy wrote: We have a problem with our 'mailman' list http://listserv.enar-eu.org/mailman/admindb/board+subs I would like to accept for the mailing list that are still pending but every time I want to do so, I come onto a page which says: Bug in Mailman version 2.1.8b1 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. So, have you asked the site's webmaster/list-manager to extract the information from the error logs? Without that info, we/he's not going to get very far. Armed with the trackback, we may be able to help a bit more, or the same error may be in this list's archive. -- ``What is a committee? A group of the unwilling, picked from the unfit, to do the unnecessary.'' (Richard Harkness) -- 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] Problem with mailman install
LuKreme wrote: On 17-May-2009, at 19:29, Mark Sapiro wrote: See the FAQ at http://wiki.list.org/x/tYA9 to understand more about this error. My confusion about the error is that mailman has ALWAYS been setu for uid/gid mailman, and has been for years and years. Yes, and the mail/mailman wrapper is group mailman and SETGID so that the pipe invoked by the MTA actually runs as effective group mailman and has appropriate access. However, the MTA invokes the pipe as some user:group determined by the MTA which may or may not be mailman. In order to provide some security against just anyone with shell access being able to run the wrapper from the command line, upon invocation the wrapper checks the original group with which the MTA invoked the wrapper, and if it is not the group the wrapper expects, the wrapper issues the group mismatch error. This is all explained in more detail in the FAQ. -- 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] Problem with mailman install
On 18-May-2009, at 08:35, Mark Sapiro wrote: In order to provide some security against just anyone with shell access being able to run the wrapper from the command line, upon invocation the wrapper checks the original group with which the MTA invoked the wrapper, and if it is not the group the wrapper expects, the wrapper issues the group mismatch error. This is all explained in more detail in the FAQ. Yes, but the MTA did not change. Recompiling mailman via ports with the same options it had been compiled with before failed (WITH_MAIL_GID=mailman). Restoring from backup (which files are gid mailman) worked. Same permissions on the mailman executable: 14 -rwxr-sr-x 1 root mailman 13661 Jun 8 2007 mail/mailman -- There is a road, no simple highway, between the dawn and the dark of night -- 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] Problem with mailman install
LuKreme wrote: Yes, but the MTA did not change. Recompiling mailman via ports with the same options it had been compiled with before failed (WITH_MAIL_GID=mailman). Restoring from backup (which files are gid mailman) worked. Same permissions on the mailman executable: And the group mismatch error you reported at the start of this thread said Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group nobody. Indicating that yes, the wrapper was compiled WITH_MAIL_GID=mailman, but it should have been compiled WITH_MAIL_GID=nobody. This has nothing to do with the gid of the files. It has to do only with the gid with which the MTA invokes the wrapper. -- 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] Problem with mailman install
I have had mailman running for many years now, and have updated it semi regularly over the years (currently 2.1.9). A few days ago, I tried to post a message to a list I host and got: Command died with status 4: /usr/local/mailman/mail/mailman post listname. Command output: No such file or directory I went in and tried to look at the install, but everything appeared to be fine. So I tried to reinstall via portupgrade mailman. After the upgrade completed, I got this error: Command died with status 2: /usr/local/mailman/mail/mailman post gfamily. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group nobody. This is odd since my current install of mailman has permissions like this: So I tried $ export MM_USERNAME=nobody $ export MM_GROUPNAME=nobody $ export MM_USERID=65534 and made sure that in pkgtools.conf I had 'mail/mailman' = 'WITH_MAIL_GID=nobody', and ran the port install again, only to get the same error. At each step I ran bin/check_perms and nothing was wrong. Finally I just went into my backups and restored /usr/local/mailman with a cp -rp and now everything works (except ports thinks I have version 2.1.11) So, for future reference, what SHOULD I have done? And does anyone know how to tell ports I have 2.1.9 instead of 2.1.11? -- Do not meddle in the affairs of Dragons for you are crunchy and taste good with ketchup -- 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] Problem with mailman install
[oops, left something out] This is odd since my current install of mailman has permissions like this: 8 -rwxr-xr-x 1 rootmailman 7622 Jun 8 2007 add_members 6 -rwxr-xr-x 1 rootmailman 6008 Jun 8 2007 arch 4 -rwxr-xr-x 1 rootmailman 2569 Jun 8 2007 b4b5-archfix mailman was compiled on my system with GID mailman, but trying to setup 2.1.11 with the same build options fails, so assuming I upgrade at some point, how do I get this to work? -- Do not meddle in the affairs of Dragons for you are crunchy and taste good with ketchup -- 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] Problem with mailman install
LuKreme wrote: A few days ago, I tried to post a message to a list I host and got: Command died with status 4: /usr/local/mailman/mail/mailman post listname. Command output: No such file or directory status 4 means the execve that runs python returned. The no such file or directory can refer to either /usr/local/mailman/mail/mailman or to the path to Python that the mail wrapper is using. I went in and tried to look at the install, but everything appeared to be fine. So I tried to reinstall via portupgrade mailman. After the upgrade completed, I got this error: Command died with status 2: /usr/local/mailman/mail/mailman post gfamily. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group nobody. This is odd since my current install of mailman has permissions like this: See the FAQ at http://wiki.list.org/x/tYA9 to understand more about this error. So I tried $ export MM_USERNAME=nobody $ export MM_GROUPNAME=nobody $ export MM_USERID=65534 and made sure that in pkgtools.conf I had 'mail/mailman' = 'WITH_MAIL_GID=nobody', and ran the port install again, only to get the same error. At each step I ran bin/check_perms and nothing was wrong. I can't help you much with all this package specific stuff. You might be better off asking for help using resources specific to the package you are installing. My guess is that the 'WITH_MAIL_GID=nobody' change should have fixed the group mismatch problem, particularly if the prior setting was 'WITH_MAIL_GID=mailman'. Possibly the environment changes messed this up somehow. Finally I just went into my backups and restored /usr/local/mailman with a cp -rp and now everything works (except ports thinks I have version 2.1.11) So, for future reference, what SHOULD I have done? And does anyone know how to tell ports I have 2.1.9 instead of 2.1.11? If you have a file named last_mailman_version in Mailman's data/ directory, it probably has contents 0x2010bf0 If so, change the contents to 0x20109f0 I don't know what you SHOULD have done to fix the original problem, since I don't know what the underlying cause was. -- 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] Problem with mailman install
On 17-May-2009, at 19:29, Mark Sapiro wrote: status 4: /usr/local/mailman/mail/mailman post listname. Command output: No such file or directory status 4 means the execve that runs python returned. The no such file or directory can refer to either /usr/local/mailman/mail/mailman or to the path to Python that the mail wrapper is using. Very odd, the path was there, the executable was there, permissions where right, and python appeared to be running. I certainly didn't do anything to change python's settings either before or after. See the FAQ at http://wiki.list.org/x/tYA9 to understand more about this error. My confusion about the error is that mailman has ALWAYS been setu for uid/gid mailman, and has been for years and years. If you have a file named last_mailman_version in Mailman's data/ directory, it probably has contents 0x2010bf0 If so, change the contents to 0x20109f0 That file has the right info, it's just the ports DB that is off since I replaced the install from backups 'behind its back'. -- What are you, Ghouls? There are no dead students here. This week. -- 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] problem with mailman and postfix
Hi all! I have a problem. When i send a email to my mailing list, i always got this error: *Oct 27 22:48:13 kim postfix/smtpd[10355]: connect from col0-omc2-s9.col0.hotmail.com[65.55.34.83] Oct 27 22:48:14 kim postfix/smtpd[10355]: NOQUEUE: reject: RCPT from col0-omc2-s9.col0.hotmail.com[65.55.34.83]: 554 5.7.1 [EMAIL PROTECTED]: Relay access denied; from= [EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo= col0-omc2-s9.col0.hotmail.com *How i can repair this? Here is my postfix config: # # ispCP ω (OMEGA) a Virtual Hosting Control System # # @copyright2001-2006 by moleSoftware GmbH # @copyright2006-2008 by ispCP | http://isp-control.net # @versionSVN: $ID$ # @linkhttp://isp-control.net # @authorispCP Team # # @license # This program is free software; you can redistribute it and/or modify it under # the terms of the MPL General Public License as published by the Free Software # Foundation; either version 1.1 of the License, or (at your option) any later # version. # You should have received a copy of the MPL Mozilla Public License along with # this program; if not, write to the Open Source Initiative (OSI) # http://opensource.org | [EMAIL PROTECTED] # # Postfix directory settings; These are critical for normal Postfix MTA functionallity command_directory= /usr/sbin daemon_directory = /usr/lib/postfix # Some common configuration parameters mynetworks_style = host myhostname = kim.v-info.info mydomain = $myhostname smtpd_banner = $myhostname ESMTP ispCP 1.0.0 RC6 OMEGA Managed setgid_group = postdrop # Receiving messages parameters mydestination = $myhostname, $mydomain append_dot_mydomain = no append_at_myorigin = yes local_transport = local virtual_transport= virtual transport_maps = hash:/etc/postfix/ispcp/transport alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases # Delivering local messages parameters mail_spool_directory = /var/mail # Mailboxquota # = 0 for unlimited # = 104857600 for 100 MB mailbox_size_limit = 0 mailbox_command = procmail -a $EXTENSION # Message size limit # = 0 for unlimited # = 104857600 for 100 MB message_size_limit = 0 biff = no recipient_delimiter = + local_destination_recipient_limit = 1 local_recipient_maps = unix:passwd.byname $alias_maps # ispCP Autoresponder parameters ispcp-arpl_destination_recipient_limit = 1 # Delivering virtual messages parameters virtual_mailbox_base = /var/mail/virtual virtual_mailbox_limit= 0 virtual_mailbox_domains = hash:/etc/postfix/ispcp/domains virtual_mailbox_maps = hash:/etc/postfix/ispcp/mailboxes virtual_alias_maps = hash:/etc/postfix/ispcp/aliases, hash:/var/lib/mailman/data/virtual-mailman virtual_minimum_uid = 1004 virtual_uid_maps = static:1004 virtual_gid_maps = static:8 # SASL paramters smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = broken_sasl_auth_clients = yes smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname smtpd_sender_restrictions= reject_non_fqdn_sender, reject_unknown_sender_domain, permit_mynetworks, permit_sasl_authenticated smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:12525, check_policy_service inet:127.0.0.1:6, permit smtpd_data_restrictions = reject_multi_recipient_bounce, reject_unauth_pipelining # TLS parameters; activate, if avaible/used #smtpd_use_tls = yes #smtpd_tls_loglevel = 2 #smtpd_tls_cert_file = /etc/postfix/cert.pem #smtpd_tls_key_file = /etc/postfix/privkey.pem #smtpd_tls_auth_only = no #smtpd_tls_received_header = yes # AMaViS parameters; activate, if available/used #content_filter = amavis:[127.0.0.1]:10024 # Quota support; activate, if available/used #virtual_create_maildirsize
Re: [Mailman-Users] problem with mailman and postfix
William Lebel wrote: I have a problem. When i send a email to my mailing list, i always got this error: *Oct 27 22:48:13 kim postfix/smtpd[10355]: connect from col0-omc2-s9.col0.hotmail.com[65.55.34.83] Oct 27 22:48:14 kim postfix/smtpd[10355]: NOQUEUE: reject: RCPT from col0-omc2-s9.col0.hotmail.com[65.55.34.83]: 554 5.7.1 [EMAIL PROTECTED]: Relay access denied; from= [EMAIL PROTECTED] to=[EMAIL PROTECTED] proto=ESMTP helo= col0-omc2-s9.col0.hotmail.com *How i can repair this? I think virtual_alias_domains = virtual-info.eu in your Postfix config will do it. -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: OK, now I understand what you are asking. I restarted mailman and let it run for several minutes with no error in /var/log/mailman/error. Then I submitted a help to -request. That is when the error occurred. I suppose it might mot be the help request per se but rather anything that causes mailman to do something. I tried to run a couple of other commands and they all do the same thing. I am reluctant to actually send a test to the list out of fear it might destroy something and make matters worse. Here is the traceback. Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 580, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 632, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 664, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 61, in __init__ self.lock() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 77, in lock self.lockfile.lock() File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock self.__write() File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) SHUNTING: 1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212 ArchRunner is trying to archive a message it found in qfiles/archive/. It has encountered the lock permission denied and moved the message to qfiles/shunt/1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212.pck What is the message (use bin/dumpdb or bin/show_qfiles to see it). Here is the process (shouldn't this be running as 'mailman'?): mail 5961 0.1 0.7 11100 7356 ?R17:28 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s How are you starting Mailman. Are you running bin/mailmanctl as root or starting it as a 'service' as root? If so, it should be setting the uid and gid of itself and the runners as those of MAILMAN_USER and MAILMAN_GROUP from Defaults.py/mm_cfg.py and supplemental groups as those associated with MAILMAN_USER. So, if I understand your configuration, MAILMAN_USER:MAILMAN_GROUP are mailman:mail. If that's correct, I would expect the runners to be running as user 'mailman'. That may be the cause of the permissions error. -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
Mark Sapiro wrote: OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. If the files are 755, that's OK, but they aren't executable so they really should be 644. Sorry. They are indeed 644. Brain was out to lunch. Yes, that's why I said (was). However, if CommandRunner is now 2773, it is likely that 2771 is another runner and was at the time. In any case, 2771 was the pid of the process that tried to create the lock. I asked, because I don't believe that the IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' error came from your 'help' command mailed to -request. In any case, where did this error come from?. If it is in Mailman's error log, there should also be a traceback. What is that? OK, now I understand what you are asking. I restarted mailman and let it run for several minutes with no error in /var/log/mailman/error. Then I submitted a help to -request. That is when the error occurred. I suppose it might mot be the help request per se but rather anything that causes mailman to do something. I tried to run a couple of other commands and they all do the same thing. I am reluctant to actually send a test to the list out of fear it might destroy something and make matters worse. Here is the traceback. Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 580, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 632, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 664, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 61, in __init__ self.lock() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 77, in lock self.lockfile.lock() File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock self.__write() File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) SHUNTING: 1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212 Here is the process (shouldn't this be running as 'mailman'?): mail 5961 0.1 0.7 11100 7356 ?R17:28 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s Thanks for your patience and continued help. signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature -- 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] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? signature.asc Description: OpenPGP digital signature -- 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If= archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Then that wasn't the problem. Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. If the files are 755, that's OK, but they aren't executable so they really should be 644. And yes, the contents of archives/public are symlinks (the permissions of which are irrelevant). That's so archives can be changed from public to private and vice versa by just removing/creating symlinks. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? Yes, that's why I said (was). However, if CommandRunner is now 2773, it is likely that 2771 is another runner and was at the time. In any case, 2771 was the pid of the process that tried to create the lock. I asked, because I don't believe that the IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' error came from your 'help' command mailed to -request. In any case, where did this error come from?. If it is in Mailman's error log, there should also be a traceback. What is that? -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
signature.asc Description: OpenPGP digital signature -- 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] Problem Migrating Mailman to New Server
That advanced the ball. The problem was that the mailman's primay group was mailman (Mandriva automagically creates a primary group for each user with the same name as the user name, that has been a problem more than once). I changed the primary group to mail. Thanks. However, I am now getting permission denied errors on the database folders. IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' I ran check_perms and all is OK. This has always been about ownership/permissions but I question why check_perms doesn't/won't fix it. What is it supposed to be? FWIW, the owner:group for /usr/lib/mailman and /var/lib/mailman trees is mailman:mail. I should also note that the command (it was just a help command to req) did work but I did not want to try actually mailing something to a list until this is all fixed. Thanks again for your help and my ISP seems to be accepting email from the python.org domain again. Mark Sapiro wrote: Where are your aliases? The mail wrapper is compiled to to expect to be invoked by the 'mail' group. Postfix will invoke the wrapper as the user and that user's primary group corresponding to the owner of the aliases.db file in which the pipe command was found. I.e., if the aliases.db file is userx:groupy, postfix will invoke the wrapper as userx:groupx where groupx is userx's primary group. -- Mark Sapiro mark at msapiro.net http://mail.python.org/mailman/listinfo/mailman-usersThe 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: However, I am now getting permission denied errors on the database folders. IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' I ran check_perms and all is OK. This has always been about ownership/permissions but I question why check_perms doesn't/won't fix it. What is it supposed to be? Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. FWIW, the owner:group for /usr/lib/mailman and /var/lib/mailman trees is mailman:mail. I should also note that the command (it was just a help command to req) did work but I did not want to try actually mailing something to a list until this is all fixed. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Dennis Putnam wrote: Mark Sapiro wrote: Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. OK, now we are making progress. Thanks. I can indeed see the list if I supply the list name in the link like you suggested. I guess that means the scriptalias is correct so the question now becomes, why do they not show up on the admin or listinfo links? Does this also mean if I start mailman it will work in spite of the incorrect web interface? Yes, Mailman will probably work if you start it as long as aliases or whatever is required for mail delivery to the list are in place. As far as lists missing from the listinfo overview, we are back to the FAQ at http://wiki.list.org/x/lYA9. Assuming the lists are public (Privacy options... - advertised = Yes), the list doesn't appear on the overview because VIRTUAL_HOST_OVERVIEW = On (the default), and the host portion of the list's web_page_url attribute does not exactly match the host portion of the URL used to access the page. Perhaps you had VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py on the old server and didn't carry it over. Or, perhaps you changed it in Defaults.py on the old server; if so, this is why you shouldn't do that. I'm making some progress as the problems so far seem to be ownerhip and permissions since the copy had to be done as root. I could not find anything that tells me what the group and owner should be for each associated directory but I think I have them all set to mailman:mail. Now I am getting this error from postfix: status=bounced (Command died with status 2: /usr/lib/mailman/mail/mailman post mailman. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mail, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group mail, or re-run configure, providing the command line option `--with-mail-gid=mailman'. ) Oct 20 19:25:15 dap002 postfix/qmgr[27883]: 9D0D819835: removed Oct 20 19:25:20 dap002 postfix/smtp[28602]: 202FF19836: to=[EMAIL PROTECTED], relay=mail.bellsouth.net[207.115.11.17]:25, delay=6.8, delays=0.01/0.01/3.2/3.6, dsn=2.0.0, status=sent (250 ok ; id=20081020232532H05001u3qhe) Oct 20 19:25:20 dap002 postfix/qmgr[27883]: 202FF19836: removed I don't think I understand what to do at this point. Everything other then what I copied was set per the Mandriva installer. signature.asc Description: OpenPGP digital signature -- 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: I'm making some progress as the problems so far seem to be ownerhip and permissions since the copy had to be done as root. I could not find anything that tells me what the group and owner should be for each associated directory but I think I have them all set to mailman:mail. bin/check_perms will help. I don't think mailman:mail is correct. The user is not important, but the group should be Mailman's group (the setting for MAILMAN_GROUP in Defaults.py. Run bin/check_perms -f as root. That should make group and mode correct. Now I am getting this error from postfix: status=bounced (Command died with status 2: /usr/lib/mailman/mail/mailman post mailman. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mail, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group mail, or re-run configure, providing the command line option `--with-mail-gid=mailman'. ) See the FAQ at http://wiki.list.org/x/tYA9. I don't think I understand what to do at this point. Everything other then what I copied was set per the Mandriva installer. Where are your aliases? The mail wrapper is compiled to to expect to be invoked by the 'mail' group. Postfix will invoke the wrapper as the user and that user's primary group corresponding to the owner of the aliases.db file in which the pipe command was found. I.e., if the aliases.db file is userx:groupy, postfix will invoke the wrapper as userx:groupx where groupx is userx's primary group. -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. Thanks for the reply but I've already been there. That does not seem to be my problem. All the config files were copied from the working server as is (the mm_cfg.py file is correct). The new server has exactly the same hostname and IP address. The only (intentional) difference, other then the hardware, is the underlying OS (Mandriva Free 2007 Spring replacing Mandriva 2007). I suppose it is possible that this version of Mandriva put the Mailman files someplace different then the previous version (why it doesn't follow the standard is beyond me) but so far I have not found any other location with config files. I think Mailman needs a command that lists all the file paths it is using. signature.asc Description: OpenPGP digital signature -- 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. Thanks for the reply but I've already been there. That does not seem to be my problem. All the config files were copied from the working server as is (the mm_cfg.py file is correct). The new server has exactly the same hostname and IP address. The only (intentional) difference, other then the hardware, is the underlying OS (Mandriva Free 2007 Spring replacing Mandriva 2007). I suppose it is possible that this version of Mandriva put the Mailman files someplace different then the previous version (why it doesn't follow the standard is beyond me) but so far I have not found any other location with config files. I think Mailman needs a command that lists all the file paths it is using. grep PREFIX Mailman/Defaults.py You said bin/list_lists shows the lists, so presumably they are where they should be unless the web server is pointing at CGI wrappers from a different installation. Have you checked where the scriptalias in the web server points? Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: Mark Sapiro wrote: Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. OK, now we are making progress. Thanks. I can indeed see the list if I supply the list name in the link like you suggested. I guess that means the scriptalias is correct so the question now becomes, why do they not show up on the admin or listinfo links? Does this also mean if I start mailman it will work in spite of the incorrect web interface? Yes, Mailman will probably work if you start it as long as aliases or whatever is required for mail delivery to the list are in place. As far as lists missing from the listinfo overview, we are back to the FAQ at http://wiki.list.org/x/lYA9. Assuming the lists are public (Privacy options... - advertised = Yes), the list doesn't appear on the overview because VIRTUAL_HOST_OVERVIEW = On (the default), and the host portion of the list's web_page_url attribute does not exactly match the host portion of the URL used to access the page. Perhaps you had VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py on the old server and didn't carry it over. Or, perhaps you changed it in Defaults.py on the old server; if so, this is why you shouldn't do that. -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem Migrating Mailman to New Server
I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? I thought I just needed to do a simple copy of the /var/lib/mailman directory to the new server but perhaps there is more to it then that. TIA. signature.asc Description: OpenPGP digital signature -- 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] Problem Migrating Mailman to New Server
Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. -- Mark Sapiro [EMAIL PROTECTED]The 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] Problem With Mailman Migration
I've recently moved our mailman service to a different server. It appears to be working well in all regards but one. When I attempt to manage a list from the webpage interface on the correct server it sends me to the admin password authorization page on the old server. All lists constantly refer back to the old server for admin tasks. I have set the mm_cfg.py file properly with our new servers address (x.domain.tld), and have run withlist -l -r fix_url both in -a mode and individually on the various lists with no results. I also would like to know how to shutdown the old mailman admin web page. I have edited out the reference to mailman in httpd.conf and restarted the daemon with no success; there are no aliases to mailman in the httpd.conf file aside from what I edited. The server platform is Mac Server 10.4.11. Thank you for your help. -- Michael J Wise Technology Coordinator Thomas Jefferson School 4100 S. Lindbergh Blvd. St. Louis, MO 63127 (314)843-4152 x171 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem With Mailman Migration
Michael J Wise wrote: I've recently moved our mailman service to a different server. It appears to be working well in all regards but one. When I attempt to manage a list from the webpage interface on the correct server it sends me to the admin password authorization page on the old server. All lists constantly refer back to the old server for admin tasks. I have set the mm_cfg.py file properly with our new servers address (x.domain.tld), and have run withlist -l -r fix_url both in -a mode and individually on the various lists with no results. This is exactly the kind of thing that fix_url is supposed to fix. The fact that it doesn't indicates problems with your host settings in Defaults.py/mm_cfg.py What you want to start with in mm_cfg.py is (with your own host names of course) DEFAULT_URL_HOST = 'www.example.com' DEFAULT_EMAIL_HOST = 'example.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) If you don't have that, do that, restart Mailman and run fix_url again I also would like to know how to shutdown the old mailman admin web page. I have edited out the reference to mailman in httpd.conf and restarted the daemon with no success; there are no aliases to mailman in the httpd.conf file aside from what I edited. Then there is some non-obvious magic at work. If you don't have the ScriptAlias for Mailman in httpd.conf, how is httpd getting to those CGI scripts? You might get a clue from your httpd access_log. The server platform is Mac Server 10.4.11. Thank you for your help. Which I assume is still the Apple modified Mailman 2.1.5. Maybe these are Apple questions. -- Mark Sapiro [EMAIL PROTECTED]The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] : Problem Running mailman
Hi, I installed mailman and go for Check Installation phase as per mailman Installation Manual [EMAIL PROTECTED]:/usr/local/mailman$ bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 45, in module from Mailman import mm_cfg ImportError: cannot import name mm_cfg Regards Smita -- Forwarded message -- From: Mark Sapiro [EMAIL PROTECTED] Date: Oct 24, 2007 9:03 PM Subject: Re: [Mailman-Users] : Problem Running mailman To: QA Engg [EMAIL PROTECTED], Mailman-Users@python.org QA Engg wrote: I tried the procedure to install mailman from the Wikipedia and following errors [EMAIL PROTECTED]:~$ emerge -p mailman bash: emerge: command not found [...] You are trying to follow instructions for a package and perhaps even an OS which you do not have. [EMAIL PROTECTED]:~$ # groups mailman [EMAIL PROTECTED]:~$ cron mailman cron: can't open or create /var/run/crond.pid: Permission denied [EMAIL PROTECTED]:~$ # cd /usr/local/mailman/cron crontab -u mailman crontab.in [EMAIL PROTECTED]:~$ # su - mailman In 3 of the four lines, the '#' you typed is actually the 'root' shell prompt in the example you are copying. Thus you are typing comments, not commands. [EMAIL PROTECTED]:~$ $ cd /usr/local/mailman/cron bash: $: command not found Here and in the following you typed a '$' prompt as opposed to the '#' above so bash told you there is no '$' command. You need to get some help and instruction from somone who knows something about Unix/Linux. That is beyond the scope of the mailman-users@python.org list. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] : Problem Running mailman
QA Engg wrote: I installed mailman and go for Check Installation phase as per mailman Installation Manual [EMAIL PROTECTED]:/usr/local/mailman$ bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 45, in module from Mailman import mm_cfg ImportError: cannot import name mm_cfg Your installation was not successful. -- Forwarded message -- From: Mark Sapiro [EMAIL PROTECTED] Date: Oct 24, 2007 9:03 PM Subject: Re: [Mailman-Users] : Problem Running mailman To: QA Engg [EMAIL PROTECTED], Mailman-Users@python.org snip You need to get some help and instruction from somone who knows something about Unix/Linux. That is beyond the scope of the mailman-users@python.org list. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] : Problem Running mailman
QA Engg wrote: I tried the procedure to install mailman from the Wikipedia and following errors [EMAIL PROTECTED]:~$ emerge -p mailman bash: emerge: command not found [...] You are trying to follow instructions for a package and perhaps even an OS which you do not have. [EMAIL PROTECTED]:~$ # groups mailman [EMAIL PROTECTED]:~$ cron mailman cron: can't open or create /var/run/crond.pid: Permission denied [EMAIL PROTECTED]:~$ # cd /usr/local/mailman/cron crontab -u mailman crontab.in [EMAIL PROTECTED]:~$ # su - mailman In 3 of the four lines, the '#' you typed is actually the 'root' shell prompt in the example you are copying. Thus you are typing comments, not commands. [EMAIL PROTECTED]:~$ $ cd /usr/local/mailman/cron bash: $: command not found Here and in the following you typed a '$' prompt as opposed to the '#' above so bash told you there is no '$' command. You need to get some help and instruction from somone who knows something about Unix/Linux. That is beyond the scope of the mailman-users@python.org list. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] : Problem Running mailman
hi, I tried the procedure to install mailman from the Wikipedia and following errors [EMAIL PROTECTED]:~$ emerge -p mailman bash: emerge: command not found [EMAIL PROTECTED]:~$ emerge mailman bash: emerge: command not found [EMAIL PROTECTED]:~$ zless /usr/share/doc/mailman-$version/README.gentoo.gz gzip: /usr/share/doc/mailman-/README.gentoo.gz: No such file or directory /usr/share/doc/mailman-/README.gentoo.gz: No such file or directory [EMAIL PROTECTED]:~$ zless /usr/share/doc/mailman-2.1.9/README.gentoo.gz gzip: /usr/share/doc/mailman-2.1.9/README.gentoo.gz: No such file or directory /usr/share/doc/mailman-2.1.9/README.gentoo.gz: No such file or directory [EMAIL PROTECTED]:~$ ebuild /var/db/pkg/net-mail/mailman-2.1.9 /mailman-$VERSION.eb uild config bash: ebuild: command not found [EMAIL PROTECTED]:~$ # groups mailman [EMAIL PROTECTED]:~$ cron mailman cron: can't open or create /var/run/crond.pid: Permission denied [EMAIL PROTECTED]:~$ # cd /usr/local/mailman/cron crontab -u mailman crontab.in [EMAIL PROTECTED]:~$ # su - mailman [EMAIL PROTECTED]:~$ $ cd /usr/local/mailman/cron bash: $: command not found [EMAIL PROTECTED]:~$ $crontab crontab.in bash: crontab.in: command not found [EMAIL PROTECTED]:~$ $ cd .. bash: $: command not found [EMAIL PROTECTED]:~$ $ bin/mmsitepass bash: $: command not found [EMAIL PROTECTED]:~$ $ bin/newlist mailman bash: $: command not found [EMAIL PROTECTED]:~$ $ bin/config_list -i data/sitelist.cfg mailman bash: $: command not found [EMAIL PROTECTED]:~$ $ bin/check_perms -f bash: $: command not found [EMAIL PROTECTED]:~$ Regards Smita On 10/20/07, Mark Sapiro [EMAIL PROTECTED] wrote: QA Engg wrote: 2.2 Create the Installatio Directory 1. You cannot install Mailman on a filesystem that is mounted with the nosuid option not gettting the meaning of set to group 2. cd $prefix 3. chgrp mailman . 4. chmod a+rx,g+ws . -- Sucessfully run Was the above 'cd $prefix' actually 'cd /usr/local/mailman'? Because the next step is telling you that /usr/local/mailman is not group mailman and/or not g+ws. 3 Build and install mailman 3.1 Run Configure *cd mailman-version* *./configure* This isn't the problem here, but you may wish to specify some options to configure such as --with-cgi-gid=, --with-mail-gid=, --with-mailhost= and --with-urlhost= Shows errors 1) checking permissions on /usr/local/mailman... configure: error: 2) * Installation directory /usr/local/mailman is not configured properly! 3) * Directory must be owned by group mailman: /usr/local/mailman Indicating that 'chgrp mailman .' above was not run in the /usr/local/mailman directory. You must fix the above and rerun configure. Then you can run 'make install' *sudo make install* 4 Check Your Installlatio 4.1 1. *bin/check_perms -f * bash: bin/check_perms: @PYTHON@: bad interpreter: No such file or directory 2. You have to run /usr/local/mailman/bin/check_perms which won't exist until you get the proper ownership and permissions on /usr/local/mailman and successfully run configure and make install. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] : Problem Running mailman
Hi, 2.1 Set up your system 1. Add the group and User *groupadd mailman :-* groupadd: group mailman exists *useradd -c''GNU Mailman'' -s /no/shell -d /no/home -g mailman mailman :- * no error but shows details about the command Useradd 2. Create the istallation Directory 2.2 Create the Installatio Directory 1. You cannot install Mailman on a filesystem that is mounted with the nosuid option not gettting the meaning of set to group 2. cd $prefix 3. chgrp mailman . 4. chmod a+rx,g+ws . -- Sucessfully run 3 Build and install mailman 3.1 Run Configure *cd mailman-version* *./configure* Shows errors 1) checking permissions on /usr/local/mailman... configure: error: 2) * Installation directory /usr/local/mailman is not configured properly! 3) * Directory must be owned by group mailman: /usr/local/mailman *sudo make install* 4 Check Your Installlatio 4.1 1. *bin/check_perms -f * bash: bin/check_perms: @PYTHON@: bad interpreter: No such file or directory 2. *cd mailman/archives * No such directory 3. *chown Apache 2 private* chown: `Apache': invalid user 4. *chmod o-x private* chmod: cannot access `private': No such file or directory 5 Set up your web server ScriptAlias /mailman/ $prefix/cgi-bin/ OR Exec/mailman/* $prefix/cgi-bin/* -- Forwarded message -- From: Mark Sapiro [EMAIL PROTECTED] Date: Oct 20, 2007 2:12 AM Subject: Re: [Mailman-Users] : Problem Running mailman To: QA Engg [EMAIL PROTECTED], Mailman-Users@python.org QA Engg wrote: And trying to run mailman but show the problem with /usr/local/mailman directory i.s Permission problem Have you tried running Mailman's bin/check_perms http://www.list.org/mailman-install/node9.html. when I tired to cd /usr/local/mailman directory it is showing error that Directory does not exist Did you specify some other 'prefix' option to configure? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] : Problem Running mailman
QA Engg wrote: 2.2 Create the Installatio Directory 1. You cannot install Mailman on a filesystem that is mounted with the nosuid option not gettting the meaning of set to group 2. cd $prefix 3. chgrp mailman . 4. chmod a+rx,g+ws . -- Sucessfully run Was the above 'cd $prefix' actually 'cd /usr/local/mailman'? Because the next step is telling you that /usr/local/mailman is not group mailman and/or not g+ws. 3 Build and install mailman 3.1 Run Configure *cd mailman-version* *./configure* This isn't the problem here, but you may wish to specify some options to configure such as --with-cgi-gid=, --with-mail-gid=, --with-mailhost= and --with-urlhost= Shows errors 1) checking permissions on /usr/local/mailman... configure: error: 2) * Installation directory /usr/local/mailman is not configured properly! 3) * Directory must be owned by group mailman: /usr/local/mailman Indicating that 'chgrp mailman .' above was not run in the /usr/local/mailman directory. You must fix the above and rerun configure. Then you can run 'make install' *sudo make install* 4 Check Your Installlatio 4.1 1. *bin/check_perms -f * bash: bin/check_perms: @PYTHON@: bad interpreter: No such file or directory 2. You have to run /usr/local/mailman/bin/check_perms which won't exist until you get the proper ownership and permissions on /usr/local/mailman and successfully run configure and make install. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] : Problem Running mailman
QA Engg wrote: And trying to run mailman but show the problem with /usr/local/mailman directory i.s Permission problem Have you tried running Mailman's bin/check_perms http://www.list.org/mailman-install/node9.html. when I tired to cd /usr/local/mailman directory it is showing error that Directory does not exist Did you specify some other 'prefix' option to configure? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] : Problem Running mailman
Hi all, Download mailman 2.1.9 Install it on my linux based system It automatically takes Apache as web server and Qmail as Email server And trying to run mailman but show the problem with /usr/local/mailman directory i.s Permission problem when I tired to cd /usr/local/mailman directory it is showing error that Directory does not exist please Help he regarding that Regards User -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem with mailman in combination with sendmail
Dear list, I try to get to run mailman 2.1.9 with sendmail on Debian 4.0. With mailman everything seems to be fine. Well, I can create new lists and get a confirmation of that. Check_perms -f says that everything is all right and in the log-files of mailman are no errors at all. I configured it with: ./configure --prefix=/usr/local/mailman --with-mail-gid=mail --with-cgi-gid=www-data --with-mailhost=h1228898.stratoserver.net --with-urlhost=h1228898.stratoserver.net With: --with-mail-gid=mail I am not so very sure. In the manual is written: On systems using sendmail, the ‘sendmail.cf’ configuration file designates the group id of sendmail processes using the DefaultUser option. So I watched sendmail.cf and it`s written: # default UID (can be username or userid:groupid) O DefaultUser=mail:mail I added the user mail with useradd -g mail -s /bin/false mail - so this should be correct? Sendmail I installed with: apt-get install sendmail In /etc/aliases I have the default-mailmanlist and I have: help: |/usr/local/mailman/mail/mailman post help help-admin:|/usr/local/mailman/mail/mailman admin help help-bounces: |/usr/local/mailman/mail/mailman bounces help help-confirm: |/usr/local/mailman/mail/mailman confirm help help-join: |/usr/local/mailman/mail/mailman join help help-leave:|/usr/local/mailman/mail/mailman leave help help-owner:|/usr/local/mailman/mail/mailman owner help help-request: |/usr/local/mailman/mail/mailman request help help-subscribe:|/usr/local/mailman/mail/mailman subscribe help help-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe help After that I did newaliases and got a confirmation of that. In sendmail.cf there is No entry for smrsh, so I should not have that. The problem is still: If I send a mail to the mailinglist it`s not posted to the members of the list. Has anybode experiences with mailman in combination with sendmail? Is there anything that is important to look at? What I don`t understand: If I get a confirmation after creating a mailinglist or after subscribing a user to a list it should mean that sendmail runs correctly? Or not Thank you very much, Kai -- Pt! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with mailman in combination with sendmail
Kai Behncke wrote: With: --with-mail-gid=mail I am not so very sure. In the manual is written: On systems using sendmail, the 'sendmail.cf' configuration file designates the group id of sendmail processes using the DefaultUser option. So I watched sendmail.cf and it`s written: # default UID (can be username or userid:groupid) O DefaultUser=mail:mail I added the user mail with useradd -g mail -s /bin/false mail - so this should be correct? Yes. That all should be correct. Sendmail I installed with: apt-get install sendmail In /etc/aliases I have the default-mailmanlist and I have: help: |/usr/local/mailman/mail/mailman post help help-admin:|/usr/local/mailman/mail/mailman admin help help-bounces: |/usr/local/mailman/mail/mailman bounces help help-confirm: |/usr/local/mailman/mail/mailman confirm help help-join: |/usr/local/mailman/mail/mailman join help help-leave:|/usr/local/mailman/mail/mailman leave help help-owner:|/usr/local/mailman/mail/mailman owner help help-request: |/usr/local/mailman/mail/mailman request help help-subscribe:|/usr/local/mailman/mail/mailman subscribe help help-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe help After that I did newaliases and got a confirmation of that. In sendmail.cf there is No entry for smrsh, so I should not have that. The problem is still: If I send a mail to the mailinglist it`s not posted to the members of the list. Are you sending to the 'help' mailing list ([EMAIL PROTECTED])? Has anybode experiences with mailman in combination with sendmail? Is there anything that is important to look at? What happens to the mail to the list. Is it returned as undeliverable? If so, why? Look in sendmail's maillog and see what sendmail did with the mail. What I don`t understand: If I get a confirmation after creating a mailinglist or after subscribing a user to a list it should mean that sendmail runs correctly? Or not It means that sendmail is accepting mail via an SMTP connection FROM Mailman and delivering it to the recepient addresses. It does not say anything about whether or not sendmail knows how to deliver mail TO Mailman or even if the mail gets to sendmail. Note I just tried to connect to h1228898.stratoserver.net port 25 from two different machines and was unable to connect. This means that at least at this time sendmail is not listening for a port 25 connection from the outside, and thus mail from the outside cannot be delivered to this machine. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] problem updating mailman in Plesk from 2.15 to 2.19
Can anyone assist with resolving this problem for me? Need to know about updating Mailman in Plesk from 2.15 to 2.19 I received the following response from Support at tecktonic who tried to update Mailman for me: I worked on this for quite a bit yesterday and came to the conclusion today after talking with my senior that it runs the risk of breaking plesk by forcing an install. Also, there are currently no mailman 2.1.9 releases for the current distro you are running, CentOS 4.5. The release that I had been looking at in plesk was for CentOS 5. If one is released it can be upgraded easily without fear of breaking anything. This, however, is not the case at the moment. Thank you. Mervyn Kahn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] problem updating mailman in Plesk from 2.15 to 2.19
On 8/23/07, Mervyn Kahn wrote: If one is released it can be upgraded easily without fear of breaking anything. This, however, is not the case at the moment. I've worked at a project where they were using Plesk, and after a great deal of customization work by the hosting facility staff, they were able to work out a way to upgrade the system. What they ended up doing was a from-source (not binary package) install of the appropriate recent version of Python for the updated version of Mailman, but in a separate non-standard location. This way, you don't step on any programs or processes that are built-in to the system that need the old version of Python, but you can tell other programs where they can get the more up-to-date version. Then they did a from-source (not binary package) install of the Mailman code, again in a non-standard location, and told it where to find the non-standard location for the more recent version of Python they had installed. They then worked to integrate the new version of Mailman into the Plesk package, changing calling paths in the appropriate programs, using symlinks to change locations in binary programs that could not be edited, etc My understanding is that, in the end, they were able to get most of the standard Plesk stuff working with the updated version of Mailman, but that some of what we consider to be Mailman-standard stuff was broken. They didn't care, since they had their Plesk integration. Oh, and since they needed to do the same sort of thing for various other packages on the system, and each one was dependant on a different version of Python, they ended up with about four or five versions of Python installed in various different locations. Not fun. But if you know what you're doing and you can handle doing installs direct from the original source code as opposed to keyboard monkeys who can't deal with anything that doesn't come in a pre-digested binary package, then you should be able to get where you want to be. Just don't try to do this at Rackspace, 11, or any of those other lowest-common-denominator hosting facilities. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem with mailman
I have problem with mailman Curentlu my listadress are [EMAIL PROTECTED] How to change it to my own domain And can i use my isps smtpserver to send mail? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with mailman
mattias jonsson wrote: I have problem with mailman Curentlu my listadress are [EMAIL PROTECTED] How to change it to my own domain And can i use my isps smtpserver to send mail? Where will your Mailman be hosted? If you are asking about changing to your own domain which will still be hosted by your ISP, then this is a question for your ISP. If you are asking about hosting your lists on your own server, then you begin by installing Mailman on your server. It is best if you have your own MTA on your server. It may be possible to use your ISP for outgoing mail if the ISP will accept the volume. It is not easy to use a foreign MTA for incoming mail to Mailman. You need to setup something with fetchmail/procmail or some similar processes to retrieve the mail from the foreign MTA and deliver it to Mailman on the local host. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with mailman and exim.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alberto V. I. wrote: I create mailman list and then I receive the notificacion to admin email, then I create anyother list without problems, beeing notified by mailman, but I cannot receive mails to list, If I send any mail to list, I obtain no result. I followed : /usr/share/doc/mailman/README.Exim4.Debian I did everything but/except : and list all your Mailman domains inPOSTFIX_STYLE_VIRTUAL_DOMAINS. All the rest things are made, do I need to use virtual domains? I have no idea what is in this Debian document, but the best instructions for Mailman/Exim integration are documents linked from http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.019.htp As far as POSTFIX_STYLE_VIRTUAL_DOMAINS is concerned, this is only applicable if you are using Postfix and have set MTA = 'Postfix' in mm_cfg.py. What is in your exim_main.log and/or your exim_reject.log for the posts you attempt to send to your Mailman lists? - -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhBUZVVuXXpU7hpMRAt+1AJ4wzhQ4Ced1FcEs+4iTz9r+XnHuJACg9Rxj 8+0cy1vakXGzziBICIQVuHY= =HH4z -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem with mailman and exim.
Hi, I am new at this list. I have a problem with mailman and exim: I create mailman list and then I receive the notificacion to admin email, then I create anyother list without problems, beeing notified by mailman, but I cannot receive mails to list, If I send any mail to list, I obtain no result. I followed : /usr/share/doc/mailman/README.Exim4.Debian I did everything but/except : and list all your Mailman domains inPOSTFIX_STYLE_VIRTUAL_DOMAINS. All the rest things are made, do I need to use virtual domains? Using mailman 2.1.9 and exim 4.63 under debian GNU/Linux. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
stupidmail4me a écrit : Precisely Mr Hermann. As such, it has to be invoked via mailertable (for an entire domain) or via aliases for specific addresses. mhmm.. just took a look at this piece of code, it could be just what I need to ease the burden of creating new lists, thanks :) I'd just need to patch it a bit to support a virtual domain set up (one instance of mailman per domain). Anyway, regarding your problem, it might be a wrong variable in the mm-handler, or maybe you forgot to add the virtusertable feature to your .mc file (and then the virtuser_domain won't be taken into account by sendmail). It's difficult to say without reviewing all the relevant parts of your configuration. Regards, -- Clement Hermann (nodens) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
stupidmail4me a écrit : Here's the setup: OpenBSD 4.0 Mailman 2.1.8p3 I have in my mc file I have VIRTUSER_DOMAIN(`lists.foo.org') set (and yes, I've run m4 and made the cf file). In mailertable I've got lists.foo.org mailman:lists.foo.org. But if I try and send a message I get a 550 5.1.1 User Unknown. I'm not sure I understand what you're trying, but I never added a mailman mailer, and so a mailman:domain definition in the mailertable. Rather, the mailman mails should go thru the local mailer, then thru prog with pipes aliases (local name: |command). Also, IIRC, putting a domain in mailertable will prevent the virtusertable to be checked, so the virtuser_domain is useless here. However, I'm not really sure about the order, need a sendmail expert here ;) I'm almost sure that you cannot have both, though. Regards, -- Clément Hermann -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
--- Clement Hermann [EMAIL PROTECTED] wrote: stupidmail4me a écrit : Here's the setup: OpenBSD 4.0 Mailman 2.1.8p3 I have in my mc file I have VIRTUSER_DOMAIN(`lists.foo.org') set (and yes, I've run m4 and made the cf file). In mailertable I've got lists.foo.org mailman:lists.foo.org. But if I try and send a message I get a 550 5.1.1 User Unknown. I'm not sure I understand what you're trying, but I never added a mailman mailer, and so a mailman:domain definition in the mailertable. Rather, the mailman mails should go thru the local mailer, then thru prog with pipes aliases (local name: |command). Also, IIRC, putting a domain in mailertable will prevent the virtusertable to be checked, so the virtuser_domain is useless here. However, I'm not really sure about the order, need a sendmail expert here ;) VIRTUSER_DOMAIN is not useless, it still gets run through virtusertable. You need a VIRTUSER_DOMAIN so that it runs through a mailer (which becomes the local mailer, in this case, mm-handler). I'm almost sure that you cannot have both, though. Regards, -- Clément Hermann __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
stupidmail4me a écrit :
VIRTUSER_DOMAIN is not useless, it still gets run
through virtusertable. You need a VIRTUSER_DOMAIN so
that it runs through a mailer (which becomes the
local mailer, in this case, mm-handler).
right, Though I usually use {W} for this purpose (the virtusertable is
checked weither you use local-host-names or virtuser_domain)?
Do you use a specific mailer macro to execute mailman without using
aliases ? I do not know the mm-handler you're talking about.
Is the mailertable used even when the domain is in virtuser_domain, then ?
I'm almost sure that you cannot have both, though.
Regards,
--
Clément Hermann
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Teach CanIt if this mail (ID 3642254) is spam:
/NOTE:/ This message has been trained as non-spam. If this is wrong,
please correct the training as soon as possible.
Spam
http://antispam.eolas-services.com/canit/b.php?c=si=3642254m=b91d8971ab61
Not spam
http://antispam.eolas-services.com/canit/b.php?c=ni=3642254m=b91d8971ab61
Forget previous vote
http://antispam.eolas-services.com/canit/b.php?c=fi=3642254m=b91d8971ab61
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
Clement Hermann wrote: Do you use a specific mailer macro to execute mailman without using aliases ? I do not know the mm-handler you're talking about. mm-handler is a script in the contrib/ directory of the distribution. it is intended to be invoked by Sendmail to receive all mail addressed to a specific domain (the one used for the Mailman list addresses) and deliver it properly to Mailman. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
Precisely Mr Hermann. As such, it has to be invoked via mailertable (for an entire domain) or via aliases for specific addresses. --- Mark Sapiro [EMAIL PROTECTED] wrote: Clement Hermann wrote: Do you use a specific mailer macro to execute mailman without using aliases ? I do not know the mm-handler you're talking about. mm-handler is a script in the contrib/ directory of the distribution. it is intended to be invoked by Sendmail to receive all mail addressed to a specific domain (the one used for the Mailman list addresses) and deliver it properly to Mailman. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem hooking mailman up with sendmail
I'm pulling my hair out on this one. I have mailman working on one machine and can't get it to work on another with the exact same config. Here's the setup: OpenBSD 4.0 Mailman 2.1.8p3 I have in my mc file I have VIRTUSER_DOMAIN(`lists.foo.org') set (and yes, I've run m4 and made the cf file). In mailertable I've got lists.foo.org mailman:lists.foo.org. But if I try and send a message I get a 550 5.1.1 User Unknown. What am I doing wrong? For the life of me I'v tried everything?!?!?!?! __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem hooking mailman up with sendmail
stupidmail4me wrote: I have in my mc file I have VIRTUSER_DOMAIN(`lists.foo.org') set (and yes, I've run m4 and made the cf file). In mailertable I've got lists.foo.org mailman:lists.foo.org. But if I try and send a message I get a 550 5.1.1 User Unknown. Have you installed aliases for the list(s) in /etc/aliases or ?? -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] problem with mailman GUI
Im running mailman version 2.1.8 on Redhat ES v4. I have had it running successfully for over 2 years now. Suddenly I am having problems with the gui interface. Everything runs fine for lists that are already created but the problem comes when trying to add a new list. I can add the list through the command line fine but if I use the gui it just comes back to the same page without adding the list. If I add the list by command line then the gui wont save any changes to the configuration. I dont get any error messages that I can find either. I originally thought it to be a permission problem but the older lists have the same permissions. I have tried upgrading to 2.1.9 and downgrading to 2.1.5 but they all act the same. Any ideas on where to look for this problem..thanks in advance! darryl -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem with mailman and qmail
Hi, Running mailman together with qmail on a server. Thought it worked just fine because the mails were sent to the members. Now I notice that for example the messages to the administrator/moderator that there are pending moderator request isn't sent out. When I check my mail logs I see rows like this. Oct 9 21:06:28 server qmail: 1160420788.602712 delivery 16629: deferral: Illegal_command:_mailowner/preline:_fatal:_unable_to_copy_input:_broken_pipe /Failed_to_start_/usr/lib/mailman/mail/mailman./ Oct 9 21:07:26 server qmail: 1160420846.907264 delivery 16637: deferral: Illegal_command:_mailowner/Failed_to_start_/usr/lib/mailman/mail/mailman./pr eline:_fatal:_unable_to_copy_input:_broken_pipe/ My .qmail files looks like this: .qmail-listname: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman post listname .qmail-listname-admin: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailowner listname .qmail-listname-bounces: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman bounces listname .qmail-listname-confirm: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman confirm listname .qmail-listname-join: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman join listname .qmail-listname-leave: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman leave listname .qmail-listname-owner: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailowner listname .qmail-listname-request: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailcmd listname .qmail-listname-subscribe: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman subscribe listname .qmail-listname-unsubscribe: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman unsubscribe listname Any hints on what could be wrong? I'm not that familiar with qmail so I have a hard time searching for errors. //kim -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with mailman and qmail
On 10/9/06, Kim Leandersson [EMAIL PROTECTED] wrote: Hi, Running mailman together with qmail on a server. Thought it worked just fine What version of mailman are you using? As of recent versions, these should look like: .qmail-listname-admin: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailowner listname mailman owner listname .qmail-listname-request: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailcmd listname mailman request listname -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with mailman and qmail
On 10/9/06, Patrick Bogen [EMAIL PROTECTED] wrote: On 10/9/06, Kim Leandersson [EMAIL PROTECTED] wrote: Hi, Running mailman together with qmail on a server. Thought it worked just fine What version of mailman are you using? As of recent versions, these should look like: .qmail-listname-admin: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailowner listname mailman owner listname Rather, 'admin' for listname-admin and 'owner' for listname-owner .qmail-listname-request: |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /usr/lib/mailman/mail/mailman mailcmd listname mailman request listname -- - Patrick Bogen -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] problem running Mailman on 2.6.11.7
Hi all. I'm attempting to get Mailman running on a Slackware-10.0 machine with 2.6.11.7 and Grsecurity installed. After running check_perms_grsecurity.py and then running ./mailmanctl start, I received several errors such as this: Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 76, in ? import CheckFixUid File /usr/local/mailman/bin/CheckFixUid.py, line 6, in ? class CheckFixUid: File /usr/local/mailman/bin/CheckFixUid.py, line 12, in CheckFixUid if os.geteuid() != uid: NameError: name 'uid' is not defined I googled for checkfixuid, and the closest I came to a fix is http://www.mail-archive.com/cooker@linux-mandrake.com/msg126675.html Unfortunately, I can't test that patch since its been packaged within an RPM. Any other ideas on how to fix this are appreciated. Thanks. -- Any society that would give up a little liberty to gain a little security will deserve neither and lose both. -- Benjamin Franklin pgpCYaRjsfufp.pgp Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] problem running Mailman on 2.6.11.7
Igor Gueths wrote: Hi all. I'm attempting to get Mailman running on a Slackware-10.0 machine with 2.6.11.7 and Grsecurity installed. After running check_perms_grsecurity.py and then running ./mailmanctl start, I received several errors such as this: Traceback (most recent call last): File /usr/local/mailman/bin/qrunner, line 76, in ? import CheckFixUid File /usr/local/mailman/bin/CheckFixUid.py, line 6, in ? class CheckFixUid: File /usr/local/mailman/bin/CheckFixUid.py, line 12, in CheckFixUid if os.geteuid() != uid: NameError: name 'uid' is not defined I googled for checkfixuid, and the closest I came to a fix is http://www.mail-archive.com/cooker@linux-mandrake.com/msg126675.html Unfortunately, I can't test that patch since its been packaged within an RPM. Any other ideas on how to fix this are appreciated. Thanks. check_perms_grsecurity.py and its 'child' CheckFixUid.py are user contributed software. I suggest you follow up with the contributor. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] problem with mailman and qmail?
Hi, I've been running mailman for some years and are satisfied with how it works and thougt I collected some knowledge about it. I've been running mailman with both postfix and sendmail as MTA:s without any problem. A couple of months ago we decided to give the hosting software plesk a chance and now the challenge began for me. Plesk is using qmail and I haven't really understood what I doing wrong now but maybe you could help me out. The server hosts several domains which have the ability to create mailman lists via the webbinterface. This works great, the problem comes every month when the monthly reminders are sent out. I'll try to describe this with an example. An explicit example: The address [EMAIL PROTECTED] is a member of the list [EMAIL PROTECTED], the problem is that this address isn't working. So when mail is sent to [EMAIL PROTECTED] a bounce is produced. This bounce would in an ideal world be sent to [EMAIL PROTECTED] that would be extracted to the list administrator. However, when the monthly reminder is sent out we (as postmaster) get the following (see below). Everywhere in the header we see [EMAIL PROTECTED] and not [EMAIL PROTECTED] The problem also seems to be that [EMAIL PROTECTED] isn't accepting any mails. Any hints on how to get the maillists to send bounces to [EMAIL PROTECTED] I've tried both searching the Internet and talking to the Plesk support without any luck so any help is deeply appreciated. //kim # .qmail-manskor-bounces ### Plesk# .qmail-manskor-bounces |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /var/mailman/mail/mailman bounces manskor Bounce sent to postmaster ## Hi. This is the qmail-send program at plesk.chs.chalmers.se. I tried to deliver a bounce message to this address, but the bounce bounced! [EMAIL PROTECTED]: This address no longer accepts mail. --- Below this line is the original bounce. Return-Path: Received: (qmail 14566 invoked from network); 1 Dec 2005 05:01:21 +0100 Received: from emil.chs.chalmers.se (HELO mail.chs.chalmers.se) (129.16.159.10) by plesk.chs.chalmers.se with SMTP; 1 Dec 2005 05:01:21 +0100 Received: by mail.chs.chalmers.se (Postfix) id B0EED9C8B; Thu, 1 Dec 2005 05:01:18 +0100 (CET) Date: Thu, 1 Dec 2005 05:01:18 +0100 (CET) From: [EMAIL PROTECTED] (Mail Delivery System) Subject: Undelivered Mail Returned to Sender To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=5C84D9C80.1133409678/mail.chs.chalmers.se Message-Id: [EMAIL PROTECTED] This is a MIME-encapsulated message. --5C84D9C80.1133409678/mail.chs.chalmers.se Content-Description: Notification Content-Type: text/plain This is the Postfix program at host mail.chs.chalmers.se. I'm sorry to have to inform you that your message could not be 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 Postfix program [EMAIL PROTECTED]: host mail.medic.chalmers.se[129.16.30.218] said: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in virtual alias table (in reply to RCPT TO command) --5C84D9C80.1133409678/mail.chs.chalmers.se Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mail.chs.chalmers.se X-Postfix-Queue-ID: 5C84D9C80 X-Postfix-Sender: rfc822; [EMAIL PROTECTED] Arrival-Date: Thu, 1 Dec 2005 05:01:18 +0100 (CET) Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; host mail.medic.chalmers.se[129.16.30.218] said: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in virtual alias table (in reply to RCPT TO command) --5C84D9C80.1133409678/mail.chs.chalmers.se Content-Description: Undelivered Message Content-Type: message/rfc822 Received: from localhost (localhost [127.0.0.1]) by mail.chs.chalmers.se (Postfix) with ESMTP id 5C84D9C80 for [EMAIL PROTECTED]; Thu, 1 Dec 2005 05:01:18 +0100 (CET) Received: from mail.chs.chalmers.se ([129.16.159.10]) by localhost (emil.chs.chalmers.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04445-08 for [EMAIL PROTECTED]; Thu, 1 Dec 2005 05:01:13 +0100 (CET) Received: from plesk.chs.chalmers.se (plesk.chs.chalmers.se [129.16.159.21]) by mail.chs.chalmers.se (Postfix) with ESMTP id 5BCA49C8A for [EMAIL PROTECTED]; Thu, 1 Dec 2005 05:00:08 +0100 (CET) Received: (qmail 11621 invoked from network); 1 Dec 2005 05:00:08 +0100 Received: from localhost (HELO plesk.chs.chalmers.se) (?U2FsdGVkX18V/[EMAIL PROTECTED]) by localhost with SMTP; 1 Dec 2005 05:00:08 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit
Re: [Mailman-Users] problem with mailman and qmail?
Kim Leandersson wrote: However, when the monthly reminder is sent out we (as postmaster) get the following (see below). Everywhere in the header we see [EMAIL PROTECTED] and not [EMAIL PROTECTED] The problem also seems to be that [EMAIL PROTECTED] isn't accepting any mails. You need to arrange aliases or whatever qmail uses to route mail to Mailman so that mail to mailman(-*)@... gets routed to the mailman list regardless of which domain it is sent to. Any hints on how to get the maillists to send bounces to [EMAIL PROTECTED] I've tried both searching the Internet and talking to the Plesk support without any luck so any help is deeply appreciated. This is by design. Password reminders are sent from the site list because the particular user may be a member of more than one list, in which case, sending the reminder from the list would require a reminder per list. In the current implementation, the reminder is sent once per site/virtual-host for all lists that include that member. If you are using virtual hosts, the sitelist name refers to the one site list, but depending on context, the domain associated with the site list can be any of the virtual host email domains. Thus they all have to be deliverable. # .qmail-manskor-bounces ### Plesk# .qmail-manskor-bounces |/var/qmail/bin/preline /var/qmail/bin/mm_wrapper /var/mailman/mail/mailman bounces manskor I understand this is how qmail does routing, but this routes bounces for the 'manskor' list. Do you have similar routing for all the addresses of the mailman (site) list. I.e. .qmail-mailman, .qmail-mailman-bounces, etc., and if so, they have to be made to apply to all domains that mailman serves. Also see http://www.list.org/mailman-install/qmail-issues.html. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] problem with mailman and qmail-ldap
- mailman 2.1.5-9 - apt-get - Linux Debian testing. - MTA : qmail with ldap. My problem is : I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. The problems had began when i updated the libc6 four days ago. The version the libc6 is 2.3.5-6. What is my problem ? Thanks you Gabriel -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] problem with mailman and qmail-ldap
gabo wrote: I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. This seems to indicate that the mail reaches Mailman and is queued, but there is some problem with one or more of the qrunners. Look at the Mailman logs 'error' and 'qrunner' to see if qrunners are dying and what might be causing it. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] problem with mailman and qmail-ldap
Mark Sapiro wrote: gabo wrote: I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. This seems to indicate that the mail reaches Mailman and is queued, but there is some problem with one or more of the qrunners. Look at the Mailman logs 'error' and 'qrunner' to see if qrunners are dying and what might be causing it. nothing abount this in the error and qrunner log, only shuting and smtp cannot connection, error messages. Nov 01 12:03:20 2005 (21469) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 223, in _dispose res = Results(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File /usr/lib/python2.3/email/Header.py, line 144, in make_header h.append(s, charset) File /usr/lib/python2.3/email/Header.py, line 272, in append ustr = unicode(s, incodec, errors) UnicodeDecodeError: 'ascii' codec can't decode byte 0xda in position 14: ordinal not in range(128) Nov 01 12:03:20 2005 (21469) SHUNTING: 1130857400.1742439+75ef1b3c5e1079f2ee995e954fd2a65f7e650a65 Nov 01 17:24:53 2005 (21472) Cannot connect to SMTP server server.xxx.xxx.xxx on port 25 qrunner log: Nov 02 06:25:05 2005 (11143) RetryRunner qrunner caught SIGHUP. Reopening logs.Nov 02 15:02:25 2005 (11136) ArchRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:25 2005 (11136) ArchRunner qrunner exiting. Nov 02 15:02:25 2005 (11139) IncomingRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:25 2005 (11139) IncomingRunner qrunner exiting. Nov 02 15:02:25 2005 (11140) NewsRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:25 2005 (11140) NewsRunner qrunner exiting. Nov 02 15:02:26 2005 (11141) OutgoingRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11141) OutgoingRunner qrunner exiting. Nov 02 15:02:26 2005 (11142) VirginRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11142) VirginRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master watcher caught SIGTERM. Exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11136, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11139, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11140, sig: None, sts: 15, class: NewsRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11141, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Nov 02 15:02:26 2005 (11137) BounceRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11138) CommandRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11138) CommandRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11138, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11142, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Nov 02 15:02:26 2005 (11143) RetryRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11143) RetryRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11143, sig: None, sts: 15, class: RetryRunner, slice: 1/1) Nov 02 15:02:26 2005 (11137) BounceRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11137, sig: None, sts: 15, class: BounceRunner, slice: 1/1) Nov 02 15:02:26 2005 (26683) ArchRunner qrunner started. Nov 02 15:02:27 2005 (26684) BounceRunner qrunner started. Nov 02 15:02:27 2005 (26685) CommandRunner qrunner started. Nov 02 15:02:27 2005 (26686) IncomingRunner qrunner started. Nov 02 15:02:27 2005 (26687) NewsRunner qrunner started. Nov 02 15:02:27 2005 (26688) OutgoingRunner qrunner started. Nov 02 15:02:27 2005 (26689) VirginRunner qrunner started. Nov 02 15:02:27 2005 (26690) RetryRunner qrunner started. Nov 02 15:02:29 2005 (26684) BounceRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:29 2005 (26684) BounceRunner qrunner exiting. Nov 02 15:02:29 2005 (26685) CommandRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:29 2005 (26685) CommandRunner qrunner exiting. Nov 02 15:02:29 2005 (26686) IncomingRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:29 2005 (26686) IncomingRunner qrunner exiting. Nov 02 15:02:29 2005
Re: [Mailman-Users] problem with mailman and qmail-ldap
gabo wrote: Mark Sapiro wrote: gabo wrote: I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. This seems to indicate that the mail reaches Mailman and is queued, but there is some problem with one or more of the qrunners. Look at the Mailman logs 'error' and 'qrunner' to see if qrunners are dying and what might be causing it. nothing abount this in the error and qrunner log, only shuting and smtp cannot connection, error messages. log messages snipped The next time this occurs, look in qfiles/* and see where the undelivered messages are. Don't worry about shunted messages in qfiles/shunt, or the archive/, bad/, bounces/, commands/, news/ or virgin/ queues either. Undelivered messages that will be delivered automatically following a mailmanctl restart will almost certainly be in one of in/, out/ or retry/. Once you've located the messages, check the state of the corresponding runner. A command like $ ps -fwu mailman or whatever the equivalent is on your system normally gives something like: UIDPID PPID C STIME TTY TIME CMD mailman 1564 1 0 Jul02 ?00:00:00 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start mailman 1565 1564 0 Jul02 ?00:33:00 /usr/bin/python /var/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 1566 1564 0 Jul02 ?00:00:53 /usr/bin/python /var/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 1567 1564 0 Jul02 ?00:00:23 /usr/bin/python /var/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 1568 1564 0 Jul02 ?00:03:31 /usr/bin/python /var/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 1569 1564 0 Jul02 ?00:00:09 /usr/bin/python /var/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 1570 1564 0 Jul02 ?00:08:01 /usr/bin/python /var/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 1571 1564 0 Jul02 ?00:01:32 /usr/bin/python /var/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 1572 1564 0 Jul02 ?00:00:00 /usr/bin/python /var/mailman/bin/qrunner --runner=RetryRunner:0:1 -s If the specific qrunner isn't there, that's the problem. Maybe some system log can help determine why it died. If it is there, maybe you have tools to help figure why it isn't doing what it should be. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Problem with Mailman archives
Hi I use the Mailman program to run 5 mailing lists, great program to do it, but now (after an upgrade I think) the archives are no longer functioning: Not Found The requested URL /pipermail/listacac/ was not found on this server. Must I create the pipermail account? I have Mailman 2.1.5 in a Debian box (Linux gentzen 2.6.7 #2 SMP Mon Jul 19 16:03:29 WEST 2004 i686 GNU/Linux). Thanks. -- At\'e breve Professor Auxiliar Pedro Quaresma Departamento de Matem\'atica Faculdade de Ci\^encias e Tecnologia Universidade de Coimbra P-3001-454 COIMBRA, PORTUGAL correio-e: [EMAIL PROTECTED] p\'agina: http://www.mat.uc.pt/~pedro/ telef: +351 239 791 181; fax: +351 239 832 568 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Problem with Mailman archives
Pedro Quaresma wrote: I use the Mailman program to run 5 mailing lists, great program to do it, but now (after an upgrade I think) the archives are no longer functioning: Not Found The requested URL /pipermail/listacac/ was not found on this server. Must I create the pipermail account? This is normally handled in Apache with something like Alias /pipermail/ /var/mailman/archives/public/ in the appropriate place in httpd.conf. Also, the web server must follow symlinks in the /var/mailman/archives/public/ directory. (The actual path may be different in your case.) See http://www.list.org/mailman-install/node10.html. -- Mark Sapiro [EMAIL PROTECTED] The 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://www.python.org/cgi-bin/faqw-mm.py 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://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
