Re: [Mailman-Users] Erratic mail delivery times

[Mark Sapiro]

On 07/21/2014 06:50 PM, Peter Shute wrote:
> 
> That was my impression too. It sounds less disruptive, but I wonder if the 
> resulting variability of behaviour of Reply and Reply all would just cause 
> confusion.


In 2.1.18-1, with minor exceptions, 'reply' and 'reply all' do the same
things on a munged message as on a non-munged message. The exceptions
are due to the fact that in 2.1.18-1 the Munge From action always puts
the original From: in Reply-To: so the original From: is always
somewhere. The implication of this is that with list settings
first_strip_reply_to = Yes and reply_goes_to_list = This List, in the
unmunged case, reply goes only to the list and in the munged case, it
goes to the list and the original From: which may mean the original
From: gets a dupe or only a direct and not a list copy.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Moving Archive Lists

[Mark Sapiro]

On 07/21/2014 08:43 PM, Stephen J. Turnbull wrote:

> 
> How old was the old Mailman?  AFAIK old configs should automatically
> be upgraded if necessary when you upgrade Mailman, unless they're very
> very old (< 2.1.9 at a guess).


Way older than that. Even config.db files from Mailman 2.0.x will be
properly converted/upgraded. There's even code in Mailman/versions.py,
which is what does the work, to address Mailman 1.0 lists, but I won't
guarantee it works on 1.0.x or the oldest 2.0.x config.db files but it
does the best it can to map things as closely as possible to their
current equivalents.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Senders' email addresses not in archives

[Mark Sapiro]

On 07/21/2014 09:14 PM, Stephen J. Turnbull wrote:
> Conrad G T Yoder writes:
> 
>  > [Using 2.1.17]
>  > 
>  > Is there a way to have their email addresses get into the archives
>  > and still have the Mung From option turned on?
> 
> It looks to me (version 2.1.18, though) like the from corruption is
> performed in the CookHeaders Handler.  Perhaps you can move the
> ToArchive Handler ahead of CookHeaders in the global pipeline (or list
> by list if you prefer).  If I were you I'd wait for confirmation from
> Mark that that's safe, though. :-)  It *should* be safe (since
> subscriber delivery takes place after ToArchive, ToArchive must be
> working on copies of the message and metadata or it would mess delivery
> up), but I haven't audited the code.


In 2.1.16 and 2.1.16, the message gets Munged in CookHeaders as Stephen
suggests. Thus it's the Munged message that gets archived and included
in digests and gated to Usenet.

Beginning in 2.1.18, CookHeaders still determines what to do with
headers like From: and Reply-To:, but they aren't actually changed
there. Essentially, CookHeaders tells WrapMessage what to do and
WrapMessage does it.


> To do this, GLOBAL_PIPELINE is a Python list, in Defaults.py.  Copy
> the whole line to mm_cfg.py, and edit it to move the ToArchive (and
> its trailing comma) ahead of CookHeaders.  The usual caveat about
> "don't ever edit Defaults.py" applies here.


That would work and is safe, but instead, I would move CookHeaders to a
place just after ToUsenet.

This can be done as Steve suggests by Copying the whole GLOBAL_PIPELINE
list to mm_cfg.py and editing it there, but this leads to problems if
GLOBAL_PIPELINE is changed in a subsequent release. A better way is to
put something like

GLOBAL_PIPELINE.remove('CookHeaders')
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('AfterDelivery'),
'CookHeaders')

in mm_cfg.py. The first line removes CookHeaders from GLOBAL_PIPELINE.
The second line[1] inserts CookHeaders in GLOBAL_PIPELINE ahead of
AfterDelivery which is just after ToUsenet.

This way if GLOBAL_PIPELINE is changed in a subsequent release, the
changes in Defaults.py will be effective because mm_cfg.py is not
overriding the whole thing but just moving something.

[1] The second line is probably wrapped here, but it doesn't mater if it
is or not as Python ignores line breaks inside parens. I.e.,

(xxx\nyyy)

is the same as

(xxxyyy)

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Erratic mail delivery times

[Peter Shute]

Stephen J. Turnbull wrote:
>  > That was my impression too. It sounds less disruptive, but 
> I wonder  > if the resulting variability of behaviour of 
> Reply and Reply all  > would just cause confusion.
> 
> But you're right, people do report the difference.  So it 

It's the people who don't notice the difference that I'm worried about. If 
someone has been relying on the fact that clicking Reply will create a private 
reply, they're going to try it on a munged one and not notice. Then it'll be 
them defending themselves for whatever inappropriate remark they've 
accicentally sent to the list, not the Yahoo user. I can see myself getting 
caught out by it, it's hard to remember to look how it's set up.

I'm still all for rejecting and forwarding them by hand, with an explanatory 
note at the top. Then at least the private replies will only go to me. But we 
need 2.1.18-1 to help us detect them reliably.

> N.B.  You're posting from edu.au.  Do you really have that 
> many yahoo.COM users that you care about a difference in 
> their treatment?
> If the majority of your Yahoo!/AOL users are from a different 
> country, they may very well *not* have "p=reject" policies.  Eg:

I did recently realise they weren't all affected, but most of our yahoo users 
are on yahoo.com.

Peter Shute
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Senders' email addresses not in archives

[Stephen J. Turnbull]

Conrad G T Yoder writes:

 > [Using 2.1.17]
 > 
 > Is there a way to have their email addresses get into the archives
 > and still have the Mung From option turned on?

It looks to me (version 2.1.18, though) like the from corruption is
performed in the CookHeaders Handler.  Perhaps you can move the
ToArchive Handler ahead of CookHeaders in the global pipeline (or list
by list if you prefer).  If I were you I'd wait for confirmation from
Mark that that's safe, though. :-)  It *should* be safe (since
subscriber delivery takes place after ToArchive, ToArchive must be
working on copies of the message and metadata or it would mess delivery
up), but I haven't audited the code.

To do this, GLOBAL_PIPELINE is a Python list, in Defaults.py.  Copy
the whole line to mm_cfg.py, and edit it to move the ToArchive (and
its trailing comma) ahead of CookHeaders.  The usual caveat about
"don't ever edit Defaults.py" applies here.

HTH

Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Erratic mail delivery times

[Stephen J. Turnbull]

Peter Shute writes:

 > That was my impression too. It sounds less disruptive, but I wonder
 > if the resulting variability of behaviour of Reply and Reply all
 > would just cause confusion.

