- dovecot - dovecot.org

Re: [Dovecot] I keep getting password mismatches
by Mark 18 Feb '07

18 Feb '07

i have that: #%PAM-1.0auth required pam_nologin.soauth include system-authaccount include system-authsession include system-auth[root@School-Mail ~]# and i`m still not able to login with a webmail ldap client ot with thunderbird (also ldap) the error messages are still the same. > Date: Thu, 15 Feb 2007 10:10:13 -0800> From: tengel(a)fluid.com> To: dovecot(a)dovecot.org> Subject: Re: [Dovecot] I keep getting password mismatches> > Mark wrote:> > > > auth(default): passwd(mark,127.0.0.1): password mismatch> > > > The strange thing is that i can login with ssh using my username and > > password but i can`t do anything related to dovecot..> > Do you have a PAM stack installed to allow your dovecot process access > to authentication? (/etc/pam.d/dovecot e.g.)> > http://wiki.dovecot.org/PasswordDatabase/PAM> > -te> > -- > Troy Engel | Systems Engineer> Fluid, Inc | http://www.fluid.com _________________________________________________________________ Probeer Live.com: je eigen persoonlijke opstartpagina met alleen de dingen die jij belangrijk vindt op één plek. http://www.live.com/getstarted

1 0

[Dovecot] [Fwd: wrong dovecot GID while upgrading]
by Zbigniew Szalbot 17 Feb '07

17 Feb '07

Sorry to have bothered - just read the updating file...! I should have let the upgrading process remove the dovecot user... Warm regards, ZS ---------------------------- Original Message ---------------------------- Subject: wrong dovecot GID while upgrading From: "Zbigniew Szalbot" <zbyszek(a)szalbot.homedns.org> Date: Sat, February 17, 2007 21:10 To: dovecot(a)dovecot.org -------------------------------------------------------------------------- Hello, I tried to upgrade dovecot from 1.0.rc7 to rc22 but I got this error at the end of the upgrade process: Dovecot has reserved the groupname 'dovecot' and gid '143': ERROR: groupname 'dovecot' already in use by gid '1003' Please resolve these issues and try again: Either remove the conflicting group or if you wish to continue using a legacy gr oup override DOVECOT_GID. *** Error code 1 Stop in /usr/ports/mail/dovecot. So I went to /usr/ports/mail/dovecot and edited the Makefile to change the GID into: DOVECOT_UID?= 1003 DOVECOT_GID?= 1003 SCRIPT_ENV+= DOVECOT_UID=${DOVECOT_UID} \ DOVECOT_GID=${DOVECOT_GID} I saved the makefile and ran portupgrade again but I got stopped by exactly the same error. I'd appreciate suggestions how to resolve this. Thank you! -- Zbigniew Szalbot -- Zbigniew Szalbot

1 0

[Dovecot] Dovecot "open files" (again?)
by falz 17 Feb '07

17 Feb '07

