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
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
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 corruptio
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 not
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 th
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 tak
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
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
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,
> a
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 recei
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 comme
[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
> > 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:
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 li
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 info
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
ap
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
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
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 fea
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-ma
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 mo
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 quest
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/di
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 n
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
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:
> B
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/mailm
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
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}
==
29 matches
Mail list logo
