From: Gordon <mo...@re...> - 2011-12-14 05:29:22
|
I have had Motion servers send emails with jpg attachments in the past. I realized those systems were Debian with Motion running as root. In this Ubuntu system I'm running Motion from the stock repository, which runs as unprivileged user motion (which is a good thing). As I did with root back then, I'm using Mutt with command line arguments to send the message; this is the only way I know to email with an attachment. The problem is that the motion user cannot send the email message. In testing with "sudo -u motion mutt" the program comes up and I create the message (with no attachment for test), but the program hangs when it tries to send the message. Ctrl-C breaks me out and that is as far as I get. No error message, and nothing in any of the log files to point the way. I don't see any particular place where permission to send email is being granted or denied in Postfix (assumed group permission, but it doesn't look that way). Mutt works as expected when run as a regular privileged (shell) user. I could try to run motion as a privileged user by editing "NAME=" in the /etc/init.d/motion file, but I'd rather stay with the motion user if possible. Not a problem with Motion itself, but I imagine others have encountered this or similar problems using Motion to email pictures or videos. Thank you. |
From: John <jo...@to...> - 2011-12-14 13:24:51
|
On 12/13/11 23:11, Gordon wrote: [snip] > Not a problem with Motion itself, but I imagine others have encountered > this or similar problems using Motion to email pictures or videos. http://www.lavrsen.dk/foswiki/bin/view/Motion/SupportQuestion2009x03x23x115315 I recently updated that entry with possible reason why problem occurs (assuming it is same issue as yours). The method indicated worked for me. I will put my solution here as the page above doesn't come up easiliy in a search: on_movie_end /usr/local/bin/motion_send_mail %f contents of motion_send_mail (bulk of script copied from someone else's example). Complexity of the uuencode line (not relevant to your issue) is due to what is needed to get Android phone to play video: #!/bin/sh # Motion sample script to send an e-mail at start of an event. # Replaces the former 'mail' option. # Just define this script as 'on_event_start'-script in motion.conf like that: # on_event_start send_mail "%Y-%m-%d %T" #change to suit your needs: #location of 'mail' binary MAIL="/bin/mail" #Destination e-mail address TO="no...@no..." #Subject of the e-mail SUBJECT="Motion detected" #echo -e "This is an automated message generated by motion.\n\nMotion detected: $1\n\n" | $MAIL -s "$SUBJECT" $TO mencoder $1 -o $1.mp4 -speed 0.1 -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -sws 9 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=512:threads=auto:turbo=1:global_header:threads=auto:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh uuencode $1.mp4 Video.mp4 | $MAIL -s "$SUBJECT" $TO rm $1.mp4 |
From: Gordon <mo...@re...> - 2011-12-14 17:00:56
|
Thanks, though I do not think that will help with my problem. I am surprised, however, that what you list works for you. I used Mutt in the past because Mail did not support attachments. I don't see here how Mail is sending your video attachment. In my case I have Motion create a video and a last-best jpg (output_normal best) from the video for each motion event. I email just that jpg, which should give me enough information to determine if I need to connect to the server to review the associated video. ----- Original Message ----- From: "John" <jo...@to...> To: mot...@li... Sent: Wednesday, December 14, 2011 7:56:59 AM Subject: Re: [Motion-user] Event Email w/ Attachment - Motion User in Ubuntu On 12/13/11 23:11, Gordon wrote: [snip] > Not a problem with Motion itself, but I imagine others have encountered > this or similar problems using Motion to email pictures or videos. http://www.lavrsen.dk/foswiki/bin/view/Motion/SupportQuestion2009x03x23x115315 I recently updated that entry with possible reason why problem occurs (assuming it is same issue as yours). The method indicated worked for me. I will put my solution here as the page above doesn't come up easiliy in a search: on_movie_end /usr/local/bin/motion_send_mail %f contents of motion_send_mail (bulk of script copied from someone else's example). Complexity of the uuencode line (not relevant to your issue) is due to what is needed to get Android phone to play video: #!/bin/sh # Motion sample script to send an e-mail at start of an event. # Replaces the former 'mail' option. # Just define this script as 'on_event_start'-script in motion.conf like that: # on_event_start send_mail "%Y-%m-%d %T" #change to suit your needs: #location of 'mail' binary MAIL="/bin/mail" #Destination e-mail address TO="no...@no..." #Subject of the e-mail SUBJECT="Motion detected" #echo -e "This is an automated message generated by motion.\n\nMotion detected: $1\n\n" | $MAIL -s "$SUBJECT" $TO mencoder $1 -o $1.mp4 -speed 0.1 -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -sws 9 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=512:threads=auto:turbo=1:global_header:threads=auto:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh uuencode $1.mp4 Video.mp4 | $MAIL -s "$SUBJECT" $TO rm $1.mp4 ------------------------------------------------------------------------------ Cloud Computing - Latest Buzzword or a Glimpse of the Future? This paper surveys cloud computing today: What are the benefits? Why are businesses embracing it? What are its payoffs and pitfalls? http://www.accelacomm.com/jaw/sdnl/114/51425149/ _______________________________________________ Motion-user mailing list Mot...@li... https://lists.sourceforge.net/lists/listinfo/motion-user http://www.lavrsen.dk/twiki/bin/view/Motion/WebHome |
From: John <jo...@to...> - 2011-12-15 00:44:53
|
On 12/14/11 11:00, Gordon wrote: > Thanks, though I do not think that will help with my problem. I am surprised, however, that what you list works for you. I used Mutt in the past because Mail did not support attachments. I don't see here how Mail is sending your video attachment. Here is the relevant line modified into a more generic instantiation: uuencode <filname> | /bin/mail -s "<subject>" <recipient email address> This is not specific to type of file. You should be able to simply specify an image file instead of a movie file. If your problem is other than not being able to send attatchments without privilege issues, then please clarify. If your problem needing to get mutt to work, than like you I had same problem. Instead, I used /bin/mail instead to send an attatchment. John |
From: Gordon <mo...@re...> - 2011-12-15 06:38:26
|
Thank you masam, but John's suggestion did the trick. > Here is the relevant line modified into a more generic instantiation: > uuencode <filname> | /bin/mail -s "<subject>" <recipient email address> Not being familiar with the uuencode program, I did not read your first message correctly. Yes, changing my script to include this command works great, and with no changes to the motion user account. Thanks for the help. I did run into one problem, however. I started to test your mencoder line since I also have an Android phone, but that brought to light a related problem: The attachments don't show up in the native Android mail program, but do show up in a normal email program. On the phone the message does not indicate any attachment is present, yet it's there in the same message in my regular email application. This happens with JPG attachments and a video file re-encoded with your mencoder routine (which made a Motion-created MPEG4 file blurry and about three times larger, for some reason). I receive attachments on the phone all the time with no problem (Captivate w/ Froyo 2.2). Any idea what is going on here? Thanks. |
From: John <jo...@to...> - 2011-12-15 12:58:49
|
On 12/15/11 00:38, Gordon wrote: > Thank you masam, but John's suggestion did the trick. > >> Here is the relevant line modified into a more generic instantiation: >> uuencode<filname> | /bin/mail -s "<subject>"<recipient email address> > > Not being familiar with the uuencode program, I did not read your first message correctly. Yes, changing my script to include this command works great, and with no changes to the motion user account. Thanks for the help. I did run into one problem, however. > > I started to test your mencoder line since I also have an Android phone, but that brought to light a related problem: The attachments don't show up in the native Android mail program, but do show up in a normal email program. On the phone the message does not indicate any attachment is present, yet it's there in the same message in my regular email application. This happens with JPG attachments and a video file re-encoded with your mencoder routine (which made a Motion-created MPEG4 file blurry and about three times larger, for some reason). I receive attachments on the phone all the time with no problem (Captivate w/ Froyo 2.2). > > Any idea what is going on here? > > Thanks. I use the gmail app have not tried with another email app. I can't offer any assistance with attachments in your situation. In another email there was an alternate approach provided (do not send the atatchment but a link instead). I am not sure of your situation but keep in mind that the system that houses the videos will need to be available at the time the videos are viewed (could be hours). In my case that was a showstopper but this may not apply to you. John |