aws-lambda-ses-forwarder icon indicating copy to clipboard operation
aws-lambda-ses-forwarder copied to clipboard

Thoughts on forwarding via LMTP/SMTP directly rather than SES

Open jbouse opened this issue 7 years ago • 7 comments

Curious if you had potentially thought about being able to forward directly via LMTP or SMTP to a final mail server rather than requiring the modification of the From address and sending through SES.

jbouse avatar Jan 08 '18 02:01 jbouse

In cloud's world is very simple build large project with ±zero operating costs. SMTP is little different - is hard to get low-cost quality way to receive and forward email to my Inbox. SES is pay-as-you-go.

And then lot of implementations simple (I say „dumb“) SMTP forwarder is broking at least one anti-spam policy like SPF, DKIM and DMARC. Just re-using From header when forward is invalid.

For example: I have my personal Inbox secured to very strict policy (SPF, DKIM, DMARC) and my experience is: only big players (Gmail, Yahoo, Amazon, etc.) and some exceptions know do it right.

jakubboucek avatar Jan 08 '18 05:01 jakubboucek

The situation I'm looking at the SES receiving the email is the last stop before it goes into the mailbox yet to use this solution you have to have another final destination that sending it back to SES can deliver to. If your SES receiving rules pass it to the lambda function it should just need to then be passed to the receiving mailbox server.

jbouse avatar Jan 08 '18 14:01 jbouse

Please let me know sipliest way, how to deliver any message from AWS Lambda to my Gmail inbox (receiving mailbox server) than SMTP via SES.

jakubboucek avatar Jan 08 '18 14:01 jakubboucek

If you're using Gmail for you inbox than SES is fine but if you already have you run your own IMAP server that you want the mail to be delivered into with SES receiving it for you then it doesn't

jbouse avatar Jan 08 '18 14:01 jbouse

if you already have you run your own IMAP server

That's the point. Most of people have e-mail on some service like a Google.

jakubboucek avatar Jan 09 '18 08:01 jakubboucek

And there is the rub as I'm not most people as I run my own IMAP server.

jbouse avatar Jan 09 '18 13:01 jbouse

Unfortunately, part of Japan email recipients ( NTT Docomo, au, Softbank, etc.) is not suitable Amazon SES. Because this recipients email server is a bit strange.

If Amazon SES send many email , gmail will be ok, but this Japan recipients will soon block. Also, Amazon SES does not support Tokyo Region, too.

It would be great if I could send emails received by Amazon SES directly to an external SMTP server.

na-ka-mu-ra- avatar Dec 09 '19 06:12 na-ka-mu-ra-