[Mailman-Users] Newbie Question: Can`t send mails to my list

[Mark Sapiro]

Kai Behncke wrote:
>
>Thank you for answering. For me as a mailman/sendmail newbie this is really not easy.
>
>Well, the Mailman aliases I had already inserted in /etc/mail/aliases
>
>like that:
>"mailman:              "|/var/lib/mailman/mail/mailman post mailman"
>mailman-admin:        "|/var/lib/mailman/mail/mailman admin mailman"
>mailman-bounces:      "|/var/lib/mailman/mail/mailman bounces mailman"
>mailman-confirm:      "|/var/lib/mailman/mail/mailman confirm mailman"
>mailman-join:         "|/var/lib/mailman/mail/mailman join mailman"
>mailman-leave:        "|/var/lib/mailman/mail/mailman leave mailman"
>mailman-owner:        "|/var/lib/mailman/mail/mailman owner mailman"
>mailman-request:      "|/var/lib/mailman/mail/mailman request mailman"
>mailman-subscribe:    "|/var/lib/mailman/mail/mailman subscribe mailman"
>mailman-unsubscribe:  "|/var/lib/mailman/mail/mailman unsubscribe mailman"


These are only for the mailman list. You need another set of 10 like

complicate:          "|/var/lib/mailman/mail/mailman post complicate"
complicate-admin:    "|/var/lib/mailman/mail/mailman admin complicate"
etc.

for the 'complicate' list and simarly for all other mailman lists. Then
you need to run the newaliases command to update the actual sendmail
database after you add the aliases to /etc/mail/aliases.

This may fix the entire problem,


>If I look at the sendmail-log is says at /var/log/mail.log (I think this is the right logfile?):
>
>"Sep  9 19:30:00 h1228898 sm-mta[9439]: l89HU0cm009439: from=<complicate-bounces at lists.gforge.geoplp.de>, size=1872, class=-60, nrcpts=1, msgid=<mailman.0.1189358998.9438.complicate at lists.gforge.geoplp.de>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]
>Sep  9 19:30:00 h1228898 sm-mta[9442]: l89HU0vb009442: from=<complicate-bounces at lists.gforge.geoplp.de>, size=1944, class=-60, nrcpts=1, msgid=<mailman.1.1189358998.9438.complicate at lists.gforge.geoplp.de>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]
>Sep  9 19:30:01 h1228898 sm-mta[9444]: l89HU0vb009442: to=<Kai-Behncke at gmx.de>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=229944, relay=mx0.gmx.net. [213.165.64.100], dsn=2.0.0, stat=Sent (Message accepted {mx057})
>Sep  9 19:30:01 h1228898 sm-mta[9441]: l89HU0cm009439: to=<mailman-owner at lists.gforge.geoplp.de>, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=229872, relay=mx0.stratoserver.net. [81.169.163.94], dsn=2.0.0, stat=Sent (OK id=1IUQbh-0001o6-RB)
>Sep  9 19:30:50 h1228898 sm-mta[9451]: l89HUnA7009451: from=<complicate-bounces at lists.gforge.geoplp.de>, size=1957, class=-60, nrcpts=1, msgid=<mailman.0.1189359049.9450.complicate at lists.gforge.geoplp.de>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]
>Sep  9 19:31:09 h1228898 sm-mta[9453]: STARTTLS=client, relay=mail-in-2.serv.uni-osnabrueck.de., version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
>Sep  9 19:31:13 h1228898 sm-mta[9453]: l89HUnA7009451: to=<kbehncke at igf.uni-osnabrueck.de>, delay=00:00:23, xdelay=00:00:23, mailer=esmtp, pri=229957, relay=mail-in-2.serv.uni-osnabrueck.de. [131.173.17.163], dsn=2.0.0, stat=Sent (l89HV4Rg012816 Message accepted for delivery)
>Sep  9 19:31:35 h1228898 sm-mta[9456]: l89HVZZ1009456: from=<complicate-bounces at lists.gforge.geoplp.de>, size=2071, class=-60, nrcpts=1, msgid=<mailman.0.1189359094.9455.complicate at lists.gforge.geoplp.de>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]
>Sep  9 19:31:38 h1228898 sm-mta[9458]: l89HVZZ1009456: to=<kbehncke at igf.uni-osnabrueck.de>, delay=00:00:03, xdelay=00:00:03, mailer=esmtp, pri=230071, relay=mail-in-3.serv.uni-osnabrueck.de. [131.173.17.149], dsn=2.0.0, stat=Sent (l89HVZ6x026973 Message accepted for delivery)"
>
>What could that mean?


Almost all of the above entries are for outgoing notifications from
Mailman. One pair of entries (note the same esmtp id - l89HU0cm009439)
-

Sep  9 19:30:00 h1228898 sm-mta[9439]: l89HU0cm009439:
from=<complicate-bounces at lists.gforge.geoplp.de>, size=1872,
class=-60, nrcpts=1,
msgid=<mailman.0.1189358998.9438.complicate at lists.gforge.geoplp.de>,
proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]

Sep  9 19:30:01 h1228898 sm-mta[9441]: l89HU0cm009439:
to=<mailman-owner at lists.gforge.geoplp.de>, delay=00:00:01,
xdelay=00:00:01, mailer=esmtp, pri=229872, relay=mx0.stratoserver.net.
[81.169.163.94], dsn=2.0.0, stat=Sent (OK id=1IUQbh-0001o6-RB)

is a notice to <mailman-owner at lists.gforge.geoplp.de> from the
complicate list, which has been sent to the MX at mx0.stratoserver.net
which may or may not kno how to send it back.


>You wrote it could be a DNS-problem?
>What do you mean with that?
>Do I need  a DNS-Server to use mailman/sendmail?


No, but you need appropriate DNS records somewhere in order to receive
mail. When I do

dig any lists.gforge.geoplp.de

I see among other things the following records

lists.gforge.geoplp.de. 1800    IN      MX      10 geoplp.de.
lists.gforge.geoplp.de. 1800    IN      MX      20 mx0.stratoserver.net.
lists.gforge.geoplp.de. 1800    IN      A       85.214.90.79
geoplp.de.              1800    IN      A       85.214.90.79

This all looks fine, but it raises the question of why sendmail relayed
the message above to mx0.stratoserver.net when geoplp.de is a higher
priority MX. This is not a DNS problem per se, but perhaps sendmail
determined that geoplp.de (which is the local host) couldn't deliver
to mailman-owner at lists.gforge.geoplp.de.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan