- dovecot - dovecot.org

[Dovecot] Fatal: EOF while reading environment from master Error
by Phil Bettinson 11 Sep '05

11 Sep '05

Hello all! I guess it's a standard reason for joining a mailing list, but I have a problem. For some reason, whenever I try to start dovecot, be it from the xinet.d or from the commandline, I get this rather bizzare error. I can't even work out what it means, so I can't even begin to debug it. There is nothing extra in /var/log/messages, so I'm out of ideas. I've tried it with the default config, as well as with a config that I adjusted to fit the environment. I'm currently out of ideas. I did notice that there is a brief thread on this in the mailing-list archive, but it doesn't seem to point to a solution. Hopefully someone can help. I'm running it with the command /usr/local/libexec/dovecot/imap-login I am using the 1.0.alpha1 version, running on RedHat AS 3. thanks in advance. Phil System Administrator, National Library of Wales.

2 1

[Dovecot] Inbox weirdness
by Ignacio Vazquez-Abrams 11 Sep '05

11 Sep '05

I recently had a system crash and my inbox became inaccessible via IMAP. ls -ld /var/spool/mail drwxrwxr-x 2 root mail 4096 Sep 1 07:54 /var/spool/mail ls -l /var/spool/mail/ignacio -rw-rw---- 1 ignacio mail 7222021 Sep 1 07:54 /var/spool/mail/ignacio /usr/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE] Logged in as ignacio A142 SELECT INBOX imap(ignacio): Error: open(/var/mail/ignacio.lock) failed: Permission denied imap(ignacio): Error: file_lock_dotlock() failed with mbox file /var/mail/ignacio: Permission denied imap(ignacio): Error: open(/var/mail/ignacio.lock) failed: Permission denied imap(ignacio): Error: file_lock_dotlock() failed with mbox file /var/mail/ignacio: Permission denied A142 NO Internal error occured. Refer to server log for more information. [2005-09-01 08:00:34] rpm -q dovecot dovecot-(none):0.99.14-4.fc4.i386 System is running Fedora Core 4. SELinux is not a factor in the problem. http://fedora.ivazquez.net/private/dovecot.conf Thanks in advance for any help in resolving this issue. -- Ignacio Vazquez-Abrams

4 7

[Dovecot] Dovecot Errors - Using Debian
by Mark Smith 11 Sep '05

11 Sep '05

I recieve this error when trying to apt-get dovecot-common [Error Starts] apt-get install dovecot Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: dovecot-imapd dovecot-pop3d The following NEW packages will be installed: dovecot dovecot-imapd dovecot-pop3d 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0B/568kB of archives. After unpacking 1163kB of additional disk space will be used. Do you want to continue? [Y/n] Y Selecting previously deselected package dovecot-imapd. (Reading database ... 14230 files and directories currently installed.) Unpacking dovecot-imapd (from .../dovecot-imapd_0.99.14-1_i386.deb) ... Selecting previously deselected package dovecot-pop3d. Unpacking dovecot-pop3d (from .../dovecot-pop3d_0.99.14-1_i386.deb) ... Selecting previously deselected package dovecot. Unpacking dovecot (from .../dovecot_0.99.14-1_all.deb) ... Setting up dovecot-common (0.99.14-1) ... Creating generic self-signed certificate: /etc/ssl/certs/dovecot.pem (replace with hand-crafted or authorized one if needed). hostname: Unknown host dpkg: error processing dovecot-common (--configure): subprocess post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of dovecot-imapd: dovecot-imapd depends on dovecot-common (>= 0.99.12-1); however: Package dovecot-common is not configured yet. dpkg: error processing dovecot-imapd (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of dovecot-pop3d: dovecot-pop3d depends on dovecot-common (>= 0.99.12-1); however: Package dovecot-common is not configured yet. dpkg: error processing dovecot-pop3d (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of dovecot: dovecot depends on dovecot-imapd; however: Package dovecot-imapd is not configured yet. dovecot depends on dovecot-pop3d; however: Package dovecot-pop3d is not configured yet. dpkg: error processing dovecot (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: dovecot-common dovecot-imapd dovecot-pop3d dovecot E: Sub-process /usr/bin/dpkg returned an error code (1) [Error Ends] What Should I do?? I am Using Debian Sarge PLEASE HELP _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters

2 1

[Dovecot] "$default_mail_env/cur" not found with passwd-file authentication on v1.0-test80
by OpenMacNews 10 Sep '05

10 Sep '05

hi all, i've built dovecot: Sep 09 18:04:24 Info: Dovecot v1.0-test80 starting up on OSX 10.4.2. in addition to pgsql auth, which is working 4 me, i'd like to step-by-step verify simple passwd-file authentication/testing. unfortunately, i'm having a problem with the login process NOT FINDING the ".../cur" dir. here are the details .... my config includes: ... default_mail_env = maildir:/var/Data/Mail/%d/Accounts/%1u/%u/Maildir:INDEX=/var/Data/Mail/indexes/%d/%n ... auth default { mechanisms = plain userdb passwd-file {args = /var/Settings/Security/test_user_file} passdb passwd-file {args = /var/Settings/Security/test_user_file} ... } ... my 'test_user_file' has a test user "testuser(a)testdomain.com" with an appropriately CRYPT'd pwd % grep /var/Settings/Security/test_user_file testuser testuser@mydomain.com:XXXXXXXXXX:65001:65001:/var/Data/Mail/mydomain.com/Accounts/t/testuser/Maildir:::: when i login via telnet/shell, i get: % telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK IMAP ready x login testuser(a)mydomain.com testuser x OK Logged in. Connection closed by foreign host. and my log shows: dovecot: Sep 09 18:17:39 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGJsYWtlcnNAb3BlbmV4ZWMuY29tAGJsYWtlcnM= dovecot: Sep 09 18:17:39 Info: auth(default): client out: OK 1 user=testuser(a)mydomain.com dovecot: Sep 09 18:17:39 Info: auth(default): master in: REQUEST 1 1486 1 dovecot: Sep 09 18:17:39 Info: auth(default): master out: USER 1 testuser(a)mydomain.com uid=65001 gid=65001 home=/var/Data/Mail/mydomain.com/Accounts/t/testuser/Maildir dovecot: Sep 09 18:17:39 Info: imap-login: Login: user=<testuser(a)mydomain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): Effective uid=65001, gid=65001 dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): Namespace: type=private, prefix=Private/, sep=/, inbox=yes, hidden=no, subscriptions=no dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): maildir autodetect: stat($default_mail_env/cur) failed: No such file or directory dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): mbox autodetect: data=$default_mail_env dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): mbox autodetect: INBOX file: stat($default_mail_env) failed: No such file or directory dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): mbox autodetect: has .imap/: stat($default_mail_env/.imap) failed: No such file or directory dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): mbox autodetect: has inbox: stat($default_mail_env/inbox) failed: No such file or directory dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): mbox autodetect: has mbox: stat($default_mail_env/mbox) failed: No such file or directory dovecot: Sep 09 18:17:39 Error: imap(testuser(a)mydomain.com): Ambiguous mail location setting, don't know what to do with it: $default_mail_env (try prefixing it with mbox: or maildir:) dovecot: Sep 09 18:17:39 Error: imap(testuser(a)mydomain.com): Failed to create storage for 'Private/' with data: $default_mail_env dovecot: Sep 09 18:17:39 Error: child 1496 (imap) returned error 89 ignoring, for the moment the mbox 'complaints', and worrying first about the first: dovecot: Sep 09 18:17:39 Info: imap(testuser(a)mydomain.com): maildir autodetect: stat($default_mail_env/cur) failed: No such file or directory i'm a bit stymied .... if i understand correctly, that: autodetect: stat($default_mail_env/cur) is looking for: "/var/Data/Mail/mydomain.com/Accounts/t/testuser/Maildir/cur", which, on my system, exists: % ls -d /var/Data/Mail/mydomain.com/Accounts/t/testuser/Maildir/cur /var/Data/Mail/mydomain.com/Accounts/t/testuser/Maildir/cur as i've had all this working fine with pgsql authentication, i have this sneaking suspicion that i'm missing something obvious here. thoughts? suggestions? thx! richard

