[Mailman-Users] Archives, the Forbidden Zone
Let me start with a big Thank You to the Mailman authors for their great work on this fine list management software. I have been using Mailman for over four years and have had very few problems. Recently I installed Fedora Core 3 and I am in the process of setting up the system to once again host several Mailman lists. However, I have run into a problem that I am unable to solve. It is the typical 403 Forbidden problem often seen by newbies when attempting to view the archives of a list. I have searched the mailman-users archives. I have searched Google Groups. I have read the INSTALL.REDHAT and UPGRADING files included in the mailman rpm, as well as several other pertinent files. I have found nothing that can explain why I continue to see the 403 Forbidden error. First off, the lists have been imported from backup, so there is the possibility something went wrong in that. However, check_perms reports no problems. And check_db -a also reports nothing. I also ran the 'update' command successfully. Sending mail to the lists appears to be working, as does the administrative interface. The only problem really is accessing the archives. Now before you tell me that I need to set up the Apache configuration, let me say that the mailman rpm in FC3 includes a .conf file already. I have pasted it in below for your reference. And I suppose you will ask What about the permissions on the files/directories? Ah, I'm one step ahead of you there. See the detailed output below the .conf file. So the question becomes, what is preventing the browser from accessing the archives? nathan P.S. You can see the problem for yourself at http://www.bluemarsh.com/mailman/listinfo # # httpd configuration settings for use with mailman. # ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Directory /usr/lib/mailman/cgi-bin/ AllowOverride None Options ExecCGI Order allow,deny Allow from all /Directory Alias /pipermail/ /var/lib/mailman/archives/public/ Directory /var/lib/mailman/archives/public/ Options Indexes MultiViews FollowSymLinks AllowOverride None Order allow,deny Allow from all /Directory # Uncomment the following line, replacing www.example.com with your server's # name, to redirect queries to /mailman to the listinfo page (recommended). RedirectMatch ^/mailman[/]*$ http://www.bluemarsh.com/mailman/listinfo Apache user can read the files: # echo head /var/lib/mailman/archives/private/jswat- announce/index.html | su -fm apache !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2//EN HTML HEAD titleThe jswat-announce Archives/title META NAME=robots CONTENT=noindex,follow META http-equiv=Content-Type content=text/html; charset=us- ascii /HEAD BODY BGCOLOR=#ff h1The jswat-announce Archives /h1 p [To double-check, apache cannot read root's files.] # echo head /root/.bashrc | su -fm apache head: cannot open `/root/.bashrc' for reading: Permission denied Directory permissions in detail: # ls -l / drwxr-xr-x 22 root root 4096 Nov 16 00:05 var # ls -l /var drwxr-xr-x 23 rootroot 4096 Nov 19 16:09 lib # ls -l /var/lib drwxrwsr-x 6 root mailman 4096 Nov 20 23:00 mailman # ls -l /var/lib/mailman drwxrwsr-x 4 mailman mailman 4096 Jun 16 2003 archives # ls -l /var/lib/mailman/archives drwxrws--x 13 mailman mailman 4096 Nov 20 22:33 private drwxrwsr-x 2 mailman mailman 4096 Nov 20 22:33 public # ls -l /var/lib/mailman/archives/private drwxrwsr-x 9 mailman mailman 4096 Oct 17 03:27 jswat-announce drwxrwsr-x 2 mailman mailman 4096 Feb 24 2004 jswat-announce.mbox # ls -l /var/lib/mailman/archives/private/jswat-announce drwxrwsr-x 2 mailman mailman 4096 Apr 29 2004 2004-April -rw-rw-r-- 1 mailman mailman 805 Apr 29 2004 2004-April.txt -rw-rw-r-- 1 mailman mailman 544 Apr 30 2004 2004-April.txt.gz drwxrwsr-x 2 mailman mailman 4096 Aug 17 00:05 2004-August -rw-rw-r-- 1 mailman mailman 699 Aug 17 00:05 2004-August.txt -rw-rw-r-- 1 mailman mailman 512 Aug 17 03:27 2004-August.txt.gz drwxrwsr-x 2 mailman mailman 4096 Feb 27 2004 2004-February -rw-rw-r-- 1 mailman mailman 1674 Feb 27 2004 2004-February.txt -rw-rw-r-- 1 mailman mailman 935 Feb 28 2004 2004-February.txt.gz drwxrwsr-x 2 mailman mailman 4096 May 9 2004 2004-May -rw-rw-r-- 1 mailman mailman 435 May 9 2004 2004-May.txt -rw-rw-r-- 1 mailman mailman 361 May 10 2004 2004-May.txt.gz drwxrwsr-x 2 mailman mailman 4096 Oct 16 17:28 2004-October -rw-rw-r-- 1 mailman mailman 810 Oct 16 17:28 2004-October.txt -rw-rw-r-- 1 mailman mailman 549 Oct 17 03:27 2004-October.txt.gz drwxrwsr-x 2 mailman mailman 4096 Sep 22 00:17 2004-September -rw-rw-r-- 1 mailman mailman 1455
Re: [Mailman-Users] Generic non-members rejection notice
On Sat, Nov 20, 2004 at 02:03:13PM +, Robin Becker wrote: I see this question asked, but haven't seen a reply. Is there any way to change the response message that non-members receive when rejection is the chosen action? They receive the message in Mailman/Handlers/Moderate.py's do_reject() (or the translation of that message from the correct language catalog). I managed to modify my admin gui to allow adding an attribute nonmember_rejection_notice (had to fake a getattr out as well), but I can't seem to make this message appear in rejections. In fact the code in Moderate.py doesn't seem to get used during rejections. I cchecked and it seems as though the .pck does contain the new attribute. You should add (or replace) the code in do_reject(). (If changing that text string, remember to restart Mailman after editing.) -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/ Ringo MUG Tokyo http://www.ringo.net/rss.html -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
Nathan Fiedler wrote: Now before you tell me that I need to set up the Apache configuration, let me say that the mailman rpm in FC3 includes a .conf file already. I have pasted it in below for your reference. You did reload/restart Apache, of course? -thh -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Second attempt at posting
Terry Allen wrote:
I tried earlier to post to this list but was bounced for some
unknown reason.
This post and a subsequent one were just approved by the moderator and
delivered to the list. So far there's no sign of the earlier one.
These later two may have been held because you are not a list member
if that is in fact the case.
In installing on Mac OSX 10.3.6, I have encountered the
following errors:
[server:~mailman/bin] root# ./check_perms -f
Traceback (most recent call last):
File ./check_perms, line 46, in ?
from Mailman import mm_cfg
File /usr/local/mailman/Mailman/mm_cfg.py, line 45, in ?
add_virtualhost (heard.com.au, heard.com.au)
NameError: name 'heard' is not defined
The line which begins add_virtualhost is exactly as it
appears in mm_cfg.py
Could anyone point me in the right direction to try to get
this installation up running please.
It should be
add_virtualhost ('heard.com.au', 'heard.com.au')
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Hi again,
Many thanks for that - after editing that, then running
check_perms -f, it came up with no errors, so I'll be heading to see
what happens next.
--
Bye for now, Terry Allen
___
hEARd
Postal Address:
hEARd, 26B Glenning Rd, Glenning Valley, NSW 2261, Australia
Internet -
WWW: http://heard.com.au http://itavservices.com
EMAIL: [EMAIL PROTECTED]
Phone: Australia - 02 4388 1400 / International - + 61 2 43881400
Mobile: Australia - 04 28881400 / International - 61 4 28881400
---
Non profit promotion for new music - since 1994
---
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
[Mailman-Users] Bounce notifications.
We run about 30 different listservs on the BLU server using Mailman 2.1.4. We recently upgraded from an ancient release of mailman. Some of our listserv admins are complaining about Uncaught bounce notification messages. It appears that most of these result from delayed email notification to hotmail or msn subscribers. Personally, I just ignore them. While I have not tried this, if we disable Should Mailman send you, the list owner, any bounce messages that failed to be detected by the bounce processor?, would that eliminate those messages. But, by disabling this, would the list owners lose some other important notification. -- Jerry Feldman [EMAIL PROTECTED] Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
AW: [Mailman-Users] Unable to get Mailman up and running with qmail/vpopmail
I really tried a lot until now and I have read README.QMAIL numerous times. I agree that everything looks like an alias problem, but if I want to solve this ever, I have to start investigating. I ran the script mentioned in the README.QMAIL file. To clarify where should those aliases be created? In /path/to/mailman or in /path/to/vpopmail/domains ;-) Also isn't there a way to handle all this without aliases. The tutorials I read didn't work with aliases, but added |/usr/bin/python /var/mailman/qmail-to-mailman.py to .qmail-default. This .qmail-default is supposed to reside in the mailman folder, but I also tried to put this in the apropriate vpopmail folder. I've added the lists.domain.tld, using vqadmin. My problem might be that I don't know for sure how all this works internally. That's what I believe and please correct me as this might lead me the right direction... 1. I am sending a mail to [EMAIL PROTECTED] 2. Qmail/vpopmail know the domain lists.domain.tld and take care of it 3. The user example is not known at lists.domain.tld so see what's in .qmail-default 4. From there the file qmail-to-mailman.py is called using python 5. Mailman should handle everything from there ...but, that's not how it works. Could this also be a rights problem? In one tutorial I read to compile mailman with --with-mail-gid=mailman, in the oter I read to compile it with --with-mail-gid=vchkpw (the group used by qmail/vpopmail). What is the correct way and how does this influence the process. Sorry, I know a lot of questions and I would like to say thank you in advance for any support given :-) Best regards, Alex -Ursprüngliche Nachricht- Von: Brad Knowles [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 21. November 2004 01:57 An: DIGITAL FOR YOU - Alexander Schwethelm Cc: [EMAIL PROTECTED] Betreff: Re: [Mailman-Users] Unable to get Mailman up and running with qmail/vpopmail At 5:16 PM +0100 2004-11-20, DIGITAL FOR YOU - Alexander Schwethelm wrote: What doesn't work and this is of course the most important part, is any mail to mailman. Let's say I have a list [EMAIL PROTECTED] and I send an email to this address as a list user, the mail gets stuck in the qmail queue. This sounds like a problem with the aliases definitions on the MTA. Personally, I had never heard of either of the URLs you mentioned. With regards to getting Mailman to work with qmail, the best reference I know of is found within the Mailman tarball, in the README.QMAIL file. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Has anyone successfully installed Mailman
On Sat, 20 Nov 2004, Kenneth Porter wrote: --On Saturday, November 20, 2004 9:45 PM -0500 Matthew Saltzman [EMAIL PROTECTED] wrote: Haven't actually tried it, but won't rpm complain about the missing python-devel package when you attempt to install the SRPM? Seems like that would be what dependencies in SRPMs are for. No, build prerequisites are checked at build time, not unpacking time. Note that you can do both with one command, rpmbuild --rebuild xxx.src.rpm. But if you just want to unpack it, use rpm -i xxx.src.rpm and it won't check the build prereqs. You can then unpack the tarball or inspect the spec file and patches and other support files included in the SRPM. Ah, makes sense. Thanks for the correction. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Generic non-members rejection notice
At 03:33 AM 11/21/2004, Jim Tittsler wrote: On Sat, Nov 20, 2004 at 02:03:13PM +, Robin Becker wrote: I see this question asked, but haven't seen a reply. Is there any way to change the response message that non-members receive when rejection is the chosen action? They receive the message in Mailman/Handlers/Moderate.py's do_reject() (or the translation of that message from the correct language catalog). It looks to me that this is the automatic rejection of non member posts. Where is the default message located that is sent when someone selects reject from the held messages screen. By default it sends a message that says No reason given. Tim -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
--On Sunday, November 21, 2004 12:11 AM -0800 Nathan Fiedler [EMAIL PROTECTED] wrote: I have found nothing that can explain why I continue to see the 403 Forbidden error. Anything interesting in /var/log/httpd or /var/log/messages? Alias /pipermail/ /var/lib/mailman/archives/public/ Are there symlinks here to the directories in private? Here's what I see in my installation on FC2 (where the system is installed to /var/mailman): $ ls -al /var/mailman/archives/public/ total 8 drwxrwsr-x 2 root mailman 4096 Oct 13 08:10 . drwxrwsr-x 4 root mailman 4096 Jun 9 15:02 .. lrwxrwxrwx 1 apache mailman 37 Oct 12 12:52 mailman - /var/mailman/archives/private/mailman lrwxrwxrwx 1 root mailman 39 Oct 13 08:10 t2servers - /var/mailman/archives/private/t2servers lrwxrwxrwx 1 root mailman 44 Oct 13 08:10 t2servers.mbox - /var/mailman/archives/private/t2servers.mbox lrwxrwxrwx 1 apache mailman 39 Oct 13 07:08 tvservers - /var/mailman/archives/private/tvservers -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
On Sun, 2004-11-21 at 10:06 +0100, Thomas Hochstein wrote: Nathan Fiedler wrote: Now before you tell me that I need to set up the Apache configuration, let me say that the mailman rpm in FC3 includes a .conf file already. I have pasted it in below for your reference. You did reload/restart Apache, of course? Yep. I restarted the Mailman service a few times, too. I forgot to mention that I also ran withlist fix_url on all of the lists to recreate the symbolic links from the public to private archives. Here is an example: lrwxrwxrwx 1 root mailman 48 Nov 20 15:44 jswat-announce - /var/lib/mailman/archives/private/jswat-announce n -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
On Sun, 2004-11-21 at 08:07 -0800, Kenneth Porter wrote:
Anything interesting in /var/log/httpd or /var/log/messages?
The Apache error_log just has the usual permission denied message.
Now /var/log/messages is a different story, and I never thought to look
at that one:
Nov 21 08:18:12 chip kernel: audit(1101053892.157:0): avc: denied
{ read } for pid=25155 exe=/usr/sbin/httpd name=jswat-announce dev=hda6
ino=75928 scontext=root:system_r:httpd_t
tcontext=root:object_r:mailman_data_t tclass=lnk_file
Nov 21 08:18:12 chip kernel: audit(1101053892.157:0): avc: denied
{ getattr } for pid=25155 exe=/usr/sbin/httpd
path=/var/lib/mailman/archives/public/jswat-announce dev=hda6 ino=75928
scontext=root:system_r:httpd_t tcontext=root:object_r:mailman_data_t
tclass=lnk_file
Are there symlinks here to the directories in private? Here's what I see in
my installation on FC2 (where the system is installed to /var/mailman):
Yep, I forgot to mention that I ran withlist fix_url at one point:
lrwxrwxrwx 1 root mailman 48 Nov 20 15:44 jswat-announce -
/var/lib/mailman/archives/private/jswat-announce
So does anyone understand the audit error messages? I suppose that has
something to do with SELinux being enabled on this system, but I know
next to nothing about it.
Thanks
n
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
Re: [Mailman-Users] Bounce notifications.
Jerry Feldman wrote: We run about 30 different listservs on the BLU server using Mailman 2.1.4. We recently upgraded from an ancient release of mailman. Some of our listserv admins are complaining about Uncaught bounce notification messages. It appears that most of these result from delayed email notification to hotmail or msn subscribers. There is a recent thread on this beginning at http://mail.python.org/pipermail/mailman-users/2004-November/040837.html Personally, I just ignore them. While I have not tried this, if we disable Should Mailman send you, the list owner, any bounce messages that failed to be detected by the bounce processor?, would that eliminate those messages. But, by disabling this, would the list owners lose some other important notification. Yes, it would eliminate delivering those unrecognized delayed notifications to the list owner, but it would also eliminate delivering all other unrecognized bounces, some of which may be SPAM or even desired messages sent to the list-bounces address and some of which may be real bounces in a non-standard format which should be seen. If this is a concern, you can set VERP_DELIVERY_INTERVAL to some non-zero value in mm_cfg.py so every nth post is VERP'd and real bounces will eventually be detected. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
--On Sunday, November 21, 2004 8:25 AM -0800 Nathan Fiedler [EMAIL PROTECTED] wrote: So does anyone understand the audit error messages? I suppose that has something to do with SELinux being enabled on this system, but I know next to nothing about it. That'd be my guess. You could try asking on the Fedora-Users list, or perhaps the selinux list. I know this issue came up involving copying and moving files between the web directories and web space in a user's home directory (eg. ~/public_html), and that there's some kind of context attribute that needs to be assigned to the directories and files. But I don't recall the details. This is probably like learning how to use chmod and chown for Windows users. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Generic non-members rejection notice
Speedy Gonzalis wrote: At 03:33 AM 11/21/2004, Jim Tittsler wrote: On Sat, Nov 20, 2004 at 02:03:13PM +, Robin Becker wrote: I see this question asked, but haven't seen a reply. Is there any way to change the response message that non-members receive when rejection is the chosen action? They receive the message in Mailman/Handlers/Moderate.py's do_reject() (or the translation of that message from the correct language catalog). It looks to me that this is the automatic rejection of non member posts. Where is the default message located that is sent when someone selects reject from the held messages screen. By default it sends a message that says No reason given. It's in Mailman/Cgi/admindb.py (or the appropriate language translation). In this case, you're expected to provide the message if you want one. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
On Sun, 2004-11-21 at 09:29 -0800, Kenneth Porter wrote: That'd be my guess. You could try asking on the Fedora-Users list, or perhaps the selinux list. I know this issue came up involving copying and moving files between the web directories and web space in a user's home directory (eg. ~/public_html), and that there's some kind of context attribute that needs to be assigned to the directories and files. But I don't recall the details. This is probably like learning how to use chmod and chown for Windows users. Good to know, thanks for the info. I'll read about SELinux and try asking the fedora list since someone there ought to know about this. Thanks n -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Archives, the Forbidden Zone
On Sun, 2004-11-21 at 09:29 -0800, Kenneth Porter wrote: That'd be my guess. You could try asking on the Fedora-Users list, or perhaps the selinux list. I know this issue came up involving copying and moving files between the web directories and web space in a user's home directory (eg. ~/public_html), and that there's some kind of context attribute that needs to be assigned to the directories and files. But I don't recall the details. This is probably like learning how to use chmod and chown for Windows users. It turns out the problem was simple and so was the solution. When importing my existing list data and archives from another machine, I did not know to update the selinux context labels appropriately. Thus, the kernel was unable to determine if the apache user was allowed to access the files. Normally it should be, but without the labels it wouldn't succeed. To correct the labels, I ran both of these commands as root: # fixfiles relabel # restorecon -Rv /var/lib/mailman Their descriptions sound very similiar so I probably only needed one of them. Thanks again nathan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
RE: [Mailman-Users] Email to list rejected
-Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Saturday, November 20, 2004 11:00 PM To: Tom Barton; '[EMAIL PROTECTED]' Subject: Re: [Mailman-Users] Email to list rejected Tom Barton wrote: For some reason email to my list is being rejected. I've set up a list with my email address as the only member. When I send email to the list I get: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: 550 [EMAIL PROTECTED]: Recipient address rejected: User unknown in local recipient table) This looks like an alias problem. That was it. There were two places in /etc/postfix/main.cf where alias_maps was set. The final one did not include the mailman aliases file. I checked that darned alias_maps variable 50 times, but didn't check to see if it was set elsewhere in the file. Sigh. Thanks, Mark! Should I add this to the FAQ? I'm using: foo:trb $ rpm -aq|grep mailman mailman-2.1.4-83.4 foo:trb $ rpm -aq|grep postfix postfix-2.1.1-1.4 foo:trb $ uname -a Linux foo 2.6.5-7.104-default #1 Wed Jul 28 16:42:13 UTC 2004 i686 i686 i386 GNU/Linux Mailman and postfix were installed via rpm. There are no entries in /etc/postfix/access. Should there be? Where/how is access to sending email to a list managed? How particular is it in regard to address matching? In other words, does every part of an address have to match the address in the list, or does it just look at the user id? It is done through aliases that match the user id and pipe the message to mailman. The machine is accepting email from the same address when it is sent to a user on the machine, but it is rejected when sent to a Mailman list. I thought this would be in the FAQ, but I can't find it. If you can help me figure this out, I'll add it. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Did you look at FAQ articles 1.7 and 3.14? They both mention aliases. Have you read the INSTALL and README.POSTFIX documents that are in the standard Mailman distribution? Are these or equivalents in your mailman rpm? If you don't have them, you can find them at http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/ -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Unable to get Mailman up and running withqmail/vpopmail
On Sat, 20 Nov 2004 09:02:13 -0800, Mark Sapiro [EMAIL PROTECTED] wrote: Alexander Schwethelm wrote: What doesn't work and this is of course the most important part, is any mail to mailman. Let's say I have a list [EMAIL PROTECTED] and I send an email to this address as a list user, the mail gets stuck in the qmail queue. So I am not even sure if those mails ever reach mailman in order to process the mails? Have you read the README.QMAIL file that comes with the Mailman source distribution? I just want to re-emphasize the importance of the README.QMAIL file, it's only user notes, but those are important notes you need to understand to get mailman working. I'm running the same config (qmail/vpopmail) using lists.mydomain.tld. Some quick tips from me aside from the user notes in the above mentioned readme: Let me jump on the first thing that comes to mind with your described problem. Make sure you have the mailman user's maildir setup (and make sure it's in the mailman user's home directory, which may be setup elsewhere from /home/mailman, like /usr/local/mailman). I'm not actually sure if you need the maildir setup, but it's just good practice. Then if your going the same (easier) route I did setting up mailing lists, make sure you have your .qmail-default file in the mailman home directory with |/usr/bin/python /usr/local/mailman/bin/qmail-to-mailman.py (or where ever you installed mailman). That's all assuming your not doing mailing list aliases manually per list. I highly suggest you take advantage of the qmail-to-mailman.py script. Continuing on, make sure qmail knows where to send emails going to lists.yourdomain.tld by adding lists.yourdomain.tld:mailman in the qmail virtualdomains file (if this isn't setup right, and rcpthosts is, that could be the cause of keeping an email in the queue since it doesn't know where to put it). Make sure you have lists.yourdomain.tld in the rcpthosts file for qmail. From your description, it sounds like this is already done. Last, but not least, if your still having problems, take a look at your qmail logs for any description of what problems may be in the way. Bryan Petty -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
