No such thing as a small change | |
PerlMonks |
Re^6: MTA for Perlby afoken (Chancellor) |
on Mar 21, 2024 at 23:59 UTC ( [id://11158472]=note: print w/replies, xml ) | Need Help?? |
Is there an advantage of Nullmailer vs. Email::Sender::Transport::SMTP::Persistent ? One very obvious: nullmailer works for the entire system, not just for perl scripts that happen to use E::S::T::S::P. So you will also get mails from cron when cron jobs aren't silent, smartd will complain about failing disks, mdadm will complain about failing RAIDs, sudo will complain about people trying to get root privileges, and so on. And of course, any application or user can simply invoke sendmail to send a mail. The other one is that you don't need to keep an SMTP connection open. E::S::T::S::P blocks server resources, which is not friendly. (You will probably don't mind if it is your local, bored server.) The last few times I manually fiddled with a telnet client connected to SMTP servers, they simply closed the connection after a a few seconds of idle time. Keeping an open SMTP connection is very typical for humans, but very untypical for SMTP clients. So the servers just kick you out. And I would guess the same happens with E::S::T::S::P. Probably nobody notices, as it seems to silently reconnect if needed. I don't know, I don't use Email::Sender, but if I would want to know, I would add some print statements to E::S::T::S::P::_smtp_client(). Alexander
-- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
In Section
Seekers of Perl Wisdom
|
|