1 0

[Dovecot] Lot of crashing messages
by Matt Juszczak 09 Sep '05

09 Sep '05

Receiving a lot of the following messags with 1.0-76: pid 633 (dovecot-auth), uid 0: exited on signal 6 (core dumped) Any ideas? Sometimes, our entire port 110/143 servers begin refusing connections. Hardware checks out fine. Thanks in advance, Regards, Matt

3 3

[Dovecot] Dovecot-alpha1 and Thunderbird Sent problems
by Nicholas Young 09 Sep '05

09 Sep '05

I have dovecot 1.0alpha1 setup in a semi test environment running on Solaris 2.6. When using Thunderbird 1.0.6 from Windows occasionally the client will hang after sending a message and before copying it to the Sent folder on dovecot. Sendmail logs indicate that the message has been sent correctly. The mail directory is not shared over NFS. It is in maildir format. Restarting Thunderbird and sending exactly the same message will work. This seems to imply that it is not message dependant. Once the error has occured once it continues to occur until the client is restarted. We have file system quotas however they are very large for a very small amount of mail. The filesystem is about 80% free space and about 98% free inodes. I cannot replicate the issue under Linux using Thunderbird that is current for FC3. Some hacked version 1.0.2-1.3.3 Imap workarounds turned on under dovecot are outlook-idle for imap. The issue has not been seen under Outlook. Outlook is using a local Sent-Items folder instead of an Imap one however. The connection is running over SSL so I can not sniff the traffic on the wire, I have not tried using the rawlog settings yet. I plan to start this now, however the sporadic nature of the problem may delay useful information from here. The dovecot logs are not showing error messages, just: dovecot: Sep 09 09:24:35 Info: imap-login: Login: user=.... TLS Any suggestions on where to start would be great. This issue was not reported to me when running dovecot-1.0-stable-20050718. Thanks for any help/suggestions on where to go from here. -- Nich

3 3

[Dovecot] chdir() on NFS
by Ramón Macías Zamora 09 Sep '05

09 Sep '05

