- dovecot - dovecot.org

[Dovecot] New install authentication probs
by Andy Smith 31 Mar '10

31 Mar '10

Hi, Im attempting to configure dovecot for the first time, Im trying to use a MySQL DB that is currently used by tpop3d as Ive read they support the same password format. My main prob currently, apart from that it doesnt work lol, is that Ive enabled the following debugging in dovecot.conf auth_debug = yes auth_debug_passwords = yes auth_verbose = yes But Im getting basically zero info on why my authentication is failing. In my log (which for testing Ive defined as a file in /tmp to make sure Im getting all the info logged to one place) I see just: Mar 31 19:00:17 dovecot: Info: Dovecot v1.2.10 starting up Mar 31 19:00:17 auth-worker(default): Info: mysql: Connected to localhost (ukgri d_vmail) Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64188 Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64186 Mar 31 19:00:18 auth(default): Info: new auth connection: pid=64187 each time I attempt to connect via IMAP it adds another new auth connection line to the log but doesnt tell me anything else :(. So Im stuck debugging my authentication due to lack of info. BTW Im testing IMAP via telnet, telnet to IMAP port and attempt LOGIN (I have this working to a courier IMAP installation). Have I done something wrong? Any help appreciated! thanks Andy.

2 1

[Dovecot] Can Dovecot do this...
by Robert Lopez 31 Mar '10

31 Mar '10

I need some experienced Dovecot and email administrators to give me some feed back on a project which has been assigned to me. First some background. What exists now at our college: Three email gateway systems that route email between the Internet and one of the student email system, the staff email system, or the email list server system. The gateway systems do not route email from an external system to another external system. The MTA on each gateway is Postfix. The MTA of the student email system is Luminis. The MUA of the student email system is a web interface to Luminis. The MTA of the staff email system is Exchange. There are two staff MUA. One is Outlook. The other is Outlook Web Access. Within our network we have a system (separate from above) that is a LDAP server used for implementing single sign on to many college systems including the student and staff email systems. At this time SASL is not used in any way. There is no authentication of the movement of email. Authentication is only for using a MUA. It is now proposed that certain staff members should be allowed to be at some remote location and compose an email which will be sent to SOMETHING at our college which will then cause two things to happen. First, the From: information and Reply-To: information will be re-written from what ever they may be to become that person's college email address. Second, the email will then be routed to an intended recipient be it within our community or outside of our community. For examples, if the college president were with a member of the state legislature trying to get information for the state governor, she could send an email via her personal phone system to a college financial person who would never see her personal address. Upon receiving a reply, she then could send the state governor an email and it would appear to the governor as if it came from her college account. I have been told by my management other colleges are doing this with Postfix and SASL. I posted a question about this to a Postfix list and I was told Dovecot was the best SASL to use for implementing this. So, the project as it has been described to me is this: We will make no changes to the three gateway systems. We will add a new gateway system to enable this. This new system will challenge all email being sent to it. It will collect the college account-name and the password which will then be used to see if there is a matching account in the LDAP system. If there is not then the email transfer conversation will quit. If there is a matching account then the header rewrites will occur and the email will be routed. There are many things I do not understand: Is if this senario is possible? Would postfix on the new system do the address re-writes or would Dovecot do it? What would store the information necessary for the reply routing? What would happen in one internal address to many external address situations? If the project was simplified by removing the ability to reply to an email; so it was only a way to route external to external with rewrite is is then possible? So, I would like some comment on if this is a common or know practice and if Dovecot is used in those situations (if any). Thank you. -- Robert Lopez Unix Systems Administrator Central New Mexico Community College (CNM) 525 Buena Vista SE Albuquerque, New Mexico 87106

3 2

[Dovecot] Get plugins configuration in dovecot 2.0
by Alex Baule 31 Mar '10

31 Mar '10

In 1.X to get configuration Timo said. In v1.x they're in environment variables. So if you have: plugin { foo = bar } getenv("FOO") returns "bar". But, in 2.0 ?! getenv dont work....

2 1

[Dovecot] Documentation error
by Robert Lopez 30 Mar '10

30 Mar '10

http://wiki.dovecot.org/Debugging/Authentication There appears to be an error in this line: The PLAIN mechanism's authentication format is: <authorization ID> NUL <authentication ID> NUL <password>. Authentication ID is the username who you want to log in as, and authentication ID is the username whose password you're giving. I suppose it should be: The PLAIN mechanism's authentication format is: <authorization ID> NUL <authentication ID> NUL <password>. Authorization ID is the username who you want to log in as, and authentication ID is the username whose password you're giving. -- Robert Lopez Unix Systems Administrator Central New Mexico Community College (CNM) 525 Buena Vista SE Albuquerque, New Mexico 87106

1 0

[Dovecot] Post Login Script in 2.0
by Mark Moseley 30 Mar '10

30 Mar '10

Been digging through the list archives but I didn't see anything about this specifically. I've been playing with trying to get the post-login script stuff working with 2.0 (tried with a mercurial checkout from today and one I had kicking around from a few days ago), mainly to run the courier conversion script after logins. I'm using the 'executable' arg in 'service pop' and 'service imap' and I've tried with and without "drop_priv_before_exec=yes". I've just been using the test script mentioned in the wiki that dumps the environment to a file in /tmp and then execs libexec/imap or libexec/pop. The script specified in 'executable' is definitely getting executed just fine and logins work just fine. When it executes though, they're getting just the basic environment, as opposed to the environment that shows up in 1.2.11 full of various MAIL*/NAMESPACE*/etc variables. And I see in strace output that there's no batch of env vars getting passed around anymore, even when dovecot invokes libexec/imap or libexec/pop directly. Is there a setting that tells the dovecot process to fork the post-login script with the fully populated set of environment variables? Or alternatively, in the 2.0 world, is the idea to get that info out of the /var/run/dovecot/config socket? If so, is there an example somewhere? I can post my configs, but I figured that since this is a conceptual problem, I might as well ask first without pasting a few pages of "dovecot -a" output :)

2 5

[Dovecot] Problem with IMAP on port 993
by Jerry 30 Mar '10

30 Mar '10

This is probably a misconfiguration of my MUA; however, I thought I would ask here first. I am using IMAP with Dovecot. Claws-mail is my MUA. Now, when fetching mail via port 143, everything works fine: Mar 29 10:33:00 imap-login: Info: Login: user=<user(a)domain.net>, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, TLS However, when I attempt to fetch mail via port 993, I get this message in the log: Mar 29 10:28:35 imap-login: Info: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, TLS handshaking: Disconnected I think I have everything set up correctly. # dovecot -n (portions obfuscated) # 1.2.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.3-STABLE i386 ufs log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): localhost:2000 login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_greeting: Greetings From my-domain.net verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location(default): maildir:/var/mail/vhost/my-domain.net/user:INDEX=/var/mail/vhost/my-domain.… mail_location(imap): maildir:/var/mail/vhost/my-domain.net/user:INDEX=/var/mail/vhost/my-domain.… mail_location(pop3): maildir:/var/mail/vhost/my-domain.net/user:INDEX=/var/mail/vhost/my-domain.… mail_location(managesieve): maildir:/var/mail/vhost/my-domain.net/user mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): expire mail_plugins(imap): expire mail_plugins(pop3): expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): dict_db_config: /usr/local/etc/dovecot-db.conf managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) lda: postmaster_address: postmaster(a)my-domain.net mail_plugins: expire mail_plugins: sieve sieve: /usr/local/etc/dovecot/sieve/user.sieve sieve_global_path: /usr/local/etc/dovecot/sieve/user.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: cram-md5 digest-md5 plain login username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@+ username_format: %Lu passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 438 master: path: /var/run/dovecot/auth-master mode: 438 plugin: expire: Trash 1 Spam 30 Sent 10 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf -- Jerry Dovecot.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Have the courage to take your own thoughts seriously, for they will shape you. Albert Einstein

4 6

[Dovecot] Dovecot 2.0 zlib and dbox
by Renaud Allard 30 Mar '10

30 Mar '10

Hello, As per wiki instructions, I tried to enable zlib compression of mails by adding/modifying the following snippets of configuration: plugin { zlib_save_level = 6 zlib_save = gz } and protocol imap { mail_plugins = fts fts_squat autocreate zlib imap_zlib imap_id_log = * } I am using dbox format and delivering the mails via dovecot deliver, however mails don't seem compressed at all. It is not very clear if compression is available for something else than maildir and mbox, so is compression available with dbox format? I am using dovecot-2-0-aefa279e2c70 from hg. Best Regards

2 3

[Dovecot] Dovecot 2.0beta4 HG 11014: Crashes on parsing settings via LMTP service
by Thomas Leuxner 29 Mar '10

29 Mar '10

Hi, unfortunately no core was dumped. Let me know if you need more info to debug. ==> /var/log/dovecot.log <== Mar 27 08:13:38 spectre dovecot: lmtp(8362): Connect from local Mar 27 08:13:38 spectre dovecot: lmtp(8362): Panic: file settings-parser.c: line 1501 (settings_link_get_new): assertion failed: (diff + sizeof(*old_link->array) <= old_link->parent->info->struct_size) Mar 27 08:13:38 spectre dovecot: lmtp(8362): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f055dec6712] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f055dec677a] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f055dec6b23] -> /usr/lib/dovecot/libdovecot.so.0 [0x7f055dea6993] -> /usr/lib/dovecot/libdovecot.so.0(settings_parser_dup+0x1d2) [0x7f055dea6be2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup+0x191) [0x7f055e1370c1] -> dovecot/lmtp(cmd_rcpt+0x4d4) [0x407924] -> dovecot/lmtp(client_input_handle+0x19b) [0x4066db] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xcb) [0x7f055ded144b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f055ded05c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f055dec0323] -> dovecot/lmtp(main+0x123) [0x405bf3] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x7f055d74d1a6] -> dovecot/lmtp [0x4059f9] Mar 27 08:13:38 spectre dovecot: master: service(lmtp): child 8362 killed with signal 6 (core not dumped) Regards Thomas

