From: Amooti73 <Amooti73@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Permission denied message in Debian 11
Date: Mon, 25 Oct 2021 15:36:36 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-216@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
New issue by Amooti73 on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/216
Description:
This is not really an mblaze issue, I would say. A search for "sendmail permission denied" brings quite a few results, none of which are specific to mblaze nor to Debian, except that it does not seem to happen with Ubuntu. However, I thought I would just report this challenge. I also then switched to dma to see if that might work, but the permission denied message persisted.
I was unable to find a solution within my "technical capacity". I just made a rather crude work around that would allow me to use mcom and mrep as a root user.
When one is root, then $HOME=/root, so, sorry, but I hacked the mcom script to replace $HOME with /home/user (/home/john in my case) and also placed an export statement in /root/.bashrc to so that $MBLAZE points to /home/user/.mblaze
Things worked in Debian 10, but...
I'm sure there are more "elegant" ways to handle this!
next reply other threads:[~2021-10-25 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 13:36 Amooti73 [this message]
2021-10-25 13:42 ` leahneukirchen
2021-10-25 15:08 ` Amooti73
2021-10-25 15:18 ` Amooti73
2021-10-25 15:21 ` Amooti73
2021-10-28 2:52 ` Amooti73
2021-11-06 11:13 ` Amooti73
2021-12-12 16:33 ` [ISSUE] [CLOSED] " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-216@inbox.vuxu.org \
--to=amooti73@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).