Talk:Message submission agent

Spam connection

As it stands, the article fails to explain how this is an anti-spam measure. What is there to prevent a spam-virus-worm-whatever on a client machine to connect to the configured MSA and try to send spam over that? It seems that blocking random outgoing connections and anti-spam scanning at servers which allow relay are the anti-spam measures here; the fact that there exists something called an MSA on a separate port is fairly tangential. --Joy [shallot] 23:59, 3 January 2007 (UTC)

see if the update makes this clearer --Keith Moore 8 Feburary 2007

Rename to Message Submission Agent

The reference RFC uses the "Message" term for M in MSA, not "Mail". Rename the article ? G Allegre (talk) 11:11, 21 April 2008 (UTC)

Yes Bonnerglenda (talk) 10:56, 21 March 2019 (UTC)

Examples

It would be wise to include some examples of MSAs. This is common practise. Does anyone know of any? --KitchM (talk) 19:28, 24 March 2011 (UTC)

The difference between MTA and MSA is policy and port, nothing else really, so most intelligent MTAs out there can be configured and used as MSA. I personally use Exim but it's really just one of the many. --grin ✎ 07:44, 28 March 2012 (UTC)

TLS?

The article should mention whether the message is submitted under TLS or in the clear. Port 25 operates in the clear. Likely 587 does also but it's worth mention. Does submission under TLS exist? It has another name? Thanks, ... PeterEasthope (talk) 19:49, 29 January 2020 (UTC)

465? smtps?

this article lacks information about submission over tcp port 465 / smtps. RFC8314 recommends smtps. nevertheless, there is SMTPS :-) Niki W. Waibel (talk) 00:16, 18 June 2020 (UTC)