- dovecot - dovecot.org

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