IP reputation and domain reputation are both vital when moving a server/service. Even for low visibility mailer domains. Checking the neighbourhood is an important element of that planning.
Laura I thought your blog post on DKIM very good. I've had several examples of crap concatenation and similar to your points with secondary DNS using different software giving unpredictable resolution. The first time I came across it several years ago it took a while to get to the bottom of it. It's a bit of a minefield. Are people using any opensource tools to help small providers / volunteers for micro NFPs to automate / discover / manage / keep an eye on such configurations? Christian Laura Atkins via mailop <mailop@mailop.org> writes: > On 26 Mar 2024, at 17:48, Brotman, Alex via mailop <mailop@mailop.org> wrote: > > I'm not on the sending side, but I will note there are several ESPs running > out of EC2. Some seem to use their > own IP ranges, some do not. > > Yeah, and they had problems in the past where some major ISPs were blocking > all space from EC2 and their mail > was having a horrible time getting through. I think they worked with the ISPs > to establish a way to special case > that IP space. > > I think if you're coming from an IP range you don't have direct control over > (i.e., cloud space), you must take > extra precaution to warm the IPs ( and domains, and click-track URLs, and > and and ..). Understand you're > going to have garbage neighbors (if you don't bring your own ranges), and > understand the implications of > that. > > Exactly. > > laura -- Christian de Larrinaga _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