Hi Christian, my english is very bad excuseme for that. I see that you resolve the problem describe more ahead, how compile dovecot?, can you send by mail the binary? Thanks Saludos RMZ Icesa - Orve S. A. 2261000 ext 307 Sitio de interés para Linux: www.openecuador.com [Dovecot] chdir() on NFS Christian Andersen <mailto:dovecot%40dovecot.org?Subject=%5BDovecot%5D%20chdir%28%29%20on%20NFS &In-Reply-To=55579.129.241.163.43.1079702906.squirrel%40129.241.163.43> chrian at stud.ntnu.no Fri Mar 19 19:33:39 EET 2004 * Previous message: <http://dovecot.org/pipermail/dovecot/2004-March/003068.html> [Dovecot] chdir() on NFS * Next message: <http://dovecot.org/pipermail/dovecot/2004-March/003070.html> [Dovecot] chdir() on NFS * Messages sorted by: <http://dovecot.org/pipermail/dovecot/2004-March/date.html#3069> [ date ] <http://dovecot.org/pipermail/dovecot/2004-March/thread.html#3069> [ thread ] <http://dovecot.org/pipermail/dovecot/2004-March/subject.html#3069> [ subject ] <http://dovecot.org/pipermail/dovecot/2004-March/author.html#3069> [ author ] _____ Christian Andersen said: > > Hi, > I'm having problems accessing home directories though NFS. This setup uses > LDAP and Kerberos. Users defined on the local host work fine. This is what > dovecot writes in the logs while trying to log in as the user johndoe: > > ---- > Mar 19 14:10:54 jack dovecot-auth: nss_ldap: reconnecting to LDAP > server... > Mar 19 14:10:54 jack dovecot-auth: nss_ldap: reconnected to LDAP server > after 1 attempt(s) > Mar 19 14:10:54 jack imap-login: Login: johndoe [10.0.0.30] > Mar 19 14:10:54 jack dovecot: chdir(/home/johndoe) failed: Permission > denied > Mar 19 14:10:54 jack dovecot: child 3525 (imap) returned error 89 > ---- > > The authentication is OK, but dovecot fails to get access to the home > directory. What username does dovecot try to chdir() as? > > If I 'su' from to that user I have access to /home/johndoe, and a quick > test with Courier IMAP worked fine. Postfix has no problem delivering mail > in the users maildir using procmail. > > Some relevant config options: > > default_mail_env = maildir:~/mail:INDEX=/var/indexes/%n > auth_userdb = passwd > auth_passdb = pam > auth_user = root Problem solved, I guess... I recompiled from source and just replaced the dovecot binary in /usr/sbin. Trying to do 'rpmbuild -tb' and install the resulting rpm rendered everything unusable, but I guess that's just a matter of tweaking some options to 'configure'. What's the difference between the Fedora Core 1 version (0.99.10-6) and the latest stable version (0.99.10.4)? -- Christian Andersen <http://phuzz.org> _____ size=2 width="100%" align=center> * Previous message: <http://dovecot.org/pipermail/dovecot/2004-March/003068.html> [Dovecot] chdir() on NFS * Next message: <http://dovecot.org/pipermail/dovecot/2004-March/003070.html> [Dovecot] chdir() on NFS * Messages sorted by: <http://dovecot.org/pipermail/dovecot/2004-March/date.html#3069> [ date ] <http://dovecot.org/pipermail/dovecot/2004-March/thread.html#3069> [ thread ] <http://dovecot.org/pipermail/dovecot/2004-March/subject.html#3069> [ subject ] <http://dovecot.org/pipermail/dovecot/2004-March/author.html#3069> [ author ] _____ <http://dovecot.org/cgi-bin/mailman/listinfo/dovecot> More information about the dovecot mailing list

1 0

[Dovecot] help help
by g.digiambelardini＠fabaris.it 08 Sep '05

08 Sep '05

Hi, I have a dovecot IMAP server whit the Horde/Imp webmail. I know that this request is OT, but I need an help. I created for each user a SPAM folder, where dovecot put every email tagged "SPAM", but with IMP I can't make a list of folders to poll for new mail, I tried to dcofigure IMP like that: // list of folders to poll for new mail $_prefs['nav_poll'] = array( 'value' => 'a:1:{s:5:"INBOX";b:1;s:6:"INBOX.Test";b:1;}', //'value' => 'a:0:{}', //'value' => '', 'locked' => false, 'shared' => false, 'type' => 'implicit'); but it don't work...... SOMEONE CAM HELP ME??? Di Giambelardini Gabriele System/Network Administrator __________________________________________ FABARIS s.r.l. Cel. +39 3488504467 Tel. +39 0765 22181 - Fax +39 0765 410100 Via G. Mameli, 90 02047 Poggio Mirteto (RI) Viale dell'Università, 25 00185 Roma (RM) www.fabaris.it __________________________________________

1 0

Re: [Dovecot] help help
by Brett Parker 08 Sep '05

08 Sep '05

g.digiambelardini(a)fabaris.it <g.digiambelardini(a)fabaris.it> wrote: > > > Hi, I have a dovecot IMAP server whit the Horde/Imp webmail. > I know that this request is OT, but I need an help. > I created for each user a SPAM folder, where dovecot put every email tagged > "SPAM", but with IMP I can't make a list of folders to poll for new mail, I > tried to dcofigure IMP like that: > > // list of folders to poll for new mail > $_prefs['nav_poll'] = array( > 'value' => 'a:1:{s:5:"INBOX";b:1;s:6:"INBOX.Test";b:1;}', ^ should be 10 (number of chars in INBOX.Test). > //'value' => 'a:0:{}', > //'value' => '', > 'locked' => false, > 'shared' => false, > 'type' => 'implicit'); > > but it don't work...... > SOMEONE CAM HELP ME??? Hope that helps, -- Brett Parker web: http://www.sommitrealweird.co.uk/ email: iDunno(a)sommitrealweird.co.uk

1 0

[Dovecot] Ip addr + login name
by mike 08 Sep '05

08 Sep '05

Hi everybody, Is there a way to bind client ip address that connects to pop3 with the login name? For example if the client ip address is 192.168.2.40 then his login name is 'test' and he can log in with only that account name. I think it is possible to do it with an external authentication program. Thanks.

2 1

