×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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?
midrange.com
