- dovecot - dovecot.org

[Dovecot] Dovecot + Xmail Setup Howto
by Chris L. Franklin 17 Jan '05

17 Jan '05

OK I finally found time to write this. (this is for dovecot 99.X and Xmail 1.X >= 1.17) (in dovecot 1.0 it'll able to auth against Xmail via a auth script. aka You'll only need to have 1 user account databases, XMAIL's YAY !!!) Steps: 1. Install Dovecot. (rpm or Source) >From Source : http://wiki.dovecot.org/CompilingSource >From RPM : http://wiki.dovecot.org/PrebuiltBinaries 2. Edit config (my's listed below) CODE base_dir = /var/run/dovecot/ imap_listen = * pop3_listen = * info_log_path = /var/log/dovecot login_dir = /var/run/dovecot/login login = imap login_executable = /usr/libexec/dovecot/imap-login login = pop3 pop3_executable = /usr/libexec/dovecot/pop3 verbose_ssl = no default_mail_env = /var/MailRoot/domains/%d/%n/Maildir mail_cache_fields = Envelope MessagePart client_workarounds = outlook-idle mailbox_check_interval = 5 mailbox_idle_check_interval = 30 maildir_stat_dirs = no maildir_copy_with_hardlinks = no maildir_check_content_changes = yes auth_mechanisms = plain auth_userdb = static uid=97 gid=97 home=/var/MailRoot/domains/%d/%n/Maildir auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_passdb = passwd-file /var/MailRoot/dovecotusers.tab 3. Isnatll Xmail >From Source : http://www.xmailserver.org/Readme.html#build >From RPM : (rpm -i xmail-X.rpm) 4. Configure XMail, edit server.tab Server.tab Config: http://www.xmailserver.org/Readme.html#server_tab_variables Heres Mine (with in all xmail files there are no SPACES only TABS !!!) CODE "RootDomain" "nomadcf.com" "SmtpServerDomain" "nomadcf.com" "POP3Domain" "nomadcf.com" "HeloDomain" "nomadcf.com" "PostMaster" "postmaster(a)nomadcf.com" "ErrorsAdmin" "postmaster(a)nomadcf.com" "SMTP-MaxErrors" "0" "NoSenderBounce" "1" "RemoveSpoolErrors" "1" "NotifySendLogToSender" "1" "ReceivedHdrType" "1" "SmtpMsgIPBanSpammers" "Denied due to you being a F'in SPAMMER !!!!!" "SmtpMsgIPBanSpamAddress" "550 Denied due inclusion of your email address in our spam lists" "SmtpMsgIPBanMaps" "550 Denied due inclusion of your IP in the following map" "EnableAuthSMTP-POP3" "0" "AllowNullSender" "1" "AllowSmtpVRFY" "1" "AllowSmtpETRN" "1" "CustMapsList" "list.dsbl.org.:1,blackholes.mail-abuse.org.:1,dialups.mail-abuse.org.:0" "SMTP-RDNSCheck" "1" "CheckMailerDomain" "1" "DefaultSmtpPerms" "MRVZ" 4.5 Setup Admin Account for Xmail moreinfo : http://www.xmailserver.org/Readme.html#ctrlaccounts_tab CODE (Replace BOB with you admin password, Replace ROOT with your Admin userame) cd /var/MailRoot/bin ./XMCrypt BOB | awk '{print "ROOT\t"$1"\n"}' > ../ctrlaccounts.tab 5. Setup your XMail Domains + Users It's easy'st with a interface. Heres a list of some Windows : http://www.alouria.com/ Web : http://dev.waaf.net/xmail/ Web : http://www.akxak.de/xpai/ Web : https://sourceforge.net/projects/phpxmail 6. Give Dovecot permission to the domains dir under MailRoot I used acls to do this so that Xmail can still run as root and Dovecot could still run as a non-root user. (if you rather not do this your other option is tp run xmail as the same user a dovecot See non-Acls below) CODE setfact -R -m d:u:dovecot:rwx,d:g:dovecot:rwx;d:o:---,d:m:rwx /var/MailRoot/domains setfacl -R -m u:dovecot:rwx,g:dovecot:rwx;o:---,m:rwx /var/MailRoot/domains 7. Set Xmail to listen on another port then 110 for pop3. Add "-Pp 20110 " to xmail startup options. 8. Setup User Accounts. As of 99.X of dovecot it doesn't support using a external script to check user acount info (user/password). So it needs a place to have it's own useraccount storage place. For more ways dovecot can store user info see : http://wiki.dovecot.org/Authentication I use " passwd-file /var/MailRoot/dovecotusers.tab" and create it from a modified xmail2smapost script called xmail2dovecot. (See xmail2dovecot below) 9. Restart Xmail 10. Startup Dovecot Non-Acls: To allow Xmail to so it's thing + Allow dovecot Access to XMails MailRoot. You'll need to run Xmail as the user Dovecot runs at. I found after some trial and error that is pretty easy. What you'll need. 1. Iptables 2. su Setup 1. Disable Xmail from starting at boot. 2. Stop Xmail 3. edit the user dovecot and chnage there shell to /bin/bash 4. Create a IPtables rule to route port 25 to 20025 Example: CODE iptables -t nat -A PREROUTING -p tcp --dport 25 -j REDIRECT --to-port 20025 5. Change permissions in MailRoot from root.root to dovecot.dovecot CODE chown -R dovecot.dovecot * 6. Startup Xmail as so : CODE su - dovecot -c "/var/MailRoot/bin/XMail -Mr 24 -Pl -Ph -Sl -Ql -Yi 30 -Yl -Fl -Cl -Ll -PX 0 -Sp 20025 -Pp 20110 -Fp 20079 -Ms /var/MailRoot" XMail2Dovecot Script: This a script that was Org. used with smartpost. And was called xmail2smartpost.php But I changed it to output All the user account info into a simple passwd/Shadow. (user@domain:MD5-password) Download From : http://xmail.nomadcf.com/info.php?program=xmail2dovecot After Downloading it , extract it to the MailRoot/bin/ and then edit it. And lastly Run it as like so : CODE cd /var/MailRoot/bin/ ./xmail2dovecot.php > ../dovecotusers.tab -- Chris L. Franklin --

