- dovecot - dovecot.org

[wishlist] testsuite for sieve scripts, libsievetest
by Thomas Koch 23 Sep '14

23 Sep '14

Hi, I'm writing a test suite with Haskell for my sieve script. - Just to learn Haskell. But it might become something usable. The test suite calls sieve-test and parses the output. So it would of course be much simpler for me if the output of sieve-test would be easier to parse and if I'd know what output to expect. And it would be nice, if there would be an easy way to embed libsievetest as a C library. I looked into the source and the sieve-test binary does quite a bit of setup. This might be a nice hacking project for a beginner... BTW: It would be nice, if I could just 'git clone' dovecot. Thank you for dovecot!

2 1

doveadm with multiple instances on same machine(s)
by Will Yardley 22 Sep '14

22 Sep '14

Couple questions about running doveadm with multiple instances... I have Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and main instance running. When I try to lookup something on the main instance (which is handling user auth) via its auth-userdb socket directly, I get an error: # doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser doveadm(root): Error: passdb lookup failed for myuser: Configured passdbs don't support crentials lookups When I use the default lookup map, I just get the proxy settings that are configured in the director instance's authdb. # doveadm auth lookup myuser passdb: myuser user : myuser proxy : y nopassword: y In addition, "doveadm director map" can't map the username -I get the error: doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed [then I get the whole list, but with <unknown> for each user] The director itself doesn't have the LDAP passdb that the main dovecot instance talks to, but I have, in the director config: service doveadm { inet_listener { port = 8889 } } director_doveadm_port = 8889 local 192.168.x.x/24 { doveadm_password = XXXXXX } doveadm_proxy_port = 8888 And in the main config: service doveadm { inet_listener { port = 8888 } } local 192.168.x.x/24 { doveadm_password = XXXXXXX ## same password as above }

2 2

sieve redirect to foreign email gets “Relay access denied”
by Henry Stack 22 Sep '14

22 Sep '14

I have a postfix mail server with sql authentication and I want to implement sieve on it. Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. The problem is the redirect to other servers. I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign destination. # So practically a email coming from sender(a)live.de for the local user testuser(a)server.net should be redirected to destination(a)gmail.com when the subject contains "redirect" if header :contains ["subject"] ["redirect"] {redirect "destination(a)gmail.com"; stop;} when I test it I get the following log entry /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from mail.server.net[xx.xx.xx.xx]: 554 5.7.1 <destination(a)gmail.com>: Relay access denied; from=<sender(a)live.de> to=<destination(a)gmail.com> proto=ESMTP helo=<mail.server.net>/ How can I tell postfix to let dovecot/sieve relay the email? can somebody give a hint? postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 default_process_limit = 15 disable_vrfy_command = yes dovecot_destination_recipient_limit = 1 home_mailbox = mail/ inet_interfaces = all mailbox_size_limit = 0 mydestination = mail.server.net, localhost myhostname = mail.server.net mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + smtp_tls_note_starttls_offer = yes smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_recipient_restrictions = permit_sasl_authenticated, reject_unknown_sender_domain, reject_unknown_reverse_client_hostname, reject_unknown_recipient_domain, reject_unverified_recipient, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_sender dbl.spamhaus.org, check_policy_service inet:127.0.0.1:10023 smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_authenticated_sender_login_mismatch, reject_unknown_sender_domain smtpd_tls_auth_only = no smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_loglevel = 2 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes soft_bounce = no virtual_alias_domains = mysql:/etc/postfix/mysql_virtual_alias_domains.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 512000000 virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_transport = dovecot dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot/dovecot.debug.log disable_plaintext_auth = no first_valid_gid = 99 first_valid_uid = 99 hostname = maxi.zp1.net info_log_path = /var/log/mail.info lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = xxx.xxx.xxx.xxx log_path = /var/log/dovecot/dovecot.log login_greeting = Dovecot ready, Sir. mail_debug = yes mail_gid = 99 mail_location = maildir:~/mail:LAYOUT=fs:INBOX=/var/vmail/%u/mail/ mail_plugins = acl mail_uid = 99 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 ihave namespace { location = maildir:/var/mail/public prefix = Public/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box from subject msgid size sieve = ~/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/global/ sieve_max_actions = 64 sieve_user_log = ~/.dovecot.sieve.log } postmaster_address = root(a)server.net protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem submission_host = smtp.server.net userdb { args = uid=vmail gid=vmail home=/var/vmail/%u driver = static } verbose_proctitle = yes protocol lda { mail_plugins = acl sieve } protocol imap { mail_plugins = acl autocreate acl imap_acl } protocol sieve { mail_max_userip_connections = 10 }

2 1

Authentication using AD : bug ?
by Nicolas Cauchie 22 Sep '14

22 Sep '14

Hello, I've setup a mail server (still in test) with Postfix and Dovecot, authentication made using Active Directory. I authenticate my test user in AD well in Dovecot. However, if I change this user's password in AD, the old password still works for authentication in Dovecot and the new is working too. Is there a time to make Dovecot don't "remember" the old password or is it a bug ? Restarting Dovecot don't solve the problem. Do you already heard about this ? Please tell me what conf files you maybe need. Thanks in advance Nicolas signature -----

2 1

Re: LDAP and dovecot
by dovecot＠outputservices.com 22 Sep '14

22 Sep '14

