Your message dated Wed, 19 Dec 2018 13:04:14 +0000
with message-id <20181219130414.nse6zldqt3bmmk3h@viper>
and subject line Re: torsocks: procmail spawned by mpop in torsocks fails with
"Operation not permitted"
has caused the Debian Bug report #865368,
regarding torsocks: procmail spawned by mpop in torsocks fails with "Operation
not permitted"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
865368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865368
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: torsocks
Version: 2.2.0-1
Severity: normal
Dear Maintainer,
I use procmail as my mda in mpop, with this line in the config file (as
suggested in the documentation):
delivery mda /usr/bin/procmail -f '%F' -d $USER
Running 'torsocks mpop' fails if there are any mails waiting to be collected,
with the (example) output:
new: 1 message in 31.02 KiB, total: 1 message in 31.02 KiB
retrieving message 1 of 1 (31.02 KiB): sh: 1: /usr/bin/procmail: Operation
not permitted
38
mpop: cannot write mail: output error
mpop: error during mail retrieval (account default from /home/nick/.mpoprc)
This only started happening when I upgraded to stretch, in jessie this worked
perfectly.
Running mpop not through torsocks works fine, and torsocks can write to files
generally (tested with 'torsocks wget debian.org')
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.10-ph+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages torsocks depends on:
ii libc6 2.24-11+deb9u1
Versions of packages torsocks recommends:
ii tor 0.2.9.11-1~deb9u1
torsocks suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Tags: wontfix
Hi Ulrike, thanks for looking into this for me.
> does this still occur?
This issue does still occur in Stretch, yes.
> mpop seems to have examples working with Tor though:
> https://www.mankier.com/1/mpop#Examples
I hadn't seen the section of the manpage with the working Tor
example, though, many thanks for pointing me to that. I have tested
it, and that solution works fine.
I'm closing the bug report, as this method is just as reasonable as
using torsocks, and is well documented (despite my failure to find
it).
I'm quite new to the debian bugtracker, hopefully I've done
everything right, apologies if not.
Thanks,
Nick
--- End Message ---
