FS#45338 - [mutt] Latest version (mutt-1.5.23.hg.20150606-2-x86_64.pkg.tar.xz) can not run in unattended mode

Attached to Project: Arch Linux
Opened by Greg KH (gregkh) - Monday, 15 June 2015, 22:29 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 11 July 2015, 22:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

With the latest update to mutt to the hg tree, running mutt from a procmail script causes it to hang consuming CPU cycles and the message is never sent.

Downgrading to the previous version mutt-1.5.23-2-x86_64.pkg.tar.xz fixes everything.

I am using

mutt -s "Re: ${re_subject}" "${email}" < ${respond_file}

As from a script called from procmail to send out an automated response email when receiving messages that match a specific pattern. This now does not work, the message is not sent. Running strace on the process shows nothing, I do not know where it is hanging.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Saturday, 11 July 2015, 22:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  mutt-1.5.23.hg.20150711-2 in [testing]
Comment by Gaetan Bisson (vesath) - Tuesday, 16 June 2015, 01:38 GMT
Running `mutt -s 'Re: test' my@email <<<'rofl'` directly from the command line works for me. My SMTP server is Sendmail 8.13.6/1.01.28121999. Could you try and find a simple way I could reproduce this problem from my command line?

Alternatively, if you can bisect the faulty upstream commit, I'd be happy to revert it and we could tell upstream about it.
Comment by Greg KH (gregkh) - Tuesday, 16 June 2015, 16:26 GMT
Yeah, running from a command line works here for me as well, something must be odd with the environment when spawned from procmail.

I'll run bisect to try to track this down upstream as obviously the issue is there. I'll let you know how it goes, thanks.
Comment by guido (qqqqqqqqq9) - Tuesday, 16 June 2015, 17:32 GMT
Hi, I observed the same behaviour when calling a script containing this line:

echo "" | mutt -F /home/guido/.Mutt/muttgmdf example@example.org -s "test.file" -a test.file

from a systemd.service-file
Comment by Gaetan Bisson (vesath) - Tuesday, 23 June 2015, 20:32 GMT
I was able to reproduce this issue by running guido's command inside `env -i sh` and it seems setting the TERM environment variable fixes it.

Could you try prepending TERM=xterm to your script and see if that works?
Comment by Gaetan Bisson (vesath) - Saturday, 11 July 2015, 19:41 GMT
I've created this upstream: http://dev.mutt.org/trac/ticket/3761
Comment by Kevin J. McCarthy (kevin8t8) - Saturday, 11 July 2015, 21:50 GMT
Thanks for the bug report. This should be fixed upstream now.

Loading...