- dovecot - dovecot.org

[Dovecot] sender address of sieve vacation script
by Wolfgang Burger 05 Aug '10

05 Aug '10

Hi, not entirerly sure wether this is the right place to ask. Sorry if not. I´m running dovecot on a Mac OS X Server (10.6.4). Everything works fine. When I try to enable a vacation message, I get the following error in the log: delays=0/0.01/0.09/0.1, dsn=5.0.0, status=bounced (host XXX[x.x.x.x] said: 553 Mail to <name(a)domain.tld> not allowed; missing domain name in MAIL FROM (in reply to RCPT TO command)) Where host is the mail relay. The logs on the mail relay show matching entries. Sending mails is generally working. I´ve sniffed the network traffic and the FROM Field in the SMTP transfer contains only the following text: <> I´ve allready set the value of myorigin in /private/etc/postfix/ main.cf but to no avail. Can somebody tell me where I can set the sender address of the vacation mail? Or is there something else wrong? Thank you very much. Best regards Wolfgang

3 2

[Dovecot] mobile phone access to dovecot
by casanova99 05 Aug '10

05 Aug '10

I didn't find anything interesting in the search, so I just wanted to see what other people have done (or thought about doing). I'd like to be able to access my dovecot server via IMAP, from the Internet, using the integrated e-mail client from a smart phone. I'm very concerned about security and don't feel comfortable just poking holes into the firewall for direct access from the Internet. Is there a better way to do this? Thanks. -- View this message in context: http://old.nabble.com/mobile-phone-access-to-dovecot-tp29342338p29342338.ht… Sent from the Dovecot mailing list archive at Nabble.com.

3 3

[Dovecot] IMAP access to dovecot list archives?
by Charles Marcus 05 Aug '10

05 Aug '10

Hi Timo, Before I go file a bug for Thunderbird, can you confirm that IMAP access to the dovecot mail list archives should still be working? TB is getting stuck in the account creation screen, and this may be confirmation of a bug they are having trouble isolating in the New Account Wizard. Thanks, -- Best regards, Charles

3 11

[Dovecot] LMTP: Rejecting unknown users
by Peer Heinlein 04 Aug '10

04 Aug '10

Hi! I'm using static results in LDAP-lookups: uris = ldap://127.0.0.1 dn = xxxxxxxxxxxxx dnpass = xxxxxxxxxxxx tls = no ldap_version = 3 base = xxxxxxxxxxxxxxxxx user_attrs = =home=/mail/%d/%n,=uid=10000,=gid=10000,jpberlinMailQuota=quota_rule=*:storage=%$B user_filter = (email=%u) pass_attrs = userPassword=password pass_filter = (email=%u) default_pass_scheme = PLAIN Unfortunately, LMTP accepts mail for *all* users, even for those users, that doesn't exist in LDAP at all: 010-08-04 12:27:58 auth: Debug: Loading modules from directory: /usr/lib/dovecot/modules/auth 2010-08-04 12:27:58 auth: Debug: auth client connected (pid=10049) 2010-08-04 12:27:58 lmtp(10054): Debug: none: root=, index=, control=, inbox= 2010-08-04 12:27:58 auth: Debug: master in: USER 1 tessdfdfgdsft(a)example.org service=lmtp lip=(null) r ip=(null) 2010-08-04 12:27:58 auth: Debug: ldap(tessdfdfgdsft(a)example.org,0.0.0.0): user search: base=xxxxxxxxxxxxxxxxxxx 2010-08-04 12:27:58 auth: Debug: ldap(tessdfdfgdsft(a)example.org,0.0.0.0): no fields returned by the server 2010-08-04 12:27:58 auth: Debug: master out: USER 1 tessdfdfgdsft(a)example.org home=/mail/example.org/tessdfdfgd sft uid=10000 gid=10000 2010-08-04 12:27:58 lmtp(10054): Debug: auth input: tessdfdfgdsft(a)example.org home=/mail/example.org/tessdfdfgdsft uid=10000 gid= 10000 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Effective uid=10000, gid=10000, home=/mail/example.org/tessdfd fgdsft 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no , list=yes, subscriptions=yes 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: maildir++: root=/mail/example.org/tessdfdfgdsft/Maildir, index =, control=, inbox=/mail/example.org/tessdfdfgdsft/Maildir 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, h idden=no, list=children, subscriptions=no 2010-08-04 12:27:58 lmtp(10054, tessdfdfgdsft(a)example.org) Debug: shared: root=/var/run/dovecot, index=, control=, inbox= Looks like the "allow_all_users"-Problem from the static database. :-) How can I tell LMTP do reject Mails to users, that doesn't exist in the database/LDAP? It's much better to do this in Dovecot/LMTP then in Postfix-Relay (which can then use LMTP for dynamic address verification). Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-42 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

