|
On Jan 23, 2018, at 1:04 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:
On Tue, Jan 23, 2018 at 9:04 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
We originally used the SMTP services for email but, as Brad I'm sure will
attest, it was just too much work when things went adrift. Subsequently we
switched to using PHP for mail - which was a breeze to use and much more
reliable.
Jon,
You say that you switch from IBM i SMTP to PHP. But I'm wondering if you
just switched from something like the IBM i SNDDST command to the PHP
mail() function. I think the distinction is important.
Most email APIs will simply forward messages to a separate, local service,
then return control to the originator. That separate local service runs
asynchronously and manages the communications, encryption, retries, and
final error / completion logging, which your email application may never
know about. That separate local service is called an SMTP client. And a
fairly robust one is bundled with IBM i. It runs as a pool of pre-start
jobs that may be servicing requests from multiple applications.
I wonder if the implementation of the PHP mail() command on IBM i actually
relays messages to the IBM i SMTP client under the covers? I couldn't find
any documentation on that. If not, then what SMTP client does it use?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.