Hi Chris - I have heard that AWS is really unforgiving if any spam gets
sent out of the mailserver. Have you had experience running a full
mailserver on AWS?
Despite everything we do to control outgoing spam - including send
throttling - our users get hacked and their email credentials get used
by spammers. We are able to limit the damage to a minimal amount of spam
but nevertheless we get some complaints.
Jeff
On 3/2/2019 2:27 PM, Chris wrote:
AWS has a form where you can request the outbound smtp limitations be
removed for a legitimate mail server.
Amazon Web Services - MAIL SERVER
<https://aws.amazon.com/forms/ec2-email-limit-rdns-request>
They also have a form for requesting reverse DNS on your elastic IP so
your mail doesn't run afoul of DNS validation.
Route 53 Reverse DNS
<https://aws.amazon.com/premiumsupport/knowledge-center/route-53-reverse-dns/>
On Sun, Mar 3, 2019 at 7:07 AM Eric Broch <ebr...@whitehorsetc.com
<mailto:ebr...@whitehorsetc.com>> wrote:
I'm not sure, maybe start smtp under different port.
On 3/1/2019 4:16 PM, Jeff Koch wrote:
>
> I'd like to build a qmailtoaster mailserver on an AWS instance
but as
> you probably know AWS pretty much blocks outgoing traffic on
port 25.
> So I'm thinking that I can tunnel outgoing port 25 traffic to a
server
> on a less picky hosting service. Has anyone ever done something
like
> that or have any info on how to set up that kind of tunnel? or
perhaps
> accomplish the same thing another way/
>
> Jeff
>
>
>
--
Eric Broch
White Horse Technical Consulting (WHTC)
---------------------------------------------------------------------
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
<mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com>
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com
<mailto:qmailtoaster-list-h...@qmailtoaster.com>
