--On Friday, April 22, 2011 18:14 +0200 Francis Dupont
<Francis.Dupont@xxxxxxxxxx> wrote:
> In your previous mail you wrote:
>
> So I'm having trouble guessing why your systems are still
> seeing 64.170.93.22, much less sending mail to it.
>
> => a long time ago mail.ietf.org anti-spam dropped SMTP over
> IPv6 from a MTA address without a PTR. I put a workaround
> using the IPv4 address (the old one), it was fixed but I
> didn't remove the workaround.
It then seems to me that the only thing that ought to be done on
an emergency basis is precisely for you to get rid of the
workaround. As operational practices go, leaving kludges in
place longer than needed is always a cause of problems sooner or
later.
> I agree that having a system floating around that runs an
> SMTP server but that eats messages ("blindly" or not) is
> undesirable as an operational policy.
>
> => exactly and BTW 32.98.170.64.in-addr.arpa has still a PTR to
> mail.ietf.org.
Yep. Both should probably be cleared up, but it isn't something
I could easily be convinced is an emergency.
best,
john
_______________________________________________
Ietf mailing list
Ietf@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf