New answers tagged

2

In an answer to another question on mutt, the answerer says they have no problems sending to gmail with an entry like set smtp_url = "smtps://user@gmail.com@smtp.gmail.com:465/" So it seems mutt knows about this situation. Other people suggest url-encoding the @ as %40 but perhaps it depends on the mutt version.


5

Have a look at the smtpd_sender_restrictions and smtpd_sender_login_maps settings. The former can prevent malformed from addresses, while the latter can force the sender address to match the login name. # Prevent malformed senders smtpd_sender_restrictions = reject_non_fqdn_sender # Ensure correct mail addresses reject_unknown_sender_domain # ...


2

While SMTP forging cannot be prevented, and the underlying protocol was not designed with security in mind, you can minimised in postfix the effects of email forging by your internal users. You can configure your postfix and clients to be mandatory to authenticate to send email via port 587 with authentication. That does not however prevent them from ...


4

Some ISPs and organisations have been blocking port 25/TCP to try to control spam relays for more than a decade now. One of the obvious alternatives is hosting your private domain in an international mail server company that offers your service in alternate email ports to port 25, for instance Google/Gmail. As @Stephen also correctly managed to point out ...


1

Port 25 is the standard port that is used over the internet for SMTP communication. If you wish to talk to someone else then it will be over port 25. You can use alternate ports internal to your own network; eg if you have an Amazon server you could configure it to use port 2525 and configure your local machine to talk to that port. But talking to anyone ...



Top 50 recent answers are included