On 11.08.2011 17:01, Mark Sapiro wrote: > On 8/9/2011 11:46 PM, James Brown wrote: >> I have a vds under Free-BSD-8.1-STABLE which I use for maintaining of >> public sites and etc. >> Under that vds I have a mailing system which consits from an exim-4.76 >> which receives and sends emails to/from local mail users and >> dovecot-1.2.17 which lets get receiving post to email-clients. >> I want to set up the Mailman for maintaining post lists. >> Firstly, created subdomain 'list.somename.name' in my bind-settings. It >> works correctly. >> Then, after installing the Mailman from ports, I set up my Apache to >> work with it. My Apache wokrs correctly too. >> Then I checked and changed my exim configuration file and etc and tested >> list verification command with the next result: >>> exim -bt n...@list.somename.name >>> Address rewritten as: n...@list.somename.name >>> n...@list.somename.name >>> <-- n...@list.somename.name >>> <-- n...@list.somename.name >>> <-- n...@list.somename.name >>> router = localuser, transport = local_delivery > > > For some reason, your 'mailman' router is not meeting all it's > conditions and Exim is proceeding to 'localuser'.
I found what was wrong in my exim configuration and now I have the next: > exim -bt n...@list.somename.name > Address rewritten as: n...@list.somename.name > n...@list.somename.name > <-- n...@list.somename.name > <-- n...@list.somename.name > router = mailman, transport = mailman Is your definition > > MAILMAN_HOME=/usr/local/mailman > > correct? I.e. are your lists in the directory /usr/local/mailman/lists? > Yes, it is. That is a configuration creating when installing the Mailman on the FreeBSD system from ports. Maybe it needs to me to install the Mailman from sources into home directory? > >> Further I created a site-wide mailing list and a mailing list as in >> described in /usr/local/share/doc/mailman/mailman-install.txt but it is >> not works well. >> It is possible to subscribe to list throwgh the web-form, it is possible >> to receive emails after that for subsribing confirmation to local email >> users which I tried to subsribe, is is possible to confirm subscription >> through the web but not through email > > > Because email to mailman doesn't work as above. > I improve the above but now I have the next: > 1QsvUg-0004Bz-06 <= a...@somename.name H=hostname ([0.0.0.0]) > [76.11.218.145] P=esmtpsa X=TLSv1:CAMELLIA256-SHA:256 > A=plain:a...@somename.name S=744 id=4e49050b.5050...@somename.name from > <a...@somename.name> for n...@list.somename.name > 1QsvUg-0004Bz-06 ** n...@list.somename.name (n...@list.somename.name) > <n...@list.somename.name> R=mailman T=mailman: Child process of mailman > transport returned 2 from command: /usr/local/mailman/mail/mailman > 1QsvUg-0004Bz-06 Completed The subscribes receives the next emails: > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > n...@list.somename.name > local delivery failed So, there are neither emails in the list (through e-mail) nor in the web-archive. > >> and it is impossible to receive >> emails from list and to see the archive sending to list throupgh the web. > > > Presumably this is again because mail TO the list is not received by > Mailman. > > >> With accordance to the above I have some questions: >> 1) What I do wrong? > > > For some reason, Exim is not routing list mail per the 'mailman' router. > The only thing I see is that the "require_files = > MAILMAN_HOME/lists/$local_part/config.pck" is not satisfied, presumably > because MAILMAN_HOME is not defined to the correct path. > ls -l /usr/local/mailman total 36 drwxrwsr-x 11 root mailman 1536 8 ��� 16:50 Mailman drwxrwsr-x 4 root mailman 512 8 ��� 12:09 archives drwxrwsr-x 2 root mailman 1024 8 ��� 12:09 bin drwxrwsr-x 2 root mailman 512 8 ��� 12:09 cgi-bin drwxrwsr-x 2 root mailman 512 8 ��� 12:09 cron drwxrwsr-x 2 root mailman 512 10 ��� 09:36 data drwxrwsr-x 2 root mailman 512 8 ��� 12:09 icons drwxrwsr-x 4 root mailman 512 8 ��� 12:45 lists drwxrwsr-x 2 root mailman 512 15 ��� 12:00 locks drwxrwsr-x 2 root mailman 512 13 ��� 07:30 logs drwxrwsr-x 2 root mailman 512 8 ��� 12:56 mail drwxrwsr-x 38 root mailman 512 8 ��� 12:09 messages drwxrwsr-x 2 root mailman 512 8 ��� 12:09 pythonlib drwxrwsr-x 11 root mailman 512 8 ��� 12:26 qfiles drwxrwsr-x 2 root mailman 512 8 ��� 12:09 scripts drwxrwsr-x 2 root mailman 512 8 ��� 12:09 spam drwxrwsr-x 39 root mailman 512 8 ��� 12:09 templates drwxrwsr-x 4 root mailman 512 8 ��� 12:09 tests pkg_info -L mailman-2.1.14_5 Information for mailman-2.1.14_5: Files: /usr/local/www/icons/PythonPowered.png /usr/local/www/icons/mailman.jpg /usr/local/www/icons/mm-icon.png /usr/local/www/icons/powerlogo.gif /usr/local/mailman/Mailman/Archiver/Archiver.py /usr/local/mailman/Mailman/Archiver/Archiver.pyc /usr/local/mailman/Mailman/Archiver/HyperArch.py /usr/local/mailman/Mailman/Archiver/HyperArch.pyc /usr/local/mailman/Mailman/Archiver/HyperDatabase.py /usr/local/mailman/Mailman/Archiver/HyperDatabase.pyc /usr/local/mailman/Mailman/Archiver/__init__.py /usr/local/mailman/Mailman/Archiver/__init__.pyc /usr/local/mailman/Mailman/Archiver/pipermail.py /usr/local/mailman/Mailman/Archiver/pipermail.pyc /usr/local/mailman/Mailman/Autoresponder.py /usr/local/mailman/Mailman/Autoresponder.pyc /usr/local/mailman/Mailman/Bouncer.py /usr/local/mailman/Mailman/Bouncer.pyc /usr/local/mailman/Mailman/Bouncers/AOL.pyc /usr/local/mailman/Mailman/Bouncers/AOL.py /usr/local/mailman/Mailman/Bouncers/BouncerAPI.py /usr/local/mailman/Mailman/Bouncers/BouncerAPI.pyc /usr/local/mailman/Mailman/Bouncers/Caiwireless.py /usr/local/mailman/Mailman/Bouncers/Caiwireless.pyc and etc. Is it wrong? > >> 2) Where is I need to indicate aliases after creating the new list - in >> /etc/aliases (which is a symbolic link to /etc/mail/aliases in FreeBSD) >> or in /usr/local/etc/exim/aliases? > > > You don't need aliases. List mail should be handled by the 'mailmen' > router and the 'mailman' transport. > I.e. I don't need create aliases which indicates by mailman after creating lists such the next: "The mailing list `news' has been created via the through-the-web interface. In order to complete the activation of this mailing list, the proper /etc/aliases (or equivalent) file must be updated. The program `newaliases' may also have to be run. Here are the entries for the /etc/aliases file: news: "|/usr/local/mailman/mail/mailman post news" news-admin: "|/usr/local/mailman/mail/mailman admin news" news-bounces: "|/usr/local/mailman/mail/mailman bounces news" news-confirm: "|/usr/local/mailman/mail/mailman confirm news" news-join: "|/usr/local/mailman/mail/mailman join news" news-leave: "|/usr/local/mailman/mail/mailman leave news" news-owner: "|/usr/local/mailman/mail/mailman owner news" news-request: "|/usr/local/mailman/mail/mailman request news" news-subscribe: "|/usr/local/mailman/mail/mailman subscribe news" news-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe news"" > >> 3) Does it need to create in the /usr/local/etc/exim/passwd email-users >> such as maillistn...@list.somename.name or not? > > > No. > Very thanks for information, I have deleted those users. > >> I don't read any about it in >> /usr/local/share/doc/mailman/mailman-install.txt and here >> http://www.exim.org/howto/mailman21.html and firstly I did not create 'em. >> I had the next exim logs that time: >> >>> H=mail.somename.name [xxx.xxx.xxx.xxx] sender verify fail for >>> <news-boun...@list.somename.name>: all relevant MX records point to >>> non-existent hosts >>> H=mail.somename.name [xxx.xxx.xxx.xxx] F=<news-boun...@list.somename.name> >>> rejected RCPT <mailman-ow...@list.somename.name>: Sender verify failed >>> H=mail.somename.name [xxx.xxx.xxx.xxx] sender verify fail for >>> <news-boun...@list.somename.name>: all relevant MX records point to >>> non-existent hosts >>> H=mail.somename.name [xxx.xxx.xxx.xxx] F=<news-boun...@list.somename.name> >>> rejected RCPT <a...@somename.name>: Sender verify failed >>> H=router45-readme.domainname1.net ([0.0.0.0]) [xxx.xxx.xxx.xxx] >>> F=<a...@somename.name> rejected RCPT <mailman-requ...@list.somename.name>: >>> all relevant MX records point to non-existent hosts > > > The sender verify errors are a different issue. It appears that your > list domain (list.somename.name) is not in > > domainlist local_domains = lsearch;/usr/local/etc/exim/domains > > so is not considered a local domain. > But my list domain indicated there (the second line): $cat domains somename.name:somename.name:a...@somename.name:no list.somename.name:list.somename.name:a...@somename.name:no Maybe it needs to use another syntax than for the main email domain (the first line)? > >> 4) If I need to create an email user for lists in >> /usr/local/etc/exim/passwd, how I can indicate to the Mailman its >> password for authentificaton? Or what I need to do instead? > > > You don't need local users for Mailman. > > >> 5) If I need to create an email user for lists in >> /usr/local/etc/exim/passwd, what is home directory of it I need to indicate? > > > You don't need this. > Thanks > >> As I think, I need to indicate one of the directories existing in >> /usr/local/mailman/archives, probably >> /usr/local/mailman/archives/public/nameoflist? >> I created public list named "news" through the web-form, but it was >> created the next symbolic link: >>> ls -l /usr/local/mailman/archives/public >>>> lrwxr-xr-x 1 mailman mailman news -> >>>> /usr/local/mailman/archives/private/news >> not a directory. > > > The symlink is correct. > > >> So I have the next too: >>> ls -l /usr/local/mailman/archives/private >>> total 8 >>> drwxrwsr-x 2 root mailman 512 mailman >>> drwxrwsr-x 2 root mailman 512 mailman.mbox >>> drwxrwsr-x 2 mailman mailman 512 news >>> drwxrwsr-x 2 mailman mailman 512 news.mbox > > > This looks correct. > > >> When I tried to indicate it as the email user "news" home directory in >> /usr/local/etc/exim/passwd and when I tried to indicate >> /usr/local/mailman/archives/private/news or >> /usr/local/mailman/archives/private/news.mbox as it, after sending an >> email to the list I had the next exim logs: >> >>> 1Qqh5b-0001Qz-Kx == n...@list.somename.name (n...@list.somename.name, >>> n...@list.somename.name) <n...@list.somename.name> R=localuser >>> T=local_delivery defer (13): Permission denied: while creating mailbox >>> /usr/local/mailman/archives/private/news.mbox/mbox >>> 1Qqh5b-0001Qz-Kx == n...@list.somename.name (n...@list.somename.name, >>> n...@list.somename.name) <n...@list.somename.name> R=localuser >>> T=local_delivery defer (-52): Retry time not yet reached > > > This is all because the mail is not using the 'mailman' router. Fix that > problem and everything should work. > But now, after fixing, it have new errors (see above). > >> 6) As I use an email system for my usual needs consists from exim + >> dovecot, do I need to include the dovecot in working with my Mailman >> email list by any method? > > > No. > Thanks ------------------------------------------------------ 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