[Mailman-Users] problem with mailman not working...
Troy Campbell
troy.campbell at fedex.com
Fri Jan 13 03:09:41 CET 2012
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/aliases hash:/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.$mydomain localhost
localhost.localdomain request1.localdomain
request2.localdomain
request1.rmtc.fedex.com
request2.rmtc.fedex.com
mailman.rmtc.fedex.com mailman2.rmtc.fedex.com
mynetworks = 127.0.0.1/32 146.18.0.0/16
155.161.0.0/16 161.135.0.0/16
165.150.0.0/16 170.5.0.0/16
170.86.0.0/16 172.18.64.0/18
192.189.184.0/22 198.140.0.0/22
199.81.0.0/16 199.82.0.0/16
204.135.100.0/23 204.135.106.0/23
204.135.108.0/23 204.135.92.0/23
204.135.94.0/23 204.135.96.0/23
204.135.97.0/23 172.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.com rmtc.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/access permit_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=troytest at 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=<troytest at 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?
>
More information about the Mailman-Users
mailing list