[Dovecot] More verbose logging of POP transactions?
by Philip Hallstrom 08 Sep '05

08 Sep '05

Hi all - I'm brand new to dovecot (0.99.14 on freebsd 5) and am just playing with it a bit. POP works just fine, but the only thing that shows up in my logs is this: Sep 7 11:46:25 freebsd5 pop3-login: Login: philip [10.28.61.200] Thought maybe syslog was quietly eating things, but told dovecot to use it's own log file and it didn't improve. Is there a way to turn on more detailed logging about what the user did? Along the lines of what uw-imap's pop gives you in terms of number of messages available, downloaded, deleted, etc.? I'm also interested in how much was transferred size wise... If I mised it in the conf file just let me know, but I didn't see anything... Thanks! -philip

2 1

[Dovecot] Dovecot - IMP - POP autentication problem
by Carlos Bergero 07 Sep '05

07 Sep '05

Hi, Recently I have to rush one of my mail servers to a new installation, actually GNU Linux/Debian Sarge, the system run dovecot 0.99.14 for pop and imap, and the web server, other machine, uses horde2/imp3. The problem is the following, pop clients including the imp3 cant log properly apparently, the even when a connection is made to pop3 dovecot trys to make a secure connection, I found this after sniffing the connection between the web server and the mail server, for some reason, imp cant handle it well and the some clients like OutLook also have troubles working this out. For now I work around this problem by disabling the ssl/tsl support, but that's not the solution I need. So the question is can I disable this feature without loosing the secure connection and how can I do it? Cheers, rak

1 0

[Dovecot] 1.0alpha1: new assert/core
by Jeff A. Earickson 07 Sep '05

07 Sep '05

Hi, I saw a new assert and core dump today in 1.0alpha1. Setup is Solaris 9, dovecot built with gcc 4.0.1, running as imap server for mbox format. The syslog said: IMAP(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) A gdb analysis of the core dump is attached. BTW, I save core dumps in case you need further debugging done for an assert. On another note, I have also had issues with dovecot locking up with "Too many open files" syslog error messages. Last night, after several hours of "too many open files" complaints, the master dovecot process just died -- no core dump and no complaint to syslog. Per advice of the list, I have doubled the rlim_fd_cur and rlim_fd_max kernel parameters and rebooted my imap server. I also saw in my syslog: Sep 6 16:48:53 emerald dovecot: [ID 956436 mail.error] pipe() failed: Too many open files Sep 6 16:48:53 emerald dovecot: [ID 257797 mail.crit] dup2(stderr) failed: Bad file number With students back, they have been giving dovecot a real hard workout. Jeff Earickson Colby College

1 0

Re: [Dovecot] dovecot/pop-before-smtp
by Lorens 07 Sep '05

07 Sep '05

On Tue, Sep 06, 2005 at 04:50:12PM -0700, Micah Stevens wrote: > Okay, just tried this. Doesn't work. I'm using 0.99 as packaged for RHEL 3. > Would that make a difference? Yes. The syntax changed. > login_executable = /usr/libexec/dovecot/popbsmtp.sh > /usr/libexec/dovecot/imap-login I'm fairly certain that login_executable is not the same thing as the mail_executable. > Starting IMAP daemon (dovecot): Fatal: Can't use login executable > /usr/libexec/dovecot/popbsmtp.sh /usr/libexec/dovecot/pop3-login: No such > file or directory Especially as the popbsmtp script should be launched for each login, and not at daemon start. In 1.0 there are two executables, mail_executable launched for logins, and (from memory) auth_executable launched at daemon start, so I suppose login_executable is the wrong one :-) I diagnose the error you get as meaning that the space is not ed separat out, and that dovecot tries to fork the executable named /usr/libexec/dovecot/popbsmtp.sh /usr/libexec/dovecot/pop3-login which obviously won't work. > Permissions are 777 on the popbsmtp.sh script. I double checked this. > > I tried to just copy the config as stated, but dovecot didn't parse it, > that's why I'm assuming it's for 1.x versions: Correct. Not good enough at 0.99 to say what the equivalent would be (I found that I needed 1.0 before I tried to do pbsmtp). > So I'm stuck, I also tried putting an insert statement on the user_query, > but that fails as Lorens mentioned. Problem with direct SQL is that I can't manage to make dovecot execute two SQL statements. If you're using a db with stored procedures you could maybe squeeze through that loophole, but your best bet is to find out what user_executable should be (maybe the same thing?) > Back to pop-before-smtp which doesn't work either, but it works better. :) :-) HTH

1 0

[Dovecot] 1.0-test75 and roadmap for v1.0
by Timo Sirainen 07 Sep '05

07 Sep '05

