[Mailman-Users] Messages bounce but only for one domain on one list

[Tom Caudron]

Simon said, "So if email is sent to a list subscriber labelled as
johndoe at mydomain.com and mydomain.com is in $mydestination, then it
doesn't matter what the DNS says. Postfix will attempt local delivery.
So you really need $mydestination to only be a subdomain of $mydomain,
and then stop/start Postfix."

Mine is currently "mydestination = $myhostname, localhost.$mydomain"
which works for the other two lists but not for the latest list I
created.  Is there something I'm supposed to run after I create a list
that I haven't?  I don't have a subdomain to use for mydestination. 
Maybe if I give real names it'll be easier to follow and maybe clearer. 
It's such a mess in my mind, I'm worried that I'm not being clear when I
explain it.

I have a domain (digitalelite.com) and that domain's mx is hosted by
another company (1and1.com).

Since 1and1.com doesn't offer mailing lists, I figured I'd set up my
home server (which is is no way associated with digitalelite.com) as the
mailing list server for digitalelite.com.

That home server machine name is Mordor.MiddleEarth (Yep, I'm a geek: my
home network uses the *.MiddleEarth naming convention <g>).

So what I've done is told Postfix not to accept any mail from anywhere
but itself (the external port 25 is blocked by my firewall and I've set
inet_interfaces = localhost in /etc/postfix/main.cf).

I created new lists with /usr/local/mailman/bin/newlist and I've created
an /etc/fetchmailrc that grabs each list address and points it to the
new lists like this:

----
set daemon 60

poll pop.1and1.com protocol pop3
# test mailing list
	username uid7 with password mysecret, is test here;
	username uid8 with password mysecret, is test-request here;
	username uid9 with password mysecret, is test-admin here;
# list1 mailing list
	username uid1 with password mysecret, is list1 here;
	username uid2 with password mysecret, is list1-request here;
	username uid3 with password mysecret, is list1-admin here;
# list2 mailing list
	username uid4 with password mysecret, is list2 here;
	username uid5 with password mysecret, is list2-request here;
	username uid6 with password mysecret, is list2-admin here;
----

When setting things up and trying to get it all working, I created test
and list1 lists.  Those lists work just fine in all respects.  However,
once I thought I had everything working I tried to add a list (list2). 
Only for list 2 do I get this new problem.

I think it has decided that its domain is digitalelite.com, even though
it is not.  Mail addressed to *@digitalelite.com, just for this one
list, coming from the list is getting stopped because Postfix thinks it
should be a local user and throws an error 550 as a result (because
these are not local users).  The mail gets into the archive for list2,
and it goes out to members that are not using digitalelite.com
addresses.

If it were a problem with the mydestination variable in main.cf wouldn't
that affect all lists?  Maybe not.  What could cause this behavior to
only affect some lists and not others?.  I've been staring at these
config files so long now that they are started to jumble up in my brain.

Sorry to be a newbie pest.  I have googled til my fingers bled and still
I can't find an answer there and I'm desperate.  :-)

Anyone that can shed light on this list behavior will be profusely
thanked (sure my thanks are worthless, but they're all I've got <g>)!

-Tom Caudron



On Mon, 2004-02-09 at 12:15, Simon White wrote:
> 09-Feb-04 at 11:50, Tom Caudron (caudron at digitalelite.com) wrote :
> > mydestination = $myhostname, localhost.$mydomain, $mydomain
> > 
> > which didn't fix the problem.
> 
> Postfix will try to deliver $mydestination locally.
> 
> So if email is sent to a list subscriber labelled as
> johndoe at mydomain.com and mydomain.com is in $mydestination, then it
> doesn't matter what the DNS says. Postfix will attempt local delivery.
> 
> So you really need $mydestination to only be a subdomain of $mydomain,
> and then stop/start Postfix.
> 
> If this is not the problem, please enlighten me.
> 
> Cheers,