Well, I can get away with a policy of "Friends don't let friends use
Yahoo!" and be ornery about it, so take my advice with a grain of
salt.  But I just blame Yahoo! and tell yahoo.com users (other yahoo.*
domains don't have this policy) to lump it.

But you're right, people do report the difference.  So it depends on
how many users who prefer to post from Yahoo! you have.  (In my case,
most of my Yahoo! users say "I should have got rid of my Yahoo!
account long ago.)

N.B.  You're posting from edu.au.  Do you really have that many
yahoo.COM users that you care about a difference in their treatment?
If the majority of your Yahoo!/AOL users are from a different country,
they may very well *not* have "p=reject" policies.  Eg:

$ dig +short _dmarc.yahoo.com.au TXT
"v=DMARC1\; p=none\; pct=100\; rua=mailto:dmarc-yahoo-...@yahoo-inc.com\;";

Note the "p=none".  Australian Yahoo! users don't have a reject policy
in place (yet).

Steve

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Moving Archive Lists

[Stephen J. Turnbull]

Don:

 > I’m attempting to bring it up on a new box with a yum-supplied copy
 > of mailman rather than the old-fashioned hand install.

Some systems put the configs and so on in a different place from the
"standard" mailman install.  I infer that you have the right place,
but please confirm.  On my Debian system, list configs look like

/var/lib/mailman/lists/LISTNAME/config.pck

and I've never seen a system that didn't conform to the
.../mailman/lists/LISTNAME/config.pck pattern.

 > The yum-supplied new mailman version is not the same as the version
 > on the old server,

How old was the old Mailman?  AFAIK old configs should automatically
be upgraded if necessary when you upgrade Mailman, unless they're very
very old (< 2.1.9 at a guess).

 > But the old archive lists, in the same directory with the same
 > permissions, are not showing up.

Please clarify what you mean by "old archive lists not showing up."
What's not showing up?  The list archives?  The public lists in the
mailman/listinfo page in the admin website?  It doesn't deliver posts
to those lists?  More than one of the above (please specify)?
Something else?

 > Is there some pck database file I need to upgrade or massage to
 > have the old lists be recognized?

No, Mailman 2.1 recognizes lists by the presence of a config.pck file
in the lists/ directory.  If you have the right place and
the version of Mailman that created the configs was not locally
modified and not decades old, it should recognize those configs.

HTH

Steve
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Yahoo webmail stripping out headers in digests

[Conrad G T Yoder]

Another episode in the “Just Noticed” saga: In Yahoo’s webmail, they are 
stripping out the headers of each email in the digests, so that you can’t even 
tell where a new message starts in the digest, let alone who actually sent it.  
Anyone had experience with this and know of a way to get all the individual 
headers shown again?

-Conrad

--
Truth is information.

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Senders' email addresses not in archives

[Mark Sapiro]

On 07/21/2014 07:58 PM, Conrad G T Yoder wrote:
> [Using 2.1.17]
> 
> I just realized that with the DMARC mitigation “Mung From” option turned on, 
> the senders’ email addresses are not showing up in the archives.  So, 
> basically impossible to contact them unless replying to the whole list, 
> and/or the original sender put their address somewhere in the body of the 
> message.  Is there a way to have their email addresses get into the archives 
> and still have the Mung From option turned on?


This is fixed in Mailman 2.1.18 (by not Munging the From: in archived
messages). While a fix could be backported to 2.1.17, it would probably
be easier to upgrade.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] unable to access admin interface

[Stephen J. Turnbull]

Chad Rebuck writes:

 > I'm not able to access the admin interface.  I don't reach the page
 > where I can enter my admin password.  The mailman error log doesn't
 > show anything.
 >  I'm running mailman 2.1.18-1.
 > 
 > This message appears:
 > 
 > Gateway Timeout
 > 
 > The gateway did not receive a timely response from the upstream server or
 > application.

This error doesn't indicate a Mailman problem, but rather a network or
webserver problem.  A timeout indicates that the gateway couldn't
contact the webserver at all (which is not part of Mailman, but a
completely separate package).  To check:

1.  Are you using the correct URL (including port; maybe your Mailman
is configured to use https: rather than http: or something like
that)?
2.  Is there a webserver running on the Mailman host?
3.  Is it listening to the port you're using (probably 80 = http, but
possibly 443 = https or even something else)?
4.  Is there a firewall protecting port 80 (or 443 if you're using
https: URLs) between your gateway (proxy server) and the Mailman
host?
5.  If there is a webserver running, check that it it configured to
provide CGI services (lack of CGI should not result in a network
timeout, but rather a 404 No Such Page from the webserver, or
perhaps a permission failure error -- but you never know).  Still,
I'd bet on #2 or #3 here.

HTH

Steve

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Need help with mailman bug

[Mark Sapiro]

On 07/21/2014 12:27 PM, iva.viane...@crorec.hr wrote:
> Hello,
> 
> I desperately need your help. We've been using Mailman newsletter lists
> for over 4 years now and it always worked fantastic. This morning we've
> moved to a different hosting / server and Mailman displays this bug:


See my comment in your bug report at
.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Senders' email addresses not in archives

[Conrad G T Yoder]

[Using 2.1.17]

I just realized that with the DMARC mitigation “Mung From” option turned on, 
the senders’ email addresses are not showing up in the archives.  So, basically 
impossible to contact them unless replying to the whole list, and/or the 
original sender put their address somewhere in the body of the message.  Is 
there a way to have their email addresses get into the archives and still have 
the Mung From option turned on?

-Conrad

--
Is there a suspect in your family? Contact the Ministry of Information. Ring  
100 00 00.

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] postfix errors

[Jimmy]

> > With open source software, 3rd party guides need to be treated with
> > care.

Very true, I stumbled upon the other instructions and got that mixed up
with what I was working on. I backed it all out and got it working now.
Thanks!


On Mon, Jul 21, 2014 at 8:51 PM, Stephen J. Turnbull 
wrote:

> Jimmy writes:
>
>  > I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does
> not
>  > exist on my system, postfix-to-mailman.py  isn't anywhere on my system
> at
>  > all, so that obviously presents a problem. Is that not normally in the
> RPM
>  > installation?
>
> That's right.  IIRC, postfix-to-mailman.py was developed by Bruce
> Perens and adopted by Debian because it fits their configuration
> management philosophy better.  AFAIK you'll find it on Debian and
> derivatives but not elsewhere.
>
>  > > I used the 'integrating mailman and postfix' guide but don't see
>  > > what I need to do to fix it.  Thanks
>
> With open source software, 3rd party guides need to be treated with
> care.
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Moving Archive Lists

[McGregor, Donald (Don) (CIV)]

I had a server blow up on me. It’s dead, Jim, but I have backups of the 
/usr/local/mailman directory, and
I’m attempting to bring it up on a new box with a yum-supplied copy of mailman 
rather than the
old-fashioned hand install.

I’ve got the yum-supplied version configured, and can create new lists. But the 
old archive
lists, in the same directory with the same permissions, are not showing up. The 
yum-supplied
new mailman version is not the same as the version on the old server, and I 
can’t really bring
up the old server without some heroic measures.

Is there some pck database file I need to upgrade or massage to have the old 
lists
be recognized?
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Need help with mailman bug

[iva . vianello]

Hello,

I desperately need your help. We've been using Mailman newsletter lists
for over 4 years now and it always worked fantastic. This morning we've
moved to a different hosting / server and Mailman displays this bug:

---