2 1

[Dovecot] Squirrelmail - messages not marked as read
by Kim Culhan 16 Jan '05

16 Jan '05

As of test-60 and test-61, running Squirrelmail 1.5.1[cvs] on FreeBSD 5.3-STABLE, messages are not marked as read after they are read. If I switch back to test-59, it works normally. When switching back to test-59, with log_path = /var/log/dovelog dovelog shows: dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 11:43:38 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed If I change to test-61, when starting Squirrelmail for the first time the same will logged: log dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Drafts/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Sent/dovecot.index.cache: indexid changed dovecot: Jan 14 12:00:26 Error: IMAP(kimc): Corrupted index cache file /home/kimc/Maildir/.INBOX.Trash/dovecot.index.cache: indexid changed After this initial version switch, it will not log any errors. Each time switching back to test-59 will cause the 'read' state to again work correctly (and a one-time logging as above.) Please let me know if there is anything I can do to help debug this. regards -kim -- w8hdkim(a)yahoo.com __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

4 4

[Dovecot] Proposed dovecot update changes in Fedora
by Kenneth Porter 16 Jan '05

16 Jan '05

FYI, forwarded from the Fedora development list: ------------ Forwarded Message ------------ Date: Saturday, January 15, 2005 7:16 PM -1000 From: Warren Togami <wtogami(a)redhat.com> To: John Dennis <jdennis(a)redhat.com> Cc: Development discussions related to Fedora Core <fedora-devel-list(a)redhat.com> Subject: Proposed dovecot update changes John, https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=143707 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145214 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145241 Any objections to my proposed changes? I can implement all of this and supply patches for your review, or apply it myself to CVS if you wish. I summarize each problem and my proposed solution below. 1. Unnecessary dependency on mysql/postgresql ============================================= Prereq: postgresql Prereq: mysql These lines are wrong. The package is fine without it, because RPM auto-dep pulls in the client library of mysql and postgresql rather than a larger unnecessary chunk of those databases. These dependencies are resolved properly by yum and handled automatically. Solution: Just remove those lines. 2. dovecot.conf should default to fcntl locking =============================================== https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145214#c7 Our default dovecot.conf changed from fcntl to dotlock sometime after the release of FC2. That is one of the reasons why we see this above bug. This problem must now be attacked on two fronts: 1) Our default dovecot.conf must be changed to use fcntl by default again. If someone uses a broken NFS where fcntl doesn't work, then it is up them to edit their configuration to use dotlocks. If users have not modified dovecot.conf, then upgrading to the new package will set fcntl default. 2) For exisiting users who have modified dovecot.conf, it would be dangerous to force a change to fcntl during %post. Then "mail_extra_groups = mail" is the correct line to add durin 3. FC2 should not link to mysql/postgresql (???) ================================================ https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=145241#c1 FC2 dovecot originally did not link to mysql and postgresql, so arguably we should not add those dependencies in an update. Unfortunately our current FC2 update is linked in this way, so we would be breaking existing users if they did begin using this functionality in FC2. I am guessing that the likelihood of this is very low and we should go ahead. (However we could just as easily leave it as is, then it would only be a minor annoyance rather than a real problem.) FC3 dovecot did link to mysql/postgresql libs, so we must not change that or split into sub-packages because then an update would break existing users. FC4 we have the option of splitting mysql/postgresql into sub-packages, which is probably the correct thing to do based on the php precedent. Thoughts? Warren Togami wtogami(a)redhat.com -- fedora-devel-list mailing list fedora-devel-list(a)redhat.com http://www.redhat.com/mailman/listinfo/fedora-devel-list ---------- End Forwarded Message ----------

