Just to throw my experience in the ring in case it's helpful to anyone: I had a sender deliver just fine to T-Online until a couple of weeks ago when they were blocked for (what I determined after conversation with tosa@) not having a website with contact info available at the outbound mta's parent domain name (ehlo outbound.*mtaparentname*.com). Once a website redirect was put up they unblocked. I'm guessing it's some combination of automated crawling for contact info and manually unblocking the false negatives as they come up (as people who monitor their bounces reach out). Just my $0.02. *Zack Aab* (He/him) Consultant, Packaged Technology Operations, Shift Paradigm *O* +1 (512) 717-4097 <+15127174097> | *C* +1 (404) 317-6729 <+14043176729> | *W* shiftparadigm.com <https://www.shiftparadigm.com/>
On Fri, Oct 21, 2022 at 12:52 PM Grant Taylor via mailop <mailop@mailop.org> wrote: > On 10/21/22 10:30 AM, Laura Atkins via mailop wrote: > > I know a number of mailservers that are able to successfully send mail > > to t-online.de and have never contacted the tosa@ address. > > I wonder if that hints at a thus-far un-discussed aspect of T-Online's > policy. > > There is every chance that T-Online did some sort of analysis of email > traffic to identify likely legitimate senders and primed their white > list with those domains / IPs. E.g. ratio of outgoing messages to > domains / IPs verses spam complaints therefrom. > > Similarly, I suspect that T-Online also primed their white list with the > email oligarchies. -- If I can borrow / re-use what I consider to be > an apt description. > > After all, every single list has to start from something. Good lists > organically grow (and shrink) over time as needed. > > > > -- > Grant. . . . > unix || die > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