Bug in Mailman version 2.1.18-1

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster can find this information in the Mailman error logs.

--

This message pops up in administration panel when I try to access the page
where I usually confirm to send out or delete newsletters.

Can you help me? I can't send any newsletters out.

Thanks, Iva

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] unable to access admin interface

[Chad Rebuck]

I'm not able to access the admin interface.  I don't reach the page where I
can enter my admin password.  The mailman error log doesn't show anything.
 I'm running mailman 2.1.18-1.

This message appears:

Gateway Timeout

The gateway did not receive a timely response from the upstream server or
application.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] postfix errors

[Mark Sapiro]

On 07/21/2014 10:43 AM, Jimmy wrote:
> I just found where the postfix-to-mailman line came from:
> 
> http://wiki.list.org/display/DOC/Integrating+Mailman+with+postfix
> 
> And see that Mark specifically recommends not using this doc. I'm backing
> that config out.


Thanks for bringing that FAQ up. It is terribly misleading despite the
Warning I added in sec 4. I didn't write it, and I have now added a
stronger warning against following it at the top.

I see from other posts that you have things working now. I'm glad you
got it straightened out.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Erratic mail delivery times

[Peter Shute]

Stephen J. Turnbull wrote:

> IIRC the big difference between 2.1.17 and 2.1.18-1[1] is that in
> 2.1.17 the DMARC-mitigation features[2] are applied to *all* 
> posts, whereas in 2.1.18 you have the option of checking the 
> DMARC policy and only making those ugly changes to posts 
> *from domains with a "p=reject"
> DMARC policy* (requires an additional Python package to make 
> the DNS check for the policy).

That was my impression too. It sounds less disruptive, but I wonder if the 
resulting variability of behaviour of Reply and Reply all would just cause 
confusion.

Peter Shute
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Erratic mail delivery times

[Stephen J. Turnbull]

Peter Shute writes:

 > Thanks, Dave. How are you coping with yahoo emails if you've only
 > got 2.1.17? I can't remember what changes it's got in it, but I
 > thought the latest dealt with it better.

IIRC the big difference between 2.1.17 and 2.1.18-1[1] is that in
2.1.17 the DMARC-mitigation features[2] are applied to *all* posts,
whereas in 2.1.18 you have the option of checking the DMARC policy and
only making those ugly changes to posts *from domains with a "p=reject"
DMARC policy* (requires an additional Python package to make the DNS
check for the policy).  You can also (in >= 2.1.18) "preemptively"[3]
reject such posts before trying to distribute them, and thus
distribute only posts that will not trigger DMARC rejects.

2.1.18-1 may also have some minor improvements in bounce handling, but
as far is I know this is still problematic as many receiving hosts
don't tell you that it's a DMARC reject, and even those that do have a
wide variety of idioms for indicating that.  So many DMARC rejects
will increment subscribers' bounce counts, even though the reject was
instigated by the poster's service provider.

Steve


Footnotes: 
[1]  Avoid 2.1.18, it has a bug that is fatal on some systems.

[2]  Encapsulation in a mini-digest which is From: mailman, or
directly munging from so that the address that appears there is
mailman's address, not the poster's.  The Reply-To field is tweaked so
that the poster can be addressed without copying the address by hand.

[3]  Usually at the Mailman host the post will pass the DMARC check,
and so the Mailman host's MTA may participate in DMARC protocols but
it will still deliver to Mailman regardless of DMARC policy at the
source.  However, due to the nature of the protocol, a Mailman list
which changes the post (even just a list tag in the Subject) will
necessarily fail the check, so Mailman knows when a DMARC reject of
distributed posts will occur.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] postfix errors

[Stephen J. Turnbull]

Jimmy writes:

 > I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not
 > exist on my system, postfix-to-mailman.py  isn't anywhere on my system at
 > all, so that obviously presents a problem. Is that not normally in the RPM
 > installation?

That's right.  IIRC, postfix-to-mailman.py was developed by Bruce
Perens and adopted by Debian because it fits their configuration
management philosophy better.  AFAIK you'll find it on Debian and
derivatives but not elsewhere.

 > > I used the 'integrating mailman and postfix' guide but don't see
 > > what I need to do to fix it.  Thanks

With open source software, 3rd party guides need to be treated with
care.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Erratic mail delivery times

[Brian Carpenter]

The latest version (which we offer) offers additional moderation features
that gives list administrators more options in working with ISPs with poor
DMARC policies.

https://mail.python.org/pipermail/mailman-announce/2014-April/000188.html


Brian Carpenter
EMWD.com

Providing Cloud Services and more for over 15 years.

T: 336.755.0685
E: br...@emwd.com
www.emwd.com
www.mailmanhost.com


 



> -Original Message-
> From: Mailman-Users [mailto:mailman-users-
> bounces+brian=emwd@python.org] On Behalf Of Peter Shute
> Sent: Monday, July 21, 2014 2:56 PM
> To: Dave Nathanson
> Cc: mailman-users@python.org
> Subject: Re: [Mailman-Users] Erratic mail delivery times
> 
> Thanks, Dave. How are you coping with yahoo emails if you've only got
> 2.1.17? I can't remember what changes it's got in it, but I thought the
latest
> dealt with it better.
> 
> Peter Shute
> 
> Sent from my iPad
> 
> > On 22 Jul 2014, at 3:59 am, "Dave Nathanson" 
> wrote:
> >
> > Hi Peter,
> > To answer your question, Dreamhost has the *almost* newest version of
> MailMan 2.1.17. They upgraded just as 2.1.18 came out and had already
> tested 2.1.17 so they went with that. And this version does have the most
> important DMARC mitigation features. So it is working for us.
> >
> > I have never had any problem with DreamHost imposing a message
> sending cap on their "1-Click" installs of Mailman. I run several
discussion lists
> there completely without incident, for 8 years Until this whole
> Yahoo/demarc mess. And we are back to normal. No host is perfect, but
> considering the low price & all the "unlimited everything" they offer, I'm
very
> happy with mine. Considering the price you have been paying, you will most
> likely need to pay more to get out of this problem, but maybe not much
> more.
> > http://www.dreamhost.com/r.cgi?250640/hosting.html
> >
> > Best,
> > Dave Nathanson
> > Mac Medix
> >
> >
> >> On Jul 20, 2014, at 1:35 PM, Peter Shute  wrote:
> >>
> >> No, it's all hosted via cpanel. Does this mail per hour limit seem odd
with
> that sort of setup?
> >>
> >> Does dreamhost keep their mailman up to date? We're still on 2.1.15,
and
> when I asked about upgrading, they wouldn't commit to any date, only that
it
> would be more likely to be months than a month.
> >>
> >> Peter Shute
> >>
> >> Sent from my iPad
> >>
> >>> On 21 Jul 2014, at 1:35 am, "Dave Nathanson"
>  wrote:
> >>>
> >>> I'm surprised that any web/email host would apply a rule intended for
a
> personal email account to a listserve. I'm guessing that you are running
> MailMan on your own computer, then using mail server provided by your
> email hosting company to send the messages. So to the email host, you do
> look like a very busy personal account.
> >>>
> >>> As I see it, your options include:
> >>>
> >>> * Discuss this limitation with your email host & see if they will
waive the
> message sending cap for your listserv.
> >>> * Use a mailman installation hosted by your email hosting company,
> which is not subject to a message sending cap.
> >>> * Changing email hosts & using a mailman installation hosted by your
> email hosting company, which is not subject to a message sending cap.
> >>>
> >>> No need to change registrars. NameCheap is a good registrar, better
> than many. I haven't used their web/email hosting.
> >>>
> >>> My email lists are all running on Mailman provided by my email host.
You
> don't even need to install it, just choose a dedicated subdomain for it to
run
> on. They do NOT limit message flow from Mailman, although they do limit
> the number of messages per hour sent from a personal mail account. No
> web/email host is perfect, but I'm pretty happy with DreamHost. Especially
> for about $100 a year for more services than I can possibly use. (And I'm
> giving it a good go!).
> >>>
> >>> Here is a Dreamhost Coupon code & link that will give you $10 off now,
> plus 1 free LIFETIME domain registration. So that's a savings of about $11
a
> year for life. MACMEDIXFREEDOM  What else is included? Tons! Check it out.
> >>> http://www.dreamhost.com/r.cgi?250640/hosting.html
> >>>
> >>> Best,
> >>> Dave Nathanson
> >>> Mac Medix
> >>>
>  On Jul 20, 2014, at 4:38 AM, Russell Woodford
>  wrote:
> 
>  Hi Peter, Mark and all
> 
>  I think I may have the solution now (Peter is one of our list
> moderators).
>  My web host is now telling me that there is a 200 emails per hour
limit
> for
>  my hosting plan. We have 1140 subscribers. That means we blow the
> limit out
>  of the water EVERY time someone posts!
> 
>  I'm not sure why they have taken so long to tell me this, as we've
been
>  running on this host for over 7 months, but it seems they throttle
the
>  outgoing mail volume, so it can take a while for all those recipients
to
>  get each message. I suppose it depends on overall server activity -
if
>  nothing else is happening, then maybe a new message does get
> straight to
>  114

