October 2011 - dovecot

[Dovecot] LDA/Postfix with quotas and without LMTP
by Steve Fatula 18 Oct '11

18 Oct '11

Reading the wiki page for dovecot2 and LDA/Postfix, the system users section (all mail delivery goes to system users)... It shows you can simply use postfix mailbox_command. There is this additional comment: "This command doesn't do a userdb lookup. If you want that (e.g. for per-user quota lookups) you need to add -d "$USER" parameter." So, i added that. Once adding it, I find I get an error: dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied Using mailbox_command in Postfix means that dovecot-lda is running as the system user getting the mail. Which means it can't access the socket file. Of course, one can simply use mode 666 on it, but, then people can use it to find out information according to the doc, which I do not want. So, I am not sure why the doc says to add -d for per user quotas, without also mentioning the problem with doing that. I don't see how it can work? Assuming I need per user quotas, and I don't want to use LMTP, is there a good way around this without the security issue? Steve

2 2

[Dovecot] Syntax to specify sdbox: mail_location path?
by mephistopheles＠operamail.com 18 Oct '11

18 Oct '11

I'm implementing sdbox. In conf.d/10-mail.conf, with "maildir:" mail_location = maildir:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/new/ With "sdbox:" mail_location = sdbox:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/mailboxes/INBOX/dbox-Mails. How do I get rid of the '/mailboxes/' and '/dbox-Mails/' path components so sdbox stores in: /my_mailbox_path/%d/%n/INBOX @ wiki2.dovecot.org/MailboxFormat/dbox#Alternate_storage points out that 'ALT=' can change the *lookup* location, and messages can be *moved* to ALT storage using 'doveadm altmove'. Unclear what TAGS are available/used for 'sdbox'.

2 1

[Dovecot] Rare error with concurrent users searching with fts-solr
by Antonio Perez-Aranda 18 Oct '11

18 Oct '11

Hi all, If I start two o more connections with diferent users that make a search text to solr I get this message many times: Error: fts_solr: Query didn't return uid If I repeat the test about 2000 times, with only one user concurrent, with 60 diferent users, without concurrent, I get between 0. If I repeat the test about 2000 times, with 2 users concurrent, I get between 3 or 10 errors. If I repeat the test about 2000 times, with 4 users concurrent, I get between 10-20 errors. After see this error, I set a tcpdump to try to watch the SOLR XML and GET, I can watch that Solr send a xml like this: <response></response> with 200 as http status When the normal response is like this <response> <lst name="responseHeader"> <int name="status">0</int> <int name="QTime">1</int> <lst name="params"> <str name="fl">uid,score</str> <str name="sort">uid asc</str> <str name="q">BLABLABLA</str> <str name="fq">+user:"ANYUSER" +uidv:1208469916 +box:"ANYFOLDER" -ns:[* TO *]</str> <str name="rows">1</str> </lst> </lst> <result name="response" numFound="0" start="0" maxScore="0.0"/> </response> At first, I think that the problems it's in Solr, but after get all GET from tcpdump, I make a python script with urllib2 and send it all to Solr with the same concurrency and I can't get any error or "empty response" Have someone made a intensive concurrency tests over Dovecot + Solr ? -- Antonio Pérez-Aranda Alcaide aperezaranda(a)yaco.es Yaco Sistemas S.L. http://www.yaco.es/ C/ Rioja 5, 41001 Sevilla Teléfono +34 954 50 00 57 Fax +34 954 50 09 29

2 1

[Dovecot] 2.1 Plans
by Steve Fatula 18 Oct '11

18 Oct '11

Back in early 2010, Timo posted about a potential 2.1 feature to in essence reduce the number of imap/pop3 processes using various techniques since the code already supports multiple connections. It even went as far as moving all idle connections. I don't see this on the 2.1 roadmap. Is it still planned perhaps for 2.1? Thousands of imap processes going away is a great thing for me! So, just curious. Reference: http://dovecot.org/list/dovecot/2010-January/046148.html Steve

2 1

[Dovecot] Convert-tool maildir > mbox
by Bertrand Jacquin 18 Oct '11

18 Oct '11

Timo, Is seems that this commit broke convertion from Maildir to Mbox using dovecot 1.2 convert-tool binary : 2009-07-09 Timo Sirainen <tss(a)iki.fi> * src/plugins/convert/convert-storage.c: convert plugin: Fixed changing hierarchy separators in mailbox names when alt_hierarchy_char isn't set. [a9f719f9a509] <HEAD> Since, I get the following : $ convert-tool user1 /var/mail/example.com/user1 Maildir:/var/mail/example.com/user1 mbox:/var/mail/example.com/user1-mbox alt_hierarchy_char=_ Error: Mailbox conversion: Couldn't create mailbox Sent/test: Mailbox doesn't allow inferior mailboxes Error: Internal failure Strace give show me a failure after : access("/var/mail/example.com/user1/.Sent.test/cur", W_OK) = 0 stat("/var/mail/example.com/user1-mbox/Sent/test", 0x7fff843e73b0) = -1 ENOTDIR (Not a directory) write(2, "Error: Mailbox conversion: Couldn"..., 103Error: Mailbox conversion: Couldn't create mailbox Sent/test: Mailbox doesn't allow inferior mailboxes ) = 103 lstat("/var/mail/example.com/user1/.dovecot.convert.lock", {st_mode=S_IFREG|0644, st_size=12, ...}) = 0 unlink("/var/mail/example.com/user1/.dovecot.convert.lock") = 0 Is that somethinh known ? Didn't find anything interesting in archives. Maybe that kind of conversion have evolved since 2.0 ? Thanks, Beber

2 1

