Re: [Mailman-Users] Problems sending to prodigy.net mail server addresses

2019-02-11 Thread Richard Johnson
I sent postmas...@prodigy.net an email, and again, after the first one didn't receive a reply. They finally replied to both messages saying it was a problem on their side (which I think we all knew already. :) They said to send them another note if it happens again. We'll see... Thanks to al

Re: [Mailman-Users] Problems sending to prodigy.net mail server addresses

2019-02-11 Thread Carl Zwanzig
On 2/11/2019 1:21 PM, Joseph Brennan wrote: The DNS records look perfect to me. If you're going through a time warp to Prodigy maybe the new top-levels like .place don't work yet? You get the error after MAIL FROM because that's the earliest point when a server is allow Prodigy isn't the only o

Re: [Mailman-Users] Problems sending to prodigy.net mail server addresses

2019-02-11 Thread Joseph Brennan
On Tue, Feb 5, 2019 at 1:07 AM Richard Johnson wrote: > I run a small mailman server for our historical recreation group. Lately, > I've been seeing messages like: > > : host al-ip4-mx-vip1.prodigy.net[144.160.235.143] said: > 550 5.7.1 Connections not accepted from servers without a valid sen

Re: [Mailman-Users] MM 3.1.1 equivalent for bounce_unrecognized_goes_to_list_owner

2019-02-11 Thread Mark Sapiro
On 2/11/19 1:00 AM, M4tze wrote: > > Thanks Mark for you quick response. Setting > UnrecognizedBounceDisposition.discard via shell works. Is it possible to > change the default behavior for new lists? Or do I have to update these > settings each time a new list is created? Currently, forward_unr

Re: [Mailman-Users] MM 3.1.1 equivalent for bounce_unrecognized_goes_to_list_owner

2019-02-11 Thread M4tze
Hi, On 08.02.19 22:37, Mark Sapiro wrote: > On 2/8/19 4:34 AM, M4tze wrote: >> If there is no equivalent config option, I would try to change the code >> in order to discard such messages automatically, but I am not so much >> into MM development. Could you help me out finding relevant functions?