On Wed, 23 Sep 2020 13:47:23 -0500 Jerry Malcolm wrote:
> But gmail, outlook, and a bunch of other MTAs won't accept it and > bounce it back (with no reason attached). I'm hosting on AWS. So > the recommendation was to proxy my outbound mail through AWS's SES > server so it appeared that the mail came from 'trusted' Amazon. Now > I realize that Amazon changes the message id, and I get this 'forged' > flag. Are you sure about that? It would break threading on most traditional mail clients. In your list emails you are DKIM signing Message-Id and sending directly from AWS. If you are doing the same thing with SES, then obviously that would break DKIM. OTOH if you aren't signing Message-Id on the other mail perhaps doing so would discourage Amazon from overwriting the header. > Would it be better if I went through the headers on outbound and > removed headers that referenced Mozilla (or Outlook, or iPhone, or > ???) in order to make the SES message id change not trigger the rule? I doubt it would make much difference. Most spam filtering wont have that rule. And even in SA it was only 1.6.points.