1 0

Re: [Dovecot] istream-limit.c - assertion failed
by Kim Culhan 15 Jan '05

15 Jan '05

On Fri, January 14, 2005 4:44 pm, Mail Admin said: > dovecot: Jan 14 12:25:49 Error: IMAP(xxxuser): file istream-limit.c: > line 85 (_seek): assertion failed: (v_offset <= lstream->v_size) I think this is the same problem I was having, try this.. After running configure and before doing a make, edit config.h: /* Define if you have FreeBSD-compatible sendfile() */ /* #define HAVE_FREEBSD_SENDFILE */ ^^ ^^ Comment out the define for FreeBSD as above and do a make and install. Please report your results.. -kim -- w8hdkim at yahoo.com __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

1 0

Fwd: [Dovecot] Upgraded and authentication fails with LDAP
by Ren Galskap 15 Jan '05

15 Jan '05

Note: forwarded message attached. In addition to what I've already posted, the output from gdb when I try to use mutt is: Program received signal SIGABRT, Aborted. 0x18234dcf in kill () from /lib/libc.so.5 And then it dies. __________________________________ Do you Yahoo!? All your favorites on one personal page � Try My Yahoo! http://my.yahoo.com

6 12

[Dovecot] istream-limit.c - assertion failed
by Mail Admin 14 Jan '05

14 Jan '05

dovecot: Jan 14 12:25:49 Error: IMAP(xxxuser): file istream-limit.c: line 85 (_seek): assertion failed: (v_offset <= lstream->v_size) That error message is generated when squirrelmail 1.4.4-rc1 attempts to access this peculiar message partially quoted below. It doesn't happen (after copying the message to our testing account) accessing it through squirrelmail now. But it did. The server is running test61 configured --without-pop3d --with-ssl=openssl and --disable-ipv6 and running on FreeBSD 5.2.1. I'm not sure if this bit of a message is useful, but I have seen that error message in dovecot's log more than just this once. Thanks, Derek Message-id: <xxxmessageid> MIME-version: 1.0 Content-type: multipart/mixed; boundary=MS_Mac_OE_3188476518_1255852_MIME_Part User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --MS_Mac_OE_3188476518_1255852_MIME_Part Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable [bunch of readable text stuff here] --MS_Mac_OE_3188476518_1255852_MIME_Part Content-type: multipart/appledouble; boundary="MS_Mac_OE_3188476515_1257535_MIME_Part" --MS_Mac_OE_3188476515_1257535_MIME_Part Content-type: application/applefile; name="xxx.doc" Content-transfer-encoding: base64 Content-disposition: attachment [something short encoded here] --MS_Mac_OE_3188476515_1257535_MIME_Part Content-type: application/msword; name="xxx.doc"; x-mac-creator="4D535744"; x-mac-type="5738424E" Content-disposition: attachment Content-transfer-encoding: base64 [something big encoded here] --MS_Mac_OE_3188476515_1257535_MIME_Part-- --MS_Mac_OE_3188476518_1255852_MIME_Part--

1 0

RE: [Dovecot] Strange behavior of mysql 4.1.8/9 + dovecot1.0-test58~test61 on Fedora 3 x86_64 machine
by #LIU QI# 14 Jan '05

14 Jan '05