4 7

Re: [Dovecot] Shared mailboxes errors
by Nikita Koshikov 04 Aug '10

04 Aug '10

On Tue, 03 Aug 2010 23:16:38 +0200 Leander S. wrote: > Hi Nikita Koshikov, > > when I googled for my SERVERBUG which I'm having right now I found your > configuration. > I'm trying to make use of the antispam plugin as you do. Unfortunately > I'm always getting a [SERVERBUG] error mesage with my MTC when I try > moving mails. The antispam debug.log doesn't really tell a lot of more: > > > ### Dovecot AntiSpam ### > # mail signature (used with any backend requiring a signature) > #antispam_signature = X-Spam-Status > #antispam_signature_missing = move > > antispam_mail_sendmail = /usr/local/bin/sa-learn > antispam_mail_sendmail_args = --username=%u;--debug;all > antispam_mail_spam = --spam > antispam_mail_notspam = --ham > antispam_mail_tmpdir = /tmp > antispam_spam = Spam > antispam_unsure = Virus > antispam_trash = Trash > First of all - what OS is this ? BSD ? And how did you install your spamassassin (ports\compiling from source)? Show your local.cf file (/etc/mail/spamassassin or /usr/local/etc/mail/spamassasin). After reading perldoc Mail::SpamAssassin::Conf add to your local.cf for debugging: bayes_file_mode 0777 bayes_path /tmp/.spamassassin/bayes Create folder /tmp/.spamassassin and set permitions 777. Restart spamd with dovecot and try it. > I also read through the sa-learn script but wasn't able to figure out > where this number 9 is coming from ;/ > ... SIGKILL 9 Term Kill signal - but where from ?! > sa-learn has lots of die() function, this should be enough for raising SIGKILL. > > > Do you maybe have any idea? I tried different Dovecot versions already - > alwys the same ... Might there maybe somethign wrong with my syntax? > > > > Any way - thanks a lot in advance & regards > If you stuck after all, remember that sa-learn has -D key, it generate tons of output. Create wrapper and run sa-learn with -D keyword from dovecot, save result and have fun.

2 1

[Dovecot] Dovecot 1.2.13 intermittent authentication failures
by C. Bensend 04 Aug '10

04 Aug '10

Hey folks, I recently upgraded my mail server from an older OpenBSD -CURRENT snapshot to the latest (Aug 1). As part of this upgrade, I updated all of my packages to their latest versions. Since this upgrade, dovecot has begun failing to authenticate intermittently. I use it primarily for web mail (Squirrelmail 1.4.20) and leave myself logged in during the day. This problem manifests itself by kicking me back to the "Username or password incorrect" screen occasionally (several times an hour) when the page refreshes. I am not using sieve, and while I have the PostgreSQL version of the OpenBSD package installed, I do not currently use it for authentication. I am authenticating against the OpenBSD system. The only error I get in the mail log is: Aug 3 11:00:09 fusion dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<benny>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured There are no errors in the Apache error log... Squirrelmail's version wasn't upgraded, so I don't think this is a Squirrelmail problem as far as I can tell. My config is pretty simple: # 1.2.13: /etc/dovecot.conf Warning: fd limit 128 is lower than what Dovecot can use under full load (more than 640). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: OpenBSD 4.8 i386 base_dir: /var/dovecot/ listen: *, [::1] ssl_cert_file: /etc/ssl/webmail.crt ssl_key_file: /etc/ssl/private/webmail.key login_dir: /var/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot mail_location: maildir:~/Maildir mbox_write_locks: fcntl imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com auth default: mechanisms: plain login passdb: driver: bsdauth userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix Everything seems to be working just fine (ie, I don't get any other IMAP errors or see any problems), it's just that it will spontaneously fail to authenticate. When this happens, it may take more than one try to get logged back in. I checked with the OpenBSD port's maintainer, and he hadn't heard of any similar issues (and he uses it himself). Can anyone please help? Thank you so much! Benny -- "Something's going on in this house - last night, I saw a face!" "Did it have a nose?" "Yes!" "That sounds like a face all right." -- Scary Movie 4