http://dovecot.org/test/ Keywords are finally stored in maildir filenames and listed in "dovecot-keywords" file. It should be possible to just rename 0.99.x's .customflags file to dovecot-keywords (but it can't be renamed back after modification). Also fixed another uid/sequence mixup bug with setting keywords in general (in mbox too). Fixed SHA1 checksum generation with big-endian machines (used only in passwords). I think I'll forget about the master/config rewrite for a while and leave it for Dovecot v2.0. That would mean the next release will be called 1.0-alpha1. After that there should be only bugfixes and some smaller features and optimizations left. I looked through my TODO and found the following missing features / optimizations that pretty much have to be done before v1.0. Anything important missing? - keywords: - add some limits to how many there can be - send FLAGS/PERMANENTFLAGS untagged replies when they change (required by IMAP RFC) - remove unused keywords from keyword list? (only when adding new ones) - mail cache file - cache _all_ headers that are marked to be cached when headers are being parsed, not just the ones client is requesting at that time. - compression should drop fields with last_used < (latest_mail_index_date - month) - when parsing mbox or saving message, parse the mail through index-mail so things gets saved into cache immediately - mbox - when we're updating flags with lazy writing, we're still parsing the mbox, just not writing to it! - always add empty line after mail. - make the parser require it too? syncing should make sure there always exists two LFs at end of file. raw-mbox-stream should make sure the last message ends with LF even if it doesn't exist in the file - COPY doesn't work to same mailbox (lock assert crash) - keep mbox lock for two extra seconds after sync to make sure we notice changes made by other mbox writer software - maildir - hardlink copying doesn't update indexes (does it even work?) - deliver needs quota integration somehow so it returns out-of-quota failure as fatal instead of temporary Probably after v1.0: - Full NFS support - Try to handle out-of-quota/disk space situations well

8 18

[Dovecot] 1.0.alpha1: Namespaces
by Wolfram Schlich 06 Sep '05

06 Sep '05

Hi, I'm currently using 1.0.alpha1 without luck regarding a namespace issue. Maybe it's a general understanding problem on my side, but let's see :-) I would like to have my mail stored in Maildir format below ~/.maildir/, which works fine so far. I want any (sub)folders to be created like this: ~/.maildir/ /cur /new /tmp /.Folder/ /cur /new /tmp /.Subfolder/ /cur /new /tmp BUT ;) Dovecot seems to disregard my namespace settings: --8<--[ /etc/dovecot.conf ]--8<-- default_mail_env = maildir:~/.maildir:INDEX=MEMORY namespace private { separator = / # prefix = # location = maildir:~/.maildir inbox = yes hidden = no } --8<-- Every new (sub)folder I create is stored as ~/.maildir/.Folder resp. ~/.maildir/.Folder.Subfolder in the filesystem. Are namespaces the right way? Is it possible at all? Thanks in advance. -- Wolfram Schlich

5 7

Re: [Dovecot] An alternate "dovecot-auth" daemon using cyrus-sasl
by Andrey Panin 06 Sep '05

06 Sep '05

On 249, 09 06, 2005 at 01:35:58PM +0400, Dmitry Butskoy wrote: > Andrey Panin wrote: > > >On 248, 09 05, 2005 at 03:48:19PM +0400, buc wrote: > > > > > >>We use dovecot in a heterogeneous environment (Windows/Linux desktops > >>and Linux servers). For unified authentication we use a sheaf > >>"Samba/Openldap" (i.e., Samba NT domain with openldap backend and > >>pam/nss_ldap for Linux). > >> > >> > >So why you can't use dovecot with openldap as passdb ? > > > Yes, now we use dovecot with pam, which uses openldap by pam_ldap etc... > But PAM can handle plain passwords only, therefore it is not suitable > for NTLM. > I have not found it in examples, but may be dovecot`s ntlm can take > appropriate password hashes from openldap directly? > (sambaLMPassword/sambaNTPassword) Yes, dovecot can handle LM/NTLM password hashes and it can fetch them from OpenLDAP directly (look at doc/dovecot-ldap.conf) In general you can store passwords in any supported form, just add proper password scheme prefix. For example: {NTLM}69943C5E63B4D2C104DBBCC15138B72B For more information read here: http://wiki.dovecot.org/Authentication > >>Windows users are authenticated well everywhere, but there is one old > >>issue. As "SPA" (NTLM) against NT domain is not supported by dovecot, it > >>is necessary to use default "plain" method. In addition to security > >>problems, it does also a problem of password unification. Each time a > >>user changes the password, he should do it one more time for the mail > >>program. > >> > >>I know that dovecot supports NTLM, however against local database only > >>(not for NT domain controller). In early versions support of cyrus-sasl > >>(which supports NTLM now) had been incorporated, however it like not > >>work and now is removed. > >>Fortunately, there is a possibility to substitute dovecot-auth > >>executable. Therefore I have tried to make an alternate variant of > >>dovecot-auth, which supports all that we need. > >> > >>For us, it seems to be more useful to create an auth daemon using > >>cyrus-sasl, rather than to add domain support to existing ntlm code. > >>First of all, it is easier for implementation. Besides it enables use of > >>all mechanisms supported by cyrus-sasl (present and future), including > >>GSSAPI. Anyway, it will be the useful additive to dovecot. > >> > >> > > > >Dovecot doesn't support cyrus-sasl for a good reason - it's a mess. > > > > > Certainly, I do not suggest to switch to use cyrus-sasl in upstream dovecot. > > But can give this patch the right to a life? Somewhere in "unofficial > patches"... > > >>I have made appropriate patches for both dovecot-1.0-stable and > >>dovecot-1.0.alpha1. > >>The idea is to copy "src/auth" to "src/auth-cyrus", strip all unneeded > >>from newly created directory and add cyrus-sasl support. The resulting > >>code probably looks not so elegantly as if it has been written > >>separately, however this way allows to not make a lot of things from the > >>scratch. > >> > >> > >>The patch against 1.0.alpha1 is > >>here: http://dmitry.butskoy.name/dovecot/dovecot-1.0.alpha1-cyrus.tar.gz . > >>To be more readable, it is not a flat patch (due to a lot of whole > >>files add/remove). It is a tarball with 3 files: a list of files to > >>initial copy from auth/ to auth-cyrus/, a patch for resulting tree, and > >>a script which automates this steps (:-)). (The script should be run in > >>the root of the main source, i.e. a dir with src/ and doc/ subdirs). > >> > >>I already have successfully tested this patch with PLAIN method. > >>However before testing of other methods, it would be desirable that > >>somebody have looked at it. > >> > >>Whether someone could check up my patch (just fluently having read), > >>at least for obvious bugs and typos? > >> > >> > > Dmitry Butskoy <Dmitry(a)Butskoy.name> > Saint-Petersburg, Russia > Red Hat Certified Engineer 809003662809495 > > -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

