@se7en @Untersuchende i have no idea how to even use [neo]mutt. the manuals seemed cryptic.

@icedquinn @Untersuchende
2021-01-24-134018_953x247_scrot.png

@icedquinn @Untersuchende Didn't fix it

[13:41 root@lappy se7en] > ls -ld /usr/bin/mutt_dotlock
-rwxr-sr-x 1 root mail 15K Nov 23 00:26 /usr/bin/mutt_dotlock

@Untersuchende @icedquinn Fixed, and logged for the future.
2021-01-24-135714_484x602_scrot.png

@se7en @Untersuchende why do you use torify

@icedquinn @Untersuchende Because I prefer to use the cock.li onion

@se7en @Untersuchende oh. i've just been using the proxy settings, or the full captive proxy that forces everything through it.

@icedquinn @Untersuchende To my knowledge, mutt has no native proxy. I'm also using this decades old thing now:

[14:00 se7en@lappy ~] > which FetchMailAlive
FetchMailAlive is a function
FetchMailAlive ()
{
if test -f $CONF_FILE && test -f $FETCHMAIL; then
if test -f $PID_FILE; then
if ! kill -0 `cut -d \ -f1 $PID_FILE` 2> /dev/null; then
eval $($TSOCKS $FETCHMAIL);
echo New FetchMail started. 1>&2;
fi;
else
eval $($TSOCKS $FETCHMAIL);
echo New FetchMail started. 1>&2;
fi;
else
echo Fetchmail not installed or configured properly. 1>&2;
fi
}

@se7en @Untersuchende

tbh i would clunk most of that and use mbsync or fdm. (well, i have used both but for different reasons.)

procmail is very, very dead and has never-fixed issues.

fetchmail is probably fine since it still gets maintained.

@icedquinn @Untersuchende It's all I know. I'm not a stickler, I just really know no good alternatives

@se7en @Untersuchende https://github.com/neomutt/neomutt/issues/99 bummer.

@Untersuchende @se7en huh i just went checking.

mbsync doesn’t have an option for a socks proxy option either. fdm does. msmtp does too.

well i guess torify works fine.

@icedquinn @Untersuchende Yes, it's a process that formerly worked and I am finishing fixing it. Meanwhile, this is also an issue for a long while

https://freespeechextremist.com/notice/A3ZirvFhWi7I6e9UXI

my `dnscrypt-proxy -h` doesn't show any of those flags.

@icedquinn
Neither does mine. However it was formerly standard (and working) behavior