similar to: cache

I have a really weird problem. To whit: I compiled dovecot 0.99.10 on two different systems: a linux-ppc box running Debian, and a Mac OS X Server v. 10.2.8. It compiled fine on both. The same Maildir's are being served up on both -- the OS X server exports home directories to the clients via NFS. BUT the OS X box orders mailboxes this way: INBOX Deleted Items Sent Items . . . And the

Hey, I am setting up Dovecot on Debian with Postfix. I am telling Dovecot to use maildir:~/Maildir but it persists in dumping mail in mbox format in /var/mail/username. Can anyone suggest ideas? My config file is attached. Thanks Kevin -------------- next part -------------- ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment #

I having a hard time working this out, I've looked in the wiki and various other places but am still cueless (stupid me) mercury:/etc/dovecot# imtest -a graeme 203.96.154.204 S: * OK dovecot ready. C: C01 CAPABILITY S: * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN S: C01 OK Capability

hi there... i HAVE practically searched in ALL messages from 2004 year, and haven't any luck with this problem, so I'm inserting here "dovecot.conf" content: ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based

Hi, I am running dovecot 0.99.10.4 on SuSE 9. I installed it using apt-get from the gwdg repository. The dovecot service is configured to start at boottime in run level 3 and 5. However, it dies immediately with this error (/var/log/mail.err): dovecot: Login process died too early - shutting down Starting the service afterwords from a prompt as root with the command: /etc/init.d/dovecot

Hello, It looks like the "mail_always_cache_fields" and "mail_never_cache_fields" can be used to control dovecot's caching decisions. I cannot seem to find any documentation regarding how these fields should be used. What are acceptable values for these fields? I am quite new to this so any help would be much appreciated. Regards, Siva -------------- next part

I have been having a problem with the test releases...I am now using Test 59. When I delete a message using SquirrelMail (IMAP) the message stays in the message list....but you can't open it anymore because it can't be found, if I logout and log back in...the message is gone from the list. I thought it could be a problem with the cache, so I added mail_never_cache_fields = MessagePart

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I'm migrating to Dovecot from Courier-IMAP. I use Postfix with Maildir for delivery. When I use Dovecot as the IMAP server all of my folders are missing, the only thing that remains is the Inbox folder. Has anyone else experienced this issue? I have enclosed my configuration. Thanks, Chris - -- Chris Horry

Hi folks. New to both dovecot and openldap. Trying to set up virtual domains using the wanderingbarque howto: http://www.wanderingbarque.com/mailserver.html Platform is RH enterprise 3. Only difference is I'm trying to use phamm instead of jamm: http://phamm.rhx.it/ dovecot doesn't seem to want to play nice with my openldap; everything else (postfix, etc) seems to work alright.

Hello, it seems that there is some bug in authentication cache code in dovecot version 1.1.alpha4 - after login attempt with wrong password the correct password also will fail. I can reproduce it very easy: $telnet 10.10.10.30 110 +OK Server. <861.2.46e6c679.jZ8QYpFmU8ZN6XIq7zPhkw==@server2> user testuser +OK pass pass +OK Logged in. quit +OK Logging out. Connection closed by foreign host.

https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz.sig There are a couple of changes still coming, but now would be a good time to make sure anything unexpected hasn't broken. The final release should be out early next week. * auth: Use timing safe comparisons for everything related to passwords. It's unlikely

https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz.sig There are a couple of changes still coming, but now would be a good time to make sure anything unexpected hasn't broken. The final release should be out early next week. * auth: Use timing safe comparisons for everything related to passwords. It's unlikely

On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig > > * auth: Use timing safe comparisons for everything related to > passwords. It's unlikely that these could have been used for > practical attacks, especially because Dovecot delays

Hi, We try to configure dovecot as usual (all our servers have dovecot+vpopmail+qmail or postfix). We set up dovecot with the next outcome: - imap ok - imaps ok - imap STARTTLS NOT OK Debug: root at s13:/home/lucas# gnutls-cli --starttls -p 143 ip Resolving 'ip'... Connecting to 'ip'... - Simple Client Mode: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID

Hi folks, I can't get dovecot to authenticate properly against ldap/pam. I've been fiddling with it for several days now, to no avail. It keeps crashing with: Child died with signal 11 The system is Solaris9. Enclosed is a trace of dovecot-auth for a connection to pop with correct username and password and my config. Any help is appreciated. Cheers Benjamin

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

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only

Dovecot users list, I started having problems with Outlook not syncing with Dovecot a public imap folder upon issuing a send/receive in the client; eventually Outlook timed out, and I received the following error in the Dovecot log. Jan 23 09:20:23 imap(user at mydom.com): Error: FETCH [] for mailbox projects.myfolder UID 120 got too little data: 7744 vs 7759 Jan 23 09:20:23 imap(user at

Ok, I have narrowed my IMP/Dovecot attachment problem down to what I think is a bug in Dovecot. The test that follow are performed on 0.99.11. When you download an attachment in IMP it uses the php function imap_fetchbody() which contacts the IMAP server and retrieves just the mime chunk you are looking for. It does this by first fetching some information about the email, and then grabs the