Some additional tests. I tried to add a test connection in the main.c under auth, which should be the main file of dovecot-auth. The test connection is done as the first statement in the int main() function. However, it still reports that the connection fails due to access denied. What should I do?? Any suggestions are welcomed. -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of #LIU QI# Sent: Friday, January 14, 2005 11:41 AM To: dovecot(a)dovecot.org Subject: [Dovecot] Strange behavior of mysql 4.1.8/9 + dovecot1.0-test58~test61 on Fedora 3 x86_64 machine I've built & configured the dovecot to use mysql as the passdb and userdb. However, dovecot-auth always claims that the username/password of mysql server is wrong (access denied by mysql server) during the connection. When I set the password to NULL, it can successfully connect to mysql server! I am 100% sure that I typed the correct password (by copy & paste), and I can successfully use this username/password connect to mysql server by mysqladmin and other mysql clients. I even wrote a C program which also successfully connects to mysql server. Furthermore, even I want to use pam_mysql in dovecot, the pam library also claims that it cannot connect to mysql server, but pam_mysql can be successfully used in postfix (exactly the same pam configuration, the same database, the same table, and the same username/password). Can anybody give me a hint why? Thank you very very very very much.... Crying for help....

1 0

[Dovecot] base dn and filter strings are concatenated
by Kazuo Moriwaka 14 Jan '05

14 Jan '05

Hello, When I set LDAP auth's search base dn, base dn and filter strings are concatenated. It cause filter cannot match any entries... I fixed it. Please check following patch. p.s. LDAP userdb/passdb's debug print have " fields=..." but it print junks. regards, -- Kazuo Moriwaka <moriwaka(a)valinux.co.jp> Index: src/auth/passdb-ldap.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/passdb-ldap.c,v retrieving revision 1.21 diff -r1.21 passdb-ldap.c 161a162 > str_free(str); 162a164 > str = t_str_new(512); 172c174 < conn->set.base, conn->set.scope, filter, --- > base, conn->set.scope, filter, Index: src/auth/userdb-ldap.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/userdb-ldap.c,v retrieving revision 1.25 diff -r1.25 userdb-ldap.c 174a175 > str_free(str); 175a177 > str = t_str_new(512); 187c189 < conn->set.base, conn->set.scope, filter, --- > base, conn->set.scope, filter,

1 0

[Dovecot] maildir and /var/spool/mail
by Steve Hickel 14 Jan '05

14 Jan '05

All, Not sure what to do next. Have imap working in that I can see messages in inbox. When I create a folder it won't create one. Looking at maillog shows that I don't have rights to folder /var/spool/mail/.sent or whatever folder I am trying to create. I have procmailrc and dovecot.conf point to /home/Maildir but for some reason something is tied to /var/spool/mail. Of course I am running FC3 and sendmail. Someone have any ideas as to what to try next? thanks in advance, Steve Hickel -- Steve Hickel <steve(a)korehicom.com> Kore/HiCom Corporation

6 8

[Dovecot] REQUEST: Different port(protocol) should be able to use a different certification.
by NAJIMA Hiroki 14 Jan '05

14 Jan '05

Hello, I want to use a different certificate for a different port(protocol). I searched http://wiki.dovecot.org/ and the mail archives. But such mechanism were not found. Could you implement a such mechanism? Or already implemented it, please teach how to do. I am assuming the following situations. MailAddress: [users](a)example.com SMTP Server: smtp.example.com POP3 Server: pop3.example.com IMAP Server: imap.example.com And pop3, imap, smtp are alias of real.example.com When use IMAPS, user connents imap.example.com POP3S, user connents pop3.example.com But one Certification file certificates only one FQDN. For example, dovecot.conf written that protocols = imaps pop3s ssl_cert_file = /etc/ssl/certs/imap.example.com.cert.pem ssl_key_file = /etc/ssl/private/imap.example.com.key.pem # imap.example.com.cert.pem's CN is imap.example.com In this pattern. MUA such as Thunderbird warn when connect pop3s because FQDN is different. I have an simple idea in this problem. dovecot.conf protocols = imaps pop3s - ssl_cert_file = /etc/ssl/certs/imap.example.com.cert.pem - ssl_key_file = /etc/ssl/private/imap.example.com.key.pem # certification for imaps + imaps_ssl_cert_file = /etc/ssl/certs/imap.example.com.cert.pem + imaps_ssl_key_file = /etc/ssl/private/imap.example.com.key.pem # certification for pop3s + pop3s_ssl_cert_file = /etc/ssl/certs/pop3.example.com.cert.pem + pop3s_ssl_key_file = /etc/ssl/private/pop3.example.com.key.pem Dovecot uses imaps_ssl_cert/key whenever MUA connects imaps port, uses pop3s_ssl_cert/key whenever MUA connected dovecot's pop3s port. Could you discuss it? #If it was already discussed, please show pointer(URL) that discussion. Regards. ----- NAJIMA Hiroki

2 2