On Dovecot 2.4, auth-legacy setting for the auth service appears to be no-op when using lua passdb
So, I used https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html#exim-authe... to ensure exim still worked. Unfortunately, that doesn't seem to be the case. Sender verification, auth, etc. *will* fail until you specifically start sending back those old params as well as the updated ones. I am using lua for the passdb/userdb however, so presumably it's just not documented that this is an "exercise for the reader" when using lua.
In particular you need to deliver the 'mail' and 'quota' fields as they previously existed (colon separated) alongside the new dovecot params.
Hope this helps someone else out there.
Cheers,
Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh@webpros.com www.webpros.com
On 14/08/2025 21:09 EEST Andy Baugh via dovecot <dovecot@dovecot.org> wrote:
So, I used https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html#exim-authe... to ensure exim still worked. Unfortunately, that doesn't seem to be the case. Sender verification, auth, etc. *will* fail until you specifically start sending back those old params as well as the updated ones. I am using lua for the passdb/userdb however, so presumably it's just not documented that this is an "exercise for the reader" when using lua.
In particular you need to deliver the 'mail' and 'quota' fields as they previously existed (colon separated) alongside the new dovecot params.
Can you explain in bit more detail what you are doing?
Aki
Honestly it's very bizarre behavior. I spent a few days trying to actually get a root cause of why this actually worked, as nothing in exim's source suggests it even *should* help. $auth1 is just the user field from the authserver's response, and the rest should just be discarded. At this point I'm thinking it's some kind of bug that our exim setup was relying on. For now I actually stopped passing the old params via user/passdb, as in some cases providing the old mail or quota params will cause IMAP logins to fail. At this point I think I'm mostly going to need to read through a bit more of the exim and dovecot source to figure out these weird edge cases, but I'm leaving off resolving that to another time, as I still have a few weeks to polish up our integration and there's a few other things that look like easier targets.
Cheers,
Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh@webpros.com http://www.webpros.com/
From: Aki Tuomi <aki.tuomi@open-xchange.com> Sent: Friday, August 15, 2025 12:25 AM To: Andy Baugh <andy.baugh@webpros.com>; Andy Baugh via dovecot <dovecot@dovecot.org> Subject: Re: On Dovecot 2.4, auth-legacy setting for the auth service appears to be no-op when using lua passdb
[You don't often get email from aki.tuomi@open-xchange.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
On 14/08/2025 21:09 EEST Andy Baugh via dovecot <dovecot@dovecot.org> wrote:
So, I used https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html#exim-authe... to ensure exim still worked. Unfortunately, that doesn't seem to be the case. Sender verification, auth, etc. *will* fail until you specifically start sending back those old params as well as the updated ones. I am using lua for the passdb/userdb however, so presumably it's just not documented that this is an "exercise for the reader" when using lua.
In particular you need to deliver the 'mail' and 'quota' fields as they previously existed (colon separated) alongside the new dovecot params.
Can you explain in bit more detail what you are doing?
Aki
participants (2)
-
Aki Tuomi
-
Andy Baugh