[Dovecot] upgrading: should I and what will change?
by Joshua Paine 06 Sep '05

06 Sep '05

I've been running dovecot 0.99.11 with postfix and postgresql in a production environment with about 25 real users and a couple hundred aliases split over a few domains for nearly a year now. No problems of any kind that I have noticed. Should I upgrade to the latest dovecot? What changes, if any, will I have to make? I've looked through the archives for a couple months without seeing much, and I don't see anything specific in the docs about upgrading. -Joshua <><

2 1

[Dovecot] Dovecot-LDA & OpenBSD
by Björn Ketelaars 06 Sep '05

06 Sep '05

Im having a bit of a problem with compiling dovecot-lda on OpenBSD. I used information from wiki.dovecot.org but this, unfortunately, resulted in some errors. Am I missing something? make all-recursive Making all in src Making all in libsieve if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/mnt/files/dovecot-1.0-test80/src/lib -I/mnt/files/dovecot-1.0-test80/src/lib-mail -I/mnt/files/dovecot-1.0-test80/src/lib-storage -I/mnt/files/dovecot-1.0-test80/src/lib-storage/index/mbox -DSYSCONFDIR=\""/usr/local/etc"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -MT deliver.o -MD -MP -MF ".deps/deliver.Tpo" -c -o deliver.o deliver.c; then mv -f ".deps/deliver.Tpo" ".deps/deliver.Po"; else rm -f ".deps/deliver.Tpo"; exit 1; fi In file included from common.h:4, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib/lib.h:6:22: config.h: No such file or directory In file included from /mnt/files/dovecot-1.0-test80/src/lib/lib.h:23, from common.h:4, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib/compat.h:17:4: #error uoff_t size not set In file included from /mnt/files/dovecot-1.0-test80/src/lib/lib.h:23, from common.h:4, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib/compat.h:37: error: conflicting types for `socklen_t' /usr/include/sys/types.h:95: error: previous declaration of `socklen_t' In file included from common.h:5, from deliver.c:5: /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:428: error: syntax error before "mail_get_virtual_size" /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:428: warning: type defaults to `int' in declaration of `mail_get_virtual_size' /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:428: warning: data definition has no type or storage class /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:431: error: syntax error before "mail_get_physical_size" /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:431: warning: type defaults to `int' in declaration of `mail_get_physical_size' /mnt/files/dovecot-1.0-test80/src/lib-storage/mail-storage.h:431: warning: data definition has no type or storage class In file included from deliver.c:13: /mnt/files/dovecot-1.0-test80/src/lib/istream.h:5: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:20: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:25: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:51: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/istream.h:54: error: syntax error before "uoff_t" In file included from deliver.c:15: /mnt/files/dovecot-1.0-test80/src/lib/ostream.h:7: error: syntax error before "uoff_t" /mnt/files/dovecot-1.0-test80/src/lib/ostream.h:57: error: syntax error before "uoff_t" *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1/src. *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1/src (line 384 of Makefile). *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1 (line 283 of Makefile). *** Error code 1 Stop in /mnt/files/dovecot-lda-0.1 (line 188 of Makefile). -- Insanity in individuals is something rare - but in groups, parties, nations and epochs, it is the rule.

1 0

[Dovecot] how to migrate from one server to another?
by Bram Mertens 06 Sep '05

06 Sep '05

Hi I have purchased and installed a new PC and would like to transfer my mail (in Maildir format) to it. Are there any precautions I must take before copying the mail over? I will disable mail delivery temporarily so no new mail gets written to disk but I don't know if dovecot has to be stopped before copying/editing mail for backup or migrating purposes. Anything else I must pay attention to? TIA Bram

2 2

[Dovecot] dovecot + openwebmail
by Peter McEvoy 05 Sep '05

05 Sep '05

Hi, I'm trying to add some sanity to a badly thought out mail system that, for various reasons, cant be fixed from the bottom up at this moment in time. The system is debian sarge, exim 4.5, doing virtual domains and delivering into mboxes in /var/spool/virtual/$domain/$user , there is webmail access and this allows user to create folders in (dont shoot me!) /etc/openwebmail/users/$domain/$username/mail/ , the files in this directory appear to be mboxes in that each mail begins with a From: line, the naming of these files is completely arbitrary. Im trying to add imap access that would ideally give users access to the mail in /var , and also in the openwebmail dirs, though the latter is not essential, just desirable. All mails are owned by user mail. I've installed dovecot-imapd version 0.99.14-1, but if this doesnt have the namespace additions from version 1.0-test, I can easily install that. Reading the wiki, it seems I can achieve this with namespaces, something like namespace private { separator = / inbox = yes prefix = location = mbox:/etc/openwebmail/users/%d/%u/mail:INBOX=/var/spool/virtual/%d/%u } But, Im not quite sure where this would go in the config file, going by the example config you can just shoehorn them into the middle of the file, but I'm not 100% sure... I had been trying to use things like.. default_mail_env = mbox:/var/folders/%d/%u:INBOX=/var/spool/virtual/%d/%u:INDEX=/var/indexes/%d/%n Having created the necessary folders in /var , but I didnt have much success (the authentication part worked straight away using my passwd file), And having read more and been told about namespaces on the irc channel, it seemed like I should go that way anyway. If anyone could give me a steer in the right direction, or even tell me i'm wasting my time (tho dont bother telling me how much better maildir etc is, i know!) Thanks for your time. -- Pete

