Re: [qmailtoaster] mailserver on AWS

Hi Gary - great info - thanks - jeff On 3/2/2019 4:34 PM, Gary Bowling wrote: I looked into this at one point. But you can get a VPS at linode for $25/month capable of running a full qmailtoaster. Obviously not powerful enough for a million users, but I have over 1000 spread across 10 or so

Re: [qmailtoaster] mailserver on AWS

I looked into this at one point. But you can get a VPS at linode for $25/month capable of running a full qmailtoaster. Obviously not powerful enough for a million users, but I have over 1000 spread across 10 or so domains on it with no issues. Wi

Re: [qmailtoaster] mailserver on AWS

I've been researching moving my toaster from its current home into AWS, which is why I had those URLs bookmarked. Haven't actually done it yet, so I don't know how AWS deals with complaints. Sorry I can't be more helpful on that front. -Chris On Sun, Mar 3, 2019 at 8:53 AM Jeff Koch wrote: >

Re: [qmailtoaster] mailserver on AWS

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 not

Re: [qmailtoaster] mailserver on AWS

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 use

Re: [qmailtoaster] mailserver on AWS

Thanks Carl - I'll give it a try - Jeff On 3/2/2019 2:23 PM, CarlC Internet Services Service Desk wrote: Actually, what you do is set this up on the remote server... You create the SSH tunnel where the remote server [with port 25 open to the world], connected via SSH Tunnel to the remote serve

Re: [qmailtoaster] mailserver on AWS

AWS has a form where you can request the outbound smtp limitations be removed for a legitimate mail server. Amazon Web Services - MAIL SERVER They also have a form for requesting reverse DNS on your elastic IP so your mail doesn't run a

RE: [qmailtoaster] mailserver on AWS

Actually, what you do is set this up on the remote server... You create the SSH tunnel where the remote server [with port 25 open to the world], connected via SSH Tunnel to the remote server [and what port on the remote server you want the tunnel to connect to]... Usually, I use key pairs so I c

Re: [qmailtoaster] mailserver on AWS

I just did a quick search https://aws.amazon.com/it/about-aws/whats-new/2011/12/13/amazon-simple-email-service-gets-simpler-with-smtp/ > Il giorno 2 mar 2019, alle ore 12:17, r...@mattei.org ha scritto: > > I recall that it was ok to have smtp on aws. > > Make sure your security groups have a

Re: [qmailtoaster] mailserver on AWS

I recall that it was ok to have smtp on aws. Make sure your security groups have a rule. > Il giorno 2 mar 2019, alle ore 12:04, CarlC Internet Services Service Desk > ha scritto: > > Jeff [and Eric], > > Look at SSH port forwarding... I've done this before and it works great... > You cou

Re: [qmailtoaster] mailserver on AWS

Carl, how do you incorporate this in qmail? On 3/2/2019 12:04 PM, CarlC Internet Services Service Desk wrote: Jeff [and Eric], Look at SSH port forwarding... I've done this before and it works great... You could do what Eric suggested, start on a different port, then on another server at a

RE: [qmailtoaster] mailserver on AWS

Jeff [and Eric], Look at SSH port forwarding... I've done this before and it works great... You could do what Eric suggested, start on a different port, then on another server at a more reasonable host provider, forward that port 25 to your AWS instance via SSH. https://www.ssh.com/ssh/tunnel

Re: [qmailtoaster] mailserver on AWS

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