Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

2020-02-17 Thread Lindsay Haisley (linode)


On Feb 17, 2020, at 10:45 AM, Phil Stracchino  wrote:
> 
>> On 2020-02-17 10:56, Bill Cole wrote:
>> RedHat has a policy of nailing down nominal versions of software with 
>> each major RHEL release and then backporting whatever fixes they deem 
>> important into their packages over the life of the major release, adding 
>> their own subordinate versioning. 

> An unfortunate side effect of this is that it makes it very difficult to
> support some software on Red Hat because you don't know for sure what
> codebase you're actually running, except that it's probably neither fish
> nor fowl nor good red meat.

This is common practice for all major distributions. The only way to keep up 
with upstream versions is to install from same from the git-go. This has its 
own pitfalls, but I do this for Mailman and have never had a problem.

Sent from my iPhone


--
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] Some site blocking our emails from mailman 2.1.29 ?

2018-11-30 Thread Lindsay Haisley (linode)



Sent from my iPhone

> On Nov 30, 2018, at 4:17 PM, Matthew Goebel  wrote:
> 
> We've recently had one or two sites block email coming from one of our
> lists.
> They seem to indicate it is because of sending address having bounces in it?

Email is probably the most stressed service on the Internet. It's also probably 
the most complex and widely misunderstood. There are tons of people out there 
writing solutions to address email abuse problems. Way too many of them have no 
idea what's in the email RFC's and how the system is supposed to work.
--
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] OT - Smart .forward replacement?

2018-11-25 Thread Lindsay Haisley (linode)
On Nov 25, 2018, at 1:06 PM, Mark Sapiro  wrote:
> 
> A .forward normally does not cause issues with DMARC because .forward
> redirection normally does not transform the message in ways that break
> DKIM signatures.

Which assumes that the sending system includes a DKIM signature in the original 
message. If it does not, and the receiving system relies on SPF for DMARC 
alignment, then DMARC will fail since mail redirected through a .forward  will 
always fail SPF validation.

Sent from my iPhone

--
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