How to get ssmtp working with Zoneminder - Revision history

Snake: /* Installation of SSMTP */

2020-10-15T11:46:39Z

Installation of SSMTP

← Older revision		Revision as of 07:46, 15 October 2020
Line 24:		Line 24:

	You may not need mailutils, but that installs the "mail" utility that I find quite handy to send emails from the command line.		You may not need mailutils, but that installs the "mail" utility that I find quite handy to send emails from the command line.
			NOTE: After debian 9, ssmtp has been deprecated in favor of alternatives such as msmtp. See https://wiki.zoneminder.com/SMS_Notifications

	=== Configuration of SSMTP ===		=== Configuration of SSMTP ===

Snake: /* Why do you need this */

2020-07-23T18:11:16Z

Why do you need this

← Older revision		Revision as of 14:11, 23 July 2020
Line 3:		Line 3:
	===Why do you need this===		===Why do you need this===

	If you want Zoneminder to send you emails about alarms, you need to configure a way for ZM to send emails. SSMTP is one of several ways, and a lightweight and efficient one.		If you want Zoneminder to send you emails about alarms, you need to configure a way for ZM to send emails. SSMTP is one of several ways, and a lightweight and efficient one. MSMTP can also be used.


	=== Background===		=== Background===

Snake at 01:16, 26 January 2018

2018-01-26T01:16:41Z

← Older revision		Revision as of 21:16, 25 January 2018
Line 153:		Line 153:
	==== Gotcha while testing an event ====		==== Gotcha while testing an event ====
	I spent a good half hour frustrated by zmfilter.pl not matching my event I wanted to email. Remember, that everytime ZM thinks it has "emailed" an event out, it enables a flag next to the event in its DB that says "IsEmailed=1". This is how ZM knows which events it needs to email to you as zmfilter runs on schedule. So you can't keep testing email with an old event. In my case, I was testing an event when not using the "new mail modules" and ZM thought it sent out, but as I wrote earlier, the old mail modules don't work with ssmtp but because there was no error detected, ZM marked that event as "emailed" and zmfilter would never match it again. So be aware of this.		I spent a good half hour frustrated by zmfilter.pl not matching my event I wanted to email. Remember, that everytime ZM thinks it has "emailed" an event out, it enables a flag next to the event in its DB that says "IsEmailed=1". This is how ZM knows which events it needs to email to you as zmfilter runs on schedule. So you can't keep testing email with an old event. In my case, I was testing an event when not using the "new mail modules" and ZM thought it sent out, but as I wrote earlier, the old mail modules don't work with ssmtp but because there was no error detected, ZM marked that event as "emailed" and zmfilter would never match it again. So be aware of this.

			== See Also ==

			* [[SMS_Notifications]]

Snake: /* Configuration of ZoneMinder */

2018-01-20T00:30:08Z

Configuration of ZoneMinder

← Older revision		Revision as of 20:30, 19 January 2018
Line 88:		Line 88:

	'''Below two options in 1.30 or higher'''		'''Below two options in 1.30 or higher'''
	* SSMTP_Mail: check this ~~off~~.		* SSMTP_Mail: check this.
	* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp		* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp

Snake: /* Configuration of ZoneMinder */

2017-03-17T01:16:53Z

Configuration of ZoneMinder

← Older revision		Revision as of 21:16, 16 March 2017
Line 87:		Line 87:
	* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN		* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN

	'''Below two options in >1.30 ~~only~~'''		'''Below two options in 1.30 or higher'''
	* SSMTP_Mail: check this off.		* SSMTP_Mail: check this off.
	* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp		* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp

Snake: /* Configuration of ZoneMinder */

2017-03-17T01:15:15Z

Configuration of ZoneMinder

← Older revision		Revision as of 21:15, 16 March 2017
Line 87:		Line 87:
	* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN		* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN

	'''Below in >1.30'''		'''Below two options in >1.30 only'''
	* SSMTP_Mail: check this off.		* SSMTP_Mail: check this off.
	* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp		* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp

Snake at 01:14, 17 March 2017

2017-03-17T01:14:12Z

← Older revision		Revision as of 21:14, 16 March 2017
Line 86:		Line 86:
	* FROM_EMAIL: I put in root@localhost		* FROM_EMAIL: I put in root@localhost
	* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN		* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN

			'''Below in >1.30'''
	* SSMTP_Mail: check this off.		* SSMTP_Mail: check this off.
	* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp		* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp

Erwing: /* Background */ Typo

2017-01-23T11:48:11Z

Background: Typo

← Older revision		Revision as of 07:48, 23 January 2017
Line 7:		Line 7:

	=== Background===		=== Background===
	SSMTP is a really light mail transfer agent (MTA) that a lot of people use in Linux. It is much more lightweight ~~that~~ sendmail for sure and I am told postfix too.		SSMTP is a really light mail transfer agent (MTA) that a lot of people use in Linux. It is much more lightweight than sendmail for sure and I am told postfix too.
	Note that SSMTP does not really run a daemon process in your box, so trying "telnet localhost 25" is going to fail (and also why a traditional Zoneminder configuration of using local host fails)		Note that SSMTP does not really run a daemon process in your box, so trying "telnet localhost 25" is going to fail (and also why a traditional Zoneminder configuration of using local host fails)
	Instead what is does is this:		Instead what is does is this:
Line 14:		Line 14:

	If you are running ZM on a "not to high end" machine and are monitoring more than 3-4 HD cameras, you will want to be prudent on what you want to install. SSMTP is a great choice.		If you are running ZM on a "not to high end" machine and are monitoring more than 3-4 HD cameras, you will want to be prudent on what you want to install. SSMTP is a great choice.


	=== Installation of SSMTP===		=== Installation of SSMTP===

Snake: /* Configuration of ZoneMinder */ Missing steps.

2016-12-26T03:07:44Z

Configuration of ZoneMinder: Missing steps.

← Older revision		Revision as of 23:07, 25 December 2016
Line 87:		Line 87:
	* FROM_EMAIL: I put in root@localhost		* FROM_EMAIL: I put in root@localhost
	* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN		* URL: If you have configured your ZM to be accessible using a public DNS (maybe using no-ip DDNS or others), you should put in the web address here. It will be something like http://yourzoneminderurl.domain:port/zm (unless you have changed it). When you get alarms, ZM provides a link and uses this url as a base. You can put in a LAN IP here too, but then you will only be able to access it from your LAN
			* SSMTP_Mail: check this off.
			* SSMTP_Path: Depends on your distribution. Try $ whereis ssmtp

	BTW, the reason you need to use NEW_MAIL_MODULES with SSMTP is that if this is checked, ZM uses two Perl packages called MIME::Lite and Net::SMTP instead of MIME::Entity. MIME::Entity uses configuration from mail files that SSMTP does not use. And if you don't check this, you will see your logs saying "mail is sent" but nothing is really sent.		BTW, the reason you need to use NEW_MAIL_MODULES with SSMTP is that if this is checked, ZM uses two Perl packages called MIME::Lite and Net::SMTP instead of MIME::Entity. MIME::Entity uses configuration from mail files that SSMTP does not use. And if you don't check this, you will see your logs saying "mail is sent" but nothing is really sent.

Asker: /* ssmtp.conf */

2016-07-10T10:31:03Z

ssmtp.conf

← Older revision		Revision as of 06:31, 10 July 2016
Line 43:		Line 43:
	UseTLS=YES		UseTLS=YES
	AuthUser=pp@gmail.com		AuthUser=pp@gmail.com
	AuthPass=something		AuthPass=something # remember if you use 2 factor auth, generate an app specific password
	</nowiki>		</nowiki>