[Dovecot] Wrong UIDs returned from mailbox_transaction_commit_get_uids()
Hi,
Wrong UIDs are returned from mailbox_transaction_commit_get_uids() in
dovecot-1.1.rc3.
The problem is in:
int mailbox_transaction_commit(struct mailbox_transaction_context **t)
{
uint32_t tmp;
return mailbox_transaction_commit_get_uids(t, tmp, tmp, tmp);
}
It should be:
int mailbox_transaction_commit(struct mailbox_transaction_context **t)
{
uint32_t tmp1, tmp2, tmp3;
return mailbox_transaction_commit_get_uids(t, tmp1, tmp2, tmp3);
}
After this fix it works OK.
Thanks,
Ron
You rock. That's why Blockbuster's offering you one month of Blockbuster Total
Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
Hi, El Martes, 1 de Abril de 2008 a las 04:14, Bill Cole escribió: That's a question about the competence of the people maintaining that repository. Presumably these would be the people who blessed a pre-release version of Dovecot almost 18 months ago, in a period when such versions were being released every few days *due to bugs*, and who have not updated their build at any time since. It seems to me that these are not people who should be tasked or trusted with being the gatekeepers of software deployment, as that seems to be demonstrably beyond their competence. RedHat (and CentOS) has his own policy about releases, and more or less it is: no update will break a working instalation. So they try to port any security patches to their running versions -and this is a lot of work, they have their own forked version of almost any package!-, but almost never add any new funcionality. This policy has one great point: it's easy to understand, and it gives few surprises. And this is great most of the times. Pre-1.0 Dovecot is the kind of software that doesn't fit well in that policy: a lot of changes, and no standard stable version. So they chose one version -1.0rc15 in this case-, because their other option was not including dovecot. That's exactly why I'm compiling dovecot from source, but I usually like the default policy. Aagur. -- Joseba Torre. CIDIR Bizkaia. signature.asc Description: This is a digitally signed message part.
[Dovecot] Confusion of Sieve filter scripts and the file separator. (Amatuer Siever)
Hello, I have just been playing around with sieve filters to split up all my incoming mail into the correct directories. I have created some subdirectories to put mailing list emails in and just want to check if my thinking is correct. I am using namespaces with the '/' character as the separator. When creating the fileinto line on my sieve scripts I thought I would have to use the '/' character to separate the folders (as horde mail also does), but that doesn't work (and produces a Invalid folder error) instead I must use the '.' character. I am using the dovecot deliver module and managesieve for my sieve stuff (dovecot 1.0.13). I am just wondering if this is the correct behaviour or if it is a bug of sorts. Cheers. From, Jack
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
On Mon, 2008-03-31 at 15:10 -0500, Chris Richards wrote: Dovecot is version 1.0.rc15 I agree with others that it would be a good idea to upgrade from rc15, but.. Mar 31 14:00:58 myserver dovecot: IMAP(me): Maildir /home/me/.Maildir sync: UID inserted in the middle of mailbox (85953 85053, file = msg.XL7B:2,) This is a procmail configuration problem: http://wiki.dovecot.org/MailboxFormat/Maildir#procmail signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Segfault with soft disk quota
On Mon, 2008-03-31 at 14:30 -0400, Tim Boyer wrote: RHEL 5.1, dovecot 1.0.rc15 on a x86 system. dovecot -n says .. Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): open(/home/bfarner/Mail/.imap/INBOX/.temp.dg.denmantire.com.4668.564b08eac94 4fe4a) failed: Disk quota exceeded File creation failed with EDQUOT. I fixed a lot of these just before the v1.0.0 release. Strange thing is - he's over disk quota, but just over the soft quota - nowhere close to the hard quota. Kernel decided that he was over quota, for whatever reason and failed the syscall. (I don't know how exactly the soft/hard quota rules work) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
Joseba Torre wrote: Hi, El Martes, 1 de Abril de 2008 a las 04:14, Bill Cole escribió: That's a question about the competence of the people maintaining that repository. Presumably these would be the people who blessed a pre-release version of Dovecot almost 18 months ago, in a period when such versions were being released every few days *due to bugs*, and who have not updated their build at any time since. It seems to me that these are not people who should be tasked or trusted with being the gatekeepers of software deployment, as that seems to be demonstrably beyond their competence. RedHat (and CentOS) has his own policy about releases, and more or less it is: no update will break a working instalation. So they try to port any security patches to their running versions -and this is a lot of work, they have their own forked version of almost any package!-, but almost never add any new funcionality. This policy has one great point: it's easy to understand, and it gives few surprises. And this is great most of the times. Pre-1.0 Dovecot is the kind of software that doesn't fit well in that policy: a lot of changes, and no standard stable version. So they chose one version -1.0rc15 in this case-, because their other option was not including dovecot. That's exactly why I'm compiling dovecot from source, but I usually like the default policy. Aagur. I guess it will drawn groans, but this is largely the reason that I chose Gentoo for my server distros. Roughly speaking with most main distros you get a stuck in stone set of packages + bug fixes for those packages each week. This causes few surprises, but it means that if you need some new feature you are immediately into compiling from source. Additionally big version upgrades seem to be approximately once a year and it appears in most cases this is a take the server down, upgrade it, bring it up and check the configs kind of process (ie fairly major) Gentoo goes the other way - everything remains permanently unstable (if you want to think in those terms). Every time you upgrade you get the latest and greatest versions... There is a package masking process so that there isn't too much suprise with stuff breaking and local patches are applied to keep upgrades as simple as possible. This falls somewhere between a Redhat weekly upgrade kind of stability and a redhat operating system version upgrade experience - ie I wouldn't trust it to run unattended every sunday without someone watching it, yet on the other hand I can take a year old server and upgrade all the software on it to latest stable in an hour without (usually) taking it down. Pays your money and takes your choice I guess... Suits my needs though (I often need new features and up to date software) Ed W
Re: [Dovecot] [PATCH] deliver tries to compile already compiled sieve script
Hello,
I've solved it. The compiled sieve script had the same mtime as the
uncompiled script. Dovecot used to see if compilation is needed. It
has to be =.
If you wonder why the mtime is the same, I write and compile the sieve
script right after each other automated. Apparently mtime doesn't have a
good resolution in time...
Patch to dovecot-sieve-1.1.4 is attached, can it be included?
Thanks,
Alexander
Alexander Prinsier wrote:
I should have mentioned I'm running dovecot 1.1.rc3
Alexander
Alexander Prinsier wrote:
Hello,
I'm trying to setup dovecot with sieve support in a way where all sieve
scripts are precompiled. All sieve scripts are in /var/cache/sieve/.
I believe I discovered a bug here. I describe below how to reproduce it.
Dovecot and the user that deliver runs as do not have write permission
in /var/cache/sieve/.
h01:/var/cache/sieve# ls -la
total 16
drwxr-xr-x 2 ecp ecp 4096 Mar 31 21:32 .
drwxr-xr-x 10 root root 4096 Mar 31 20:14 ..
-rw-r--r-- 1 ecp ecp88 Mar 31 21:32 [EMAIL PROTECTED]
-rw-r--r-- 1 ecp ecp 132 Mar 31 21:32 [EMAIL PROTECTED]
When deliver runs it logs this error:
open(/var/cache/sieve/[EMAIL PROTECTED]) failed:
Permission denied
This indicates deliver tries to compile the script, even though the
compiled version already is there.
To verify I tested another case. I make the compiled script immutable
and I did a chmod 777 on /var/cache/sieve/. Then deliver logs this error:
rename(/var/cache/sieve/[EMAIL PROTECTED],
/var/cache/sieve/[EMAIL PROTECTED]) failed: Operation not
permitted
And deliver created the file [EMAIL PROTECTED]
Some relevant pieces of my dovecot.conf:
protocol lda {
mail_plugins = quota cmusieve
...
}
plugin {
sieve = /var/cache/sieve/%u.sieve
}
Anyone can help me? Is this an error on my end, or really a bug?
Alexander
--- dovecot-sieve-1.1.4.orig/src/sieve-cmu.c2008-02-16 19:24:51.0
+0100
+++ dovecot-sieve-1.1.4/src/sieve-cmu.c 2008-04-01 11:30:24.0 +0200
@@ -869,7 +869,7 @@ dovecot_sieve_compile(script_data_t *sda
return -1;
}
} else {
- if (st.st_mtime st2.st_mtime)
+ if (st.st_mtime = st2.st_mtime)
return 1;
}
[Dovecot] Segfault with soft disk quota
RHEL 5.1, dovecot 1.0.rc15 on a x86 system. dovecot -n says [EMAIL PROTECTED] mail]# dovecot -n # /etc/dovecot.conf protocols: pop3 pop3s login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login login_process_size: 64 first_valid_uid: 100 mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd I had one user whose Outlook kept giving disconnection problems. I looked at the logs, and found this: Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): open(/home/bfarner/Mail/.imap/INBOX/.temp.dg.denmantire.com.4668.564b08eac94 4fe4a) failed: Disk quota exceeded Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): Fixed index file /home/bfarner/Mail/.imap/INBOX/dovecot.index: log file sync pos 2,115528 - 3, 24 Mar 31 14:05:31 dg.denmantire.com dovecot: POP3(bfarner): Fixed index file /home/bfarner/Mail/.imap/INBOX/dovecot.index: messages_count 3 - 0 Mar 31 14:05:31 dg.denmantire.com dovecot: pop3-login: Login: user=bfarner, method=PLAIN, rip=192.168.0.37, lip=192.168.0.2 Mar 31 14:05:31 dg.denmantire.com pop3[4668]: segfault at rip 004452e8 rsp 7fff56ccd460 error 4 Mar 31 14:05:31 dg.denmantire.com dovecot: child 4668 (pop3) killed with signal 11 Strange thing is - he's over disk quota, but just over the soft quota - nowhere close to the hard quota. Easy for me to fix, but I figured I'd also submit it as a bug. I don't follow the list so if you need any more info, please copy my email on the reply. Thanks... -- Tim Boyer Chief Technology Officer Denman Tire Corporation
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
On 4/1/2008, Ed W ([EMAIL PROTECTED]) wrote: I guess it will drawn groans, but this is largely the reason that I chose Gentoo for my server distros. No groan here... I love the flexibility Gentoo gives... you can easily leave the primary system at 'stable', then just set certain packages to unstable for the latest/greatest. My servers have been running nonstop for over 3 years, with just a few minor hiccups now and then that are quickly resolved by digging through logs and/or hitting google and/or the forums... To be fair, most distros *do* have the ability to use extra 'unstable' repos, at least for most major packages, and if I wasn't using Gentoo, I would at *least* be using those... -- Best regards, Charles
Re: [Dovecot] Wrong UIDs returned from mailbox_transaction_commit_get_uids()
It should be:
int mailbox_transaction_commit(struct mailbox_transaction_context **t)
{
uint32_t tmp1, tmp2, tmp3;
return mailbox_transaction_commit_get_uids(t, tmp1, tmp2, tmp3);
}
How/where does this help? The tmp values are ignored in any case, so I
don't think this is the right fix for it.
The problem occurs if transaction_commit() is hooked.
In mail_log plugin I wanted to print the committed UIDs. I changed
mail_log_transaction_commit()
to:
{
...
ret = lbox-super.transaction_commit(t, uid_validity_r,
first_saved_uid_r,
last_saved_uid_r);
if (0 == ret) {
i_info(uid_validity=%u, first_uid=%u, last_uid=%u,
*uid_validity_r, *first_saved_uid_r, *last_saved_uid_r);
}
return ret;
}
the result was:
Apr 1 14:59:37 ha-test1 deliver([EMAIL PROTECTED]): uid_validity=1202218363,
first_uid=1202218363, last_uid=1202218363
These values are equal to the UID validity.
After changing mailbox_transaction_commit() as described above, I got correct
values:
Apr 1 15:09:50 ha-test1 deliver([EMAIL PROTECTED]): uid_validity=1202218363,
first_uid=139, last_uid=139
Ron
You rock. That's why Blockbuster's offering you one month of Blockbuster Total
Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com
Re: [Dovecot] [PATCH] deliver tries to compile already compiled sieve script
On Tue, 2008-04-01 at 11:50 +0200, Alexander Prinsier wrote: Hello, I've solved it. The compiled sieve script had the same mtime as the uncompiled script. Dovecot used to see if compilation is needed. It has to be =. If you wonder why the mtime is the same, I write and compile the sieve script right after each other automated. Apparently mtime doesn't have a good resolution in time... Patch to dovecot-sieve-1.1.4 is attached, can it be included? Committed. signature.asc Description: This is a digitally signed message part
[Dovecot] FreeBSD port: port's patch for 1.1rc3
For those who wants testing 1.1rc3 on FreeBSD, this is a simple patch
against /usr/ports/mail/dovecot.
To apply:
# cd /usr/ports/mail/dovecot
# patch -p1 /tmp/patch_dovecot_1.0.13-1.1.rc3.diff
Hope I did not forget something important... This is an adaptation of
the existing port.
PS: for port's maintainer: Which way will take 1.0 vs 1.1 upgrade ? a
new mail/dovecot10 port or ?
Hope this helps
--
Geoffroy Desvernay
diff -bruN dovecot-1.0.13/Makefile dovecot/Makefile
--- dovecot-1.0.13/Makefile 2008-04-01 14:41:12.0 +0200
+++ dovecot/Makefile2008-04-01 14:29:33.0 +0200
@@ -7,9 +7,9 @@
#
PORTNAME= dovecot
-DISTVERSION= 1.0.13
+DISTVERSION= 1.1.rc3
CATEGORIES=mail ipv6
-MASTER_SITES= http://www.dovecot.org/releases/1.0/
+MASTER_SITES= http://www.dovecot.org/releases/1.1/rc/
MAINTAINER=[EMAIL PROTECTED]
COMMENT= Secure and compact IMAP and POP3 servers
diff -bruN dovecot-1.0.13/distinfo dovecot/distinfo
--- dovecot-1.0.13/distinfo 2008-04-01 14:41:12.0 +0200
+++ dovecot/distinfo2008-04-01 14:43:56.0 +0200
@@ -1,3 +1,3 @@
-MD5 (dovecot-1.0.13.tar.gz) = 281bd9dee8d6c1674977257acc80ce64
-SHA256 (dovecot-1.0.13.tar.gz) =
16da29b2bc08d0178a09323bf0787a2a0e953075655566a7b4b6b148c87ac25f
-SIZE (dovecot-1.0.13.tar.gz) = 1774025
+MD5 (dovecot-1.1.rc3.tar.gz) = eed10a2f5142ebdf88276c0a82f548e1
+SHA256 (dovecot-1.1.rc3.tar.gz) =
5a72318a6f4d12a1da7104de94b439a8523142c0f54af1f1ff64966820ef9460
+SIZE (dovecot-1.1.rc3.tar.gz) = 329
diff -bruN dovecot-1.0.13/files/patch-dovecot-example.conf
dovecot/files/patch-dovecot-example.conf
--- dovecot-1.0.13/files/patch-dovecot-example.conf 2008-04-01
14:41:12.0 +0200
+++ dovecot/files/patch-dovecot-example.conf2008-04-01 14:38:52.0
+0200
@@ -1,5 +1,5 @@
dovecot-example.conf.orig 2008-03-04 05:48:12.0 +
-+++ dovecot-example.conf 2008-03-05 22:49:08.554336095 +
+--- dovecot-example.conf.orig 2008-04-01 14:30:50.0 +0200
dovecot-example.conf 2008-04-01 14:38:28.0 +0200
@@ -12,7 +12,7 @@
# Default values are shown for each setting, it's not required to uncomment
# any of the lines. Exception to this are paths, they're just examples with
@@ -15,9 +15,9 @@
#protocols = imap imaps
+protocols = %%PROTOCOLS%%
- # IP or host address where to listen in for connections. It's not currently
- # possible to specify multiple addresses. * listens in all IPv4 interfaces.
-@@ -210,6 +212,7 @@
+ # A space separated list of IP or host addresses where to listen in for
+ # connections. * listens in all IPv4 interfaces. [::] listens in all IPv6
+@@ -213,6 +214,7 @@
# doc/wiki/MailLocation.txt
#
#mail_location =
@@ -25,7 +25,7 @@
# If you need to set multiple mailbox locations or want to change default
# namespace settings, you can do it by defining namespace sections.
-@@ -256,6 +259,7 @@
+@@ -273,6 +275,7 @@
# used only for creating mbox dotlock files when creation fails for INBOX.
# Typically this is set to mail to give access to /var/mail.
#mail_privileged_group =
@@ -33,7 +33,7 @@
# Grant access to these supplementary groups for mail processes. Typically
# these are used to set up access to shared mailboxes. Note that it may be
-@@ -320,6 +324,7 @@
+@@ -339,6 +342,7 @@
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = no
@@ -41,7 +41,7 @@
# Valid UID range for users, defaults to 500 and above. This is mostly
# to make sure that users can't log in as daemons or other system users.
-@@ -333,6 +338,7 @@
+@@ -352,6 +356,7 @@
# belongs to supplementary groups with non-valid GIDs, those groups are
# not set.
#first_valid_gid = 1
@@ -49,7 +49,7 @@
#last_valid_gid = 0
# Maximum number of running mail processes. When this limit is reached,
-@@ -506,19 +512,19 @@
+@@ -501,19 +506,19 @@
protocol imap {
# Login executable location.
@@ -73,7 +73,7 @@
# Maximum IMAP command line length in bytes. Some clients generate very long
# command lines with huge mailboxes, so you may need to raise this if you
get
-@@ -528,7 +534,7 @@
+@@ -527,7 +532,7 @@
# Support for dynamically loadable plugins. mail_plugins is a space
separated
# list of plugins to load.
#mail_plugins =
@@ -82,15 +82,15 @@
# Send IMAP capabilities in greeting message. This makes it unnecessary for
# clients to request it with CAPABILITY command, so it saves one round-trip.
-@@ -563,6 +569,7 @@
+@@ -562,6 +567,7 @@
# accept '/' suffix in mailbox names in subscriptions list.
# The list is space-separated.
- #imap_client_workarounds = outlook-idle
-+ imap_client_workarounds = delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
+ #imap_client_workarounds =
++ imap_client_workarounds = delay-newmail netscape-eoh tb-extra-mailbox-sep
Re: [Dovecot] FreeBSD port: port's patch for 1.1rc3
Geoffroy Desvernay wrote: For those who wants testing 1.1rc3 on FreeBSD, this is a simple patch against /usr/ports/mail/dovecot. To apply: # cd /usr/ports/mail/dovecot # patch -p1 /tmp/patch_dovecot_1.0.13-1.1.rc3.diff Hope I did not forget something important... This is an adaptation of the existing port. PS: for port's maintainer: Which way will take 1.0 vs 1.1 upgrade ? a new mail/dovecot10 port or ? Hope this helps -- Geoffroy Desvernay I'm not the maintainer but I've also made a dovecot port for 1.1 as a separate port since it is still in development and may require a few config changes, I discussed that with the maintainers. I made it for work purposes and I have been keeping up with necessary changes to keep it working while I use 1.1, and intended to submit it for inclusion in the ports collection but haven't got around to it yet (I'd like to add a few compile options for new things since 1.1). Been really busy at work and haven't had time, but I guess if people show they are interested I could try to speed that up.
[Dovecot] Unknown internal error
Hello, I just found this message in our dovecot logfiles: Disconnected: BUG: Unknown internal error Should I worry about this ? There are no complaints yet (although it is not limited to one user). It seems to occur with different clients (Apple/MacOS mail, Windows/Thunderbird, Pine). We're running dovecot 1.0.10 on Solaris 10 with mboxes (NFS) and local index storage. There are no such messages before the upgrade (from version 1.0.5). Regards. Martin --- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 [EMAIL PROTECTED] fax: ++49 761 203-8242www.informatik.uni-freiburg.de
[Dovecot] v1.1.rc4 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz.sig I didn't have time/energy to fix everything I wanted, so it'll probably be a few more RCs left until v1.1.0. This is anyway an important release, because it fixes two buffer overflows in search code which have been in all v1.1 releases (but not v1.0). Really stupid mistakes, I must have been tired or something when writing the code.. Anyway I now added code to notice these kind of buffer overflows when they happen (if --enable-debug is used), so hopefully these will be the last ones. * Fixed two buffer overflows in str_find_init(). It was used by SEARCH code when searching for headers or message body. Added code to catch these kind of overflows when compiling with --enable-debug. Found by Diego Liziero. + LDAP: Added debug_level and ldaprc_path settings (OpenLDAP-only) + Squat: Added fts_squat = partial=n full=m settings. See the wiki. - dbox metadata updating fixes. - quota: backend=n didn't work - SEARCH RECENT may have returned non-recent messages if index files were created by v1.0. - If mailbox was opened as read-only with EXAMINE, STOREs were permanently saved. - LDAP: Templates were somewhat broken (by richs at whidbey.net) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] FreeBSD port: port's patch for 1.1rc3
On Tue, Apr 01, 2008 at 12:00:30PM -0400, Adam McDougall wrote: Geoffroy Desvernay wrote: For those who wants testing 1.1rc3 on FreeBSD, this is a simple patch against /usr/ports/mail/dovecot. To apply: # cd /usr/ports/mail/dovecot # patch -p1 /tmp/patch_dovecot_1.0.13-1.1.rc3.diff Hope I did not forget something important... This is an adaptation of the existing port. PS: for port's maintainer: Which way will take 1.0 vs 1.1 upgrade ? a new mail/dovecot10 port or ? Hope this helps -- Geoffroy Desvernay I'm not the maintainer but I've also made a dovecot port for 1.1 as a separate port since it is still in development and may require a few config changes, I discussed that with the maintainers. I made it for work purposes and I have been keeping up with necessary changes to keep it working while I use 1.1, and intended to submit it for inclusion in the ports collection but haven't got around to it yet (I'd like to add a few compile options for new things since 1.1). Been really busy at work and haven't had time, but I guess if people show they are interested I could try to speed that up. While on the subject, I've been tracking dovecot 1.1.x beta's/rc's for NetBSD pkgsrc in pkgsrc-wip: http://pkgsrc.se/wip/dovecot Geert
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
Timo Sirainen wrote: On Mon, 2008-03-31 at 15:10 -0500, Chris Richards wrote: Dovecot is version 1.0.rc15 I agree with others that it would be a good idea to upgrade from rc15, but.. I'm working on this Mar 31 14:00:58 myserver dovecot: IMAP(me): Maildir /home/me/.Maildir sync: UID inserted in the middle of mailbox (85953 85053, file = msg.XL7B:2,) This is a procmail configuration problem: http://wiki.dovecot.org/MailboxFormat/Maildir#procmail Ok, As I read this, basically you're saying that I need to append the / to my delivery dirs? Or that I need to append the / and only deliver to Maildir, instead of Maildir/new? Here's my .procmailrc # .procmailrc # routes incoming mail to appropriate destinations PATH=/usr/bin:/usr/sbin:/bin:/sbin MAILDIR=$HOME/.Maildir # all mailboxes live here DEFAULT=$MAILDIR/new/ # This is where incoming mail goes LOGFILE=$HOME/.procmail_log DELIVER=/usr/lib/dovecot/deliver SHELL=/bin/sh :0: * ^X-Spam-Flag: YESS * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* $MAILDIR/.Spam/new/ I changed the .procmailrc to append the / to the dir. Is that all I need to do? Thanks, Chris
[Dovecot] stalling on LOGIN
I'm getting strange timeouts occasionally on Dovecot 1.0.rc15 on Debian 4.0, and haven't been able to figure out the cause. $ ./src/imaptest [EMAIL PROTECTED] host=localhost pass=foo mbox=~/dovecot-crlf - select=0 Logi Logo 100% 100% 24 7/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 - 3 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 4 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 5 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 6 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 7 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 8 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 9 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 10 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 11 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 12 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test Eventually, I get: Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. $ sudo /usr/sbin/dovecot -n # /etc/dovecot/dovecot.conf protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 8 last_valid_uid: 8 mail_location: maildir:/var/mail/%1d/%d/%1n/%n mail_debug: yes auth default: mechanisms: plain login debug: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 432 user: mail group: mail # dovecot-ldap.conf hosts = localhost:389 dn = cn=admin,dc=example,dc=com dnpass = secret auth_bind = yes auth_bind_userdn = uid=%n,ou=people,associatedDomain= %d,o=accounts,dc=example,dc=com ldap_version = 3 base = dc=example.com,dc=com user_filter = (mail=%u) user_global_uid = mail user_global_gid = mail I've tried enabling all the debugging, but there don't seem to be any errors. Any ideas? Thanks, Brandon PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] stalling on LOGIN
on 4-1-2008 12:34 PM Brandon Keepers spake the following: I'm getting strange timeouts occasionally on Dovecot 1.0.rc15 on Debian 4.0, and haven't been able to figure out the cause. $ ./src/imaptest [EMAIL PROTECTED] host=localhost pass=foo mbox=~/dovecot-crlf - select=0 Logi Logo 100% 100% 24 7/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 00 10/ 10 - 3 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 4 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 5 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 6 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 7 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 8 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 9 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 10 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 11 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test - 12 stalled for 16 secs in command: 2 LOGIN [EMAIL PROTECTED] test Eventually, I get: Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. Error: [EMAIL PROTECTED]: Unexpected BYE: * BYE Disconnected for inactivity. $ sudo /usr/sbin/dovecot -n # /etc/dovecot/dovecot.conf protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login first_valid_uid: 8 last_valid_uid: 8 mail_location: maildir:/var/mail/%1d/%d/%1n/%n mail_debug: yes auth default: mechanisms: plain login debug: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 432 user: mail group: mail # dovecot-ldap.conf hosts = localhost:389 dn = cn=admin,dc=example,dc=com dnpass = secret auth_bind = yes auth_bind_userdn = uid=%n,ou=people,associatedDomain=%d,o=accounts,dc=example,dc=com ldap_version = 3 base = dc=example.com,dc=com user_filter = (mail=%u) user_global_uid = mail user_global_gid = mail I've tried enabling all the debugging, but there don't seem to be any errors. Any ideas? Thanks, Brandon Upgrade. rc15 way over a year old. I think backports has newer version. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
Chris Richards wrote: Ok, As I read this, basically you're saying that I need to append the / to my delivery dirs? Or that I need to append the / and only deliver to Maildir, instead of Maildir/new? Here's my .procmailrc # .procmailrc # routes incoming mail to appropriate destinations PATH=/usr/bin:/usr/sbin:/bin:/sbin MAILDIR=$HOME/.Maildir # all mailboxes live here DEFAULT=$MAILDIR/new/ # This is where incoming mail goes LOGFILE=$HOME/.procmail_log DELIVER=/usr/lib/dovecot/deliver SHELL=/bin/sh :0: * ^X-Spam-Flag: YESS * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* $MAILDIR/.Spam/new/ I changed the .procmailrc to append the / to the dir. Is that all I need to do? Thanks, Chris Never mind. I've figured this out. The above configuratioon seems to do Bad Things to mail delivery. I've change my config to the following, and things seem to be working: # .procmailrc # routes incoming mail to appropriate destinations PATH=/usr/bin:/usr/sbin:/bin:/sbin MAILDIR=$HOME/.Maildir # all mailboxes live here DEFAULT=$MAILDIR/new/ # This is where incoming mail goes LOGFILE=$HOME/.procmail_log DELIVER=/usr/lib/dovecot/deliver SHELL=/bin/sh :0: * ^X-Spam-Flag: YESS * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* $MAILDIR/.Spam/new/ Thanks, Chris
Re: [Dovecot] v1.1.rc4 released (updated managesieve)
Timo Sirainen schreef: http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc4.tar.gz.sig I updated the managesieve patch to apply cleanly against the new dovecot-1.1.rc4 release: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc4-managesieve-0.10.1.diff.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc4-managesieve-0.10.1.diff.gz.sig Regards, Stephan.
Re: [Dovecot] stalling on LOGIN
On Apr 1, 2008, at 3:50 PM, Scott Silva wrote: on 4-1-2008 12:34 PM Brandon Keepers spake the following: Upgrade. rc15 way over a year old. I think backports has newer version. That did it. Thanks Another reason not to use Debian stable. Thanks, Brandon PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] stalling on LOGIN
On Tue, Apr 01, 2008 at 04:12:13PM -0400, Brandon Keepers wrote: On Apr 1, 2008, at 3:50 PM, Scott Silva wrote: on 4-1-2008 12:34 PM Brandon Keepers spake the following: Upgrade. rc15 way over a year old. I think backports has newer version. That did it. Thanks Another reason not to use Debian stable. well there are backports.org :) http://packages.debian.org/etch-backports/dovecot-common Philipp -- If you have problems in Windows: REBOOT If you have problems in Linux: BE ROOT
[Dovecot] Dumb proxying?
I'm a database noob, and it really seems like it would be overkill for my setup: I just want to proxy all connections from my DMZ to my internal mail server -- same internal server for all users. I used to use perdition for this set up, but am having issues getting it to play nicely with my new servers. Can I bypass all of the SQL stuff and just have dovecot forward all POP/IMAP connections to a specific server? Or perhaps set up a wild card lookup in the database (preferably something serverless like sqlite) so that no matter the query, it'll return one server? I don't really want to add database management to my list of jobs I have to do, especially for ~1000 users, and when I don't handle user creation/deletion. -- Dan Bongert [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] Dumb proxying?
Dan Bongert wrote: I'm a database noob, and it really seems like it would be overkill for my setup: I just want to proxy all connections from my DMZ to my internal mail server -- same internal server for all users. I used to use perdition for this set up, but am having issues getting it to play nicely with my new servers. iptables?
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
On Tue, 2008-04-01 at 14:55 -0500, Chris Richards wrote: DEFAULT=$MAILDIR/new/ # This is where incoming mail goes $MAILDIR/.Spam/new/ Do these really work? They're not writing mails to new/new/ directory? I think they should have been without the new/ part. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
Timo Sirainen wrote: On Tue, 2008-04-01 at 14:55 -0500, Chris Richards wrote: DEFAULT=$MAILDIR/new/ # This is where incoming mail goes $MAILDIR/.Spam/new/ Do these really work? They're not writing mails to new/new/ directory? I think they should have been without the new/ part. Yeah, that was what I discovered. *g* Later, Chris
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
At 11:20 AM +0300 4/1/08, Timo Sirainen wrote: On Mon, 2008-03-31 at 15:10 -0500, Chris Richards wrote: Dovecot is version 1.0.rc15 I agree with others that it would be a good idea to upgrade from rc15, but.. Mar 31 14:00:58 myserver dovecot: IMAP(me): Maildir /home/me/.Maildir sync: UID inserted in the middle of mailbox (85953 85053, file = msg.XL7B:2,) This is a procmail configuration problem: http://wiki.dovecot.org/MailboxFormat/Maildir#procmail That's a surprise. I saw that and considered it, but I interpreted it to mean that mh delivery from procmail into a Maildir's 'new' subdirectory created a file with the inode *number* in the filename. I was suspecting the UID lock issue fixed in rc26: http://www.dovecot.org/list/dovecot-news/2007-March/35.html Which does not explain how Dovecot could reuse a UID, but that just seemed weird and wrong in any case... -- Bill Cole [EMAIL PROTECTED]
Re: [Dovecot] DoveCot IMAP and inconsistent state messages
Charles Marcus wrote: No groan here... I love the flexibility Gentoo gives... you can easily leave the primary system at 'stable', then just set certain packages to unstable for the latest/greatest. My servers have been running nonstop for over 3 years, with just a few minor hiccups now and then that are quickly resolved by digging through logs and/or hitting google and/or the forums... To be fair, most distros *do* have the ability to use extra 'unstable' repos, at least for most major packages, and if I wasn't using Gentoo, I would at *least* be using those... My other box is Gentoo, and I quite like it. The biggest problem I had with it was that about a year ago when I was give control of it, it hadn't been synced in like 3 years, and it was so woefully out of date that when I tried to emerge -upDN world, it couldn't reliably upgrade because some packages no longer existed, including core packages (and the system profile). Other than that, the only problem I've had was when a Metalog (sysloger) update came out that caused my entire system to hang at boot because the portage package didn't properly move a couple of files. Later, Chris
