similar to: Dovecot does not recognize imported messages

Today I tried to import mail directly on the server's home directory on the server. I copied it directly. I didn't use the imap protocol. Dovcot didn't recognize these emails. I didn't display these imported emails on my page, recalculating disk quotas. It will not increase the used capacity. I try to send an email to this user, dovcot recognizes all the emails, and recalculates

I changed the user permissions, this is a must. Because an email is sent to this user, all emails are identified. > Did you do something like "chown -R vmail:vmail /var/mail" after copy messages? > > ??, 8 ??? 2019 ?. ? 12:57, lty via dovecot <dovecot at dovecot.org>: > > Today I tried to import mail directly on the server's home directory on the server. I

I'm returning to qmail and dovecot after having suffered a complete failure with a different mail system and I'm now trying to figure out the easiest way to recover our messages from the failed system. The messages are stored as RFC822 in individual files and I can easily identify which message belongs to whom. I have qmail and dovecot configured to use Maildir format. I know I can

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i build mysql (currently v5.0.22) on OSX 10.4.7 w/ threading enabled. i.e., i build the reentrant libs: libmysqlclient_r.dylib rather than the 'usual': libmysqlclient.dylib currently, to make Dovecot 'play nice' and recognize the reentrant libs, I: perl -pi -e

i'm running dovecot 1.2.9 and, among other things, i have the zlib plugin enabled. A shell script runs once a day to compresses all not still compressed files on the users maildirs. so far so good, it works fine, there's no problem on that. what i think is not happening 100% correctly is the following: 1) user receives a message 2) BEFORE the compress routine runs,

Hi, y'all, long-time Mac OS X Server user Bill here with a thorny question for the mailing list since nobody at discussions.apple.com can quite put their finger on the answer. While well-aquainted with other aspects of Server, Dovecot is a bit of a mystery still to me. So here it goes: Background I'm struggling to migrate from MacOS X 10.6 to 10.9. I tried twice using the "live

Hi! Usually dovecot auto detects or repairs the size of a maildir message. So I can place a message named "foo" in the cur directory and dovecot uses it. Now I tried the same with a zlib compressed message but here dovecot doesn't recognize/repair the size of the message. When I access this folder via IMAP the connection is diconnected and in dovecot logs I see the following

We're using dovecot-2.1.16 on CentOS (rpm package from epel repo). Maildir format on ext4. > What exactly do you mean by "Dovecot started reindexing"? Selecting thread sort on the javamail client, the imap process opens all files in the folder and updates the following files on disk: dovecot.index dovecot.index.cache dovecot.index.log dovecot.index.log.2 dovecot.index.thread

Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on

Hi Timo and other dovecot fans, why, when I'm trying to read certain "Drafts" emails that I just created, or edited, do the dovecot children die (or so I think). In mutt, the behaviour is that I "c =Drafts" then select the email and I get "connection closed to squeaky.rubberduck.com". In Mail.app - she just loops, trying to read those headers again and again

On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any. This problem seemed to start happening in alpha3 (and persists in alpha4). When I revert back to alpha2, the messages show up again. It looks like a problem with the dovecot.index*

Hi, i'm google for it and i searched the archives, but i can't find the problem i have or a hint for a solution. I'm using Postfix as MTA, the new messages deliver by postfix to the maildir: /mail/domain.tld/userpart/new/ Dovecot sometimes show the new mails directly (it's very unusual) but mostly it needs for an hour that dovecot recognize the new messages. Reconnecting of the

Hi Perhaps I've been going too far OT in my previous thread or perhaps I just didn't explain my problem clear enough so forgive me for trying again. I have configured fetchmail to fetch my mail from my ISP's POP3-server. I have set up procmail to filter messages and deliver all non-filtered messages to the folder ".IN-catchall/" in "$HOME/Maildir" After sending

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 23 Apr 2015, David Gessel wrote: > I'm inclined to believe, as trivial as it may be to enumerate, that: > > Something is triggering dovecot to believe the indexes need to be rebuilt. > When checking mail during the rebuild, clients get confused by UIDs in transition. > > I would think that sdbox would alleviate these

We found that there are historically corrupted mails in the tmp/ directory, For example, Maildir/tmp/ or Maildir/.Drafts/tmp/ exists. We suspect that it may be caused by network transmission, or the user interrupted the network link. Can the dovecot team possibly fix this problem? dovecot --version 2.2.36

This one is for vmail which is attached. Bill On 11/10/2016 8:29 PM, Ben Johnson wrote: > On 11/10/2016 3:46 AM, Bill Shirley wrote: >> I don't use the Anti-Spam plugin; I just fire off a BASH script every >> four hours with >> crontab which iterates thru the vmail email accounts and trains >> Spamassassin 'per-user' >> accounts. If the script

I recently moved from Fedora 13 to Fedora 14 and consequently to dovecot 2.0.8. Since then, I have observed that messages are not being marked as read in all cases. The general behavior is: 1. Use my mail client to read all unseen messages. All mail folders show no messages unread. 2. Tell mail client to check for new mail. 3. Mail client now says that some folders have new mail (1 or more

Hi, Currently using dovecot 2.3.2.1 and pigeonhole 0.5.2 on two identical hosts. I recently noticed ".dovecot.sieve" and ".sieve/managesieve.sieve" are not replicating from one host to the other in either direction. Mail is having no trouble replicating on both hosts with dsync, it is only sieve files that are not replicating for unclear reasons. # doveconf -n host 1:

Hi, I'm trying to migrate a user from Outlook.com IMAP to Dovecot. I'm using a setup similar to that on http://wiki2.dovecot.org/Migration/Dsync: imapc_host = imap-mail.outlook.com imapc_user = [...]@hotmail.com imapc_password = [...] imapc_features = rfc822.size fetch-headers mail_prefetch_count = 20 imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = yes ssl_client_ca_dir =

I'm using RC15 on Solaris 9. The wiki indicates that when a dovecot-shared file exists, "Dovecot uses the same permissions and GID when it creates index files, dovecot-uidlist file, new mail files, etc." In my case, Dovecot *is* creating new index files based on dovecot-shared, but dovecot-uidlist and individual message files don't completely match the permissions/group