search for: imaphost

...ovecot-pop3: #%PAM-1.0 @include common-auth @include common-account @include common-session (for this protocol everything works fine, I don't want to limit it.) dovecot-imap: #%PAM-1.0 @include common-auth auth sufficient pam_listfile.so item=rhost sense=allow file=/etc/dovecot/imaphosts onerr=fail auth required pam_listfile.so item=user sense=allow file=/etc/dovecot/imapusers onerr=fail @include common-account @include common-session If I'm not wrong, once the user is authenticated, PAM checks if the remote IP address is in imaphosts; if it's true, it retur...

This is not strictly Dovecot question, but a more general IMAP one. I'm running a Dovecot server and have a user who is claiming that some email sent to him, say, on 30 May, showed up in his mailbox on 02 Jun. I've checked Postfix logs, and the message was correctly received on 30 May and passed to Dovecot. A similar issue happens every few days. This leaves me with two possibilities:

I have read through http://wiki.dovecot.org/Quota/Dict, which suggests a database schema for using quota. For 1.2, this includes a username, bytes and messages. Is there any way to modify the queries used to split out username into localpart and domain? This would enable me to put the current quota information in my main mailbox table and display it to users in my admin interface. Or

Has anyone implemented a script to block IPs which are attacking on POP3 ports using dovecot logs to indicate repetitive failed login attempts? sshblack does this nicely for ssh (port 22) attacks by monitoring the /var/log/secure file. I am considering rewriting this to POP3 port (110), but if it has already been done, I sure don't need the practice. Thanks!

...3). According to http://wiki2.dovecot.org/SSL/DovecotConfiguration it should behave the same way as Dovecot 1 did. So, with Dovecot 2.0.rc4 it hits the first user who wants to establish a secure connection. It's hard to explain this to users. ;-) Of course, I could simply run "telnet <imaphost> 993" manually after installation. I also tried running "ssl-params" manually before starting Dovecot but it stays in foreground forever and doesn't seem to finish (what is it waiting for?) So it would be really great if Dovecot 2 could do this on its own like Dovecot 1 did....