3 6

[Dovecot] dovecot: auth(default): Fatal: Unknown database driver 'mysql'
by Glen Lee Edwards 29 Mar '10

29 Mar '10

I just tried upgrading from 1.1.rc6 to v1.2.11, and am getting the following error: dovecot: auth(default): Fatal: Unknown database driver 'mysql'. If I change the respective line in dovecot-sql.conf from driver = mysql to driver = pgsql the error message changes accordingly: dovecot: auth(default): Fatal: Unknown database driver 'pgsql'. I quit using 1.1.rc6 because it started choking on my Debian system, so I'm back to using the stable Debian version - 1:1.0.15-2.3+lenny1. Where are the drivers kept when I do a default build, and where in the configuration file does it tell dovecot to look for the drivers? Other suggestions on a fix? Glen

3 7

[Dovecot] Which Authentication Method Best Between FreeBSD and Macintosh?
by Martin McCormick 29 Mar '10

29 Mar '10

I recently discovered that I need to occasionally forward Email from a FreeBSD system to a Macintosh. Imap does look like the best solution to this problem. The mail program on the Mac lists several protocols such as pop (okay with me) and SSL certificates which I want to avoid if at all possible. Which of the several listed methods of authentication should I compile in as I build dovecot on the FreeBSD system? Options for dovecot 1.2.10 [X] KQUEUE kqueue(2) support [ ] SSL SSL support [ ] IPV6 IPv6 support [ ] MANAGESIEVE ManageSieve support [ ] GSSAPI GSSAPI support [ ] VPOPMAIL VPopMail support [ ] BDB BerkleyDB support [ ] LDAP OpenLDAP support [ ] PGSQL PostgreSQL support [ ] MYSQL MySQL support [ ] SQLITE SQLite support � � IPV6 is not used here and my laziness says to avoid creating any new data bases or data base servers to support something I will probably use once every 2 or 3 months for one or 2 messages. I just want to get on the Mac and read messages posted in a certain account on the FreeBSD system. Sorry if this all sounds a bit odd, but I usually read mail on the FreeBSD box. Occasionally, I get a message containing a 20-mile-long URL that works better when using the Mac's safari browser tools. Presently, I have succeeded in compiling dovecot on the freeBSD system which runs and looks like it is ready to work. The Mac contacts the freeBSD box and then both appear to get a death grip on each other and nothing much happens until I force a quit of mail on the Mac. Thanks for any suggestions. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Telecommunications Services Group

1 0