Re: newbie question on a dovecot buffer

2019-11-05 Thread Aki Tuomi via dovecot
On 6.11.2019 6.47, Plutocrat via dovecot wrote: > On 06/11/2019 01.41, Richard Bown via dovecot wrote: > > Can I use Dovecot as a buffer between my mail providers Dovecot servers >> and the several IMAP mail clients on my own network ? >> ie,  so Dovecot would mirror the mail on my account

Re: newbie question on a dovecot buffer

2019-11-05 Thread Plutocrat via dovecot
On 06/11/2019 01.41, Richard Bown via dovecot wrote: > Can I use Dovecot as a buffer between my mail providers Dovecot servers > and the several IMAP mail clients on my own network ? > ie,  so Dovecot would mirror the mail on my account with my mail provider, So > my local dovecot server

newbie question on a dovecot buffer

2019-11-05 Thread Richard Bown via dovecot
Hi apologies for what will seem a daft question I'm getting problems with my mail provider who is using dovecot. I've loaded Dovecot on a 8 core ARMHF SBC version 2.2.33.2 on Ubuntu 18.04. The SBC is headless. and the load looks very light and only needs to store/cache 4GB of mail Can I use

Trying to replace anti spam plugin with IMAPSieve; no joy

2019-11-05 Thread Brad Koehn via dovecot
I’m trying to follow the instructions on the wiki to move from antispam to IMAPSieve, but it’s not working at all. A bit of a background: dovecot-core 2:2.3.8-4~buster dovecot-imapd 2:2.3.8-4~buster dovecot-lmtpd 2:2.3.8-4~buster dovecot-managesieved

Re: sievec *.sieve problem.

2019-11-05 Thread Reio Remma via dovecot
On 05/11/2019 10:03, Sami Ketola via dovecot wrote: On 5 Nov 2019, at 9.53, Reio Remma via dovecot > wrote: Hello! For the second time I've tripped onto this banana peel. :) I had 2 sieve files in a directory that I wanted to compile: sievec *.sieve The result

Re: sievec *.sieve problem.

2019-11-05 Thread Sami Ketola via dovecot
> On 5 Nov 2019, at 9.53, Reio Remma via dovecot wrote: > > Hello! > > For the second time I've tripped onto this banana peel. :) > > I had 2 sieve files in a directory that I wanted to compile: > > sievec *.sieve > > The result of this is that first.sieve is compiled into second.sieve