[Dovecot] doveadm mailbox list shows file system directories as mailboxes
by Jürgen Obermann 18 Oct '11

18 Oct '11

Hello. In our dovecvot we use mbox format with the default filesystem layout. Therefore it is not possible to have mailboxes which are subfolders of other mailboxes containing messages. The command "doveadm mailbox list" includes the file system directories, that contain only subfolders, as normal mailboxes in the output: archiv archiv/daemon archiv/dovecot Did I miss something in the dovecot configuration or is there a bug in the command "doveadm mailbox list"? # 2.0.13: /opt/local/etc/dovecot/dovecot.conf # OS: SunOS 5.10 sun4v auth_verbose = yes disable_plaintext_auth = no listen = imap.hrz.uni-giessen.de localhost mail_fsync = always mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = mail_log notify managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date mmap_disable = yes namespace { inbox = yes location = prefix = separator = / type = private } namespace { hidden = yes list = no location = prefix = Mail/ separator = / subscriptions = yes type = private } Thanks, Jürgen -- Hochschulrechenzentrum der | Mail: Juergen.Obermann(a)hrz.uni-giessen.de Justus-Liebig-Universitaet | WWW: http://www.uni-giessen.de/obermann/ Heinrich-Buff-Ring 44 | Tel: 0641-99-13054 (0641-99-13001) D-35392 Giessen, Germany | Fax: 0641-99-13009

3 2

Re: [Dovecot] Spammers attempting SASL Auth
by Tom Pawlowski 17 Oct '11

17 Oct '11

Take a look at: http://hg.dovecot.org/dovecot-2.0/file/962df5d9413a/src/auth/auth-request.c on line 536. That's the auth service catching illegal characters and rejecting the attempt. It'll happen with or without a valid user. So, working as it should. As for spammers trying to brute force valid logins, yep, pretty common. Higher rate of success if they can mail from a known good server and account. * Simon Brereton <simon.brereton(a)buongiorno.com> [2011-10-17 11:51:15 -0400]: > On 17 October 2011 11:31, Robert Schetterer <robert(a)schetterer.org> wrote: > > Am 17.10.2011 17:16, schrieb Simon Brereton: > >> Hi > >> > >> This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. > >> > >> Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] > >> Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars > >> Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 > >> Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known > >> > >> > >> Simon > >> > > > > this maybe a brute force attack,or more easy someone missconfigured his > > client , you may use fail2ban etc to block it > > not directly related to dovecot > > 17 queries in 30 seconds is not a misconfigured client :) > > And I'm already using Fail2Ban - but as someone on this list pointed > out recently, that doesn't apply if they try X attempts on the same > connection. Although, I don't think that was case here - maybe I > should update my dovecot jail with that illegal chars line. But, be > that as it may - all these attempts failed because the user didn't > exist. What if the user exists though? Does this illegal chars make > a hole for them to enter through? > > Simon > -- Tom Pawlowski OIT-CSS System Administrator office: Hill 147 email: tompru(a)jla.rutgers.edu phone: (732) 445-2634

2 1

Re: [Dovecot] Spammers attempting SASL Auth
by Robert Schetterer 17 Oct '11

17 Oct '11

Am 17.10.2011 17:51, schrieb Simon Brereton: > On 17 October 2011 11:31, Robert Schetterer <robert(a)schetterer.org> wrote: >> Am 17.10.2011 17:16, schrieb Simon Brereton: >>> Hi >>> >>> This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. >>> >>> Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] >>> Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars >>> Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 >>> Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known >>> >>> >>> Simon >>> >> >> this maybe a brute force attack,or more easy someone missconfigured his >> client , you may use fail2ban etc to block it >> not directly related to dovecot > > 17 queries in 30 seconds is not a misconfigured client :) > > And I'm already using Fail2Ban - but as someone on this list pointed > out recently, that doesn't apply if they try X attempts on the same > connection. Although, I don't think that was case here - maybe I > should update my dovecot jail with that illegal chars line. But, be > that as it may - all these attempts failed because the user didn't > exist. What if the user exists though? Does this illegal chars make > a hole for them to enter through? > > Simon > as i posted you offlist, this is a smtp attack, look at your i.e fail2ban postfix rules, fail2ban dovecot ruel is for banning pop3/imap brute force -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

Re: [Dovecot] Spammers attempting SASL Auth
by Robert Schetterer 17 Oct '11

17 Oct '11

Am 17.10.2011 17:16, schrieb Simon Brereton: > Hi > > This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. > > Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] > Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars > Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 > Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known > > > Simon > this maybe a brute force attack,or more easy someone missconfigured his client , you may use fail2ban etc to block it not directly related to dovecot -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 1

[Dovecot] Spammers attempting SASL Auth
by Simon Brereton 17 Oct '11

17 Oct '11

Hi This is a new one on me - I've never seen spammers attempt to use to SASL Auth to inject spam. None of the users they are trying (newsletter, dummy, test, etc.) exist, but what worries me is the illegal chars error - is this a known vulnerability in dovecot they are trying to exploit? I'm running 1:1.2.15-7 installed from apt-get.. Oct 17 15:07:16 mail postfix/smtpd[14422]: connect from unknown[208.86.147.92] Oct 17 15:07:16 mail dovecot: auth(default): passdb(newsletter(a)mydomain.net,208.86.147.92): Attempted login with password having illegal chars Oct 17 15:07:17 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<test(a)mydomain.net>, method=PLAIN, rip=208.86.147.92, lip=83.170.64.84 Oct 17 15:07:18 mail postfix/smtpd[14403]: warning: 208.86.147.92: hostname default-208-86-147-92.nsihosting.net verification failed: Name or service not known Simon

1 0