[Mailman-Users] Mailman-2.1 / Postfix 2.0 problems

Jon Carnes jonc at nc.rr.com
Thu Dec 4 15:13:07 CET 2003


On Thu, 2003-12-04 at 05:41, M. Lewis wrote:
> I'm running Mailman -2.1.1-4 and Postfix-2.0.16-4.
> 
> Monday morning at 5:00am my logs started filling with messages. As close as I 
> can pin down what initiated the problem was the sending out of users 
> passwords as that cron job starts at 5:00am on the first of the month.
> 
> Since that time, mailman is logging the following errors to smtp-failures:
> 
> Dec 04 02:14:21 2003 (16062) delivery to benncorley at yahoo.com failed with code 
> 450: <mailman-bounces at localhost.localdomain>: Sender address rejected: Domain 
> not found
> Dec 04 02:14:23 2003 (16062) delivery to robert-kuruupkat at comcast.net failed 
> with code 450: <mailman-bounces at localhost.localdomain>: Sender address 
> rejected: Domain not found
> Dec 04 02:14:25 2003 (16062) delivery to ed at bearorifice.com failed with code 
> 450: <mailman-bounces at localhost.localdomain>: Sender address rejected: Domain 
> not found
> Dec 04 02:14:27 2003 (16062) delivery to cpm at bitket.com failed with code 450: 
> <mailman-bounces at localhost.localdomain>: Sender address rejected: Domain not 
> found
> 
> As you can see, the messages are every two seconds apart. So you can imagine 
> how many of these messages I've gotten since 5:00am Monday.
> 
> My guess is it is a problem with Mailman and it's config somehow. What is 
> strange though is Mailman has been running fine for quite some time now. It 
> hasn't been upgraded or touched. I have recently upgraded Postfix to v2.0 so 
> I assume there is some interaction between that upgrade and the mailman 
> config.
> 
> Is there an easy way of fixing this problem short of deleting all lists and 
> re-creating them? I'd hate to lose the archives and have to re-create the 
> lists. I have searched the archives, but haven't really found anything that 
> seemed appropriate.
> 
> Thanks for any pointers!
> Mike

I'm positively stunned sometimes by some of these...

Not to be too disparaging, but you recently upgraded Postfix and now
"Mailman" is giving you errors, sooooooo naturally the problem *must* be
Mailman?

Alright.  Well then go into ~mailman/Mailman/mm_cfg.py and modify the
following...

  DEFAULT_EMAIL_HOST = 'localhost.localdomain'
  DEFAULT_URL_HOST = 'localhost.localdomain'
  # host exists and is resolvable (i.e., if it's the 
  # default of "localhost" be
  # sure there's a localhost entry in your /etc/hosts file!)
  SMTPHOST = 'localhost'


Obviously your old Postfix accepted any locally sent mail - mail sent
directly from applications running on the server.

Now, I understand not accepting mail from "localhost.localdomain" as a
lot of Newbies have that as their servers host name, but really you
should loosen up on your Postfix rule sets and accept any mail from
127.0.0.1 (and make sure that Mailman uses that as the delivery address
- it's the default).  That will also fix this particular problem.

Good Luck - Jon Carnes





More information about the Mailman-Users mailing list