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

[Mark Sapiro]

On 2/4/19 9:29 PM, Richard Johnson wrote:
> 
> The messages are all sent to the mailing list "cor...@cortha.org".  I have 
> the mailing list setup with "host_name" set as "cortha.org", so that the 
> address used in the messages will be "cor...@cortha.org" and replies will go 
> there.  The system which is actually handling the mailing list is officially 
> named "peacock.place", but an MX points there from cortha.org.  The reverse 
> DNS (PTR) record gives the peacock.place name, since that's the official 
> hostname.


The list domain is not relevant here. The outgoing MTA needs to identify
itself as peacock.place in HELO/EHLO which seems to be the case, so that
should all be OK.


> Personally, I think Prodigy just has a problem with no one else has and it 
> seems to be their own, but I'm wondering if there's some way to work with 
> them?


I would try emailing postmas...@prodigy.net.

-- 
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] Problems sending to prodigy.net mail server addresses

[Dmitri Maziuk via Mailman-Users]

On Mon, 4 Feb 2019 21:29:19 -0800
Richard Johnson  wrote:
 
> What seems strange is that MOST of the time messages go through just
> fine, but ever now-and-then I'll get this failure notice.

Off the top of my head 1) they've a round-robin cluster of MXers in
which some are configured differently, or 2) they've transient DNS
lookup failures.

FWIW I do have 
  smtpd_helo_restrictions = reject_unknown_helo_hostname
  smtpd_sender_restrictions = reject_unknown_sender_domain
on our servers because vast majority of our legitimate senders come
from .edu addersses (or their home ISPs) while b0rk3d DNS is a common
feature of spam.

-- 
Dmitri Maziuk 
--
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] held messages not visible in web interface

[Mark Sapiro]

On 2/4/19 6:29 PM, Keith Seyffarth wrote:
> Chip Davis  writes:
> 
>> When this has happened to me, it was because the poster removed the 
>> post on his own.  When a post is held for moderation, the sender gets 
>> a note to that effect which includes a URL where they can go to cancel 
>> the held post.
>>
>> At least, that's the way my Mailman instances work.  YMMV, of course.
> 
> I don't think that's the case in this case, Chip, as nearly all the
> messages that have supposedly been held are spam, and I have yet to see
> a spammer retract a message from any other list.
> 


See .

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