I'm a new dovecot user, just began using it last week. I switched from courier because my research showed that Dovecot did indexes, and allows me to store them anywhere I chose. I did this, and it fixed some severe disk IO issues that my server had. (25k horde only webmail install using imap proxy). I'm using quotas, and by default had it set to 'dirsize'. my postfix is already creating 'maildirsize' files, so I opted to change dovecot to use this instead. However, when I do, I run into the "too many open files" issue that's been reported many times on the list. I've seen a lot of mention of too many open files, but I haven't seen it related to the quota type used. It's possible that simply my using 'dirsize' as the quota type slows things down enough to not have the issue? I don't really know. Anyhow. I doubled my max open files in FreeBSD's /boot/loader.conf to: kern.maxfiles="24656", but to no avail. When I have it set to maildirsize, the open files on the system grows uncontrollably. Under normal use, it's somewhere below 5k: sysctl -a | grep openfiles kern.openfiles: 4415 I looked into the patch mentioned here: - http://www.dovecot.org/list/dovecot/2006-November/017536.html - http://dovecot.org/list/dovecot-cvs/2006-November/006776.html Those patches already appear to be in rc15, which I'm already running (Via FreeBSD's ports). I also applied the patch mentioned here awhile back: - http://www.dovecot.org/list/dovecot/2005-June/007647.html and rebuilt, but it didn't help out either. There are also freebsd specific notes on forcing a limit on dovecot itsself using login.conf, but that wouldnt really fix anything, it would just cause dovecot to not interfere with other running daemons. - http://www.mail-archive.com/ports@openbsd.org/msg08646.html Any thoughts? TSS, you mention a few times in these notes that you're unable to reproduce this. Perhaps try with the maildir as quota? More details about my setup: - FreeBSD 4.8 (yea, I know) - Imapproxy (http://www.imapproxy.org/) - Postfix to create maildir++ maildirsize folders - MySQL backend The work of this is spread out between several servers, dovecot is running on the server that's the final SMTP delivery location, and has local disks with the maildirs. --falz

2 5

[Dovecot] upgrade from 1.0rc7
by Zbigniew Szalbot 17 Feb '07

17 Feb '07

Hello, Have been to dovecot website but could not find information on what I need to check before I upgrade from the current 1.0rc7 which I am using on a FreeBSD 6.2 system. Will the old conf (virtual users, no ssl) file work with upgraded dovecot? Many thanks! -- Zbigniew Szalbot

2 1

Re: [Dovecot] Reply-To header
by Kenny Dail 17 Feb '07

17 Feb '07

> On Saturday 17 February 2007 00:13, Mark E. Mallett wrote: > > On Sat, Feb 17, 2007 at 12:33:40AM +0200, Timo Sirainen wrote: > > > On Fri, 2007-02-16 at 15:16 -0600, Richard Laager wrote: > > > > I see you've added a Reply-To header later. The canonical response in > > > > this case is for someone to reference: > > > > http://www.unicom.com/pw/reply-to-harmful.html > > > > A canonical response to that is > > > > http://www.metasystema.net/essays/reply-to.mhtml > > My mind was not changed, sorry. First, RFC 822 is obsolete, and RFC 2822 does > not contain the quoted paragraph. Instead it says that '[w]hen > the "Reply-To:" field is present, it indicates the mailbox(es) to which the > author of the message suggests that replies be sent.' - the author, not the > mailing list software. There are other fields for that. Fortunately Dovecot's set-up, does make it the author's choice. -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] Problem/workaround with X-Keywords and Apple's Mail.app
by Joey Coleman 17 Feb '07

17 Feb '07

Hello, I've just switched from UW-IMAP to Dovecot, and for the most part, things are good. However, I encountered the problem with the X-Keywords header not being written back into individual messages in an mbox file (originally described in [1], and Timo gave a clue as to maybe why in [2]). What was happening for me is that Apple's Mail.app would flag a message as spam, which happily sets a couple keywords in the message, but those weren't being written back (at least, I didn't see them in the file on the server). The "DO NOT DELETE..." message had a perfectly fine X-IMAP header, and up until I switched things were working great. The user visible symptom of this happened every time new spam arrived in my Junk folder [3] --- the new spam would arrive, be flagged as spam by Mail.app, and the earlier pieces of mail would promptly be unflagged! Anyway, Timo's clue in [2] prompted me to turn off both mbox_lazy_writes and mbox_dirty_syncs (the latter just on the off- chance... it's a low-volume server, so I can deal with the inefficiency). Lo and behold, Mail.app started acting sane again *and* the X-Keywords header appeared immediately. Oddly, during all of this, the Status and X-UID keywords would appear in the messages just fine; no clue as to why those and not X- Keywords. Version details are: - Dovecot 1.0rc13 [4] - FreeBSD 5.3-RELEASE - Apple Mail.app 2.1 (752/752.2) cheers, --joey [1] http://dovecot.org/list/dovecot/2006-March/011872.html [2] http://dovecot.org/list/dovecot/2006-June/014126.html [3] And it felt really strange while troubleshooting this as I found myself *hoping* for another piece of spam to arrive. Bleh. [4] Yes, two versions behind current, but in my defense, I did check the announcements and they didn't seem to mention the problem.

