- dovecot - dovecot.org

[Dovecot] dove 2.0.7 virtual no mails INBOX pop3
by Robert Schetterer 12 Nov '10

12 Nov '10

Hi Timo, i have no mails from INBOX over pop3 other folders work ok as well as imap like set Virtual POP3 INBOX namespace default { # type = private separator = / prefix = "" list = yes # hidden = no subscriptions = yes } namespace virtual { # type = private prefix = "virtual/" separator = / # location = virtual:/etc/dovecot/virtual:LAYOUT=maildir++ location = virtual:/etc/dovecot/virtual hidden = yes list = no subscriptions= no } namespace real { # type = private prefix = "RealMails/" separator = / list = no hidden = yes } namespace { type = shared separator = / # Mailboxes are visible under "shared/user@domain/" # %%n, %%d and %%u are expanded to the destination user. prefix = "shared/%%u/" #prefix = "shared/%%d/%%u/" # Mail location for other users' mailboxes. Note that %variables and ~/ # expands to the logged in user's data. %%n, %%d, %%u and %%h expand to the # destination user's data. #location = maildir:/usr/local/virtual/%d/%%u/:INDEX=~/shared/%%d/%%u/ location = maildir:/usr/local/virtual/%%d/%%u/:INDEX=~/shared/%%d/%%u/ #Use the default namespace for saving subscriptions. subscriptions = no # List the shared/ namespace only if there are visible shared mailboxes. list = children inbox = no } /etc/dovecot/virtual/INBOX/dovecot-virtual RealMails/* -RealMails/Trash -RealMails/Trash/* -RealMails/Sent -RealMails/Sent/* -RealMails/Templates -RealMails/Templates/* -RealMails/Drafts -RealMails/Drafts/* -RealMails/Archives -RealMails/Archives/* unseen -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] correct syntax for multiple ports
by Kilburn Abrahams 12 Nov '10

12 Nov '10

Hi, What is the correct format to specify multple ports in dovecot 2. With dovecot 1.2 listen = *:143 *:6188 worked fine. I cannot find any mention in the wiki2 about the different combinations of listen, address and port parameters and dovecot complains about the combinations I tried. Does not seem to work 1. inet_listener imap { listen = *:143 *:6188 } 2. inet_listener imap { address = *:143 *:6188 } 3. inet_listener imap { port = 143, 6188 or port = 143 6188 } This start dovecot, but roundcube will not connect on port 143, although Thunderbird will connect on 1432 and 6188 listen = *, :: 1. inet_listener imap { port 143 port = 6188 } Regards K

2 4

[Dovecot] Phantom email message
by Marc Perkel 12 Nov '10

12 Nov '10

Got sort of a strange problem on one email account. Everything works fine with Thunderbird/IMAP showing the correct unread message count. But on my DroidX smartphone one of my email accounts always shows one unread message, but I can't bring any unread messages up. It's like there's something there making it think there's a message when there isn't. The email client is K-9 mail Anyone have any ideas?

4 5

[Dovecot] --exec-mail
by David Woodhouse 12 Nov '10

12 Nov '10

Most of my IMAP access is achieved by 'ssh $mailhost exec dovecot --exec-mail imap'. I'm testing Dovecot 2.0, and this doesn't seem to work any more — and I can't seem to work out how to make it work. The wiki page at http://wiki2.dovecot.org/Upgrading/2.0 has no mention of it. I looked through the git history to find the commit that broke it and see if I could find the replacement that way, but it was the commit entitled 'Initial commit for v2.0 master rewrite.', and wasn't particularly edifying. Once upon a time in the dim and distant past, I believe I used to run /usr/libexec/dovecot/imap directly. But that doesn't set the environment up correctly, so isn't the right way to do it... is it? -- dwmw2

2 2

[Dovecot] setting up Dovecot
by Scott Berry 12 Nov '10

12 Nov '10

Hello there, I am a new user of Dovecot. I am using version 1.2.12. Here is the config file: I attached the dovecot.conf file as a screenshot using dovecot -n because I am blind and haven't quite figured out how to copy from the terminal to Gnome yet. My intentions here are as follows: 1. To allow only pop3s because I want to use ssl for security. 2. I am going to be using fetchmail to grab the mail and give it to dovecot. 3. There will be three people adventually grabbing their mail through pop3s. Another question I have is when you tell someone to configure their mail client through pop3s how does that work as far as the server name meaning like most ISp's have pop.whatever.whatever.? Also I am using a smarthost with postfix to send out the mail through Google how do I tell someone how to configure the smtp server in their mail client such as Isp's such as smtp.whatever.whatever. I am using Windows for two of the clients with Windows Mail on a Vista machine and Windows Mail on a Windows 7 machine and Evolution on a Ubuntu linux machine. Looks to me like everything is copeastetic except for how to log in. The SSL cert file in "/etc/ssl/certs/dovecot.pem" is a bit tricky cause I didn't create the cert so I am not sure of the password but I did try my normal root password. Not sure if that works. Other than this actually Dovecot is quite easy to config.

2 1

[Dovecot] Dovecot 2.0.7 Virtual plugin
by Henrique Fernandes 12 Nov '10

12 Nov '10

Well, it seens the virtual plugins is not working correctly or i miss undertood how to configurate it. http://wiki2.dovecot.org/Plugins/Virtual as this wiki says, I should be possible to make an ndeamespace namespace { prefix = virtual/ separator = / location = virtual:~/Maildir/virtual } And in side of ~/Maildir/virtual create virtual folders and inside of those folders create dovecot-vitual. But it does not work. Right if i make this conf, on my imap client it shows a folder called virtual ( the prefix, or whtever i put in there ) and show nothing, only shows something if i create a dovecot-virtual inside of ~/Maildir/virtual/ i would appreciate if someone explain what i am doind wrong. Thanks! my dovecot -n # 2.0.7: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian squeeze/sid mail_debug = yes mail_location = maildir:~/TesteEmail/Maildir mail_plugins = " virtual" namespace { inbox = yes location = prefix = separator = / } namespace virtual { location = virtual:~/TesteEmail/virtual/ prefix = virtual/ separator = / } passdb { driver = pam } ssl = no userdb { driver = passwd } protocol imap { mail_plugins = " virtual virtual" } []'sf.rique

2 5

[Dovecot] Authentication Failure
by Carlos Mennens 11 Nov '10

11 Nov '10

I am unable to login to my new mail server running Dovecot and Postfix for some reason. When I check the mail logs, I am seeing: Nov 11 16:06:29 mail dovecot: imap-login: Disconnected (no auth attempts): rip=10.1.10.204, lip=192.168.0.200, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48 Nov 11 16:06:36 mail dovecot: auth: Error: pam(carlos,10.1.10.204): pam_authenticate() failed: Authentication failure (/etc/pam.d/dovecot missing?) Nov 11 16:06:53 mail dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<carlos>, method=PLAIN, rip=10.1.10.204, lip=192.168.0.200, TLS Nov 11 16:07:12 mail dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<carlos(a)iamghost.com>, method=PLAIN, rip=10.1.10.204, lip=192.168.0.200, TLS Below is my configuration file for Dovecot: # 2.0.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35 x86_64 auth_mechanisms = plain login mail_location = maildir:~/mail passdb { driver = pam } protocols = imap service auth { unix_listener auth-client { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/mail.crt ssl_key = </etc/ssl/private/mail.key userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep } Does anyone know what is causing this error or how I can resolve this?

1 0

[Dovecot] $MAIL environment variable to override mail_location works in v1.2.16 but not in v2.0.7 for /usr/libexec/dovecot/imap
by Giam Teck Choon 11 Nov '10

11 Nov '10

Hi, For the past day, I have been researching about making dovecot to support mailfront (http://untroubled.org/mailfront/) imapfront-auth natively and able to use mailfront imapfront-auth with dovecot imap v1.2.16 without starting any dovecot related services and no /etc/dovecot.conf file is required. More information about this can be read at: http://lists.untroubled.org/?list=bgware&cmd=showthread&month=201011&thread… However, same trick can't be used for dovecot v2.0.7. First error is /etc/dovecot/dovecot.conf must be exists so I just simply touch /etc/dovecot/dovecot.conf with empty content to bypass that error. I noticed v2.0.7 is not using $MAIL environment variable to override mail_location? I have read the following: http://wiki2.dovecot.org/MailLocation Any idea to override mail_location setting? I have tried various setting of environment variables such as below: --------------------8<----------8<----------8<----------8<--------------------- #!/bin/sh # $MAIL, $HOME, $MAILDIR, $MAILBOX are the same in mailfront # imapfront-auth if [ -n "$MAIL" ]; then # make dovecot imap escape colon by replacing single : to :: export MAIL=maildir:`echo $MAIL | sed 's@:@::@g'` fi export USERDB_KEYS="$USERDB_KEYS mail" # For knowing all env. uncomment the below line and # see /tmp/imapd-log.txt # printenv >>/tmp/imapd-log.txt exec "$@" --------------------8<----------8<----------8<----------8<--------------------- The above script is being placed between imapfront-auth and dovecot imap (/usr/libexec/dovecot/imap). Thanks for any kind assistance. Kindest regards, Giam Teck Choon

2 5

[Dovecot] dovecot dictionary attacks
by PA 11 Nov '10

11 Nov '10

Hi, I been using dovecot for awhile and its been solid, however I been having some issues with dictionary attacks. I installed fail2ban and for the most part is working fine. However today I got another spammer relaying through my server. Looking at the logs I see the following dictonary attack from 94.242.206.37 Nov 10 03:04:38 pop dovecot: pop3-login: Disconnected: rip=94.242.206.37, lip=209.213.66.10 Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(aarhus,94.242.206.37): lookup Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(abaft,94.242.206.37): lookup Nov 10 03:04:38 pop dovecot: auth(default): shadow(abaft,94.242.206.37): unknown user Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(aarhus,94.242.206.37): unknown user Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(aaron,94.242.206.37): lookup Nov 10 03:04:38 pop dovecot: auth(default): shadow(aaron,94.242.206.37): unknown user Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(ababa,94.242.206.37): lookup ..... And so on.. Then that ip gets banned by fail2ban [root@pop ~]# grep 94.242.206.37 /var/log/fail2ban.log 2010-11-10 03:04:42,416 fail2ban.actions: WARNING [dovecot] Ban 94.242.206.37 However on my smtp mail server that ip is already sending out all sorts of spam with the sasl username of Paramus. This username Paramus never shows up on the dovevot dictionary attack, as a matter of fact the user Paramus is nowhere to be found on the dovecot log at all and I have logs going back months. Does anyone have any idea what could of happened here. I mean if the user/passwd was already harvested by 94.242.206.37 why would they bother to start another dict. attack. I'm just not sure how they guess the username/password as its not on any logs that goes back months and I don't have a dovecot record for that user. /var/log/maillog:Nov 10 02:46:16 mrelay3 postfix/smtpd[27776]: 3B64928015: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 02:47:54 mrelay3 postfix/smtpd[27776]: 247AB28016: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 02:48:00 mrelay3 postfix/smtpd[27785]: 87DE128016: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 02:56:00 mrelay3 postfix/smtpd[27792]: 9728628015: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 03:05:38 mrelay3 postfix/smtpd[27808]: D529F28015: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 03:06:00 mrelay3 postfix/smtpd[27808]: DDF7C2801B: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=Paramus Any help would be appreciated. paul

2 3

[Dovecot] Sieve problem with managesieve
by Simone Caruso 11 Nov '10

11 Nov '10

I have a problem with a sieve script.. my config is dovecot 1.2.15 with managesieve, and roundcube. Now i have this script WORKING: -- require ["fileinto"]; # rule:[TracSvil] if anyof (header :contains "From" "xxx(a)example.com") { fileinto "INBOX.Trac Svil"; stop; } -- And this script NOT working: require ["fileinto"]; # rule:[TracSvil] if anyof (header :is "From" "trac(a)ardeek.com") { fileinto "INBOX.Trac Svil"; stop; } Can someone explain me the difference between these script? there is any error in the second script? Greetings! -- Simone Caruso IT Consultant p.iva: 03045250838

3 3

[Dovecot] dovecot dictionary attacks
by Paul Amaral 11 Nov '10

11 Nov '10

Hi, I been using dovecot for awhile and its been solid, however I been having some issues with dictionary attacks. I installed fail2ban and for the most part is working fine. However today I got another spammer relaying through my server. Looking at the logs I see the following dictonary attack from 94.242.206.37 Nov 10 03:04:38 pop dovecot: pop3-login: Disconnected: rip=94.242.206.37, lip=209.213.66.10 Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(aarhus,94.242.206.37): lookup Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(abaft,94.242.206.37): lookup Nov 10 03:04:38 pop dovecot: auth(default): shadow(abaft,94.242.206.37): unknown user Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(aarhus,94.242.206.37): unknown user Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(aaron,94.242.206.37): lookup Nov 10 03:04:38 pop dovecot: auth(default): shadow(aaron,94.242.206.37): unknown user Nov 10 03:04:38 pop dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=209.213.66.10 rip=94.242.206.37 resp=<hidden> Nov 10 03:04:38 pop dovecot: auth(default): shadow(ababa,94.242.206.37): lookup ..... And so on.. Then that ip gets banned by fail2ban [root@pop ~]# grep 94.242.206.37 /var/log/fail2ban.log 2010-11-10 03:04:42,416 fail2ban.actions: WARNING [dovecot] Ban 94.242.206.37 However on my smtp mail server that ip is already sending out all sorts of spam with the sasl username of Paramus. This username Paramus never shows up on the dovevot dictionary attack, as a matter of fact the user Paramus is nowhere to be found on the dovecot log at all and I have logs going back months. Does anyone have any idea what could of happened here. I mean if the user/passwd was already harvested by 94.242.206.37 why would they bother to start another dict. attack. I'm just not sure how they guess the username/password as its not on any logs that goes back months and I don't have a dovecot record for that user. /var/log/maillog:Nov 10 02:46:16 mrelay3 postfix/smtpd[27776]: 3B64928015: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 02:47:54 mrelay3 postfix/smtpd[27776]: 247AB28016: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 02:48:00 mrelay3 postfix/smtpd[27785]: 87DE128016: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 02:56:00 mrelay3 postfix/smtpd[27792]: 9728628015: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 03:05:38 mrelay3 postfix/smtpd[27808]: D529F28015: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=paramus /var/log/maillog:Nov 10 03:06:00 mrelay3 postfix/smtpd[27808]: DDF7C2801B: client=unknown[94.242.206.37], sasl_method=LOGIN, sasl_username=Paramus Any help would be appreciated. paul

1 0

[Dovecot] Getting the Sender from a Email
by Alex Baule 10 Nov '10

10 Nov '10

Hi Timo.... I need to get the Sender from a Email. Using this mail_get_first_header(mail, "From", &header) , i get the email in this format "Name <user@dom>" , in dovecot there is a way to get only the user@dom ? Tks !

2 1

[Dovecot] dovecot2.0+ldap auth problems
by Antonio Perez-Aranda 10 Nov '10

10 Nov '10

I'm using a config from dovecot 1.2 adapted to 2.0 After update config, and restart dovecot service: If I do a doveadm user user1 then it is found correctly. If I do a doveadm auth user1 then it is ask for the password user, and it's running correctly. But if I tray to login by telnet using IMAP then I get: . login user1 pass1 Connection closed by foreign host. I can see at logs a Info line with: Internal login failre with auth failed It's very odd that with doveadm runs ok and but not with IMAP.

1 1

[Dovecot] Help! LDAP/AD Problem with dovecot
by Christian Fischer 10 Nov '10

10 Nov '10

Hey Folks, i am trying to get Dovecot LDA to work with Active Directory dovecot --version 1.2.9 While using Postfix to deliver mail, dovecot does only imap-Services, passdb is auth bind and userdb is static. NOW i want to use Sieve Scripts. So LDA of dovecot is required. So userdb lookup is required. With use of virtual Mailboxes i have a working postfix setup, which needs to be transferred to dovecot. dovecot-ldap-userdb.conf uris = ldap://192.168.0.42 auth_bind = yes dn = myldapuser@mydomain dnpass = mypass #ldap_version = 3 base = DC=base,DC=com deref = never scope = subtree user_attrs = sAMAccountName=mail=maildir:/home/vmail/%$/.EMAIL, =uidNumer=5000, =gidNumber=5000 user_filter = (&(objectClass=user)(|(sAMAccountName=%u)(mail=%u)(othermailbox=%u))) pass_attrs = sAMAaccountName=user,userPassword=password pass_filter = (&(objectClass=person)(sAMAaccountName=%u)) My errors are: - While logging in with IMAP 2010-11-10 00:32:30 imap-login: Error: Timeout waiting for handshake from auth server. my pid=16293, input bytes=0 - manual execution of deliver -d myuser(a)domain.tld: 010-11-10 00:34:16 deliver(myuser(a)domain.tld): Error: userdb lookup(...): Connecting timed out As i said - postfix works! Thankx for any help!

2 1

[Dovecot] Problem with dovecot delivery (version 2.0.7)
by Maxime Longuepee 10 Nov '10

10 Nov '10

Hi! I've been having an issue with dovecot since yesterday and can't figure it out. All my users can send mail without any problem but all incomming mail are deffered. Here is the log from postfix complaining the mail has been deferred: Nov 9 23:35:51 www postfix/pipe[50019]: A20EB145FC2C: to=, relay=dovecot, delay=819, delays=819/0.01/0/0.01, dsn=4.3.0, status=deferred (temporary failure) And here is the log from dovecot complaining it can't complete the operation /var/log/dovecot-deliver.log: Nov 09 23:35:51 lda(EMAIL REMOVED FOR PRIVACY): Fatal: setresgid(6(mail),6(mail),6(mail)) failed with euid=143(dovecot): Operation not permitted If anyone could help me, it would be much appreciated! Thanks!

4 10

[Dovecot] need to block user by IP address (tried denyhosts, xinetd, iptables etc)
by Tom 10 Nov '10

10 Nov '10

Hi, I am kind of restricted to using packaged versions of software due to company policy, and we have f12 on our mail server with dovecot-1.2.15-2.fc12.i686 package. we have recently had some brute force attacks on the pop3 and imapd and this results in many processes being used for login attempts. Our dovecot is hosted on a Virtual Private Server which restricts access to IPTABLEs and also make a limit on the number of processes that can be running So I can't restrict the attackers IP addresses via IPTABLES, as we don't have access to that. I can't really patch dovecot as we are reliant on the distro packages. I spent some time trying to get dovecot to run under xinetd but had no luck, and I read some reports that it was not possible using recent versions. I was hoping some advice on what avenue I should proceed with to automatically block brute force attacks on the dovecot server, (that dont use iptables) Thanks, Tom

5 5

[Dovecot] emails getting mangled when dragging from Exchange account to IMAP shared folders
by Scott Goodwin 10 Nov '10

10 Nov '10

I'm having the most frustrating issue, and I'm at a loss for what is happening. I'm not even sure it is with Dovecot, but that's why I'm posting this here... if it isn't a dovecot issue, maybe someone can get me headed in the right direction? I've posted relevant dovecot and config info at the bottom of this post. Here's the scenario: We recently migrated our email from Postfix+Dovecot+Amavis+SA to Exchange (not my choice, unfortunately). Now, users have to use Outlook (as opposed to before, when they could choose between Outlook and Thunderbird), and have the new Exchange account set up, as well as their old IMAP account, which they still use for shared project folders. So, emails come in to Exchange, then they drag the emails from the Exchange mailbox to the shared branch under their IMAP account, and into the appropriate job folder. Emails to one specific user in my organization (let's call him Roy(a)Ocean.org) is having his emails mangled when dragging certain items from his Exchange mailbox to the IMAP account. I can't reproduce the issue with any other user. Also, this only seems to happens with emails from one other specific domain (let's call them tornado.org) So, in summary, user1(a)Tornado.orgsend an email to Roy(a)Ocean.organd Sue(a)Ocean.org. Both drag the email from their Exchange box into any folder (shared or otherwise) in the IMAP tree. Sue's copy makes it in just fine, while Roy's copy gets mangled. Here's the headers of the resultant email after Roy has dragged it into the shared folder: ======================================== From: "User1" <User1(a)tornado.org> To: "Roy", "Sue" References: <B3457C1920D7A2438CCC19EF2A527293372B11(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293372D9A(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933A2C3D(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933A310E(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933A3683(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933A3B97(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933D103B(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933D192F(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933D1B12(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933FD341(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933FD8F8(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933FD9A0(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272933FDFDD(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272934C8927(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272934C8B46(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272934C8D76(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272934C8D7A(a)abc027.abc.local> <B3457C1920 ======================================== And here's the email body: ======================================== D7A2438CCC19EF2A5272934C8D95(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272934C8DB6(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272934C8F0D(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935008B5(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293500C27(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935011BC(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293525B1D(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293525D81(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293526139(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293526416(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935524A6(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935524C9(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A527293589E1C(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935BF6A9(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935E7414(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935E75E2(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935E75E8(a)abc027.abc.local> <B3457C1920 D7A2438CCC19EF2A5272935E75F4(a)abc027.abc.local> <B3457C1920D7A2438CCC19EF2A5272935E800E(a)abc027.abc.local> Subject: RE: Some Subject Date: Tue, 26 Oct 2010 15:11:01 -0700 Message-ID: <B3457C1920D7A2438CCC19EF2A52729364D0A0(a)abc027.abc.local> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0118_01CB7755.52354760" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrhmOPG84jptRwERxazrnj4Ne2YAQAACMtAAAAjcPAAAAu+gAAAE1hAAAAZWCAAABMaEAAADGzwACO3fdAACN0HsAEpVUrgAPt2jvAAAcrbcABrFxCQAAAXwjAAABGv8AAAI35QAYbDMHAAAPjDYAADNREgAA5XR4AAHoOFcAFtPWTAAIubCCAALwf/MAADBptQACzN6nAAAC61kAAAEN+AAACfkjAAO7MG4AAHLrMQALmKX6AAAUlCcAAAq9SgAAuoo+AAABqqMABXq+FwAD5jAAABYqZYoAOISoLgAAAd//AAAKVPYAApG8DwAAt6dsAAKxpd8AEy9g6gAADrZVAAAE4WgAAlXdkQAPY4tNAAAWY+kAFsS/RgAFtG7qAAAGJT8AAAPLUwAAA2xsAAACamEAAC4ufAADaZyfAAKizZ0AAAZ9EAAAWRHAAAAOgkgAAAUUOgAAQWBBAAij+IkAAE2k1wAAPgAgAANGrwsAACt+wgAC0EW9AAAEDpoAA12EJgAAAyAtAAAyATYAAgyfBQAKS/7/AAAEPWEAABNsTAAAAZujAALLkhkAAwwG5AAAMVt8AAAE3iwAEhzNqgAA8qbEAAIqDaMAA0UTmgAEE0hxAAlsz9IAABAdrAAFIwRcAAZxd5oAAOziPQAJEu45AAOaFlIAAeeCygADwtnbAD9zXHwAApeNOAACk/pfAAABxl0AAAWgGAAAB7d4AACGbyQACNOVmwABF68KAAKuKysAAsiR5gADDcY1AAOMAK8ACO561QABCk+7AAI5IqsAAJGVEgAFjaIkAANWSCQAACuaAwAAAKUQAABugScAAAbmTQAADspwAAzNO+MAAiFH8wAAEA4mAAMv6E0AEtz2wQADWsQHAAO4pvkACIRgpAAAApFcAAABO4UABmP4/QAAEJ/lABNOByMAAF28awAACwfDA= Content-Language: en-us X-OlkEid: C664F3259FA9393D4124CD409B5CAE330696EE82 content-class: urn:content-classes:message This is a multi-part message in MIME format. ------=_NextPart_000_0118_01CB7755.52354760 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit <SNIP> =========================================================================== Obviously, it's breaking the message in the References header, and I've tracked down the following byte sequence at the breaking point: 0D:09:0A:09 ...which is CR,TAB,CR,LF. What puzzles me is why Roy's gets broken here, when the others' do not; they're the exact same email, so you'd think they would all get broken. I can't figure out A) where that byte sequence is coming from (our Exchange server, Tornado.net's exchange server, or one of the two of our external spam filtering service... they use BigFish.com, and we use MxLogic), or B) if that's even the issue. I've rebuilt Roy's entire machine, reconfigured Outlook from scratch, still happening. When he logs onto another machine and sets up his Exchange account on another outlook, it still happens. Our Exchange administrator (I don't have access to Exchange) says there is nothing wrong with his Exchange account, for what it's worth. I don't expect anyone to have the solution here, since there are many variables, and there is other info that would probably be needed. What I DO want is to be pointed in the right direction on how I might track this down. For example, what is the path that this mangled email would take in this case? Even with full logging in Dovecot and postfix, I can't see any info on the path that this email follows in our system, and where it might be getting mangled. Does it actually go through the same path as an email that was actually sent to the IMAP account, or is it different when it is dragged in from another account in the same mail client? Is this more likely a problem with Postfix, or Sieve, or....? (I've disabled Amavis and SA to get them out of the picture, and same problem). Here's the dovecot config info; please let me know if you want any other config info, and thanks ahead of time! # dovecot --version 1.1.19 # dovecot -n # 1.1.19: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-hardened-r9 x86_64 Gentoo Base System release 1.12.13 protocols: imaps imap managesieve listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(managesieve): 127.0.0.1:2000 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_cert_file: /etc/ssl/dovecot/imapd.crt ssl_key_file: /etc/ssl/dovecot/imapd.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(managesieve): no valid_chroot_dirs: /var/mail first_valid_uid: 206 last_valid_uid: 206 first_valid_gid: 206 last_valid_gid: 206 maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): acl mail_plugins(imap): acl mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(managesieve): sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): ~ sieve(default): sieve(imap): sieve(managesieve): ~/.dovecot.sieve namespace: type: private separator: . location: maildir:~/Maildir inbox: yes list: yes subscriptions: yes namespace: type: public separator: . prefix: shared. location: maildir:/var/mail/shared list: yes lda: postmaster_address: postmaster(a)jensenmaritime.com hostname: mail.jensenmaritime.com mail_plugins: cmusieve mail_plugin_dir: /usr/lib/dovecot/lda sieve_global_path: /var/mail/.dovecot.sieve sieve: ~/.dovecot.sieve sendmail_path: /usr/lib/sendmail auth_socket_path: /var/run/dovecot/deliver-auth auth lda: default_realm: jensenmaritime.com user: postmaster passdb: driver: ldap args: /etc/dovecot/lda-ldap.conf userdb: driver: static args: allow_all_users=yes user=%Lu uid=206 gid=206 home=/var/mail/%Lu socket: type: listen master: path: /var/run/dovecot/deliver-auth mode: 384 user: vmail group: vmail auth default: mechanisms: PLAIN LOGIN default_realm: jensenmaritime.com user: postmaster passdb: driver: ldap args: /etc/dovecot/default-ldap.conf userdb: driver: static args: user=%Lu uid=206 gid=206 home=/var/mail/%Lu socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: acl: vfile # grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf uris = ldap://127.0.0.1:389/ ldap_version = 3 base = ou=users,ou=accounts,dc=jensenmaritime,dc=com scope = onelevel auth_bind = yes pass_filter = (&(objectClass=CourierMailAccount)(!(disableimap=*))(mail=%Lu)) pass_attrs = auth_username_format=%Lu # uname -a Linux milne 2.6.28-hardened-r9 #4 SMP Mon Jun 7 10:50:28 PDT 2010 x86_64 Intel(R) Xeon(R) CPU E5405 @ 2.00GHz GenuineIntel GNU/Linux (Using Gentoo 64-bit Linux)

3 9

Re: [Dovecot] Todays Performance Data for 2.0.x
by Timo Sirainen 09 Nov '10

09 Nov '10

Dividing the imap processes's system CPU usage by number of imap processes: imap : 0.478872 of 975 imap : 0.460797 of 1242 imap : 0.409641 of 2482 imap : 0.424035 of 4711 imap : 0.488494 of 6148 imap : 0.56809 of 7031 imap : 0.734864 of 6965 So it's about 0.5 seconds of system CPU per imap login. I also get something like 0.3 seconds of system CPU per imap login on my system. Also setting: service imap { service_count = 0 } (i.e. reuse imap processes) reduced the system CPU usage to almost nothing. But if you use different UIDs for different users you can't do that. So, yeah, looks like the process initialization is wasting time somewhere. I'll look further into it.

2 3

[Dovecot] Can't expand ~ for mail root dir
by Leo Baltus 09 Nov '10

09 Nov '10

Hi, I am not an this list, I hope it gets through: We just moved from dovecot-1.2.12 to dovecot-2.0.6. One of our users wants his mail directly in his homedir which worked fine so far but with 2.0.6: Nov 09 15:19:25 imap(foo.bar(a)example.com): Error: user foo.bar(a)example.com: Initialization failed: Initializing mail storage from mail_location setting failed: No home directory for system user. Can't expand ~ for mail root dir in: ~:INBOX=/e/ml/tech1/home/foo from dovecot.conf: userdb { args = /some/path/to/passwd driver = passwd-file } passwd: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:~:INBOX=/e/ml/tech1/home/foo We've changed that for now: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:/e/ml/tech1/home/foo:INBOX=/e/ml/tech1/home/foo ~/mail did work but was not desired by the user: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:~/mail:INBOX=/e/ml/tech1/home/foo ~/ didn't work either: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:~/:INBOX=/e/ml/tech1/home/foo -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services /NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beheer(a)omroep.nl, 035-6773555 \/

2 1

[Dovecot] mdbox & trash
by Daniel L. Miller 09 Nov '10

09 Nov '10

Is there a way I can setup "trash" folders to be stored in a different subdirectory using mdbox? The goal is to provide a way to identify the trash folders for my backup solution (rsync) and avoid copying trash. -- Daniel

2 1

[Dovecot] how can I use different LDAP config for LDA and AUTH?
by Zhou, Yan 09 Nov '10

09 Nov '10

Hi there, I am setting up mail client with DoveCot and, at the same time, use Postfix to deliver message to DoveCot via LDA. I want to support having user name "jsmith" on my mail client, and that gets all messages for email address: dovecotdemo@domain. (The user name is different from what is in the email address). In addition, all user & password look up is handled by LDAP. Here is my problem: 1. my mail client will login as "jsmith", that goes through LDAP to find mail/home/password for this user. (this matches user name) 2. When postfix delivers a message, DoveCot LDA will find a match with email address "dovecotdemo@domain", it goes through the same LDAP configuration. (this matches email address). You can see the two search criteria are different, but by default they use the same passdb and userdb configuration. I want to use a different LDAP config. file for LDA to use, where it will match the email address (so that it is different from the default dovecot-ldap.conf, which is used by authentication). DoveCot Deliver can specify a separate configuration file with "-c", so I tried that. But I cannot get LDA to use a different configuration. Would should be an example of config file used by Deliver? Anyone running into this problem? Thanks, Yan NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message has been content scanned by the Axway MailGate. MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. For more information on Axway products please visit www.axway.com.

2 1

[Dovecot] dovecot sieve plugin
by maximatt 09 Nov '10

09 Nov '10

hi... ¿exist some way to extract message body contect to a variable with dovecot sieve plugin? ¿:(? it's needed to do something like these: if address :matches ["From"] ["*"] { set "sender" "${0}"; <extract body content> # i try using something like "if body :raw :contains ["*"]" and use ${1} but i cant make work. set :encodeurl "body" "something more <body content>"; notify :message "Test msg from ${sender}" "mailto:someone@domain.com ?body=${body}"; } thanks in advance! ;) PD: sorry if these message could be off toppic. :( -- *Salu2 ;)*

2 2

[Dovecot] 2.0, hourly performance stats
by Ralf Hildebrandt 08 Nov '10

08 Nov '10

I'm getting constantly high numbers of page reclaims & involuntary context switches for dovecot/auth. page reclaims = minor faults = cpu switching back to system-mode, But why is the auth process doing that so excessively? Same for the large number of involuntary context switches... Attached is my "dovecot -n" output. Date: Sun, 07 Nov 2010 20:40:34 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 205.93 1.32 2.76 25280 0 0 0 0 0 261 1425 ssl-params 288.71 0.40 0.48 468 0 0 8 0 0 8 1 pop3 0.59 0.80 0.20 651 0 0 48 16 0 12 13 managesieve 0.51 0.00 0.28 576 0 0 416 0 0 13 7 imap 4677.82 0.19 0.89 1480 0 0 488 16 0 23550 136 pop3-login 181.77 0.32 0.28 780 0 0 8 0 0 46 9 Date: Sun, 07 Nov 2010 21:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 303.62 1.10 2.20 26208 0 0 0 0 0 235 1362 ssl-params 301.12 0.00 0.12 467 0 0 8 0 0 7 1 pop3 0.26 0.40 0.36 618 0 0 0 8 0 5 18 managesieve 0.53 0.00 0.28 576 0 0 352 0 0 13 7 imap 2856.91 0.12 0.46 655 0 0 0 0 0 13465 105 pop3-login 228.84 0.76 0.24 779 0 0 0 0 0 90 14 Date: Sun, 07 Nov 2010 22:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 243.12 0.99 4.56 23762 0 0 0 0 0 222 1419 ssl-params 301.25 0.40 0.80 471 0 0 8 0 0 6 4 pop3 0.43 0.40 0.80 623 0 0 0 8 0 6 4 managesieve 0.43 0.00 0.20 577 0 0 536 0 0 14 7 imap 3.63 0.16 0.36 669 1 0 856 0 0 63 93 pop3-login 181.81 0.60 0.40 782 0 0 0 0 0 52 53 Date: Sun, 07 Nov 2010 23:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 232.83 1.72 2.26 25613 0 0 0 0 0 254 1175 ssl-params 149.63 0.00 0.16 469 0 0 40 0 0 10 1 pop3 25.68 0.28 0.12 741 0 0 9696 16 0 109 14 managesieve 0.25 0.40 0.28 576 0 0 8 0 0 11 2 imap 0.32 0.00 0.16 625 0 0 0 0 0 11 11 pop3-login 69.88 0.48 0.24 779 0 0 0 0 0 27 6 Date: Mon, 08 Nov 2010 00:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs managesieve 0.29 0.00 0.36 576 0 0 8 0 0 7 16 imap 0.58 0.80 0.36 637 0 0 0 0 0 10 9 Date: Mon, 08 Nov 2010 01:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 421.98 1.32 1.66 24216 0 0 0 0 0 267 723 ssl-params 538.47 0.00 0.16 470 0 0 8 0 0 7 1 pop3 0.19 0.80 0.96 671 1 0 760 8 0 22 221 managesieve 0.63 0.40 0.13 578 0 0 192 0 0 9 11 managesieve-lo 18616.9 86.77 32.49 319768 1 0 168 0 0 63448 48838 imap 42.28 0.00 0.52 676 0 0 0 0 0 182 63 pop3-login 361.68 0.76 0.40 780 0 0 0 0 0 52 2 Date: Mon, 08 Nov 2010 02:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 592.76 0.97 1.40 23640 8 0 8272 0 0 307 321 ssl-params 676.93 0.00 0.24 468 0 0 136 0 0 18 10 pop3 6.10 0.24 0.44 672 1 0 1688 8 0 35 40 managesieve 0.71 0.12 0.14 572 5 0 1632 0 0 17 38 managesieve-lo 1023.50 1.45 0.46 6066 1 0 184 0 0 1104 317 imap 0.87 0.80 0.44 674 1 0 640 0 0 18 25 pop3-login 361.79 0.72 0.32 780 0 0 112 0 0 56 11 Date: Mon, 08 Nov 2010 03:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 600.71 0.96 1.18 22902 0 0 56 0 0 235 212 ssl-params 242.66 0.00 0.16 471 0 0 136 0 0 15 6 pop3 0.20 0.16 0.28 675 1 0 1312 8 0 32 15 managesieve 0.46 0.00 0.36 580 1 0 480 0 0 11 12 managesieve-lo 286.21 0.60 0.44 1048 1 0 184 0 0 50 88 imap 0.34 0.80 0.28 675 0 0 0 0 0 9 20 pop3-login 361.43 0.84 0.32 780 0 0 112 0 0 55 13 Date: Mon, 08 Nov 2010 04:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 587.34 0.90 1.52 22075 14 0 14288 0 0 443 375 ssl-params 275.27 0.00 0.12 469 0 0 136 0 0 14 15 pop3 23.90 0.37 0.80 2906 5 0 36856 24 0 3885 136 managesieve 0.45 0.12 0.16 577 1 0 472 0 0 10 20 managesieve-lo 357.38 0.14 0.52 1271 1 0 184 0 0 100 28 imap 0.42 0.00 0.40 671 0 0 0 0 0 9 56 pop3-login 363.16 0.12 0.64 782 0 0 112 0 0 263 23 Date: Mon, 08 Nov 2010 05:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 1005.53 0.91 1.60 21583 0 0 0 0 0 238 92 ssl-params 172.31 0.40 0.80 469 0 0 0 0 0 6 3 pop3 0.11 0.16 0.28 667 0 0 0 8 0 11 18 managesieve 0.42 0.80 0.20 577 0 0 520 0 0 13 4 managesieve-lo 84.84 0.80 0.52 1049 0 0 0 0 0 45 11 imap 0.51 0.12 0.76 664 0 0 0 0 0 10 11 pop3-login 361.78 0.64 0.28 773 0 0 0 0 0 13 2 Date: Mon, 08 Nov 2010 06:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 467.35 0.16 0.17 797 0 0 0 0 0 8 9 ssl-params 273.33 0.00 0.16 470 0 0 0 0 0 5 3 pop3 0.14 0.12 0.36 667 0 0 0 8 0 14 1 managesieve 0.20 0.00 0.28 576 0 0 0 0 0 10 1 managesieve-lo 640.83 0.13 0.44 1272 0 0 0 0 0 87 17 imap 0.33 0.40 0.32 665 0 0 0 0 0 10 47 pop3-login 362.87 0.60 0.24 774 0 0 0 0 0 13 3 Date: Mon, 08 Nov 2010 07:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 468.95 0.96 1.34 21628 0 0 0 0 0 243 218 ssl-params 83.87 0.00 0.12 469 0 0 0 0 0 7 1 pop3 0.11 0.16 0.24 667 0 0 0 8 0 11 6 managesieve 0.83 0.00 0.88 577 0 0 536 0 0 9 12 managesieve-lo 231.47 0.18 0.96 1381 0 0 0 0 0 106 17 imap 0.71 0.12 0.80 665 0 0 0 0 0 10 47 pop3-login 292.13 0.56 0.28 779 0 0 0 0 0 46 7 Date: Mon, 08 Nov 2010 08:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 452.63 0.83 1.44 20188 0 0 16 0 0 286 121 ssl-params 289.68 0.00 0.80 470 0 0 136 0 0 14 6 pop3 1.37 0.80 0.17 681 1 0 1936 16 0 55 28 managesieve 0.24 0.40 0.20 580 0 0 256 0 0 14 5 managesieve-lo 1952.41 4.93 1.58 18647 0 0 8 0 0 3673 1339 imap 0.17 0.40 0.19 665 0 0 0 0 0 6 48 pop3-login 96.75 0.60 0.28 777 0 0 112 0 0 41 14 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

4 9

[Dovecot] Expunge -A cannot find users
by Kilburn Abrahams 08 Nov '10

08 Nov '10

Hi List, If I use doveadm expunge in this format expunge will delete the email doveadm expunge -u test(a)planetseafood.com mailbox Archive ON '8-Nov-2010' But in this format doveadm expunge -A mailbox Archive ON '8-Nov-2010', it will list all the users in the database and display the following and no messages are expunged. doveadm(test@planetseafood.com@planetseafood.com): Info: User no longer exists, skipping. The iterate_query = SELECT username AS username, domain FROM mailbox which is correct for the DB layout. I am not using the expire plugin. Is this a permissions issue? Thanks Kilburn

2 2

[Dovecot] Estimación de horas del cambio a Dovecot 2.0
by Antonio Perez-Aranda 08 Nov '10

08 Nov '10

Actualmente tenemos dovecot 1.2.15 que ha demostrado ser bastante estable, pero con el que podemos tener problemas de corrupción en ficheros de índices de Dovecot (dovecot-uidlist). Este problema, podría llegar a ocasionar la descarga de todos los correos desde el cliente del usuario. En Dovecot 2.0 tenemos una mejor gestión sobre NFS mediante un nuevo sistema llamado director. Con este director se consigue que dovecot haga a su vez de proxy/balanceador e intente direccionar las conexiones de un usuario a un mismo servidor si este permite conexiones. En resumen, conseguimos evitar escrituras "concurrentes" sobre cachés de NFS que podrían ocasionar corrupción en determinados índices de dovecot. Para este cambio básicamente deberíamos repetir ciertas pruebas que hemos realizado para dovecot 1.2 así como ciertas tareas. 1. Actualizar configuración 2. Actualizar plugin TrataSPAM (MarcaSPAM/DesmarcaSPAM) Usando skel creado por Timo durante las sesiones de Málaga. 3. Pruebas de tiempos de indexado con SQUAT 4. Búsquedas concurrentes. 5. Pruebas de IMAP IDLE. 6. Migración { Keywords, suscriptions, flags, status...} 7. Condiciones de estrés. 8. Actualizar Doc. En una primera estimación. El total de estas tareas no debería superar las 45-50 horas. A cambio obtendríamos: 1. Un mejor soporte por parte de Timo. 2. doveadm para realizar búsquedas, gestión del director, pruebas de depuración... 3. Mejoras en el comportamiento ante storage en NFS. 4. Mejoras en la coordinación con SOLR para cuando comencemos con el buscador avanzado con ficheros adjuntos. 5. Mejoras para conexiones concurrentes. La razón por la que no empezamos directamente con dovecot 2.0 es porque no preveíamos que fuera relativamente estable en poco tiempo. Observando la lista de correos y después de la conversación con Timo, la última release de dovecot 2.0 es lo suficientemente estable como para usarse en sistemas de producción. Si lo creéis necesario, podemos organizar una reunión para tomar la decisión, aunque sí que esta reunión debería ser para esta semana o a principios de la siguiente.

2 2