I really wouldn't think TTL would be a determining factor - at least if it is I'd argue against it being such. Do any DNS resolvers actually cache data for the period stated in the TTL these days? Too long of a TTL, I think resolvers will flush it out before then anyway. Maybe 900 is too short, but I'd argue that looking at TTL isn't a good way to determine spammyness.
If you look at gmail.com it's TTL is 300 seconds - now... granted that IP address is not used to actually connect to mail server to send out mail, it's just the IP address for the front facing gmail.com. If you look at Yahoo, one of their sending IPs - 98.137.65.31 - resolves to sonic315-55.consmr.mail.gq1.yahoo.com. and sonic315-55.consmr.mail.gq1.yahoo.com. has a TTL of 1800 seconds. Obviously, 1800 is larger than 900, but enough to worry about? I definitely would subscribe to the notion that TTL should not matter for this. But should and does are two different things. On Wed, Feb 26, 2020 at 3:53 PM Lyle Giese via mailop <[email protected]> wrote: > Don't know if ATT looks at this but I know they used to. The TTL for the > A record for server.divebums.com is 900 seconds. If checking this > parameter, it was recommended that this be at least 12 hrs or 43,200 > seconds. The theory was that 900 seconds indicated it was on a dynamic ip > address. > > Good luck! > > Lyle Giese > > LCR Computer Services, Inc. > On 2020-02-26 15:25, Scott Mutter via mailop wrote: > > I know this will come as a complete and absolute shock to most everyone > here. > > It's been 15 days since I originally posted this on this list. I was told > to wait about a week to let them "weed" out all of the clutter AT&T likely > gets from this abuse address... so I waited 2 weeks. > > The shocking part... it's still blocked. And I haven't received a peep > from AT&T other than the canned response I got on February 10th (16 days > ago). > > So basically all I've done is wasted 16 days waiting for a response or > resolution. > > And yet people wonder why I have zero faith in the way any of these "big" > mail providers address disputes to their clandestine blacklisting and > blocking process. > > Am I suppose to wait another decade or two for a response or resolution > from AT&T regarding this? > > For what it's worth - the IP address in this particular case > is 192.158.224.5 - I would very much love for someone to tell me what is > wrong with this IP address and why AT&T is blacklisting it. What services > do you all recommend to go to to check the reputation of a mail server's IP > address? I've been using Senderscore, Senderbase, Proofpoint, Symantec, > Spamhaus, Spamcop - this IP address comes up clean at all of those places - > but I guess those aren't good sources to double check with? > > I'm open to suggestions on how I'm suppose to handle this and what I need > to do to resolve this. Apparently checking the IP's reputation at those > sites isn't good enough. And apparently sending an email to > [email protected] is not good enough. > > > > On Tue, Feb 11, 2020 at 9:50 AM Scott Mutter via mailop <[email protected]> > wrote: > >> Anybody from AT&T able to check a couple of abuse tickets for me? >> >> AT&T is blocking one of our servers, I sent messages on February 8th and >> February 10th to [email protected] but have not heard anything >> back - other than the canned response - and the IP is still blocked. >> >> The rejection notice says to email [email protected] but I'm not >> sure if that is still valid. >> >> Ticket numbers are: >> >> 020820-180048-39537-00 >> 021020-164333-46154-00 >> >> I suppose it's possible that AT&T is just inundated with abuse requests - >> but maybe there is a better way to weed out the valid requests from the >> invalid requests. >> >> If [email protected] is no longer valid, then perhaps the >> rejection notice needs to be updated. >> >> >> _______________________________________________ >> mailop mailing list >> [email protected] >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >> > > _______________________________________________ > mailop mailing > [email protected]https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > _______________________________________________ > mailop mailing list > [email protected] > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
