I'm curious what's "wrong" with CSSMTP. There are a lot of functions in CSSMTP that any "reasonable" email sender needs in real-world implementations beyond the transmission protocol. Notable examples including checkpointing, retry, and logging capabilities. If you try to "reinvent the wheel" there's quite a lot of wheel to reinvent. And then you must maintain the bigger wheel going forward.
What are the outstanding problems that CSSMTP doesn't address? ————— Timothy Sipples Senior Architect Digital Assets, Industry Solutions, and Cybersecurity IBM Z/LinuxONE, Asia-Pacific [email protected] +65 8526 7454 Mobile ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
