From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: mail-filter/procmail/
Date: Mon, 2 Oct 2017 07:10:59 +0000 (UTC) [thread overview]
Message-ID: <1506928242.c2934bfb028481f61337525422564b5d3ecb8821.grobian@gentoo> (raw)
commit: c2934bfb028481f61337525422564b5d3ecb8821
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Mon Oct 2 07:10:42 2017 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Mon Oct 2 07:10:42 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2934bfb
mail-filter/procmail: add warning about FEATURES=sfperms interacting badly with some MTAs, bug #632102
Package-Manager: Portage-2.3.8, Repoman-2.3.1
mail-filter/procmail/procmail-3.22-r11.ebuild | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/mail-filter/procmail/procmail-3.22-r11.ebuild b/mail-filter/procmail/procmail-3.22-r11.ebuild
index 00884540ec7..c717564afa4 100644
--- a/mail-filter/procmail/procmail-3.22-r11.ebuild
+++ b/mail-filter/procmail/procmail-3.22-r11.ebuild
@@ -109,4 +109,12 @@ pkg_postinst() {
elog "/etc/procmailrc, for example:"
elog "\tDEFAULT=\$HOME/.maildir/"
fi
+ if has sfperms ${FEATURES}; then
+ ewarn "FEATURES=sfperms removes the read-bit for others from"
+ ewarn " /usr/bin/procmail"
+ ewarn " /usr/bin/lockfile"
+ ewarn "If you use procmail from an MTA like Exim, you need to"
+ ewarn "re-add the read-bit or avoid the MTA checking the binary"
+ ewarn "exists."
+ fi
}
next reply other threads:[~2017-10-02 7:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 7:10 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 6:37 [gentoo-commits] repo/gentoo:master commit in: mail-filter/procmail/ Joonas Niilola
2024-11-01 6:35 Arthur Zamarin
2024-11-01 2:55 Sam James
2024-11-01 2:55 Sam James
2024-10-31 21:29 Sam James
2024-10-31 19:32 Arthur Zamarin
2024-01-22 13:12 Sam James
2024-01-13 17:39 Sam James
2024-01-13 14:30 Sam James
2024-01-13 12:49 Arthur Zamarin
2024-01-13 12:49 Arthur Zamarin
2024-01-13 12:49 Arthur Zamarin
2023-12-02 7:13 Sam James
2022-06-03 8:11 Fabian Groffen
2021-07-23 18:28 Marek Szuba
2021-04-20 11:39 Mikle Kolyada
2021-01-06 13:50 Fabian Groffen
2020-07-16 8:45 Mikle Kolyada
2020-02-21 18:33 Mikle Kolyada
2019-09-15 20:50 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-06 16:40 Mikle Kolyada
2019-04-02 9:41 Mikle Kolyada
2019-04-02 9:41 Mikle Kolyada
2019-04-02 1:37 Thomas Deutschmann
2019-03-28 7:01 Mikle Kolyada
2019-03-26 22:44 Aaron Bauman
2019-03-26 21:09 Sergei Trofimovich
2019-03-25 22:18 Sergei Trofimovich
2019-03-25 11:49 Mikle Kolyada
2019-03-24 20:12 Sergei Trofimovich
2019-03-24 19:44 Sergei Trofimovich
2019-03-24 12:02 Richard Freeman
2016-06-15 3:35 Austin English
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=1506928242.c2934bfb028481f61337525422564b5d3ecb8821.grobian@gentoo \
--to=grobian@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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