On Fri, Jan 11, 2013 at 09:27:23AM -0800, Duane Winner wrote:
> Does anyone have any ideas on how to deal with this? [snip]
Amazon's cloud has been a prolific long-term source of spam and other
forms of abuse (e.g., brute-force ssh attacks). Thus it's long since been
a best practice to refuse all
This is not a practical comment, but... I am amazed Amazon is checking
the header From instead of the header Sender and envelope sender... and
recommending breaking standards to get around what they are doing. They
not only break mailing lists but the types of forwarding that preserve
the origina
Stephen J. Turnbull writes:
> Duane Winner writes:
>
> > >>When sending through Amazon SES, instead of using the
> > >>From address of your user, instead use your organization's email
> > >>address with a "friendly name" which identifies the user. Only
> > >>the email address portion is
Duane Winner writes:
> >>When sending through Amazon SES, instead of using the
> >>From address of your user, instead use your organization's email
> >>address with a "friendly name" which identifies the user. Only
> >>the email address portion is verified, so you can send with
> >>From add
Mark Sapiro writes:
> Duane Winner wrote:
> >
> >If I knew how to replace the "Friendly name" with something else, that
> >/might/ be another solution, but I haven't been able to figure out how
> >to do that. I'm guessing that is a Postfix question.
>
>
> I could be wrong, but I don't thi
Duane Winner wrote:
>
>If I knew how to replace the "Friendly name" with something else, that
>/might/ be another solution, but I haven't been able to figure out how
>to do that. I'm guessing that is a Postfix question.
I could be wrong, but I don't think Postfix can do that, but you could
easily
>Have you tried working directly with Amazon SES to resolve the issue?
I have not personally, but on their forums, others have posed have the same
problem, and following is a reply directly from AWS:
>>We want to accommodate as many ways to send email as we can, while also
>>providing strong p
Duane Winner writes:
> Does anyone have any ideas on how to deal with this dilemma: I am
> running Mailman+Postfix+Ubuntu in Amazon AWS, and using Amazon SES
> as a relay. Although, this problem isn't unique to just SES. This
> problem is common among many relay services, DynDNS to name
> an
Hello,
Does anyone have any ideas on how to deal with this dilemma: I am running
Mailman+Postfix+Ubuntu in Amazon AWS, and using Amazon SES as a relay.
Although, this problem isn't unique to just SES. This problem is common among
many relay services, DynDNS to name another.
To prevent against
