Also, we're evaluating Google Cloud Platform - seems a bit cheaper than
AWS. GCP just plainly states that outgoing port 25 is blocked period.
I'm not aware of any forms or options where you can request the block be
lifted. Ports 465 and 587 are open so website contact forms and
transaction notifications could use smtp auth to get emails out if you
have an email account outside of the platform.
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>