Re: [Mailman-Users] Erratic mail delivery times

[Peter Shute]

Thanks, Dave. How are you coping with yahoo emails if you've only got 2.1.17? I 
can't remember what changes it's got in it, but I thought the latest dealt with 
it better.

Peter Shute 

Sent from my iPad

> On 22 Jul 2014, at 3:59 am, "Dave Nathanson"  wrote:
> 
> Hi Peter,
> To answer your question, Dreamhost has the *almost* newest version of MailMan 
> 2.1.17. They upgraded just as 2.1.18 came out and had already tested 2.1.17 
> so they went with that. And this version does have the most important DMARC 
> mitigation features. So it is working for us. 
> 
> I have never had any problem with DreamHost imposing a message sending cap on 
> their "1-Click" installs of Mailman. I run several discussion lists there 
> completely without incident, for 8 years Until this whole Yahoo/demarc 
> mess. And we are back to normal. No host is perfect, but considering the low 
> price & all the "unlimited everything" they offer, I'm very happy with mine. 
> Considering the price you have been paying, you will most likely need to pay 
> more to get out of this problem, but maybe not much more. 
> http://www.dreamhost.com/r.cgi?250640/hosting.html
> 
> Best,
> Dave Nathanson
> Mac Medix
> 
> 
>> On Jul 20, 2014, at 1:35 PM, Peter Shute  wrote:
>> 
>> No, it's all hosted via cpanel. Does this mail per hour limit seem odd with 
>> that sort of setup?
>> 
>> Does dreamhost keep their mailman up to date? We're still on 2.1.15, and 
>> when I asked about upgrading, they wouldn't commit to any date, only that it 
>> would be more likely to be months than a month.
>> 
>> Peter Shute
>> 
>> Sent from my iPad
>> 
>>> On 21 Jul 2014, at 1:35 am, "Dave Nathanson"  
>>> wrote:
>>> 
>>> I'm surprised that any web/email host would apply a rule intended for a 
>>> personal email account to a listserve. I'm guessing that you are running 
>>> MailMan on your own computer, then using mail server provided by your email 
>>> hosting company to send the messages. So to the email host, you do look 
>>> like a very busy personal account. 
>>> 
>>> As I see it, your options include:
>>> 
>>> * Discuss this limitation with your email host & see if they will waive the 
>>> message sending cap for your listserv.
>>> * Use a mailman installation hosted by your email hosting company, which is 
>>> not subject to a message sending cap. 
>>> * Changing email hosts & using a mailman installation hosted by your email 
>>> hosting company, which is not subject to a message sending cap. 
>>> 
>>> No need to change registrars. NameCheap is a good registrar, better than 
>>> many. I haven't used their web/email hosting. 
>>> 
>>> My email lists are all running on Mailman provided by my email host. You 
>>> don't even need to install it, just choose a dedicated subdomain for it to 
>>> run on. They do NOT limit message flow from Mailman, although they do limit 
>>> the number of messages per hour sent from a personal mail account. No 
>>> web/email host is perfect, but I'm pretty happy with DreamHost. Especially 
>>> for about $100 a year for more services than I can possibly use. (And I'm 
>>> giving it a good go!). 
>>> 
>>> Here is a Dreamhost Coupon code & link that will give you $10 off now, plus 
>>> 1 free LIFETIME domain registration. So that's a savings of about $11 a 
>>> year for life. MACMEDIXFREEDOM  What else is included? Tons! Check it out.
>>> http://www.dreamhost.com/r.cgi?250640/hosting.html
>>> 
>>> Best, 
>>> Dave Nathanson
>>> Mac Medix
>>> 
 On Jul 20, 2014, at 4:38 AM, Russell Woodford  wrote:
 
 Hi Peter, Mark and all
 
 I think I may have the solution now (Peter is one of our list moderators).
 My web host is now telling me that there is a 200 emails per hour limit for
 my hosting plan. We have 1140 subscribers. That means we blow the limit out
 of the water EVERY time someone posts!
 
 I'm not sure why they have taken so long to tell me this, as we've been
 running on this host for over 7 months, but it seems they throttle the
 outgoing mail volume, so it can take a while for all those recipients to
 get each message. I suppose it depends on overall server activity - if
 nothing else is happening, then maybe a new message does get straight to
 1140 recipients.
 
 Looks like we will need to shift to a new listserver and maybe even a new
 webhost - and maybe even a new domain registrar (I've had all my eggs in
 the Namecheap basket for some years now).  Somehow I don't think I am going
 to get away with this volume of mail for the $50 a year I'm currently
 paying :-(
 
 Russell Woodford
 Geelong, Australia
 birding-aus.org
 
 
>> On 18 July 2014 11:20, Mark Sapiro  wrote:
>> 
>> On 07/17/2014 05:01 PM, Peter Shute wrote:
>> 
>> I've now enabled protocol logging on our Exchange server, a new world
> for me. I can see several possibly relevant events in yesterday's logs 
> that
> look like th

Re: [Mailman-Users] postfix errors

[Jimmy]

Backed out the 3rd party mailman module config, corrected the permissions
on the aliases* files, restarted mailman and postfix and all is functional
now. Thanks!


On Mon, Jul 21, 2014 at 1:43 PM, Jimmy  wrote:

> I just found where the postfix-to-mailman line came from:
>
> http://wiki.list.org/display/DOC/Integrating+Mailman+with+postfix
>
> And see that Mark specifically recommends not using this doc. I'm backing
> that config out.
>
>
> On Mon, Jul 21, 2014 at 1:04 PM, Jimmy  wrote:
>
>> I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not
>> exist on my system, postfix-to-mailman.py  isn't anywhere on my system at
>> all, so that obviously presents a problem. Is that not normally in the RPM
>> installation?
>>
>> Thanks
>>
>>
>> On Mon, Jul 21, 2014 at 12:05 PM, Jimmy  wrote:
>>
>>> Based on this error and the following link I think I'm missing something
>>> from my /etc/postfix/transport.
>>>
>>> "unknown mail transport error"
>>>
>>> http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps
>>>
>>> I used the 'integrating mailman and postfix' guide but don't see what I
>>> need to do to fix it.
>>> Thanks
>>>
>>>
>>> On Mon, Jul 21, 2014 at 11:01 AM, Jimmy  wrote:
>>>
 I'm not sure why it's trying to use a username 'list', if that is the
 problem. Here are the things you mentioned. Thanks.

 ==master.cf==
 mailman   unix  -   n   n   -   -   pipe
   flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
   ${nexthop} ${user}

 ==/etc/postfix/transport==
 lists.listdomain.com  mailman:

 ==postconf -n==
 alias_database = hash:/etc/aliases
 alias_maps = hash:/etc/aliases
 command_directory = /usr/sbin
 config_directory = /etc/postfix
 daemon_directory = /usr/libexec/postfix
 data_directory = /var/lib/postfix
 default_privs = nobody
 html_directory = no
 inet_interfaces = all
 inet_protocols = ipv4
 mail_owner = postfix
 mailq_path = /usr/bin/mailq.postfix
 mydestination = $myhostname localhost.$mydomain localhost
 lists.listdomain.com
 mydomain = lists.listdomain.com
 mynetworks = 10.0.0.0/8
 mynetworks_style = subnet
 newaliases_path = /usr/bin/newaliases.postfix
 queue_directory = /var/spool/postfix
 recipient_delimiter = +
 relay_domains = listdomain.com
 relayhost = mailserver.prod.listdomain.com
 sendmail_path = /usr/sbin/sendmail.postfix
 setgid_group = postdrop
 soft_bounce = no
 transport_maps = hash:/etc/postfix/transport
 unknown_local_recipient_reject_code = 550



 On Thu, Jul 17, 2014 at 11:43 AM, Jimmy  wrote:

> I am still working on this new mailman system and seeing these errors
> when an email is sent to the system. I've googled the errors and haven't
> yet found anything that helps. Any ideas? Thanks
>
> 2014-07-17T10:38:52.396296-04:00 listservhostname
> postfix/smtpd[13799]: connect from unknown[10.0.0.1]
> 2014-07-17T10:38:52.497048-04:00 listservhostname
> postfix/smtpd[13799]: 790A84583: client=unknown[10.0.0.1]
> 2014-07-17T10:38:52.613030-04:00 listservhostname
> postfix/cleanup[13802]: 790A84583: message-id=<
> 7e1decc87c4844c18882f3a27eefa...@corpexchmbx10.listdomain.com>
> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]:
> 790A84583: from=, size=5925, nrcpt=1 (queue
> active)
> 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]:
> fatal: get_service_attr: unknown username: list
> 2014-07-17T10:38:52.666526-04:00 listservhostname
> postfix/smtpd[13799]: disconnect from unknown[10.0.0.1]
> 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]:
> warning: private/mailman socket: malformed response
> 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]:
> warning: transport mailman failure -- see a previous warning/fatal/panic
> logfile record for the problem description
> 2014-07-17T10:38:53.638431-04:00 listservhostname
> postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 
> 13803
> exit status 1
> 2014-07-17T10:38:53.638453-04:00 listservhostname
> postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command
> startup -- throttling
> 2014-07-17T10:38:53.656307-04:00 listservhostname
> postfix/error[13805]: 790A84583: to=<
> systems-change...@lists.listdomain.com>, relay=none, delay=1.2,
> delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail transport
> error)
> 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]:
> 740AF107: from=, size=5114, nrcpt=1 (queue
> active)
> 2014-07-17T10:39:42.699454-04:00 listservhostname
> postfix/error[13805]: 740AF107: to=<
> systems-change...@lists.lis