2 1

[Dovecot] DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
by Gerhard Wiesinger 17 Feb '07

17 Feb '07

Hello! I see the internal message from pine with the following subject (mbox format, dovecot 1.0rc22): DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA As far as I know this message should be filtered. I never saw this before in previous 1.0 betas and 1.0rc (nearly every version tested). Any ideas Timo? Ciao, Gerhard -- http://www.wiesinger.com/

3 3

[Dovecot] Going nuts
by Mário Gamito 17 Feb '07

17 Feb '07

Hi, The subject says it all. For two days i've been trying to get IMAP and IMAPS working and nothing. I'm running CentOS 4.4 with qmail-ldap I just can't login in dovecot. Following my signature is some info. You can find my dovecot.conf at http://www.gamito.org/dovecot.conf I'm about to give up :( Any help would be appreciated. Warm Regards, Mário Gamito --------------------------------------------------------------------- [root@mail login]# telnet mail.sincity.lan 143 Trying 192.168.5.129... Connected to mail.sincity.lan (192.168.5.129). Escape character is '^]'. * OK Dovecot ready. O LOGIN gamito(a)mail.sincity.lan 143 O NO Temporary authentication failure. O LOGOUT * BYE Logging out O OK Logout completed. Connection closed by foreign host. -------------------------------------------------- [root@mail login]# tail /var/log/dovecot/dovecot.log dovecot: Feb 17 00:01:02 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=192.168.5.129 rip=192.168.5.129 resp=<hidden> dovecot: Feb 17 00:01:02 Info: auth(default): checkpassword(gamito(a)mail.sincity.lan,192.168.5.129): Executed: /usr/local/bin/auth_imap /usr/local/libexec/dovecot/checkpassword-reply dovecot: Feb 17 00:01:02 Info: auth(default): checkpassword(gamito(a)mail.sincity.lan,192.168.5.129): Received no input dovecot: Feb 17 00:01:02 Error: auth(default): checkpassword: Child 31122 died with signal 11 dovecot: Feb 17 00:01:04 Info: auth(default): client out: FAIL 1 user=gamito(a)mail.sincity.lan temp dovecot: Feb 17 00:01:10 Info: imap-login: Aborted login: user=<gamito(a)mail.sincity.lan>, method=PLAIN, rip=192.168.5.129, lip=192.168.5.129, secured -------------------------------------------------------------------------

3 10

[Dovecot] again... cross compiling
by Martin Höfling 17 Feb '07

17 Feb '07

> Create a cache file with the right values, or call configure with those > values set in the environment. OK, i ran configure with -C one time without cross compiler env set, to obtain the variables another time with -C to use the config.cache . I could not find anything related to the check whether size_t is signed. I found a variable which i set that way: ignored_signed_size=${ignore_signed_size=1} What's wrong with that? Cheers Martin P.S.: Is there a way to obtain all variables in an easy way, or to obtain the variable that has to be set by hand? -- Frag' nicht - Du könntest eine Antwort erhalten. (Markus Mehring in d.a.arnooo)

3 2

Re: [Dovecot] Reply-To header
by Kenny Dail 17 Feb '07

17 Feb '07

> On Fri, 2007-02-16 at 15:16 -0600, Richard Laager wrote: > > I see you've added a Reply-To header later. The canonical response in > > this case is for someone to reference: > > http://www.unicom.com/pw/reply-to-harmful.html > > Yes, I've read that page. It says basically that it makes replying > privately to the sender difficult. I'm sure it does, but in this list I > don't think pretty much anyone ever wants to reply to someone only > privately. Since deliberate choice is required to go in and set the maillist option, this is no different than if I configure my MUA to set the reply-to header on messages I send to the list. So the way it has been implemented for this list is not a problem at all. If people feel the need to reply to me off list, I feel that should be a deliberate choice on their part. -- Kenny Dail <kend(a)amigo.net>

1 0