Most cloud providers these days will block port 25 outbound to decrease the level of spam coming from their network. In most cases you will need to open a ticket to get it opened, maybe provide some info on how/what your spam policy is and some require you to have an active service for at least one billing cycle.
Talk to your provider and ask, they are the only ones that can help you directly with this.
The other option is to use a relay service, such as MailChannels, Sendgrid, SMTP2GO, mail.baby or similar (I’d recommend mail.baby as they’re run by good people, the same as the ones behind interserver.net, and the pricing is very fair).
I’m getting the emails but not it not sending, i check here “https://yourservergoeshere:10000/postfix/mailq.cgi?xnavigation=1” and found status all emails are in connection timeout or some of them are in Network is unreachable, This status i’m getting
Can you help me on this how to fix it?
You don’t control the rest of the world. You can’t tell every SMTP server in the world to listen on a different port. Port 25 is the SMTP port. If you don’t have port 25 (and you don’t on most major cloud providers), you don’t have a mail server.
You’ll need to use a relay service. This is documented at Amazon (and at every other major cloud provider).
But, there are benefits to letting others solve the deliverability problem. It’s probably that any IP you get at Amazon will be burned from previous abuse, and so you’ll find yourself blocked by at least a few mail servers until you jump through whatever hoops are needed to get unblocked (getting off of DNSBL/RBL lists, or contacting the server owner directly via whatever form they provide…it can be quite time-consuming, takes days or weeks to get through the Microsoft process, for instance, and you may have several to deal with).
Got it buddy so only option is left need to contact with AWS to remove this restrictions, and I don’t think the support will remove this as I want to send an bulk email. Okay let’s see thankyou @toreskev@ID10T@Joe for help me out from this situation
You’ll want to use one of the many mail relay services. Maintaining deliverability for a mail server that sends a lot of mail is a challenge, even once you get it going. People mark stuff spam even if they subscribed to it, rather than unsubscribing (even if it’s easy to unsubscribe), and so you end up in a constant battle to maintain reasonable delivery.
Anyway, that’s what we do for the forum and our website notifications. It’s not wildly expensive (about ten bucks a month for all of our outgoing mail, and we send about 15k mails every month). We’re using Mailgun, but there are many, and probably some cheaper. I think Amazon’s service would be quite a bit cheaper, actually, but it didn’t exist when I set all this up.
I believe Amazon runs an external firewall on you instance. You do have the ability to open and close both incoming and outgoing ports. Been a while so I don’t remember the specifics.
I have a low end instance just for DNS. I just looked at the interface. (I use ‘Lightsail’. It seems it is only for inbound traffic. Not what I remembered but it has been months since I set it up.
EDIT: I forgot that I had a Discourse instance running as a test bed. I just tried password reset and got an email. I don’t remember having to set up anything with Amazon to get those emails out.
Hello. I also fail with SMTP.
April hasn’t failed. It fails on the server I installed the day before yesterday.
Virtualmin > System Settings > Server Templates > Default Settings > Mail for domain > Format for usernames that include domain
username@domain：NG
username-domain: OK
I want to use username@domain, but I don’t know how to do it in [?].
The username@domain option is not recommended unless you are migrating users from another system that already uses it. The Postfix mail server has problems with SMTP authentication by users with an @ in the username, and requires that an extra Unix user be created for each mailbox for mail delivery to work.
They let a few in as I get spam from there network.