Many thanks for your quick response. After checking the logs (nothing
suspicious) I tried the "msmtpqueue" command. Sure enough, all of my VMs were
still sitting on the box. I tried to poke around further, but in frustrating
rebooted the box… what do you know, problem fixed!
When all else fails: Ctrl-Alt-Delete
Not sure why the mailer failed; as I said, no messages in the logs.
> As Michael mentioned, your best bet is to troubleshoot a mail problem. If
> it used to work and all of a sudden stopped, that might indicate an issue
> with the mail server you are have configured. It seems unusual that a test
> message would make it while a VM notification wouldn't, but you should be
> able to quickly ascertain the failure in the log files.
>
> For example, I didn't receive a VM via email the other day, and saw it was
> because one of the VPN links was down:
> Mar 5 12:32:29 voip mail.err msmtp: host=172.22.0.1 tls=on auth=off from=
> r...@voip.routed.com (mailto:r...@voip.routed.com)
> recipients=ja...@routed.com (mailto:ja...@routed.com) *errormsg='cannot
> connect
> to 172.22.0.1, port 25: Connection timed out' exitcode=EX_TEMPFAIL*
>
> I imagine you will see something similar.
>
> --James
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
