On Tue, September 11, 2007 18:24, Mark Sapiro wrote: > Alexandros G. Fragkiadakis wrote: > >> >> the last few days i get hundreds of warnings like the following: >> >> Transcript of session follows. >> >> >> Out: 220 xxx.xxx.xxx.xx ESMTP Postfix >> In: ehlo xxx.xxx.xxx.xx >> Out: 250-xxx.xxx.xxx.xx >> Out: 250-PIPELINING >> Out: 250-SIZE 20480000 >> Out: 250-VRFY >> Out: 250-ETRN >> Out: 250-AUTH PLAIN LOGIN >> Out: 250-AUTH=PLAIN LOGIN >> Out: 250-ENHANCEDSTATUSCODES >> Out: 250-8BITMIME >> Out: 250 DSN >> In: mail FROM:<[EMAIL PROTECTED]> size=1059 >> Out: 250 2.1.0 Ok >> In: rcpt TO:<megan> >> Out: 451 4.3.0 <megan>: Temporary lookup failure >> In: rset >> Out: 250 2.0.0 Ok >> In: quit >> Out: 221 2.0.0 Bye >> >> >> >> For some reason mailman tries to send email to users like "megan". This >> user does not even exist. >> >> Do you have any ideas what can be wrong? >> > > > First, your MTA appears to be doing DNS verifies during SMTP from > Mailman. This is not good. See > <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.011.htp>. > > > When your MTA receives the 'rcpt TO:<megan>' and responds with a '451', > Mailman queues the message in it's retry queue and retries in 15 > minutes. Thus the vast number of attempts to send to 'megan'. > > The 'megan' address can come from anywhere. It is unlikely to be a list > member, but it may be an owner or moderator. Mailman's > > bin/find-member --owner megan > > will find an owner or mmember, but not a moderator. > > More likely, this is a rejection notice in response to a non-member > post (undoubtedly spam) to a list. > > You need to find Mailman's retry queue (normally qfiles/retry, but in > FHS compliant RedHat /var/spool/mailman/retry). You can look at the > entry/entries with > > bin/show_qfiles qfiles/retry/* > > which will show you the contents of the entries. From this, you can then > determine the list and whether this is an owner or moderator or just spam > and remove the unwanted files from the queue. > > --
Thanks, it stopped now. Probably a spam caused this. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------ 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=show&file=faq01.027.htp