monkeyscan: python subprocess OSError: [Errno 2] No such file or directory

I'm getting this when trying to sign a key:

found 1 keys matching your request Traceback (most recent call last): File "build/bdist.linux-x86_64/egg/monkeysign/gtkui.py", line 539, in decoded File "build/bdist.linux-x86_64/egg/monkeysign/gtkui.py", line 562, in process_scan File "build/bdist.linux-x86_64/egg/monkeysign/ui.py", line 359, in export_key File "build/bdist.linux-x86_64/egg/monkeysign/ui.py", line 405, in sendmail File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory

* I could provide a full debug log, if this would be helpful and needed. However, as there are some key IDs etc. inside which I don't want to share, to begin with just the above extract. * I tried to debug this shortly: I'm unsure which file or directory this is about. The tmp keydir inside `/tmp/` gets created and populated correctly. * If there is anything I can do to debug this further or you need additional information, please let me know. * `$ monkeyscan --version 2.x` * `$ git log --oneline | head -n1 8a0bae14 Merge branch 'sidebar_logo' into '2.x'` * `$ gpg --version | head -n1 gpg (GnuPG) 1.4.18` * `$ gpg2 --version | head -n1 gpg (GnuPG) 2.1.11` * `$ dpkg -l | grep "python-qrencode\|python-gtk2\|python-zbar\|python-zbarpygtk" | cut -d " " -f -40 ii python-gtk2 2.24.0-5 ii python-qrencode 1.2-1 ii python-zbar 0.10+doc-10+b1 ii python-zbarpygtk 0.10+doc-10+b1` * Debian environment with software out of jessie, jessie-backports and stretch

mentioned in commit 74c53c59

hi!

thank you for your bug report.

do you have a local MTA installed? what happens if you type the sendmail command in a terminal?

this is probably that you do not have a properly configured MTA on your machine. you need to specify one with --mta or tell monkeysign to directly talk to your SMTP server with --smtp.

i made commit 74c53c59 to improve error handling here. this also seems similar to the bug reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723072

of course, those options should be accessible through the gui, there's issue #20 (closed) for that specific issue.

i'll close this for now, as it seems to be a configuration issue and we have other issues to track broader problems.

Status changed to closed

do you have a local MTA installed?

Yes: Postfix is running, it handles all my mails.

what happens if you type the sendmail command in a terminal?

It exists in /usr/sbin/sendmail, however it's only accessible via sudo. This is the default as it seems, because I didn't changed this. Edit: I've checked five other machines, two running wheezy, three running jessie: On all of them sendmail needs sudo to work.

this is probably that you do not have a properly configured MTA on your machine.

It seems the default sendmail -t doesn't work on my machine. I'm wondering if this is different on other machines, because, as written, at least for Postfix installations this seems to be the default.

that is very odd. when you say "needs sudo to run", what do you mean? i confirm that sendmail is in /usr/sbin/sendmail, which may cause problems for people that do not have /usr/sbin in their path (which is probably very common). This may explain why you need to run monkeysign with sudo to get the proper environment to run sendmail.

It seems I deliberately modify my PATH variable to include sbin directories, which means I have never found out about this problem.

It seems I need to hardcode the default sendmail path with the full path.

As a workaround, you should be able to do monkeysign --mta "sendmail -t" to use monkeysign.

See 7d975b0b for another patch for this.

that is very odd. when you say "needs sudo to run", what do you mean? i confirm that sendmail is in /usr/sbin/sendmail, which may cause problems for people that do not have /usr/sbin in their path (which is probably very common). This may explain why you need to run monkeysign with sudo to get the proper environment to run sendmail.

It seems I deliberately modify my PATH variable to include sbin directories, which means I have never found out about this problem.

Ah, I see. It was late over here, didn't thought about that.

It seems I need to hardcode the default sendmail path with the full path.

Seems appropriate.

See 7d975b0b for another patch for this.

Works as expected.

One last issue remains, for the moment: The From: of the mail reads georg@localhost, the mail gets bounced because it's not fully-qualified. Is this to be expected? If I got this right, the From: should be set (automatically?) to the uid of the key which was used to sign. Am I right on this? Any idea?

Anyway, thanks anarcat for your help and prompt reactions!

from should be set to the uid that was used to sign. please file a separate bug about this. it is possible monkeysign gets confused if you have a weird uid.

mentioned in issue #46