Thanks all, am going to follow up on the info Luke sent and see if I can get things moving on the AT&T side. We like to have customer emails specific to their own servers to make it easy to track abuse, but I have a feeling it’s just an issue of perhaps an old bogon block or needing to warm things up. The mail volume is typically very low; just emailed invoices coming from ecommerce stores, so that may be contributing to the problem.
David From: mailop <mailop-boun...@mailop.org> on behalf of Al Iverson <aiver...@spamresource.com> Date: Wednesday, October 12, 2016 at 12:51 PM To: "email@example.com" <firstname.lastname@example.org> Subject: Re: [mailop] att.net/blocks issues; how to get removed David, Luke is a good person to assist with this. The one suggestion I would have in addition to whatever guidance he may have, is that you perhaps do not want to switch IPs when encountering those blocks. You might actually be causing additional blocking against you. You might want to centralize your outbound email volume to a small handful of IP addresses (maybe less than 8), if you have enough volume to support at least a few thousand messages per day per IP address. THEN, in a pinch, you could temporarily disable an IP address if you run into that kind of blocking. But I'd be careful about doing that only in exceptional circumstances -- certain ISPs and blacklist groups take a dim view of changing an IP address to try to get around blocking. It's definitely not a permanent fix to any sort of blocking reactive to what's coming out of your mail servers. If bad mail or spamtrap hits emanate from IP address #1, they'll eventually emanate from IP address #2 or #3 as well. Best regards, Al Iverson -- Al Iverson www.aliverson.com<http://www.aliverson.com> (312)725-0130 On Wed, Oct 12, 2016 at 11:12 AM, Luke Martinez via mailop <email@example.com<mailto:firstname.lastname@example.org>> wrote: I replied off list. I should be able to help get David in touch with someone who can help. On Wed, Oct 12, 2016 at 10:57 AM, Vick Khera <vi...@khera.org<mailto:vi...@khera.org>> wrote: On Tue, Oct 11, 2016 at 7:21 PM, David Hubbard <dhubb...@dino.hostasaurus.com<mailto:dhubb...@dino.hostasaurus.com>> wrote: > The specific details are netblocks we’re deploying new servers on, > previously unused, all seem to be on the block list by default. How fast are you ramping up traffic on new IPs? Also, what's the netblock? Maybe others can see issues in that block, especially if it is not virgin space. _______________________________________________ mailop mailing list email@example.com<mailto:firstname.lastname@example.org> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- [https://drive.google.com/uc?id=0B4yks7mm243zU3NTbDh0djhLd0k] Luke Martinez SendGrid Deliverability Consultant 520.400.5693<tel:520.400.5693> _______________________________________________ mailop mailing list email@example.com<mailto:firstname.lastname@example.org> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________ mailop mailing list email@example.com https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop