-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Good afternoon, all.

... I thought I was through tiling my floor, then broke three tiles
(42x42cm). Let me ask you something else, then..:

($!@^}# TILES!!)

I appear to send mail alright with Mutt via Tor. The only constraint is currently that the Fcc Folder must be empty, otherwise mutt_dotlock
cannot lock the corresponding file.

This is less surprising, if you do not redirect STDERR upon startup,
i.e. call the program with

:~$ torify mutt

instead of

:~$ torify mutt 2>/dev/null

The error
“/usr/bin/mutt_dotlock: Operation not permitted” is displayed directly,
in this case.

How can I make the conflict, which must concern rights on the
mutt_dotlock executable, more obvious and easier for me to understand?

The file is currently

:~% ll /usr/bin/mutt_dotlock
- -rwxr-sr-x 1 root mail 141K Aug 12 23:00 /usr/bin/mutt_dotlock

It is quite probable that the difficulty that I am facing here, does not concern so much mutt itself but user-rights in general. Maybe you can
enlighten me anyway..?

Needless to say, none of these phenomena is observed if I start mutt
right away.

TIA,

Michael
- --
GnuPG brainpoolP512r1/5C2A258D 2015-10-02 [expires: 2017-10-01]
sub brainpoolP512r1/53461AFA 2015-10-02 [expires: 2017-10-01]

-----BEGIN PGP SIGNATURE-----

iLUEARMKAB0WIQQqRAnUVLTr0pDaCy3ouAYUXColjQUCWZWi8wAKCRDouAYUXCol jWc5Af9UrlLOi1jnRCtsEk+Dk7kzy6zFiq5khsiVgwLeDQRjYHFV8N/j9IvBBbMx 38i8IsXE8ZMRSlWOHlqMmua5+Nr9Af9N0WW6QhSnFHX1aVHbiHpq4F9xWqo5sIaN lXdDDeAU9/gF06aHcHh9IDV+APekxlLVKKFc9+z34ueHxMAnRRht
=b1rO
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)