Re: [Mailman-Users] Erratic mail delivery times

[Dave Nathanson]

Hi Peter,
To answer your question, Dreamhost has the *almost* newest version of MailMan 
2.1.17. They upgraded just as 2.1.18 came out and had already tested 2.1.17 so 
they went with that. And this version does have the most important DMARC 
mitigation features. So it is working for us. 

I have never had any problem with DreamHost imposing a message sending cap on 
their "1-Click" installs of Mailman. I run several discussion lists there 
completely without incident, for 8 years Until this whole Yahoo/demarc 
mess. And we are back to normal. No host is perfect, but considering the low 
price & all the "unlimited everything" they offer, I'm very happy with mine. 
Considering the price you have been paying, you will most likely need to pay 
more to get out of this problem, but maybe not much more. 
http://www.dreamhost.com/r.cgi?250640/hosting.html

Best,
Dave Nathanson
Mac Medix


> On Jul 20, 2014, at 1:35 PM, Peter Shute  wrote:
> 
> No, it's all hosted via cpanel. Does this mail per hour limit seem odd with 
> that sort of setup?
> 
> Does dreamhost keep their mailman up to date? We're still on 2.1.15, and when 
> I asked about upgrading, they wouldn't commit to any date, only that it would 
> be more likely to be months than a month.
> 
> Peter Shute
> 
> Sent from my iPad
> 
>> On 21 Jul 2014, at 1:35 am, "Dave Nathanson"  
>> wrote:
>> 
>> I'm surprised that any web/email host would apply a rule intended for a 
>> personal email account to a listserve. I'm guessing that you are running 
>> MailMan on your own computer, then using mail server provided by your email 
>> hosting company to send the messages. So to the email host, you do look like 
>> a very busy personal account. 
>> 
>> As I see it, your options include:
>> 
>> * Discuss this limitation with your email host & see if they will waive the 
>> message sending cap for your listserv.
>> * Use a mailman installation hosted by your email hosting company, which is 
>> not subject to a message sending cap. 
>> * Changing email hosts & using a mailman installation hosted by your email 
>> hosting company, which is not subject to a message sending cap. 
>> 
>> No need to change registrars. NameCheap is a good registrar, better than 
>> many. I haven't used their web/email hosting. 
>> 
>> My email lists are all running on Mailman provided by my email host. You 
>> don't even need to install it, just choose a dedicated subdomain for it to 
>> run on. They do NOT limit message flow from Mailman, although they do limit 
>> the number of messages per hour sent from a personal mail account. No 
>> web/email host is perfect, but I'm pretty happy with DreamHost. Especially 
>> for about $100 a year for more services than I can possibly use. (And I'm 
>> giving it a good go!). 
>> 
>> Here is a Dreamhost Coupon code & link that will give you $10 off now, plus 
>> 1 free LIFETIME domain registration. So that's a savings of about $11 a year 
>> for life. MACMEDIXFREEDOM  What else is included? Tons! Check it out.
>> http://www.dreamhost.com/r.cgi?250640/hosting.html
>> 
>> Best, 
>> Dave Nathanson
>> Mac Medix
>> 
>>> On Jul 20, 2014, at 4:38 AM, Russell Woodford  wrote:
>>> 
>>> Hi Peter, Mark and all
>>> 
>>> I think I may have the solution now (Peter is one of our list moderators).
>>> My web host is now telling me that there is a 200 emails per hour limit for
>>> my hosting plan. We have 1140 subscribers. That means we blow the limit out
>>> of the water EVERY time someone posts!
>>> 
>>> I'm not sure why they have taken so long to tell me this, as we've been
>>> running on this host for over 7 months, but it seems they throttle the
>>> outgoing mail volume, so it can take a while for all those recipients to
>>> get each message. I suppose it depends on overall server activity - if
>>> nothing else is happening, then maybe a new message does get straight to
>>> 1140 recipients.
>>> 
>>> Looks like we will need to shift to a new listserver and maybe even a new
>>> webhost - and maybe even a new domain registrar (I've had all my eggs in
>>> the Namecheap basket for some years now).  Somehow I don't think I am going
>>> to get away with this volume of mail for the $50 a year I'm currently
>>> paying :-(
>>> 
>>> Russell Woodford
>>> Geelong, Australia
>>> birding-aus.org
>>> 
>>> 
> On 18 July 2014 11:20, Mark Sapiro  wrote:
> 
> On 07/17/2014 05:01 PM, Peter Shute wrote:
> 
> I've now enabled protocol logging on our Exchange server, a new world
 for me. I can see several possibly relevant events in yesterday's logs that
 look like this:
> 2014-07-17T07:02:03.914Z,NUWVICMS2\Default NUWVICMS2,08D145520008BC68,24,
 192.168.0.36:25,192.64.112.70:38732,>,550 5.7.1 Requested action not
 taken: message refused,
 
 
 This is a 550 (extended 5.7.,1) status which is a permanent failure.
 This is a bounce and will (should) not be retried by the sending server.
 
 I doubt that this specific log mess

Re: [Mailman-Users] postfix errors

[Jimmy]

I just found where the postfix-to-mailman line came from:

http://wiki.list.org/display/DOC/Integrating+Mailman+with+postfix

And see that Mark specifically recommends not using this doc. I'm backing
that config out.


On Mon, Jul 21, 2014 at 1:04 PM, Jimmy  wrote:

> I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not
> exist on my system, postfix-to-mailman.py  isn't anywhere on my system at
> all, so that obviously presents a problem. Is that not normally in the RPM
> installation?
>
> Thanks
>
>
> On Mon, Jul 21, 2014 at 12:05 PM, Jimmy  wrote:
>
>> Based on this error and the following link I think I'm missing something
>> from my /etc/postfix/transport.
>>
>> "unknown mail transport error"
>>
>> http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps
>>
>> I used the 'integrating mailman and postfix' guide but don't see what I
>> need to do to fix it.
>> Thanks
>>
>>
>> On Mon, Jul 21, 2014 at 11:01 AM, Jimmy  wrote:
>>
>>> I'm not sure why it's trying to use a username 'list', if that is the
>>> problem. Here are the things you mentioned. Thanks.
>>>
>>> ==master.cf==
>>> mailman   unix  -   n   n   -   -   pipe
>>>   flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>>>   ${nexthop} ${user}
>>>
>>> ==/etc/postfix/transport==
>>> lists.listdomain.com  mailman:
>>>
>>> ==postconf -n==
>>> alias_database = hash:/etc/aliases
>>> alias_maps = hash:/etc/aliases
>>> command_directory = /usr/sbin
>>> config_directory = /etc/postfix
>>> daemon_directory = /usr/libexec/postfix
>>> data_directory = /var/lib/postfix
>>> default_privs = nobody
>>> html_directory = no
>>> inet_interfaces = all
>>> inet_protocols = ipv4
>>> mail_owner = postfix
>>> mailq_path = /usr/bin/mailq.postfix
>>> mydestination = $myhostname localhost.$mydomain localhost
>>> lists.listdomain.com
>>> mydomain = lists.listdomain.com
>>> mynetworks = 10.0.0.0/8
>>> mynetworks_style = subnet
>>> newaliases_path = /usr/bin/newaliases.postfix
>>> queue_directory = /var/spool/postfix
>>> recipient_delimiter = +
>>> relay_domains = listdomain.com
>>> relayhost = mailserver.prod.listdomain.com
>>> sendmail_path = /usr/sbin/sendmail.postfix
>>> setgid_group = postdrop
>>> soft_bounce = no
>>> transport_maps = hash:/etc/postfix/transport
>>> unknown_local_recipient_reject_code = 550
>>>
>>>
>>>
>>> On Thu, Jul 17, 2014 at 11:43 AM, Jimmy  wrote:
>>>
 I am still working on this new mailman system and seeing these errors
 when an email is sent to the system. I've googled the errors and haven't
 yet found anything that helps. Any ideas? Thanks

 2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]:
 connect from unknown[10.0.0.1]
 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]:
 790A84583: client=unknown[10.0.0.1]
 2014-07-17T10:38:52.613030-04:00 listservhostname
 postfix/cleanup[13802]: 790A84583: message-id=<
 7e1decc87c4844c18882f3a27eefa...@corpexchmbx10.listdomain.com>
 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]:
 790A84583: from=, size=5925, nrcpt=1 (queue
 active)
 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]:
 fatal: get_service_attr: unknown username: list
 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]:
 disconnect from unknown[10.0.0.1]
 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]:
 warning: private/mailman socket: malformed response
 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]:
 warning: transport mailman failure -- see a previous warning/fatal/panic
 logfile record for the problem description
 2014-07-17T10:38:53.638431-04:00 listservhostname
 postfix/master[13722]: warning: process /usr/libexec/postfix/pipe pid 13803
 exit status 1
 2014-07-17T10:38:53.638453-04:00 listservhostname
 postfix/master[13722]: warning: /usr/libexec/postfix/pipe: bad command
 startup -- throttling
 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]:
 790A84583: to=, relay=none,
 delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail
 transport error)
 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]:
 740AF107: from=, size=5114, nrcpt=1 (queue
 active)
 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]:
 740AF107: to=, relay=none,
 delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail
 transport error)


