similar to: Help with new syslog errmsgs

Thunderbird (2.0) is all of a sudden checking mail server capabilities and keep posting a popup saying: "Mail Server imap.bard.edu is not an IMAP4 mail server". To the best of my knowledge, neither Tbird nor DC have been updated, though the DC imap host was rebooted today 3 hours ago. Any info on what this is about? DC is currently serving out of a special port and in evaluation

From reading the wiki for a filesystem quota, I took my shot at 1) building my binaries using the mods in AIXPluginsSupport 2) changing dovecot.conf and 3) putting the plugins in the library But I'm getting this error message when I invoke dovecot: Plugin imap_quota not found from directory /usr/local/lib/dovecot Error: imap dump-capability process returned 89 It would seem that a) I have

I've been lurking for a year or more and am now actually bringing Dovecot up (it seems that any time I make a serious effort at this, something else falls in the pot and I have to give it up yet again). Index questions: I understand the indices should be placed in a non-file-system-quoted place. I have in mind to create /var/dcndx 1) Roughly how much space do indices take up (so I can size

Last Wednesday at 12:21 I made this switch, which seemed to be uneventful. In any case, no user has reported problems since the migration. Not content to leave well enough alone, this morning I scanned the syslog and maillog for dovecot related errors. What I found was that: Before the Migration=========================== I saw a lot of SSL errors that look like this: > Jan 14 11:49:23

After V1.2 had been up for a while, I started seeing tons of syslog error messages like this: Nov 5 09:11:52 mercury mail:err|error dovecot: IMAP(sdean): stat(/var/dcindx/sdean/.imap/DadEstate) failed: Permission denied (euid=202(sdean) egid=200(hcrc) missing +x perm: /var/dcindx) Ownernship and Permissions are: The index filesystem 2726 root at mercury:/var/dcindx ## ls -ald drwx--S---

I tried to disable courier-pop3 today in favour of dovecot pop3. Prior to that I ran: find /home -maxdepth 1 -type d | xargs --replace /usr/local/scripts/courier-dovecot-migrate.pl --overwrite --recursive --convert {} ( /home is hashed two levels deep: /home/a/a/aanton/Maildir/ ) After that, I got lots of errors like: Aug 9 13:02:40 postamt dovecot: IMAP(azenclu): Maildir

http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes

My production DC machine owns the mail filesystems and is running DC V1.0.15 and mbox folder format. I am looking to test V1.1.3 on another machine, which NFS mounts the mail filesystems, but has its own local index FS. I have made this test environment my default connection in TBird, and it seems to work just fine. Also, I have made sure that my TBird client isn't connecting to the

A new employee started today, when logging into his new mailbox this morning during a walk-through I got a nasty server error response in Thunderbird - something I never see, DC runs smooth as butter for us. Checking the server log I see this: == snip == dovecot: Jul 09 09:38:54 Error: IMAP(xxxxxxx): Maildir /home/x/xxxxxxx/Maildir sync: UIDVALIDITY changed (1183406107 -> 1183999134)

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors

Running current CVS HEAD I get: dovecot: Dec 01 13:27:38 Info: Dovecot v1.0-test52 starting up dovecot: Dec 01 13:33:34 Info: imap-login: Login: jtl [69.162.177.245] dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in mbox file /var/spool/mail/j/t/jtl dovecot: Dec 01 13:41:07 Error: IMAP(jtl): UIDVALIDITY changed (1100294646 -> 110192643 5) in

Found an imap crash. I'm using the CVS copy from March 23. This is running under Linux, kernel 2.6.11.something. We use mbox over NFS, everything is on the NFS server. There is currently only one dovecot server accessing the mailbox. Here's the log messages: dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): UIDVALIDITY changed (1112720886 -> 1112721068) in mbox file

After upgrading to R 2.6.0, I'm having trouble running lmer: model <- lmer(primed ~ log(dist.time)*role + 1|target.utt, data=data.utts) Error in UseMethod("as.logical") : no applicable method for "as.logical" So I thought I'd upgrade lme4 to the latest version, but unfortunately the compilation fails - perhaps there's a missing #include: R CMD INSTALL

Am seeing: > Jul 19 14:59:19 mercury mail:err|error dovecot: IMAP(jab): dotlock /var/spool/mail/jab.lock was immediately delet > ed under us > Jul 19 14:59:19 mercury mail:err|error dovecot: IMAP(jab): file_lock_dotlock() failed with mbox file /var/spool/m > ail/jab: No such file or directory what does it mean, what should I be doing to alleviate or troubleshoot the problem? -- ====

As I explained, I want to be able to run a second instance of DC through another port to do testing while not interrupting the users using the primary instance in the the regular port. I was instructed to create a second config file with different listen ports and a separate base_dir. I did so and invoked dc with -c pointing to dovecot2.conf. Jun 7 10:04:23 mercury mail:info dovecot:

I performed a hg pull today for 1.0.1 and after recompilation my log was flooded with: Jul 12 10:29:21 postamt dovecot: IMAP(kxx4): UID larger than next_uid in file /home/k/j/kxx4/Maildir/dovecot-uidlist (6 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(rexxxes): UID larger than next_uid in file /home/r/e/rexxxes/Maildir/dovecot-uidlist (1 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(sxxkim):

After installing a new server with dovecot 1.2.4, I found there is some new dovecot-uidvalidity* files in user's Maildir directory. However, I did not see such files in other servers with dovecot 1.1.2 (around 2008/07). What is function of those files? What will happen if I delete that files? I am curious why need to keep 2 files: dovecot-uidvalidity dovecot-uidvalidity.4aa4fa4c since the

Hello, I'm running dovecot-1.1.8/Maildir/ACL plugin. I sucessfully set up a Maildir shared between users of the unix group 'doveshared' via a public namespace, unix permissions and ACL files. The location of my public namespace is /path/to/public. I tried 2 sub-setups : First setup ---------- drwxrws--- 4 root doveshared 4096 Jan 30 13:39 public -rw-r----- 1 root doveshared

Hi, I'm having trouble with glmmPQL from the MASS package. I'm trying to fit a model with a binary response variable, two fixed and two random variables (nested), with a sample of about 200,000 data points. Unfortunately, I'm getting an error message that is difficult to understand without knowing the internals of the glmmPQL function. > model <- glmmPQL(primed ~

> On 31 Mar 2020, at 23.18, Ben Mulvihill <ben.mulvihill at gmail.com> wrote: > > Hello again, > > I am still stuck I'm afraid. > > I now have doveadm backup working perfectly from > a small gmail mailbox (a few hundred messages), but > when I try the same configuration (apart from usernames > and passwords obviously) with a large gmail mailbox >