Hello all! I have the last login plugin working with the IMAP service however
with LMTP, it errors.
I do not necessarily need / want the LMTP service and did not explicitly enable
it but it is throwing an error in my logs.
Jul 17 10:22:14 lmtp(184051):Error: last_login_dict: Failed to write
Just in case you did not know, dovecot has it's own repo you can add to your
system to get newest updates.
https://repo.dovecot.org/
For example with RHEL flavors:
/etc/yum.repos.d/dovecot.repo
[dovecot-2.3-latest]
name=Dovecot 2.3 RHEL $releasever - $basearch
We've changed the list dmarc mitigation to happen unconditionally now.
What does "mitigation to happen unconditionally" mean? What was changed?
Are you talking about changing the policy action?
___
dovecot mailing list -- dovecot@dovecot.org
To
it is possible to do antispoofing, like
reject_authenticated_sender_login_mismatch from postfix ?
I could be wrong, but i believe dovecot submission is only a proxy to postfix
submission. Dovecot does not directly delivery mail to the world. Meaning the
mail is still passing through postfix
It seems like Maildir is the safest mailbox format for shared storage,
but even with Maildir there are warnings about the possibility of corrupting
the index files.
Would it make sense to use shared storage for the maildirs themselves,
but use the INDEX option in mail_location to store index
I have configured a shared private namespace in dovecot so that, via ACLs,
users can access other users' mailboxes.
I set up a quota for each user and this also works well. The quota is monitored
and new messages are denied if the quota is exceeded.
There is one problem though: apparently
I also wanted to ask if it's possible to add the local server name so I can
use one database for all systems?
I suppose there's a chance there could be issues with namespace conflicts,
but this would make it much easier for me.
Not sure how you are tracking your users, in my setup each user
I'm trying to determine the last login time for my IMAP users.
There is already a built in plugin that does this without needing to use
scripting.
You can use it to save a timestamp to a database.
https://doc.dovecot.org/settings/plugin/last-login-plugin/
Thanks for your reply.
I'm now very confused. Looking at
https://github.com/dovecot/docker/blob/main/2.3.21/Dockerfile this
container clearly just installs the debian package from the community repo.
That's why I thought publishing a arm64 debian package would enable a
arm64 docker image.
I would be fantastic if dovecot could release arm64 debian packages to
the community repo, as it would allow fixing a lot of downstream problems:
- release of official arm64 docker images
- fix other downstream docker images like docker mailserver and mailcow
It looks like arm64 is gaining a
Quick Q: Can dovecot use wildcard TLS Certificates?
I'm having issues with a new dovecot/postfix stack set-up and I can't get mutt
on the local box to connect via imap - its coming back with an SSL error, and
as I'm using a wildcard cert for the domain I was wondering if that was my
issue.
Exploring the possible use of SSO using OIDC with Dovecot. Trying to understand
the functionality of OIDC as it pertains to e-mail clients like Thunderbird,
Outlook etc...
My OIDC provider will authenticate a user by intercepting the connection
attempt to the resource, present a login screen
Any known issues with installing/running roundcube and dovecot on the same
server?
There is a generic issue with doing this. That is if you have roundcube (or any
other web mail interface) on the same server as dovecot, a breach of the web
interface could be quite serious and allow access
My logging config is as follows:
# doveadm log find
Debug: /var/log/dovecot-debug.log
Info: /var/log/dovecot.log
Warning: /var/log/dovecot.log
Error: /var/log/dovecot.log
Fatal: /var/log/dovecot.log
However, I'm still getting logs in /var/log/messages which I don't want. I've
looked into
Is there any way, with postfix, to run a script on authentication failure, with
information like the IP address and the
username passed, for instance.
I wrote my own script for omprog which is part of rsyslog to read dovecot auth
fails. Because postfix authenticates with dovecot and dovecot
1) "sieve_user_email = %u" creates a warning: "Warning: sieve: Invalid
address value for setting `sieve_user_email': Missing domain"
That warning is a glitch, ignore it. I mentioned it on the list before but has
not been fixed in any of the updates.
What I am currently trying to figure out
Why convert/alias a...@aaa.com to b@bbb.local?
Why not setup dovecot to have a mailbox and receive mail for
a...@aaa.com, allowing sieve to run for a...@aaa.com, and users login as
a...@aaa.com on IMAP to check their mail?
That would work if users only had one alias, but they don't - they have
postfix (*) presents the right "rcpt to a...@aaa.com" to the milter filter,
but sieve only sees the internal b@bbb.local.
Why convert/alias a...@aaa.com to b@bbb.local?
Why not setup dovecot to have a mailbox and receive mail for a...@aaa.com,
allowing sieve to run for a...@aaa.com, and users
Dovecot ... submission server works well with all sorts of clients, but Outlook.
I thought that was M$ intent. They purposefully design their ecosystem to not
play well with others so the average person will think something is wrong with
the competitor's software, give up and just continue to
The question about best practices was more a conceptual one. Should dovecot and
postfix talk independently to the LDAP database? Or should dovecot be the
gateway for postfix to get the information out of the LDAP database?
Just my 2 cents, id have postfix talk directly to LDAP to see if a
On 05-03-2023 1:52 pm, michele.clark--- via dovecot wrote:
Hi all.
We have an install of Dovecot running with Postfix and Roundcube using virtual
mail to allow us to connect to our AD domain which got messed up after a power
issue.
I can log into our Roundcube and see all my old emails,
I tried to enable it on postfix smtp_sasl_auth_enable, but it is was not
advertise.
That is because "smtp" is not the same as "smtpd".
http://www.postfix.org/postconf.5.html#smtpd_sasl_auth_enable
___
dovecot mailing list -- dovecot@dovecot.org
On 04-22-2023 11:15 pm, Badli Al Rashid wrote:
I have set up dovecot sasl with postfix. When I check the smtp with ehlo there
is no auth advertise.
There shouldn't be on port 25. Users should do email submission on port 587 or
465.
But if you really want there to be...
I noticed starting today the Sender: header is no longer included on the
mailing list.
I used to use the Sender: header in sieve rules for sorting.
Now the list emails only come From: rando email addresses.
On the postfix mailing list it replaces the From: header with the list address
instead
I noticed starting today the Sender: header is no longer included on the
mailing list.
I used to use the Sender: header in sieve rules for sorting.
Now the list emails only come From: rando email addresses.
On the postfix mailing list it replaces the From: header with the list address
instead
I am trying to get Dovecot IMAP and Outlook to talk to each other with SSL
and client certificates enabled. In Dovecot, I have the following options
enabled:
ssl_ca = ...
ssl_verify_client_cert = yes
auth_ssl_require_client_cert = yes
auth_ssl_username_from_cert = yes
when I try to
26 matches
Mail list logo
