On Wednesday, September 18, 2024, at 2:50 PM, Дилян Палаузов wrote:
It is not clear which of the above two citations you mean as proposed solution. If you do not modify the code, you will not get your system to work in the way you want it.
My first thought about implementing a "striploginrealm" option came before I realized that I was misspelling "virtdomains" and nothing was working the way it had been explained to me.
I would still like to have a way for users to login via either "person@xxxxxxxxxxxxxxxxxxxxxx" (which works) or "person@xxxxxxxxxxxxxxxxx" (which does not) because the latter case represents the "public" email address that our users are familiar with. Our MX (mail exchange) systems receive emails sent to "sample.domain.com" addresses and re-routes them (via postfix) to their "person@xxxxxxxxxxxxxxxxxxxxxx" mailboxes on the "imap.sample.domain.com" server running cyrus-imapd.
I would still like to have a way for users to login via either "person@xxxxxxxxxxxxxxxxxxxxxx" (which works) or "person@xxxxxxxxxxxxxxxxx" (which does not) because the latter case represents the "public" email address that our users are familiar with. Our MX (mail exchange) systems receive emails sent to "sample.domain.com" addresses and re-routes them (via postfix) to their "person@xxxxxxxxxxxxxxxxxxxxxx" mailboxes on the "imap.sample.domain.com" server running cyrus-imapd.
I did have to go back and add a "loginrealms" statement, so my configuration once again looks like this:
virtdomains: userid defaultdomain: imap.sample.domain.com loginrealms: imap.sample.domain.com
without the "loginrealms" statement the system was allowing logins via any random domain, an example of which (not surprisingly) was "person@xxxxxxxxxxxxxxxxx" (because our users want to use their "public" email address) but they were getting "mailbox not found" errors. The "loginrealms" statement prevents this.
