Bug #27430 for Mail-Sender: would like timeout for MailMsg()

Mon Jun 04 18:31:27 2007 krishnoid [...] wapacut.com - Ticket created

Subject:

would like timeout for MailMsg()

MailMsg() hung on us over the weekend, partly due to a misconfigured DNS record including one bad mx in rotation with other good ones. This may be a corner case, but it would be helpful if there was at least an optional timeout value for connecting and transmitting the message. This way, persistent daemons (or programs run out of cron) using this module for sending out notification wouldn't silently hang. I'm the first to admit that mail systems should have their own monitoring, but it seems that a timeout value to MailMsg() makes sense regardless. For now, I'm wrapping my call to it in an alarm() eval {}.

Thu May 05 14:53:40 2016 cwhitener [...] gmail.com - Taken

Thu May 05 14:54:16 2016 cwhitener [...] gmail.com - Correspondence added

Hi! Unfortunately, I don't think adding extra features to this dist is likely to happen. The go-to mail sending distribution these days is Email::Sender. https://metacpan.org/pod/Email::Sender::Transport::SMTP If you look at the SMTP transport there, there's a timeout attribute you can set. Moving to this up-to-date mailer that's well maintained is the best option. My plan for this dist is to fix as much of the documentation up as possible, clean up any current bugs and mark it as deprecated. I do not plan on adding new features at this time. Hope that helps. Thanks, Chase

Thu May 05 14:54:16 2016 The RT System itself - Status changed from 'new' to 'open'

Thu May 05 15:20:39 2016 cwhitener [...] gmail.com - Correspondence added

I'm going to mark this ticket as rejected for now because marking it as resolved seems wrong. It would be a new feature and we're in maintenance mode. Thanks, Chase

Thu May 05 15:20:44 2016 cwhitener [...] gmail.com - Status changed from 'open' to 'rejected'

Bug #27430 for Mail-Sender: would like timeout for MailMsg()

Preferred bug tracker