search for: chatziathanassiou

A relatively recent development that spammers got wind of is users that have username==password, with/without the domain. I am tracking numerous 1-off attempts from bots to gain access to mailboxes this way. Situation isn't made any better if you're also using dovecot as SMTP AUTH provider for I am ashamed to admit I've relayed some spam that way. Would it be possible to deny login

...d be easy enough to add ``ignore'' at least. Using mbox storage and only tested with that, but it seems to work as expected for the time being. I'm attaching a relatively small patch for quota-dirsize.c against dovecot-1.1.18 just in case anyone's interested. Best Regards, Thanos Chatziathanassiou -------------- next part -------------- A non-text attachment was scrubbed... Name: quota-dirsize.patch Type: text/x-diff Size: 2162 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20090821/4f82f10b/attachment-0004.bin> -------------- next part --------------...

...patch to determine the domain from the server's IP. That way it is not necessary to persuade all users to switch to logging in as ``user at domain'' (which I've tried with very limited success). Would this be the correct place to post the patch and discuss ? Best Regards, Thanos Chatziathanassiou -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20081224/1629ce16/attachment-0002.bin>

We run around 5 dovecot (debian etch 1.0.rc15) POP/IMAP 'nodes' using the LVS load balancer and an NFS based SAN. it works pretty well. I love the robustness of load balancing POP/IMAP. We do a reasonable amount of throughput through these especially at peak times pushing our SAN to around 1.5k IOP/s We currently have two issues with this setup. One of which is NFS index corruption