Re: [Mailman-Users] Problem with explicit destination

2007-01-26 Thread Mark Sapiro
Julia Frizzell wrote: >Just got one in right now, so let's use this one. I've replaced our >@address with @xxx. > >As far as I can see, there's no cc in here. As i said in my original >message, we're running Mailman 2.1.5 on OS X 10.4. We have set >require_explicit_destination to Yes and acc

Re: [Mailman-Users] Problem with explicit destination

2007-01-26 Thread Julia Frizzell
Just got one in right now, so let's use this one. I've replaced our @address with @xxx. As far as I can see, there's no cc in here. As i said in my original message, we're running Mailman 2.1.5 on OS X 10.4. We have set require_explicit_destination to Yes and acceptable_aliases is blank.

Re: [Mailman-Users] Problem with explicit destination

2007-01-26 Thread Mark Sapiro
Julia Frizzell wrote: > >However, some mail still gets through. For example, this came in: > >> To: <[EMAIL PROTECTED]> > >But we're not alliancecoatings.com What about Cc:? If your list's require_explicit_destination is set to Yes, a post should be held if the list posting address or an addres

[Mailman-Users] Problem with explicit destination

2007-01-26 Thread Julia Frizzell
We have a few lists configured to accept all mail addressed to them, mainly as they are email addresses on our website set for people to make inquiries at. We have the lists configured to use explicit destination, and reject anything that is not explicity sent to the list address. However,