>>>
>>
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-arch

Re: [Mailman-Users] postfix errors

[Jimmy]

I found that the file /usr/lib/mailman/bin/postfix-to-mailman.py does not
exist on my system, postfix-to-mailman.py  isn't anywhere on my system at
all, so that obviously presents a problem. Is that not normally in the RPM
installation?

Thanks


On Mon, Jul 21, 2014 at 12:05 PM, Jimmy  wrote:

> Based on this error and the following link I think I'm missing something
> from my /etc/postfix/transport.
>
> "unknown mail transport error"
>
> http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps
>
> I used the 'integrating mailman and postfix' guide but don't see what I
> need to do to fix it.
> Thanks
>
>
> On Mon, Jul 21, 2014 at 11:01 AM, Jimmy  wrote:
>
>> I'm not sure why it's trying to use a username 'list', if that is the
>> problem. Here are the things you mentioned. Thanks.
>>
>> ==master.cf==
>> mailman   unix  -   n   n   -   -   pipe
>>   flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>>   ${nexthop} ${user}
>>
>> ==/etc/postfix/transport==
>> lists.listdomain.com  mailman:
>>
>> ==postconf -n==
>> alias_database = hash:/etc/aliases
>> alias_maps = hash:/etc/aliases
>> command_directory = /usr/sbin
>> config_directory = /etc/postfix
>> daemon_directory = /usr/libexec/postfix
>> data_directory = /var/lib/postfix
>> default_privs = nobody
>> html_directory = no
>> inet_interfaces = all
>> inet_protocols = ipv4
>> mail_owner = postfix
>> mailq_path = /usr/bin/mailq.postfix
>> mydestination = $myhostname localhost.$mydomain localhost
>> lists.listdomain.com
>> mydomain = lists.listdomain.com
>> mynetworks = 10.0.0.0/8
>> mynetworks_style = subnet
>> newaliases_path = /usr/bin/newaliases.postfix
>> queue_directory = /var/spool/postfix
>> recipient_delimiter = +
>> relay_domains = listdomain.com
>> relayhost = mailserver.prod.listdomain.com
>> sendmail_path = /usr/sbin/sendmail.postfix
>> setgid_group = postdrop
>> soft_bounce = no
>> transport_maps = hash:/etc/postfix/transport
>> unknown_local_recipient_reject_code = 550
>>
>>
>>
>> On Thu, Jul 17, 2014 at 11:43 AM, Jimmy  wrote:
>>
>>> I am still working on this new mailman system and seeing these errors
>>> when an email is sent to the system. I've googled the errors and haven't
>>> yet found anything that helps. Any ideas? Thanks
>>>
>>> 2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]:
>>> connect from unknown[10.0.0.1]
>>> 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]:
>>> 790A84583: client=unknown[10.0.0.1]
>>> 2014-07-17T10:38:52.613030-04:00 listservhostname
>>> postfix/cleanup[13802]: 790A84583: message-id=<
>>> 7e1decc87c4844c18882f3a27eefa...@corpexchmbx10.listdomain.com>
>>> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]:
>>> 790A84583: from=, size=5925, nrcpt=1 (queue
>>> active)
>>> 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]:
>>> fatal: get_service_attr: unknown username: list
>>> 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]:
>>> disconnect from unknown[10.0.0.1]
>>> 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]:
>>> warning: private/mailman socket: malformed response
>>> 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]:
>>> warning: transport mailman failure -- see a previous warning/fatal/panic
>>> logfile record for the problem description
>>> 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]:
>>> warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1
>>> 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]:
>>> warning: /usr/libexec/postfix/pipe: bad command startup -- throttling
>>> 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]:
>>> 790A84583: to=, relay=none,
>>> delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail
>>> transport error)
>>> 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]:
>>> 740AF107: from=, size=5114, nrcpt=1 (queue
>>> active)
>>> 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]:
>>> 740AF107: to=, relay=none,
>>> delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail
>>> transport error)
>>>
>>>
>>
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] postfix errors