2 10

[Dovecot] error 89 when loading plugin
by John O'Brien 04 Aug '10

04 Aug '10

Hi, I'm very confused - that's not too difficult for me. I have written a small plugin change_passwd_plugin.c I would like this custom IMAP command to be available to all users. The code contains the following. void change_passwd_plugin_init(void) { command_register("XCHANGEPASSWORD", cmd_xchangepasswd, 0); str_append(capability_string, " XCHANGEPASSWORD"); } void change_passwd_plugin_deinit(void) { command_unregister("XCHANGEPASSWORD"); } % nm 0000000000000920 T change_passwd_plugin_deinit 00000000000008ec T change_passwd_plugin_init 0000000000201248 D change_passwd_plugin_version dovecot.conf mail_plugins = change_passwd_plugin mail_plugin_dir = /usr/lib/dovecot/imap imap_capability = XCHANGEPASSWORD %ls -la /usr/lib/dovecot/imap ls -la /usr/lib/dovecot/imap total 28 drwxr-xr-x 2 root root 4096 Aug 1 16:03 . drwxr-xr-x 3 root root 4096 Aug 1 10:51 .. -rwxr-xr-x 1 root root 16969 Aug 1 16:03 change_passwd_plugin.so During login I see the following /var/log/maillog Aug 1 16:13:00 development dovecot: IMAP(test): Loading modules from directory: /usr/lib/dovecot/imap Aug 1 16:13:00 development dovecot: IMAP(test): Plugin change_passwd_plugin not found from directory /usr/lib/dovecot/imap Aug 1 16:13:00 development dovecot: child 29715 (imap) returned error 89 I don't understand why I'm getting an "error 89" reported. The login session is terminated by dovecot when the error occurs. Any assistance or ideas would be appreciated. Regards, John

4 4

[Dovecot] IMAP/POP3 Proxy Redundancy
by Cory 04 Aug '10

04 Aug '10

Looking over the list archives and Wiki there doesn't seem to be any sort of built-in host redundancy with the proxy. I would prefer to use a built in though it doesn't look like this is possible. One of the suggestions that I found in the list archives was to write a script which checks the health of the hosts and adjusts the MySQL table accordingly. Has anyone done anything like this in production? Thanks, Cory Here is a sample of what I'm testing the proxy with. CREATE TABLE `users` ( `user` varchar(255) NOT NULL, `filesystem` varchar(5) NOT NULL, PRIMARY KEY (`user`), UNIQUE KEY `idx_user` (`user`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 CREATE TABLE `hostmap` ( `id` int(11) NOT NULL auto_increment, `filesystem` varchar(5) NOT NULL COMMENT 'Filesystem identifier', `ip` int(10) unsigned NOT NULL, `alive` tinyint(1) NOT NULL default '1', PRIMARY KEY (`id`), UNIQUE KEY `idx_hostmap` (`filesystem`,`ip`) ) ENGINE=MyISAM AUTO_INCREMENT=103 DEFAULT CHARSET=latin1 password_query = SELECT user,NULL as password, INET_NTOA(hostmap.ip) as host, 'Y' AS proxy_maybe from users left join hostmap on users.filesystem=hostmap.filesystem where hostmap.alive=1 and users.user='%u' limit 1;

