similar to: imapsieve: mailbox Trash: FLAG event

> Have a look at Mailcow too, it comes with almost everything. > I?ve been running it for a year now, after many years of usin > a self-assembled stack, and it?s a bliss. Thanks for the hint. I initially discarded Mailcow because of this: "mailcow: dockerized comes with multiple containers" The installation instructions mention that Docker Compose is required. Not long ago I

> What you are looking for would be a very advanced setup > [...] I don't think so. But we'll see! I would be happy to take a pre-packaged mail server solution like iRedMail which includes RoundCube or whatever. I just need a "easy", practical guide to reconfigure it to 1) download e-mails from a multidrop, and 2) relay external e-mail to the ISP's SMTP server.

I want to run a cron job for specific users. I thought the easiest would be a sieve plugin that sets some text in managesieve.sieve. And I just have my cron job check for this setting. This is the forward sieve: if false # true { redirect :copy "test at test.com"; } So maybe something like: if false # true { # cronjob1 } Or is there a better way of doing such a

Hi, I've recently started using Dovecot as our main mail storage, and it's performing great. But I have a question/problems with quotas. First of we are using: dovecot --version 2.2.32 (dfbe293d4) Dovecot is a part of a pre set environment (mailcow-dockerized) Aside the inbox namespace we have set-up an additional archive ns (Archiwum) like this namespace Archiwum { ??? type =

Hi all, does anybody here use MacOS (Catalina) Mail, who can confirm that subfolders (i.e. folders inside folders) work for them? It seems that I cannot create/access Maildir subfolders at all. Subfolders created in Mail show up as '.folder\2esubfolder' on disk, suggesting that Apple Mail is URL-coding the dot separator before it passes it onto Dovecot. No such translation takes place

ok, I found: https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt and that helps. Can this be added to the Wiki? On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > How do you enable the imapsieve plugin? I added > sieve_plugins = imapsieve > > and it whines: > hebighonker.lerctr.org /usr/local/etc/dovecot/conf.d #

Op 11/6/2016 om 6:35 PM schreef Larry Rosenman: > also, with NO scripts defined, but imapsieve active, marking a large virtual > mailbox all seen garners: > > Nov 6 11:30:59 thebighonker dovecot: imap(ler): Panic: file > imap-sieve-storage.c: line 616: unreached > > I can provide more logs, but doing the same to (one of) the base > mailbox(es) does NOT garner > the

additional info. This happens when the mailbox definition includes the seen flag: thebighonker.lerctr.org /home/ler/MAIL-VIRTUAL $ cat list-unseen/dovecot-virtual lists/* unseen thebighonker.lerctr.org /home/ler/MAIL-VIRTUAL $ cat other-unseen/dovecot-virtual * -lists/* unseen thebighonker.lerctr.org /home/ler/MAIL-VIRTUAL $ not sure if that makes a difference. On Mon, Nov 7, 2016 at 3:31

also, it appears to NOT matter the size of the (virtual) mailbox. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

Op 11/7/2016 om 4:56 PM schreef Larry Rosenman: > also, it appears to NOT matter the size of the (virtual) mailbox. Fixed: https://github.com/dovecot/pigeonhole/commit/00651e607c6ea9145ec565dcfd2fdf7d04bb32e9 Regards, Stephan.

Op 29-11-2016 om 19:29 schreef KT Walrus: > Just noticed the Dovecot support IMAPSIEVE extension? > > Could I use this extension to update an external database with the date that the user last read the message? No, IMAPSieve is only triggered by modifications: APPEND, COPY, MOVE and STORE. > My app sends certain ?notification? messages to the user?s dovecot mail address. The user

Op 30-11-2016 om 11:37 schreef Stephan Bosch: > > > Op 29-11-2016 om 19:29 schreef KT Walrus: >> Just noticed the Dovecot support IMAPSIEVE extension? >> >> Could I use this extension to update an external database with the >> date that the user last read the message? > > No, IMAPSieve is only triggered by modifications: APPEND, COPY, MOVE > and STORE.

RFC6785 says imap.user and imap.email environment variables should be made available but I can't access them no matter what I try. Are they not implemented because vnd.dovecot.environment already provides the username? (which does work for me) If imap.user and imap.email are there, can you provide an example how to access them so I can see what I did wrong?

Op 5-12-2016 om 13:28 schreef MRob: > RFC6785 says imap.user and imap.email environment variables should be > made available but I can't access them no matter what I try. Are they > not implemented because vnd.dovecot.environment already provides the > username? (which does work for me) > > If imap.user and imap.email are there, can you provide an example how > to

The examples on the imapsieve documentation page use COPY but not APPEND to watch messages coming into a folder. Are there not circumstances that a client would APPEND a message to a folder instead of COPY? Is APPEND only used by most clients for adding a sent message to the sent folder? I'm not familiar enough with IMAP clients to know if by leaving off APPEND I am safe or I am at risk

Op 5-12-2016 om 14:32 schreef MRob: > On 2016-12-05 04:38, Stephan Bosch wrote: >> Op 5-12-2016 om 13:28 schreef MRob: >>> RFC6785 says imap.user and imap.email environment variables should >>> be made available but I can't access them no matter what I try. Are >>> they not implemented because vnd.dovecot.environment already >>> provides the

Op 5-12-2016 om 16:10 schreef MRob: > On 2016-12-05 06:13, Stephan Bosch wrote: >> Op 5-12-2016 om 14:32 schreef MRob: >> >> Could you show me your full script? I am mainly interested in the >> require statements involved. > > I don't know how I managed to compile only using direct access of > ${imap.user} before since now I get an unknown namespace error

Op 12/6/2016 om 12:23 AM schreef MRob: >>>>> I don't know how I managed to compile only using direct access of >>>>> ${imap.user} before since now I get an unknown namespace error on my >>>>> test script. >>>>> >>>>> But doing it this way compiles: >>>>> >>>>> require

Op 5-12-2016 om 14:36 schreef MRob: > The examples on the imapsieve documentation page use COPY but not > APPEND to watch messages coming into a folder. Are there not > circumstances that a client would APPEND a message to a folder instead > of COPY? Is APPEND only used by most clients for adding a sent message > to the sent folder? I'm not familiar enough with IMAP clients

RFC 6785 says I should be able to run scripts when a command changes flags on a message but I can't understand what to put in imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an invalid cause. How do I run an administrator Sieve script caused from change in flags?