Howdy, I know i've asked this before, but i think i got really no answer. I'd like to have dovecot SASL, to check AUTH against an SQL table, instead of dovecot SASL use the AUTH MECH for imap/pop3. I want this, to have the same behavior as I have now, where i use postfix with cyrus SASL on a different table (with the same login details), and when i have an user that his accounts was hacked for sending spam, i just block the send and allow the user to keep receiving emails, for example to warn him. Would this be possible? Dovecot SASL against a SQL table? Havent found much info about it, Thanks in advanced, -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20191210/2c2bec3d/attachment.html>
Howdy, I'm going back to this matter, to finish the replacement os cyrus SASL per dovecot-SASL. I want to have the same functionality that i had before, that is, SASL check's AUTH agains a different table than the users one. I was looking in the dovecot-SASL docs, and i see nothing related. (https://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL) Does someone have an ideia on how to achieve it or how it could be done? I mean, how could i check this different table to be checked in the auth? service auth { ... unix_listener /var/spool/postfix/private/auth { mode = 0660 # Assuming the default Postfix user and group user = postfix group = postfix } ... } Thanks in advanced, On 2019-12-10 20:57, Jorge Bastos via dovecot wrote:> Howdy, > > I know i've asked this before, but i think i got really no answer. > > I'd like to have dovecot SASL, to check AUTH against an SQL table, > instead of dovecot SASL use the AUTH MECH for imap/pop3. > > I want this, to have the same behavior as I have now, where i use > postfix with cyrus SASL on a different table (with the same login > details), and when i have an user that his accounts was hacked for > sending spam, i just block the send and allow the user to keep > receiving emails, for example to warn him. > > Would this be possible? Dovecot SASL against a SQL table? Havent found > much info about it, > > Thanks in advanced,-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200922/8e33091d/attachment.html>
> On 22/09/2020 20:22 Jorge Bastos <mysql.jorge at decimal.pt> wrote: > > > Howdy, > I'm going back to this matter, to finish the replacement os cyrus SASL per dovecot-SASL. > I want to have the same functionality that i had before, that is, SASL check's AUTH agains a different table than the users one. > > I was looking in the dovecot-SASL docs, and i see nothing related. (https://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL) > Does someone have an ideia on how to achieve it or how it could be done? > I mean, how could i check this different table to be checked in the auth? > service auth { > ... > unix_listener /var/spool/postfix/private/auth { > mode = 0660 > # Assuming the default Postfix user and group > user = postfix > group = postfix > } > ... > } > > Thanks in advanced, > On 2019-12-10 20:57, Jorge Bastos via dovecot wrote: > > Howdy, > > > > I know i?ve asked this before, but i think i got really no answer. > > > > I?d like to have dovecot SASL, to check AUTH against an SQL table, instead of dovecot SASL use the AUTH MECH for imap/pop3. > > I want this, to have the same behavior as I have now, where i use postfix with cyrus SASL on a different table (with the same login details), and when i have an user that his accounts was hacked for sending spam, i just block the send and allow the user to keep receiving emails, for example to warn him. > > > > Would this be possible? Dovecot SASL against a SQL table? Havent found much info about it, > > Thanks in advanced, >I am not sure what you are after, but I guess you could use the %s expansion, that should expand into Service, such as SMTP. Alternatively, you can use protocol smtp { passdb { } } to have different passdb for smtp. Aki