similar to: different login_greeting for pop3 & imap?

Is it possible to have folders on read-only partitions in Dovecot 1.0-stable? We have a NetApp fileserver which would probably be accessed via NFS (though iSCSI is possible) and which stores readonly "snapshots" of every directory accessible as .snapshot (but usually hidden from the operating system). It would be very nice to set up a "snapshot" namespace something like

I am getting this failure when trying to compile dovecot on Sparc Solaris 8: make[4]: Entering directory `/home/systems/looneytr/dovecot-1.1.rc12/src/lib' source='str-find.c' object='str-find.o' libtool=no \ DEPDIR=.deps depmode=gcc /bin/bash ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/openssl/include -g -O2 -Wall -W -Wmissing-prototypes

Hello all, Thanks for your help getting me started. I have Dovecot running now. When I troubleshoot customer email problems, I need to be able to see the number of emails they popped. In /var/log/maillog, Dovecot just tells me that they authenticated, but not what happened after they authenticated. With pop3d, I saw how many emails they popped. Can I set that in Dovecot? I checked the

I've been struggling with an odd bug in the latest 1.0-stable (20050427) release. Sometimes Dovecot seems to forget that a message has been read or deleted and marks it unread (or not deleted). As far as I've been able to determine, it seems to happen when 1) There have been several recent deliveries 2) Possibly some of those deliveries are of multiple messages 3) Possibly they are read

Is it possible to setup dovecot to have it presented different SSL certificates to connections coming at different ports. I don't see it in the docs. It seems, dovecot would present the same certificate to all connecting ports. Thanks.

Hi All This is possibly a silly question but after reading some of the docs and hunting a bit I could not find an answer. I need to run my pop3 service on both the standard 110 port and another (not really sure which yet) port. My ISP is doing shaping on port 110 destined traffic causing a nightmare with some of my machines pulling only some of their mail then crashing (and no its not anything

We are currently evaluating the migration from a proprietary, legacy mail server onto Dovecot for 20,000+ virtual domains. This is a big job and we intend to do it by initially proxying connections through to the legacy server, and moving customers over in batches by turning off the proxy feature for them. In the manual it states "This model is still a bit unfinished in current code"

Dear list, I am planing to set up dovecot-imapd on my production-mail server which currently only runs pop3 via qpopper on debian-sarge. It would be best, if I could only use imapd and use the existing pop3- server (qpopper) as it is. Is this possible? Can the user both use pop3 (qpopper) and imapd (dovecot) in parallel then? Where does dovecot-imapd store its mails? Does it store its mail in

Timo, I've noticed a couple of extra compilation errors in last night's snapshot compared to the snapshot I downloaded on Tuesday, probably due to the int -> bool change :- (gcc 3.3.2 on Solaris 8) mbox-sync.c: In function `mbox_sync': mbox-sync.c:1568: warning: comparison is always false due to limited range of data type index-search.c: In function `search_index_arg':

I've got a problem with subscriptions in 1.0-stable when migrating from UW-IMAP. I've modified the SUBSCRIPTION_FILE_NAME entries as suggested in the Wiki http://wiki.dovecot.org/Migration and included the "~/mail/" etc. hidden namespaces. The .mailboxlist files contain entries like "~/mail/somefolder" and the clients have "~/mail/" set as a prefix. In

I've had complaints from users about "MISSING_DOMAIN" in header fields and I've tracked it down to having "." in an unquoted display name. By my reading of RFC2822 (especially section 4.1) A N Other <a.n.other at somewhere.org> "A. N. Other" <a.n.other at somewhere.org> are legal, but A. N. Other <a.n.other at somewhere.org> is

It seems that Dovecot gets confused when presented with a header like: From: someone at somewhere.org i.e. with leading whitespace and no "friendly name" This shows up as ""@MISSING_DOMAIN in clients, such as Pine, that believe what Dovecot tells them rather than parsing the headers themselves (e.g. Thunderbird). Here's a sample IMAP session: xyz FETCH 728 ENVELOPE

Hmm, this is peculiar! This mailbox has been unchanged on my test server since September. I've been using it to test each new version of Dovecot just after I've compiled it. When beta1 was released, I opened this mbox with no problems. However, when I upgraded to beta2, I got "file size unexpectedly shrinked in mbox file /export/mail/a/24/vis99003/INBOX (16895967 vs 16899267)".

Talk about personal problems! I am using dovecot-0.99.13-4.FC2, and everything has been going fine for months. Earlier this afternoon, Thunderbird's status pane would say 'Sending authenticate login information...' and I would no longer receive email. When I checked with others, they were fine and dandy. I tried kmail, evolution, and even tried webmail. All had connection errors.

I've got several users testing Dovecot IMAP at the moment, but some of them are also accessing their mail via UW-IMAP at other times. (I've warned them about accessing the same folder simultaneously via UW-IMAP and Dovecot!) In addition, we have special folders "AutoSpam" and "Trash" that pruned using Washington's "mailutil" automatically every so

I've noticed that my dovecot.index.cache file has got very large (24MB, which is more than 1/3 of my INBOX size). I've tried deleting (well, renaming) the dovecot.index.* files, and re-opening my INBOX, and the new dovecot.index.cache is only 90KB so far. I'm using dovecot-1.0-stable and mbox format. My mail_cache_fields and mail_never_cache_fields are set to the default. Looking

I've been seeing lots of index cache file errors (using mbox on Solaris 8 sparc 64-bit, but with 32-bit Dovecot) since I switched my account to Dovecot 1.2.0 (we're still on 1.0.15 mostly, but I'm hoping to upgrade to 1.1.17+ this summer, or 1.2.x if it's stable enough). e.g. Error: Corrupted index cache file <path>/.imap/INBOX/dovecot.index.cache: field index too large (47

Can someone find an OS where the attached program doesn't work? It should print "success". So far tested for success: Linux 2.6, Solaris 10, FreeBSD 7.2, OpenBSD 4.2. -------------- next part -------------- A non-text attachment was scrubbed... Name: test.c Type: text/x-csrc Size: 1100 bytes Desc: not available URL:

I've been having problems with Pine 4.62 talking to Dovecot 1.0 stable. It's fine when the folder collection path is empty, but if I have "~/mail/" or "mail/" it gives access errors (I'm using the "~/mail/", "mail/" etc. hidden namespaces for backwards compatability). It seems to me that Dovecot is not replying correctly to a "LIST"

Hi all, We moved our Dovecot installation first of all to have all folders and inboxes on NetApps via NFS (with indexes local) then from a physical Solaris 8 4-way UltraSparc server running Dovecot 1.2.5 (32-bit) to a virtualised Ubuntu 8.04 64-bit server with a single virtual processor (in VMWare ESX 3.5) running Dovecot 1.2.8 (64-bit). Since the change, many of our users have experienced