From: thenktor <thenktor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Dragonly Mail Agent: wrong file ownership of config files
Date: Thu, 09 Dec 2021 21:08:29 +0100 [thread overview]
Message-ID: <20211209200829.6zVy0h2n3ie6csbrZ5kmWibwyB5U0tkfDtvn7dqvzr0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34431@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
New comment by thenktor on void-packages repository
https://github.com/void-linux/void-packages/issues/34431#issuecomment-990205549
Comment:
Indeed, thanks for your comment!
But uncommenting AUTHPATH is absolutely necessary, if you want to use an SMTP server, that requires authentication. This is very likely when using dma.
next prev parent reply other threads:[~2021-12-09 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 20:52 [ISSUE] " thenktor
2021-12-09 20:02 ` loreb
2021-12-09 20:08 ` thenktor [this message]
2022-06-18 2:13 ` github-actions
2022-06-18 12:29 ` loreb
2022-09-18 2:14 ` github-actions
2022-09-18 18:14 ` loreb
2022-09-18 20:12 ` [ISSUE] [CLOSED] " classabbyamp
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=20211209200829.6zVy0h2n3ie6csbrZ5kmWibwyB5U0tkfDtvn7dqvzr0@z \
--to=thenktor@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).