2 1

[Dovecot] expire plugin
by Arnaud2 bali 04 Aug '10

04 Aug '10

Hi I try to use expire plugin with mysql When i use my thunderbird client to delete a message, nothing is write in the mysql database. My maildir is look like /home/vmail/homes/arnaud2(a)xxx.xxxx.xxx/ and /etc/dovecot/dovecot-dict-expire.conf : connect = host=localhost user=xxxxxx password=xxxxxxxxx dbname=postfixadmin map { pattern = /home/vmail/homes/$user/$mailbox #shared/expire/$user/$mailbox table = dovecot_expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } Is pattern ok ? My detail configuration : # dovecot --version 1.2.11 # dovecot -n # 1.2.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.5 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3s managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:/%h mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota expire imap_quota autocreate mail_plugins(imap): quota expire imap_quota autocreate mail_plugins(pop3): quota expire autocreate mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve lda: postmaster_address: xxx(a)xxxxxxxx.xx mail_plugins: quota expire sieve autocreate auth_socket_path: /var/run/dovecot/auth-master auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir expire: .Trash 1 .Trash/* 1 .Spam 2 expire_dict: proxy::expire sieve: ~/.dovecot.sieve sieve_after: /home/vmail/sieve/default.sieve autocreate: Trash autocreate2: Spam autocreate3: Sent autocreate4: Inbox autocreate5: Drafts autocreate6: Templates autosubscribe: Trash autosubscribe2: Spam autosubscribe3: Sent autosubscribe4: Inbox autosubscribe5: Drafts autosubscribe6: Templates dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf # cat /etc/dovecot/dovecot-dict-expire.conf connect = host=localhost user=xxxxxx password=xxxxxxxxx dbname=postfixadmin map { pattern = /home/vmail/homes/$user/$mailbox #shared/expire/$user/$mailbox table = dovecot_expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } mysql> desc dovecot_expires; +--------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +--------------+--------------+------+-----+---------+-------+ | username | varchar(255) | NO | PRI | NULL | | | mailbox | varchar(255) | NO | PRI | NULL | | | expire_stamp | int(11) | NO | | NULL | | +--------------+--------------+------+-----+---------+-------+ # cat /etc/dovecot/dovecot-sql.conf driver = mysql connect = host=localhost user=xxxxxxx password=xxxxxxx dbname=postfixadmin user_query = SELECT CONCAT('/home/vmail/homes/',maildir) AS home, 65500 AS uid, 65500 AS gid, \ CONCAT('*:bytes=', CAST(quota AS CHAR)) AS quota_rule \ FROM mailbox WHERE username = "%u" AND active=1 password_query = SELECT username as user, password, maildir as userdb_home, 65500 as userdb_uid, 65500 as userdb_gid FROM mailbox WHERE username = '%u' AND active=1 Thank you

2 4

[Dovecot] Dovecot 2.0.rc3 Capability response
by Christian Affolter 04 Aug '10

04 Aug '10

Hi I have a question regarding the IMAP CAPABILITY command behavior of Dovecot 2.0.rc3. While connecting to a Dovecot 1.2.4 server and requesting the supported capabilities, Dovecot returns all capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ACL RIGHTS=texk QUOTA AUTH=PLAIN AUTH=CRAM-MD5 a1 OK Capability completed. Doing the same on 2.0.rc3, will return only a limited set of supported capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN a1 OK Capability completed. However after a user has logged in, Dovecot 2.0.rc3 returns all supported capabilities: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 login user(a)example.com pass a1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA ACL RIGHTS=texk] Logged in a2 CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA ACL RIGHTS=texk a2 OK Capability completed So what's the idea behind the change of this behavior? Is it planned to support different capabilities per user in the future? The reason behind my question is, that the Open-Xchange IMAP client implementation relies on the presence of the ACL capability presented before the actual login took place. Thanks for any clarifications. Regards Christian

6 8