Il giorno mar 17 nov 2026 alle ore 12:50 Paul Kudla via dovecot <dovecot@dovecot.org> ha scritto:
ok i get the question however the users email address and password is pretty much a world wide standard more for simpliciy then anything else
logging and acting on hack attempts (what i do) works better (i blacklist the offending ip in real time)
i get for extra security you might want to add a seperate username for auth
Well, the email address is mostly a "public" info, hiding the username means that an attacker has to brute-force the password AND the username. As you can't, most of the time, use custom username on online services and their username are almost every time your email address, in fact, a service compromission also expose your mail username.
dovecot is very flexable on db lookup's against a user, you will need to add a column for the new login name and have to alter the dovecot sql query on login to look at the username auth field but then return the data as per normal aka username@domain etc.
That's what i did. I've changed the password query (not the user query) in the "WHERE" caluse. something like:
SELECT email AS user, .......... WHERE username = '%u'
Previously it was
SELECT email AS user, .......... WHERE email = '%u'
I'm able to login, but to a new mailbox called with my username