[Barry S. Finkel]

On Mon, Jul 21, 2014 at 11:01 AM, Jimmy  wrote:



I'm not sure why it's trying to use a username 'list', if that is the
problem. Here are the things you mentioned. Thanks.

==master.cf==
mailman   unix  -   n   n   -   -   pipe
   flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
   ${nexthop} ${user}

==/etc/postfix/transport==
lists.listdomain.com  mailman:

==postconf -n==
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
default_privs = nobody
html_directory = no
inet_interfaces = all
inet_protocols = ipv4
mail_owner = postfix
mailq_path = /usr/bin/mailq.postfix
mydestination = $myhostname localhost.$mydomain localhost
lists.listdomain.com
mydomain = lists.listdomain.com
mynetworks = 10.0.0.0/8
mynetworks_style = subnet
newaliases_path = /usr/bin/newaliases.postfix
queue_directory = /var/spool/postfix
recipient_delimiter = +
relay_domains = listdomain.com
relayhost = mailserver.prod.listdomain.com
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
soft_bounce = no
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550



On Thu, Jul 17, 2014 at 11:43 AM, Jimmy  wrote:


I am still working on this new mailman system and seeing these errors
when an email is sent to the system. I've googled the errors and haven't
yet found anything that helps. Any ideas? Thanks

2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]:
connect from unknown[10.0.0.1]
2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]:
790A84583: client=unknown[10.0.0.1]
2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]:
790A84583: message-id=<
7e1decc87c4844c18882f3a27eefa...@corpexchmbx10.listdomain.com>
2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]:
790A84583: from=, size=5925, nrcpt=1 (queue
active)
2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]:
fatal: get_service_attr: unknown username: list
2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]:
disconnect from unknown[10.0.0.1]
2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]:
warning: private/mailman socket: malformed response
2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]:
warning: transport mailman failure -- see a previous warning/fatal/panic
logfile record for the problem description
2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]:
warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1
2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]:
warning: /usr/libexec/postfix/pipe: bad command startup -- throttling
2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]:
790A84583: to=, relay=none,
delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail
transport error)
2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]:
740AF107: from=, size=5114, nrcpt=1 (queue
active)
2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]:
740AF107: to=, relay=none,
delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail
transport error)



On 7/21/2014 11:05 AM, Jimmy wrote:> Based on this error and the 
following link I think I'm missing something

> from my /etc/postfix/transport.
>
> "unknown mail transport error"
> 
http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps

>
> I used the 'integrating mailman and postfix' guide but don't see what I
> need to do to fix it.
> Thanks


Why do you use   postfix-to-mailman.py ?
That piece is not recommended by the Mailman developers.  See

 http://wiki.list.org/pages/viewpage.action?pageId=15564817