For the record. I compiled dovecot to use the openldap libraries my openldap server uses. My email server and ldap server are on two different machines. So I just copied over my ldap libraries and placed them in the correct place and then compiled dovecot. I saw this clue in a different web page. Something about Solaris ldap libraries being bad. CPPFLAGS=-I/usr/local/openldap/include \ > LDFLAGS='-L/usr/local/openldap/lib -R/usr/local/openldap/lib' \ ./configure --prefix=/usr/local/tools/dovecot --with-ssl=openssl --with-solr --with-zlib --with-bzlib --with-ldap=yes This now allows me to authenticate with my openldap server. I am NOW able to authenticate to my ldap server. So my final configuration is: dovecot -n # 2.2.10: /usr/local/tools/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc base_dir = /dovecot/var/run/dovecot log_path = /dovecot/log/log mail_location = mbox:~/posta:INBOX=/var/mail/%u:LAYOUT=maildir++:INDEX=~/posta/index:CONTROL=~/posta/control passdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap } protocols = imap service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } ssl_cert = </dovecot/certs/dovecot.pem ssl_key = </dovecot/certs/dovecot.key ssl_prefer_server_ciphers = yes userdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap } /dovecot/etc/dovecot/conf.d/ldap.settings hosts = ldap.outputservices.com tls = no auth_bind = yes ldap_version = 3 base = dc=ldap,dc=outputservices,dc=com Thank you all.

1 0

X-DOVECOT capabilities
by Timo Sirainen 22 Sep '14

22 Sep '14

Dovecot has a few hidden features currenly, which I know some webmails have been hardcoded to use. Maybe it would be nice to have these available in a bit more globally usable way and advertise some kind of X-DOVECOT capability? I don't really like the idea of having a ton of separate X-DOVECOT-* capabilities. Maybe instead just have X-DOVECOT-1 for the current functionality and when more is added X-DOVECOT-2 etc? Then describe in Dovecot wiki page what they actually contain. Thoughts? The current list of features are at least: - STATUS (X-SIZE): Sum of all RFC822.SIZEs in a mailbox. (More efficient than FETCHing them.) - STATUS (X-GUID): Show mailbox's GUID. - SEARCH X-SAVEDBEFORE, X-SAVEDON, X-SAVEDSINCE: Search with message's saved-timestamp. - FETCH X-SAVEDATE: Fetch message's saved-timestamp. - SEARCH & FETCH X-GUID: Search/fetch message GUID - SEARCH X-MAILBOX, FETCH X-MAILBOX, FETCH X-REAL-UID: With virtual mailboxes search/fetch the mail's physical mailbox name and message UID. - X-CANCEL <tag>: Stop a (long-running) command, which once in a while goes back to the main loop. For example SEARCH or FETCH.

1 0

how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13
by Dave Myers 22 Sep '14

22 Sep '14

Hello again dovecot list ;) I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source. I upgraded why attempting to get lmtp working. I ultimately just coped the executable lmtp to the location that dovecot was expecting it to be in. but then the above error appeared. However when I get the info from dovecot I get the following... $ dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf so there seems to be an issue somewhere. I should note that I had copied my previous /conf.d/ files and then copied them back after the update. I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports something different. I am considering inserting the version_ignore=yes config option, but where should I insert it ? Thanks in advance. David -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74(a)gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France

3 3

dovecot´s multiple quota roots
by Andreas Kasenides 22 Sep '14

22 Sep '14

I am trying to find out how Dovecot behaves when there are multiple quota roots. I could not find something authoritative on this. For example, on a nicely running server that used fs quota I now have in 90-quota.conf > plugin { > quota = fs:Mail Quota:user:mount=/Mail > quota2 = maildir:Mail User Quota > } When I do > > doveadm quota get -u atrige01 > Quota name Type Value Limit > % > Mail Quota STORAGE 80036 204800 > 39 > Mail User Quota STORAGE 79306 - > 0 > Mail User Quota MESSAGE 304 - > 0 Apparently both STORAGE quotas values are the same. The question is which of the two is being used by Dovecot. If I insert a limit on the maildir quota which of the two will be used? I am using Dovecot 2.2.12. thank you

1 0

numeric username
by Jernej Porenta 22 Sep '14

22 Sep '14

Heya, does dovecot support "numeric only" usernames (in format "^0-9+$")? We are unable to deliver emails to such usernames via LMTP: Sep 22 08:41:05 razor4 postfix/lmtp[2120]: D4FD91CDC11F: to=<231588(a)example.org>, relay=example.org[private/dovecot-lmtp], delay=217653, delays=217653/0.01/0.02/0, dsn=4.2.0, status=deferred (host example.org[private/dovecot-lmtp] said: 451 4.2.0 <231588(a)example.org> Permission denied (in reply to end of DATA command)) On normal username format (^[a-z][-a-z0-9]+$) everything is working fine. Permissions are the same as on other accounts: # ls -la .mailbox -rw-------+ 1 231588 users 0 Sep 19 20:13 .mailbox Using dovecot 2.2.13 with local accounts on RHEL and (relevant) configs: auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Ln auth_username_translation = ... lmtp_address_translate = ... passdb { args = cache_key=%u%s dovecot default_fields = deny = no driver = pam master = no name = override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never } ... service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 5 protocol = lmtp service_count = 0 type = unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } .... userdb { args = default_fields = driver = passwd name = override_fields = result_failure = continue result_internalfail = continue result_success = return-ok skip = never } Thank you in advance, cheers, Jernej

1 0

don't understand error message
by Robert Watson 22 Sep '14

22 Sep '14

new installation of Dovecot 2.0.9 on Centos # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. LOGIN JohnDoe JohnDoe LOGIN BAD First parameter in line is IMAP's command tag, not the command name. Add that before the command, like: a login user pass ^] telnet> quit Connection closed. What's generating this error? Using samba4 ad for passdb/userdb. Robert

2 1