I am sorry if this is not the correct list for asking this. T try to build
dovecot 2.3.20 from source on a QNAP NAS, which is a linux variant. There is an
dovecot available, but this does not include a pigeonhole sieve,
that’s why I try to build it from source. The configure script works fine,
On 16/3/23 06:31, Aymeric Agon-Rambosson wrote:
I have a solution to my problem.
For reference, I am putting it here :
A simple way to restrict login based on uids is to modify the file as
such :
#%PAM-1.0
auth required pam_succeed_if.so uid > 500 quiet
@include common-auth
I have a solution to my problem.
For reference, I am putting it here :
I recall that my issue is that postfix authorises login with root
(or other users), even though authentication is delegated to
dovecot, and the documentation about {first,last}_valid_{g,u}id
seems to say that is should
> "dovecot" == dovecot writes:
> Me personally, this is why i prefer to use virtual users stored in a
> database for email and never use linux users. I have ultimate
> control over what users can be authenticated or receive email. I can
> add flags to the DB query to fail an otherwise
However, when we have a postfix server on the same machine, that delegates
authentication to dovecot SASL ... we can indeed log in as root on the postfix
server.
You are not logging into Dovecot with root, you are connecting to Postfix for
submission.
When you connect to dovecot using
Thank you for pointing this out. Changing the mailbox path is not an
option anymore for us, easier to avoid this mailbox name.
Thank you!
On 15.03.23 15:07, Aki Tuomi wrote:
Documentation at https://doc.dovecot.org/configuration_manual/mail_location/
provides solution(s) for you:
Documentation at https://doc.dovecot.org/configuration_manual/mail_location/
provides solution(s) for you:
SUBSCRIPTIONS
Specifies the filename used for storing subscriptions. The default is
subscriptions. If you’re trying to avoid name collisions with a mailbox named
subscriptions,
Config below.
I assumed the same at first, but deliveries for other "details" work
without issues. Dovecot's 'subscriptions' file is present in the maildir
which seems to conflict with the mailbox lookup.
Dejan
-
# 2.3.18 (9dd8408c18): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole
> On 15/03/2023 13:12 EET Dejan wrote:
>
>
> > lmtp_save_to_detail_mailbox = yes
>
> Plus-delivery conflicts with existing, reserved files such as
> "subscriptions":
>
> Message for kim+subscriptions@ results in:
>
> lmtp(kim@***.com)<14493>: Error:
>
> lmtp_save_to_detail_mailbox = yes
Plus-delivery conflicts with existing, reserved files such as
"subscriptions":
Message for kim+subscriptions@ results in:
lmtp(kim@***.com)<14493>: Error:
stat(/var/mails/***/kim/Maildir/subscriptions/tmp) failed: Not a
directory
Version: 2.3.18
On 15/3/23 18:32, Odhiambo Washington wrote:
On Wed, Mar 15, 2023 at 1:46 AM Aymeric Agon-Rambosson
wrote:
Hello everyone,
From what I understand of the documentation, it is impossible to
log in to the dovecot server as root, or as any user not in the
interval between
On Wed, Mar 15, 2023 at 1:46 AM Aymeric Agon-Rambosson <
aymeric.a...@yandex.com> wrote:
>
> Hello everyone,
>
> From what I understand of the documentation, it is impossible to
> log in to the dovecot server as root, or as any user not in the
> interval between first_valid_uid and
Le mardi 14 mars 2023 à 22:32, dove...@ptld.com a écrit :
However, when we have a postfix server on the same machine,
that delegates authentication to dovecot SASL ... we can indeed
log in as root on the postfix server.
You are not logging into Dovecot with root, you are connecting
to
13 matches
Mail list logo
