similar to: dovecot-lda delivery to Maildir/cur as 'seen'?

If something deletes and recreates the folder, it?s not really the folder to which you subscribed, is it?! On Wed, May 23, 2018 at 10:33 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > I understand that reading that paragraph makes it sounds obscure and > outdated. But the problem is that if something deletes & recreates your > folder, while you were gone, you would lose the

i'm tired of dealing with buggy clients so i'm moving more processing into the server-side. i configured procmail as LDA with maildir-style mailboxes. i would like to simulate an automatic "mark as read" feature during procmail processing. simplest way looks to be forcing delivery directly to Maildir/cur instead of Maildir/new, but i suspect this may screw up dovecot. will

If John Doe dies and a new John Doe is born, they?re not the same person, are they? On Wed, May 23, 2018 at 10:37 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > That's rather difficult semantic question. > > Aki > > On 24.05.2018 08:35, Roger Klorese wrote: > > If something deletes and recreates the folder, it?s not really the folder > to which you subscribed,

Sorry for top posting, my client is still broken. I have never seen the ghost of a "system-alerts" or similar "well-known" mail folder in the past 30 years. Compliance with an RFC obscure feature is compellong us all to clear subscriptions fol ders by hand. As we meet the problem over and over again, a non-RFC configuration option could solve the problem, and it would be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm migrating from ?old skool? solution with one mail client (MUA) on one computer, which retrieves mail via POP3, sorts it and manages it locally to installation when there are several MUAs on different devices, accessing mail via IMAP4, and all sorting and management should be server-side. Sorting is ?easy?: sieve. Here are some nuisance

Hi, I have tried to use the same Maildir dovecot uses with another program and encountered the problem that Dovecot seems to move files from new to cur in maildir-sync.c::maildir_scan_dir without adding an info part. On the page http://cr.yp.to/proto/maildir.html is written that mails have to be renamed to uniq:info when moved to the cur directory. Could this be a bug in dovecot? --

Hi, We're running a Debian server with system users where the mail is by default delivered by postfix and procmail, before being served by Dovecot (mail_location = mbox:~/Mail:INBOX=/var/mail/%u) or read by local MUAs, depending on users' preferences. For people using mostly remote MUAs, it might be interesting to use Dovecot's LDA. I read on http://wiki.dovecot.org/LDA that this

Hi, I use Sarge's dovecot for a pop3 mail collection server. IMAP is not used at all. It works well, but I would like to know why one of the accounts also keeps a copy of all e-mail copies in the cur/ folder? Thanks a lot, Wally -- Wally Winchester wally_winchester at fastmail.fm -- http://www.fastmail.fm - The way an email service should be

I've been using Dovecot in some fresh installs lately and have found it fairly easy to configure. However I'm starting on a migration that involves moving from some very old software (ancient vpopmail, qmail and Courier). On the Courier front, I've reviewed the migration page in the wiki, and it looks like the main concerns are just matching the namespace and then using the migration

Hi, we just setup a new mailserver for our company with some sieve filtering in place. Everything works as expected but there is one flaw. We setup the per user sieve filters in files within the users mailbox maildir as follows: lrwxrwxrwx 1 mail mail 21 Jan 13 17:20 .dovecot.sieve -> sieve/phpscript.sieve This link is actually picked up by dovecot and being announced as an IMAP

What should I expect performance-wise if I put 200000 messages in a Maildir store and use two or three MUAs (mutt and Thunderbird), on an Athlon dual core 2GHz with SATA drives in software RAID (Linux)? Like; would it be useless/crawling, usable or pretty fast. I imagine MUA startup / first time folder read would be slow, but daily use more or less ok. Thanks to Dovecot's indexing, I imagine

I have the following in my default.sieve file: require "fileinto"; if header :contains "X-spam-flag" "YES" { require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables", "imap4flags"]; setflag "\\Seen"; fileinto "Junk"; } This is largely unchanged, except that I

Hi, I'm using dovecot 1.1.2 (but I've noticed this since 1.1.1 which I was using until yesterday). It seems dovecot is ignoring the "S" flag in Maildir filenames, and is relying only in its Index Files to determine if a message has been read or not. I say that because if I delete the dovecot.index.* files for a mail folder, all the mails in there appear as unread. Also,

Hi ALL... I want to know if the files in /Maildir/cur & /Maildir/.Sent are modified by dovecot. I have a script which calculates the age of the mail files. I think that if they are continuously modified by dovecot I won't be able to calculate the age of the files. Can Anyone plz advise on this.... Thanks CoolAtt

Hi Friends! An opinion. I would like to facilitate the configuration of one's mail client (desktop or mobile) to my users server. Some time ago I asked the same question and you suggested me to use "Automx". So I started of good will and I looked for the Automx documentation. And here the problems started as I found several inconsistencies, even parameters (in official

I'm wondering what I'd need to do to get the "important" flag set on an incoming message according to a pre-specified header. I know the problem of this not being a "joined-up" feature in standard email, but in practice many MUAs set headers like X-priority etc, and IMAP has an "important" flag that is the obvious mapping. I'm not really sure where

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Feb 2015, George Sexton wrote: > I'm seeing two bogus messages appearing my Maildir/cur directory. They're > dovecot.index.log and dovecot-uidlist. > > -rw------- 1 gsexton users 51 Feb 4 09:04 Maildir/cur/dovecot-uidlist:2,S > -rw------- 1 gsexton users 244 Feb 4 09:04 Maildir/cur/dovecot.index.log > These

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 5 Feb 2015, George Sexton wrote: > On 2/5/2015 12:56 AM, Steffen Kaiser wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Wed, 4 Feb 2015, George Sexton wrote: >> >>> I'm seeing two bogus messages appearing my Maildir/cur directory. They're >>> dovecot.index.log

On Sun, Oct 08, 2006 at 10:25:53PM +0300, Timo Sirainen wrote: > On Fri, 2006-10-06 at 21:00 -0500, Steven F Siirila wrote: > > I am running Dovecot 1.0-rc6 along with dovecot-sieve from 2006-10-05 CVS. > > I am calling dovecot deliver from Postfix (main.cf): > > > > mailbox_command = /opt/dovecot/libexec/dovecot/deliver > > > > Upon switching to dovecot

On 2/5/2015 12:56 AM, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 4 Feb 2015, George Sexton wrote: > >> I'm seeing two bogus messages appearing my Maildir/cur directory. >> They're dovecot.index.log and dovecot-uidlist. >> >> -rw------- 1 gsexton users 51 Feb 4 09:04 >> Maildir/cur/dovecot-uidlist:2,S