Mutt - Slackware-Current

tpreitzel · 11-07-2010, 01:15 AM

This version of mutt seems to be broken ... at least as far as working with motion and msmtp to automatically transmit detected video images to my e-mail account.

I don't see any errors, mutt simply doesn't transmit the data via msmtp as it should.

I switched back to the version of Mutt in Slackware 13.1 and the automatic transmission of video detected by motion and transmitted by mutt via msmtp started working properly.

I don't know...what the problem is.

business_kid · 11-07-2010, 02:44 AM

Have a look in the ChangeLog. And make sure your muttrc hasn't been overwritten. Not much can go wrong with mutt, unless you're asking it to be graphical.

tpreitzel · 11-07-2010, 04:55 AM

Quote:

Originally Posted by business_kid

Have a look in the ChangeLog. And make sure your muttrc hasn't been overwritten. Not much can go wrong with mutt, unless you're asking it to be graphical.

I know which is why I'm scratching my head in confusion... Everything is identical with the possible exception of the system wide Muttrc in /etc/mutt ... I'm simply using the stock system wide Muttrc and my personal .muttrc which hasn't changed. The 13.1 version works great. The Slackware-Current version does not. Bizarre.

business_kid · 11-08-2010, 02:45 AM

Humour me and run
which mutt
ldd /path/to//mutt |grep found

You may be missing a dependency. It could also be a compile time option in the new mutt.

tpreitzel · 11-09-2010, 04:00 PM

Quote:

Originally Posted by business_kid

Humour me and run
which mutt
ldd /path/to//mutt |grep found

You may be missing a dependency. It could also be a compile time option in the new mutt.

Code:

ldd /usr/bin/mutt
	linux-vdso.so.1 =>  (0x00007fffbf517000) 
	libncursesw.so.5 => /lib64/libncursesw.so.5 (0x00007fa1b46e4000)
	libssl.so.0 => /lib64/libssl.so.0 (0x00007fa1b4493000)
	libcrypto.so.0 => /lib64/libcrypto.so.0 (0x00007fa1b410e000)
	libz.so.1 => /usr/lib64/libz.so.1 (0x00007fa1b3ef8000)
	libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007fa1b3cdf000)
	libgdbm.so.3 => /usr/lib64/libgdbm.so.3 (0x00007fa1b3ada000)
	libgpgme.so.11 => /usr/lib64/libgpgme.so.11 (0x00007fa1b38a6000)
	libgpg-error.so.0 => /lib64/libgpg-error.so.0 (0x00007fa1b36a3000)
	libidn.so.11 => /usr/lib64/libidn.so.11 (0x00007fa1b3471000)
	libc.so.6 => /lib64/libc.so.6 (0x00007fa1b30ef000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007fa1b2eeb000)
	libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fa1b2cd0000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa1b493e000)

Piping the output through the command, grep found, simply yields nothing with both versions of mutt, 1.4.2.3 and 1.5.21

When I switch from 1.5.21 to 1.4.2.3, mutt starts transmitting my captured video data via msmtp. Version 1.5.21 of mutt doesn't work in application with motion and msmtp. Strange

business_kid · 11-10-2010, 09:48 AM

ldd program |grep founf returning nothing means it's got it's dependencies.

I imagine it is a compile time option. Something on-by default going off-by-default or the like.

Bruce Hill · 11-11-2010, 01:45 AM

Check the configure options in the two mutt.SlackBuild scripts,
as they have (finally) with that 1.5.21 version been updated in
Slackware. For years I've always built my own Mutt for other
options that I required.

Post the /etc/Muttrc and your ~/.muttrc if you want others to
have a look, though the one in ~/ should override /etc/Muttrc.

Also, what about your ~/.msmtprc file? I'm using msmtp and getmail
and maildrop with Mutt, but not this "automatic transmission of
video detected by motion and transmitted by mutt via msmtp".

bl0tt0 · 11-11-2010, 12:28 PM

Perhaps it isn't the solution requested by the parent, but haven't they added SMTP support to mutt in the 1.5 series, making msmtp unnecessary?

tpreitzel · 11-11-2010, 08:22 PM

Quote:

Originally Posted by bl0tt0

Perhaps it isn't the solution requested by the parent, but haven't they added SMTP support to mutt in the 1.5 series, making msmtp unnecessary?

I'd like to know.

tpreitzel · 11-11-2010, 08:28 PM

Quote:

Originally Posted by Bruce Hill

Check the configure options in the two mutt.SlackBuild scripts,
as they have (finally) with that 1.5.21 version been updated in
Slackware.

I'll check a bit later. Since the ONLY difference is the two Mutt packages, the problem really must be due to configuration options.

Quote:

Post the /etc/Muttrc and your ~/.muttrc if you want others to
have a look, though the one in ~/ should override /etc/Muttrc.

Also, what about your ~/.msmtprc file? I'm using msmtp and getmail
and maildrop with Mutt, but not this "automatic transmission of
video detected by motion and transmitted by mutt via msmtp".

From motion.conf:

on_picture_save echo %f | mutt -s '[Motion Image]' -a %f xxx@xxx.xxx < '.'

From .msmtprc:

account default
host smtp.xxx.xxx
protocol smtp
user xxx
password xxx
tls on
tls_nocertcheck
auth on

From .muttrc:

Code:

set realname='Slackware User'
set pop_user="xxx@xxx.xxx"
set pop_pass="xxx"

# Where we store our emails
set folder=~/Mail
set mbox=+mbox
set spoolfile=+inbox
set record=+sent
set sort=threads # sort by emails by thread ;-)
set postponed=+drafts
set mbox_type=Maildir
set sendmail="/usr/bin/msmtp"
set from="xxx@xxx.xxx"
set use_from=yes
set envelope_from="yes" 
mailboxes +inbox

# my favourite editor is 'joe'
set editor=joe

ignore *	# this means "ignore all headers by default"
# I still want to see some basic details
unignore	date from subject to cc

# Mutt options
set edit_headers=yes
set hdrs # Allows us to create our own headers
my_hdr From: Slackware User <xxx@xxx.xxx>
my_hdr X-Mailer: `mutt -v| head -n 1`

Bruce Hill · 11-11-2010, 08:54 PM

You can easily check the build options by diffing the mutt.SlackBuild
scripts. Enabling smtp doesn't "make msmtp unnecessary." Whether
or not you use msmtp as your smtp client is a matter of choice.

I've always built mutt with:

Code:

  --enable-gpgme \
  --disable-pgp \
  --enable-pop \
  --enable-smtp \ 
  --enable-debug \
  --enable-nfs-fix \
  --enable-locales-fix \
  --enable-exact-address \
  --enable-hcache \
  --with-curses=/usr/include/ncurses \
  --with-mailpath=~/Mail \
  --with-ssl=/etc/ssl \
  --with-gnutls=/usr/include/gnutls \
  --with-sasl=/usr/include/sasl \

amongst other options, and still use msmtp as my SMTP client.

If you, as I, choose to use msmtp you must tell your MUA to call
it rather than sendmail, or other. In your ~/.muttrc you would have:

Code:

set sendmail="/usr/bin/msmtp"

rather than /usr/bin/sendmail

Seems like you still need to do some homework to determine why you're
having this problem with mutt-1.5.21.

As for me, I don't even know what you mean by "automatic transmission of
video detected by motion and transmitted by mutt via msmtp", so there is
no way I can help with that issue.

Edit: starting replying while you posted ... will look at it later