1 1

[Dovecot] dovecot and communitgate (stalker)
by tyco 05 Sep '05

05 Sep '05

hi there, i am totally new to dovecot and use communigate pro stalker.com as my mailserver. everything in communigate is fine. the only problem i do have is imap speed. i just got a login at a dovecot server and i must say WOW its so fast amazing. since communigate does not support indexing on mdir direcotries i need to find a solution. so i am wondering if it would be possible to use dovecot imap server on top of communigate as an imap server? i know that this would not work for special cgp features like shared mailboxes. etc.... thnax christof

1 0

[Dovecot] Dovecot 1.0 and ldap; does this combination works?
by Vedran Furac 05 Sep '05

05 Sep '05

Hi! After upgrading from dovecot 0.9.14 to 1.0 crashes immediately after starting when using ldap as userdb and passdb. You can find more information here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320388 I'm confused with two users: login_user and auth_user. Witch of them has to be in ldap? If anyone here has a working dovecot+ldap configuration, could he show me his configuration? Regards Vedran

3 5

[Dovecot] Dovecot-LDA: Development questions
by Steffen Kaiser 05 Sep '05

05 Sep '05

Hello, I'm tinkering with Dovecot-LDA in order to achieve: + Better intergration into sendmail, and + tweaking its way to act on errors. Attached patch is a "brainstorming" like suggestion: a) when sendmail is dropping a message, it spawns the LDA, captures stderr/stdout and, if the LDA returns an exit code != 0, generates either a DSN or, when EX_TEMPFAIL, queues the mail. Hence, it is not necessary to have mail_send_rejection() to spawn another sendmail instance. The attached patch suggest to introduce an "operation_mode", in which Dovecot-LDA behaves differently for different environments. b) Some errors, like when spooling the message into the users folders fails, because the user is out of quota, one should prefer tempfailing the message, rather than a permanent error. Attached patch includes an option "-f", which has main() to return EX_TEMPFAIL. This is the way maildrop is acting, BTW. === Sendmail supports "account+detail" syntax out-of-the-box; that is for recipient matching only the portion left of the plus-sign is significant, the trailing portion may be used by the LDA as a hint to spool the message. Usually the information is passed via command line to the LDA. The libsieve seems to already support this notation, see tokens DETAIL, subaddress, :detail and the README file: Derrick Brashear (shadow+sieve@andrew...) Did somebody used or have some idea how to make use of the "+detail" stuff of libsieve? Basically the main problem in my opinion is what to query, because the information (final physical mailbox and/or owner) one can query is neither a header nor an envelope information (besides that the envelope information is not available to the LDA anyway). Consider a BCC to one recipient that expands to numerous maildrops, then the maildrop of actual delivery attempt can not be derived from neither the envelope nor the header information. The only way to integrate the +detail stuff into Dovecot-LDA seems to be when "keep" is performed (or no Sieve script is present). Then one could spool the message into folder "detail", if it already exists -- one should be allow other people to create mailboxes ;-) This is no action of the Sieve library, but of the LDA calling sieve. The Wiki mentions in the section about to setup exim: envelope_to_add What's this setting is doing? In src/sieve-cmu.c, static int getenvelope, there is: } else if (!strcasecmp(field, "to")) { *contents = m->temp; m->temp[0] = /*FIXME:msg_getrcptall(m, m->cur_rcpt)*/m->authuser; m->temp[1] = NULL; return SIEVE_OK; So it seems appropriate to tweak dovecot_sieve_run() into: mdata.authuser = username; mdata.recipient = detail_on_commandline ? concat(username, "+", detail_on_commandline) : username ; Or better: Have the complete recipient passed via command line option? and alter getenvelope(): m->temp[0] = m->recipient; I think this tweaks would be better than have the "-d" option support the plus-syntax. === Currently, the compiled Sieve script is placed into the same directory the script is located itself. How about to _always_ file the compiled script into [CONTROLDIR]/.dovecot.sievec? That would come over the problem with the system-wide default sieve script. Otherwise: The README mentions a test application and I found a sievec and sieved application (Sieve compile / decompiler) I presume. I can not just run "make sievec" to have it compile, does somebody played around with the Sieve stuff in LDA? Regards, -- Steffen Kaiser

1 0

Re: [Dovecot] qpopper UIDLs and migrating to dovecot/maildir
by Chris Wakelin 05 Sep '05

05 Sep '05

OK, here's the patch against dovecot-1.0-stable. (I just applied it to dovecot-stable-20050901. My version of stable has a few more patches applied, so I needed to apply the patch to a clean version!) Best Wishes, Chris grant beattie wrote: > On Sun, Sep 04, 2005 at 12:30:27AM +0100, Chris Wakelin wrote: > > >>Right! Here's a patch against dovecot-1.0.alpha1 which adds an extra option: >> >>pop3_reuse_xuidl = yes >> >>which if set will use the contents of the (first) X-UIDL header, if it >>exists, instead of the result of expanding pop3_uidl_format. It will use >>pop3_uidl_format if there is no X-UIDL header. >> >>This is typically for people migrating from Qpopper who don't want their >>users to get all the mail they've left on the server a second time, but >>should also work for any other POP server that happens to write X-UIDL >>headers, if any such exist ;) >> >>I've only done rudimentary testing, but it seems to work! I also have a >>version of the patch for dovecot-1.0-stable (which is what we'll be >>using next week!) if anybody's interested (only minor differences, use >>'mail->get_header(mail, "X-UIDL")' instead of >>'mail_get_first_header(ctx->mail, "X-UIDL")') > > > this is great stuff, thanks! > > I'm using the 1.0alpha1 diff and it seems to be working fine so far. > as we will probably be running 1.0 stable in production, would you > mind forwarding me the diff against 1.0 stable? > > this is an extremely useful feature, making it even easier to migrate > from alternate POP3 servers than Dovecot already is. :) > > grant. > -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 diff -ruN dovecot-1.0-stable.orig/src/master/mail-process.c dovecot-1.0-stable/src/master/mail-process.c --- dovecot-1.0-stable.orig/src/master/mail-process.c Tue Feb 8 10:30:11 2005 +++ dovecot-1.0-stable/src/master/mail-process.c Mon Sep 5 10:29:22 2005 @@ -220,6 +220,8 @@ env_put("FULL_FILESYSTEM_ACCESS=1"); if (set->pop3_no_flag_updates) env_put("POP3_NO_FLAG_UPDATES=1"); + if (set->pop3_reuse_xuidl) + env_put("POP3_REUSE_XUIDL=1"); if (set->mbox_dirty_syncs) env_put("MBOX_DIRTY_SYNCS=1"); if (set->mbox_very_dirty_syncs) diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.c dovecot-1.0-stable/src/master/master-settings.c --- dovecot-1.0-stable.orig/src/master/master-settings.c Sun Aug 7 14:00:41 2005 +++ dovecot-1.0-stable/src/master/master-settings.c Mon Sep 5 10:29:22 2005 @@ -125,6 +125,7 @@ /* pop3 */ DEF(SET_BOOL, pop3_no_flag_updates), DEF(SET_BOOL, pop3_enable_last), + DEF(SET_BOOL, pop3_reuse_xuidl), DEF(SET_STR, pop3_uidl_format), DEF(SET_STR, pop3_client_workarounds), @@ -297,6 +298,7 @@ /* pop3 */ MEMBER(pop3_no_flag_updates) FALSE, MEMBER(pop3_enable_last) FALSE, + MEMBER(pop3_reuse_xuidl) FALSE, MEMBER(pop3_uidl_format) "%v.%u", MEMBER(pop3_client_workarounds) NULL, diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.h dovecot-1.0-stable/src/master/master-settings.h --- dovecot-1.0-stable.orig/src/master/master-settings.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/master/master-settings.h Mon Sep 5 10:29:22 2005 @@ -96,6 +96,7 @@ /* pop3 */ int pop3_no_flag_updates; int pop3_enable_last; + int pop3_reuse_xuidl; const char *pop3_uidl_format; const char *pop3_client_workarounds; diff -ruN dovecot-1.0-stable.orig/src/pop3/commands.c dovecot-1.0-stable/src/pop3/commands.c --- dovecot-1.0-stable.orig/src/pop3/commands.c Sun May 8 10:45:32 2005 +++ dovecot-1.0-stable/src/pop3/commands.c Mon Sep 5 10:29:22 2005 @@ -489,6 +489,7 @@ struct var_expand_table *tab; struct mail *mail; string_t *str; + const char *xuidl; int ret, found = FALSE; tab = t_malloc(sizeof(static_tab)); @@ -532,7 +533,15 @@ str_truncate(str, 0); str_printfa(str, ctx->message == 0 ? "%u " : "+OK %u ", mail->seq); - var_expand(str, uidl_format, tab); + if (reuse_xuidl) { + xuidl=mail->get_header(mail, "X-UIDL"); + if (xuidl != NULL) + str_append(str, xuidl); + else + var_expand(str, uidl_format, tab); + } + else + var_expand(str, uidl_format, tab); ret = client_send_line(client, "%s", str_c(str)); t_pop(); diff -ruN dovecot-1.0-stable.orig/src/pop3/common.h dovecot-1.0-stable/src/pop3/common.h --- dovecot-1.0-stable.orig/src/pop3/common.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/pop3/common.h Mon Sep 5 10:29:22 2005 @@ -18,7 +18,7 @@ extern struct ioloop *ioloop; extern enum client_workarounds client_workarounds; -extern int enable_last_command, no_flag_updates; +extern int enable_last_command, no_flag_updates, reuse_xuidl; extern const char *uidl_format; extern enum uidl_keys uidl_keymask; diff -ruN dovecot-1.0-stable.orig/src/pop3/main.c dovecot-1.0-stable/src/pop3/main.c --- dovecot-1.0-stable.orig/src/pop3/main.c Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/pop3/main.c Mon Sep 5 10:29:22 2005 @@ -41,6 +41,7 @@ enum client_workarounds client_workarounds = 0; int enable_last_command = FALSE; int no_flag_updates = FALSE; +int reuse_xuidl = FALSE; const char *uidl_format; enum uidl_keys uidl_keymask; @@ -166,6 +167,7 @@ parse_workarounds(); enable_last_command = getenv("POP3_ENABLE_LAST") != NULL; no_flag_updates = getenv("POP3_NO_FLAG_UPDATES") != NULL; + reuse_xuidl = getenv("POP3_REUSE_XUIDL") != NULL; uidl_format = getenv("POP3_UIDL_FORMAT"); if (uidl_format == NULL)

1 0