Hi! I use gmail, and get nagios alerts in my gmail account, but I dont remember having done anything special to prevent nagios alerts ending up in spam.
After a while I set up a filter in the account to label the nagios incoming mail, just for my comfort. I dont think gmail lets you customize its spam filtering rules, but it does let you mark emails in the spam folder as "not spam" emails. i guess that if you add the sender address to your contacts, they will have less possibilities to end up there. maybe also if you do a rule as i did for that incoming mails, but these are just my happy ideas. Good luck! Jorge On Thu, May 27, 2010 at 11:25 PM, Max Hetrick <[email protected]>wrote: > Drew Weaver wrote: > > > I noticed that a lot of our mail was ending up in users' junk/spam > > folder at GMail and it seems that if you send Nagios warning messages to > > Gmail they somehow assume that your server is malicious and spamming. Is > > it SOP to use a different SMTP server to deliver Nagios messages? > > I'd assume you'd have to take that up with GMail. Or check the spam > filtering settings on the user accounts. I don't use GMail, but I assume > there are junk spam filtering rules that you can do to classify mail on > the settings, like all other e-mail clients and services. > > Regards, > Max > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Nagios-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when > reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null >
------------------------------------------------------------------------------
_______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
