- dovecot - dovecot.org

[Dovecot] Encoding dovecot keywords
by Алексей Сундуков 06 May '11

06 May '11

Hello. If mailbox name include non latin chars, dovecot save it encode to modification UTF-7. Example "тест" convert to "&BEIENQQ6BEEEQg-". If replace & to + I can decode it: <?php $str = '+BEIENQQ6BEEEQg-'; echo iconv('UTF-7', 'UTF-8', $str); ?> But I can't understand what encoding use dovecot for keywords? I set "тест" (number 5) keyword: cat dovecot-keywords 0 &bcienqrbbeiepgqybdaetw-_&bdwenqrcbdoema- 1 test 2 $label1 3 $label2 4 $label3 5 &beienqq6beeeqg- but "&beienqq6beeeqg-" do not convert to "тест". Why?

4 6

Re: [Dovecot] May 05 07:20:21 imap: Warning: Time jumped forwards 16 seconds
by Alexander Moisseev 06 May '11

06 May '11

Are you got this warnings only after OS reboot? -- Alexander Moisseev

1 0

[Dovecot] May 05 07:20:21 imap: Warning: Time jumped forwards 16 seconds
by Frank Bonnet 05 May '11

05 May '11

Hello I get this warning in dovecot.log the machine is running ntpd so this is a bit strange ...

3 2

[Dovecot] Post-login scripting last login question
by Robert Schetterer 05 May '11

05 May '11

Hi Timo, is there any relation between Post-login scripting i.e like last_login writing and imap/pop3 performance i.e on cluster file systems like ocfs2 etc ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] Bug Report: Failure delay config is ignored
by Kevin Goodsell 04 May '11

04 May '11