--Barry Finkel

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] postfix errors

[Jimmy]

Based on this error and the following link I think I'm missing something
from my /etc/postfix/transport.

"unknown mail transport error"
http://wiki.list.org/display/DOC/Mailman+-+Postfix+integration+with+Mailman+generated+transport+or+other+maps

I used the 'integrating mailman and postfix' guide but don't see what I
need to do to fix it.
Thanks


On Mon, Jul 21, 2014 at 11:01 AM, Jimmy  wrote:

> I'm not sure why it's trying to use a username 'list', if that is the
> problem. Here are the things you mentioned. Thanks.
>
> ==master.cf==
> mailman   unix  -   n   n   -   -   pipe
>   flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>   ${nexthop} ${user}
>
> ==/etc/postfix/transport==
> lists.listdomain.com  mailman:
>
> ==postconf -n==
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> command_directory = /usr/sbin
> config_directory = /etc/postfix
> daemon_directory = /usr/libexec/postfix
> data_directory = /var/lib/postfix
> default_privs = nobody
> html_directory = no
> inet_interfaces = all
> inet_protocols = ipv4
> mail_owner = postfix
> mailq_path = /usr/bin/mailq.postfix
> mydestination = $myhostname localhost.$mydomain localhost
> lists.listdomain.com
> mydomain = lists.listdomain.com
> mynetworks = 10.0.0.0/8
> mynetworks_style = subnet
> newaliases_path = /usr/bin/newaliases.postfix
> queue_directory = /var/spool/postfix
> recipient_delimiter = +
> relay_domains = listdomain.com
> relayhost = mailserver.prod.listdomain.com
> sendmail_path = /usr/sbin/sendmail.postfix
> setgid_group = postdrop
> soft_bounce = no
> transport_maps = hash:/etc/postfix/transport
> unknown_local_recipient_reject_code = 550
>
>
>
> On Thu, Jul 17, 2014 at 11:43 AM, Jimmy  wrote:
>
>> I am still working on this new mailman system and seeing these errors
>> when an email is sent to the system. I've googled the errors and haven't
>> yet found anything that helps. Any ideas? Thanks
>>
>> 2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]:
>> connect from unknown[10.0.0.1]
>> 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]:
>> 790A84583: client=unknown[10.0.0.1]
>> 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]:
>> 790A84583: message-id=<
>> 7e1decc87c4844c18882f3a27eefa...@corpexchmbx10.listdomain.com>
>> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]:
>> 790A84583: from=, size=5925, nrcpt=1 (queue
>> active)
>> 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]:
>> fatal: get_service_attr: unknown username: list
>> 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]:
>> disconnect from unknown[10.0.0.1]
>> 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]:
>> warning: private/mailman socket: malformed response
>> 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]:
>> warning: transport mailman failure -- see a previous warning/fatal/panic
>> logfile record for the problem description
>> 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]:
>> warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1
>> 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]:
>> warning: /usr/libexec/postfix/pipe: bad command startup -- throttling
>> 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]:
>> 790A84583: to=, relay=none,
>> delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail
>> transport error)
>> 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]:
>> 740AF107: from=, size=5114, nrcpt=1 (queue
>> active)
>> 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]:
>> 740AF107: to=, relay=none,
>> delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail
>> transport error)
>>
>>
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] postfix errors

[Jimmy]

I'm not sure why it's trying to use a username 'list', if that is the
problem. Here are the things you mentioned. Thanks.

==master.cf==
mailman   unix  -   n   n   -   -   pipe
  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
  ${nexthop} ${user}

==/etc/postfix/transport==
lists.listdomain.com  mailman:

==postconf -n==
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
default_privs = nobody
html_directory = no
inet_interfaces = all
inet_protocols = ipv4
mail_owner = postfix
mailq_path = /usr/bin/mailq.postfix
mydestination = $myhostname localhost.$mydomain localhost
lists.listdomain.com
mydomain = lists.listdomain.com
mynetworks = 10.0.0.0/8
mynetworks_style = subnet
newaliases_path = /usr/bin/newaliases.postfix
queue_directory = /var/spool/postfix
recipient_delimiter = +
relay_domains = listdomain.com
relayhost = mailserver.prod.listdomain.com
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
soft_bounce = no
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550



On Thu, Jul 17, 2014 at 11:43 AM, Jimmy  wrote:

> I am still working on this new mailman system and seeing these errors when
> an email is sent to the system. I've googled the errors and haven't yet
> found anything that helps. Any ideas? Thanks
>
> 2014-07-17T10:38:52.396296-04:00 listservhostname postfix/smtpd[13799]:
> connect from unknown[10.0.0.1]
> 2014-07-17T10:38:52.497048-04:00 listservhostname postfix/smtpd[13799]:
> 790A84583: client=unknown[10.0.0.1]
> 2014-07-17T10:38:52.613030-04:00 listservhostname postfix/cleanup[13802]:
> 790A84583: message-id=<
> 7e1decc87c4844c18882f3a27eefa...@corpexchmbx10.listdomain.com>
> 2014-07-17T10:38:52.625741-04:00 listservhostname postfix/qmgr[13725]:
> 790A84583: from=, size=5925, nrcpt=1 (queue
> active)
> 2014-07-17T10:38:52.635273-04:00 listservhostname postfix/pipe[13803]:
> fatal: get_service_attr: unknown username: list
> 2014-07-17T10:38:52.666526-04:00 listservhostname postfix/smtpd[13799]:
> disconnect from unknown[10.0.0.1]
> 2014-07-17T10:38:53.637115-04:00 listservhostname postfix/qmgr[13725]:
> warning: private/mailman socket: malformed response
> 2014-07-17T10:38:53.637153-04:00 listservhostname postfix/qmgr[13725]:
> warning: transport mailman failure -- see a previous warning/fatal/panic
> logfile record for the problem description
> 2014-07-17T10:38:53.638431-04:00 listservhostname postfix/master[13722]:
> warning: process /usr/libexec/postfix/pipe pid 13803 exit status 1
> 2014-07-17T10:38:53.638453-04:00 listservhostname postfix/master[13722]:
> warning: /usr/libexec/postfix/pipe: bad command startup -- throttling
> 2014-07-17T10:38:53.656307-04:00 listservhostname postfix/error[13805]:
> 790A84583: to=, relay=none,
> delay=1.2, delays=0.14/1/0/0.01, dsn=4.3.0, status=deferred (unknown mail
> transport error)
> 2014-07-17T10:39:42.687502-04:00 listservhostname postfix/qmgr[13725]:
> 740AF107: from=, size=5114, nrcpt=1 (queue
> active)
> 2014-07-17T10:39:42.699454-04:00 listservhostname postfix/error[13805]:
> 740AF107: to=, relay=none,
> delay=539, delays=539/0.01/0/0, dsn=4.3.0, status=deferred (unknown mail
> transport error)
>
>
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org