|
Wrong. If it does this, it's set up wrong. Sending email from the i is no
In 99.9% of the cases, this is how it works with PC clients or clientssuch
as SNDDST, MSF, MAILTOOL, ESEND, etc.
Again, we're not talking about sending email from PC clients.
I'll leave it to you and Richard to explain how MAILTOOL and ESEND works.
But SNDDST and MSF use the IBM i SMTP client to connect send email directly
to recipients, without the help of a relay service.
I won't get into why (except reverse DNS being one) but rarely if everYou would if you dealt with email on the i as much as I have. :)
should email be delivered directly from the client to the recipient.
I don't understand your point regarding reverse DNS, but I do understand
that you "won't get into why".
The protocol itself isn't secure, just like HTTP isn't secure but HTTP overPort 25 is only for non-secure connections. 465, 587 and others are used
for SSL/TLS. When connecting to a mail router that requires that type of
authentication.
In regard to port 25 being used for non-secure communications, SMTP is not
a secure protocol. My understanding is that some server along the chain
will eventually connect to the SMTP server on port 25 at the final endpoint
to deliver the message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.