I have a set of automated tests for a system that can authenticate a user by forwarding authentication details to a server. That is, in order to authenticate a user, this system logs on to, e.g., an IMAP server using the credentials supplied by the user to verify the correctness of those credentials. I've been using dovecot as the authentication server to test IMAP, IMAPs, POP3, and APOP. To run the tests (most of which are authentication failures), I configure dovecot without authentication failure delays, since obviously I don't want to wait several minutes for the tests to finish. Setting the configuration variable auth_failure_delay to 0 worked fine in Dovecot 1.2, but since Debian updated to Dovecot 2.0 it no longer works. The tests take a very long time to run. I tried changing my passwd file to include nodelay=y, but this only works in a very limited way. For the set of tests which use the correct username, but an incorrect password, this successfully disables the failure delay. However, for the set of tests which use incorrect usernames (names not found in the user database or the password database, and which therefore don't have the extra nodelay field), the failure delay still occurs. There seems to be at least two problems here. The first is that it isn't clear what effect auth_failure_delay has. The comment in the sample config file just says "Time to delay before replying to failed authentications", which is certainly an incomplete description if not totally inaccurate. This setting seems to be completely unmentioned in the 2.0 wiki. The second problem is that the nodelay extra field can only be applied on a per-user basis. There doesn't seem to be any way to apply it to all users, or to apply it to authentication attempts for non-existent users. It seems to me that the failure delay that is actually used should either be 1) the actual value of auth_failure_delay (ideally with some random variance for extra security, but recognizing 0 as meaning disabled) or 2) some multiple of auth_failure_delay, where the multiplier increases with subsequent failures up to some max delay, with 0 still giving no delay. Config information follows. Thanks. -Kevin $ dovecot -n # 2.0.12: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian wheezy/sid auth_debug = yes auth_failure_delay = 0 auth_mechanisms = plain apop auth_verbose = yes listen = 127.0.0.1 log_path = /var/log/dovecot mail_location = maildir:~/Maildir passdb { args = /etc/dovecot/passwd driver = passwd-file } protocols = " imap pop3" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } $ cat /etc/dovecot/passwd testuser:{PLAIN}testpassword::::::nodelay=y

1 0

[Dovecot] Forwarding loop
by Brian Mihulka 04 May '11

04 May '11

I used to filter my mail through gmail with the following sieve rule. if not header :contains "X-Forwarded-To" "bmihulka(a)hulkster.net"{ redirect "bmihulka(a)gmail.com"; } With the gmail account set to forward to bmihulka(a)hulkster.net After upgrading to dovecot 1.2.9 and postfix 2.7.0 from whatever was with debian etch. I get a forwarding loop error. I don't know if this is a dovecot issue or postfix issue so I'm starting here. If anyone has any ideas or a better place to ask about this please let me know. Thanks Brian Mihulka

4 3

Re: [Dovecot] dovecot Digest, Vol 96, Issue 61
by Ceyhun Ganioglu 04 May '11

04 May '11

"Choosing the IMAP sent folder as account's sent items folder" is not working. That was the problem. But I fixed the problem using a "copy on send" rule. Many thanks ------------------------------ Message: 7 Date: Fri, 29 Apr 2011 14:41:10 -0400 From: Charles Marcus <CMarcus(a)Media-Brokers.com> To: dovecot(a)dovecot.org Subject: Re: [Dovecot] Dovecot Folder Creation Problem Message-ID: <4DBB0646.1090700(a)Media-Brokers.com> Content-Type: text/plain; charset=ISO-8859-9 On 2011-04-29 4:04 AM, Ceyhun Ganioglu wrote: > Following some tutorials on > the internet I created an Outlook rule to move the sent emails to the IMAP > server's sent mail folder. Outlook 2007+ no longer requires you to create that rule, you can now just tell it which IMAP folder to save the Sent mail to: http://office.microsoft.com/en-us/outlook-help/change-where-sent-e-mail-mess ages-are-saved-HA010164216.aspx#BM2 -- Best regards, Charles ------------------------------ _______________________________________________ dovecot mailing list dovecot(a)dovecot.org http://dovecot.org/cgi-bin/mailman/listinfo/dovecot End of dovecot Digest, Vol 96, Issue 61 ***************************************

2 1

[Dovecot] listen = ipv4, ipv6
by Leo Baltus 03 May '11

03 May '11

Hi, We want dovecot to listen on a specific ip4 & ipv6 addresses like so: listen = 145.58.1.1, [2a02:458:1::1] But on startup it tells me: Fatal: service(managesieve-login) Can't resolve address [2a02:458:1::1]: Name or service not known Wether it is in the dns or not. If I however change the listen directive to: listen = f.qd.nl where f.qd.nl resolves to an ip4 and ipv6 address dovecot starts up and binds to these ipaddresses the way we expect it. However this makes it depend on DNS which is undesirable. Maybe I am overlooking something, but if not can this be changed so we can configure ipv4 & ipv6 with ip-addresses? -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services /NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beheer(a)omroep.nl, 035-6773555 \/

2 2

[Dovecot] is reverse dns down ?
by Voytek Eymont 03 May '11

03 May '11

Hi guys, is that a genuine email from the list, I'm getting it rejected as it's missing reverse hostname: May 2 21:21:41 postfix/smtpd[18033]: NOQUEUE: reject: RCPT from unknown[194.89.34.45]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [194.89.34.45]; from=<dovecot-bounces(a)dovecot.org> to=<voytek(a)sbt.net.au> proto=ESMTP helo=<mkentta.iki.fi> # host mkentta.iki.fi mkentta.iki.fi has address 194.89.34.45 mkentta.iki.fi mail is handled by 10 mkentta.iki.fi. mkentta.iki.fi mail is handled by 100 smtp.menturagroup.com. # host 194.89.34.45 Host 45.34.89.194.in-addr.arpa. not found: 3(NXDOMAIN) -- Voytek

5 4

[Dovecot] Warning: SSL is disabled because global ssl=no, ignoring ssl=yes for subsection
by Peter Bell 02 May '11

02 May '11

Hi all, This is my first message to the list. I've been experimenting with running dovecot on my unRAID server (basically, a parity-protected array of disks, running on a slackware 13.1 platform). Someone on the unRAID forum had built a binary distribution of dovecot 1.1.20 and I got this up and running without too much trouble. Today, I've been building the latest dovecot release (2.0.12) and getting this up and running. My biggest problem has been reconstructing the configuration file but, after a few diversions, I'm now back up and running, with access to my mail once more. However, I'm just a little bit miffed that I can't get rid of this warning. My configuration: root@Tower:~# doveconf -n # 2.0.12: /usr/local/etc/dovecot/dovecot.conf doveconf: Warning: SSL is disabled because global ssl=no, ignoring ssl=yes for subsection # OS: Linux 2.6.36.2-unRAID i686 Slackware 13.1.0 fuse.shfs disable_plaintext_auth = no listen = * mail_location = maildir:/mnt/user/Maildir/%u passdb { args = /etc/passwd.dovecot driver = passwd-file } protocols = imap service auth { user = root } service imap-login { inet_listener imap { port = 143 } } ssl = no userdb { args = /etc/passwd.dovecot driver = passwd-file } root@Tower:~# Can someone point me to where the (implicit?) ssl=yes is coming from? In the meantime I will have a play at mail fetching, comparing dumping the mails straight into maildir, with using the dovecote lda. Thanks for any advice. -- ------------------------------------------------------------------- Peter Bell

2 1