Re: Assistance with doveadm backup...

Here is my command: [root@mail maelstrombackups] #mkdir -p vmailbackup [root@mail vmail]# chown: vmail:vmail /mnt/maelstrombackups/vmailbackup [root@mail vmail]# doveadm backup -u jeff maildir:/mnt/maelstrombackups/vmailbackup Only gives me the usage list, doesn’t work. Jeff > On Feb 21,

Re: Assistance with doveadm backup...

> On 21 Feb 2019, at 7.04, SH Development via dovecot > wrote: > > Not really. The suggestions in the post seemed to be: > > 1. Tar the whole directory, which I have tried in the past, but a 130G > directory takes over 18 hours to tar. > 2. It was also suggested to rsync the directory,

Re: Assistance with doveadm backup...

Sorry for being such a newbie when it comes to scripting. Created a directory for the backups on the network mounted volume. Changed the appropriate path and am getting this: dsync(root): Error: user nfsnobody: Initialization failed: Namespace 'INBOX.':

Re: Assistance with doveadm backup...

Not really. The suggestions in the post seemed to be: 1. Tar the whole directory, which I have tried in the past, but a 130G directory takes over 18 hours to tar. 2. It was also suggested to rsync the directory, but the question was brought up, and not answered, about whether it was advisable

Re: Assistance with doveadm backup...

On Feb 20, 2019, at 21:11, SH Development via dovecot wrote: > Can someone help get me started here? Does this help? https://unix.stackexchange.com/questions/489331/what-is-the-correct-way-to-use-doveadm-to-backup-emails -- This is my signature. There are many like it, but this one is mine.

Assistance with doveadm backup...

I am having trouble locating examples of how to use doveadm backup. All the examples I see are for sync. I simply want to create a backup to a network volume of the email server's vmail folders. The goal here is to have a reasonably current backup should the main drive on the email server go

LMTP and public mailboxes?

Hi, I've been using postfix and dovecot for a few years, and have been doing public mailboxes with dovecot-lda, using a postfix transport that looks like (line wrapped for the mailer): my-public-transport unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/bin/spamc -u -e \

Re: Virus scan + removal on a mdbox mail storage

Hello David, - Nachricht von David Pottage via dovecot - Datum: Wed, 20 Feb 2019 14:56:51 + Von: David Pottage via dovecot Antwort an: David Pottage Betreff: Re: Virus scan + removal on a mdbox mail storage An: dovecot@dovecot.org On 2019-02-20 01:46,

Re: Using SHA256/512 for SQL based password

On 2/20/19 3:28 PM, Robert Moskowitz via dovecot wrote: Here's how I configured my roundcube's password plugin to keep things together ($roundcubefolder/plugins/password/config.php) $config['password_algorithm']    = 'dovecot'; $config['password_algorithm_prefix'] = '{SHA512-CRYPT}';

Re: Virus scan + removal on a mdbox mail storage

On 2019-02-20 01:46, Christoph Haas via dovecot wrote: I need advice on how virus scan and removal can be done on a _mdbox_ mail storage? On a maildir storage the virus scanner (e.g. clamav etc.) can detect and remove a email that is infected, since every email and attachment are stored in

Re: Using SHA256/512 for SQL based password

On 2/20/19 5:09 AM, Yassine Chaouche via dovecot wrote: On 2/12/19 5:05 PM, Robert Moskowitz via dovecot wrote: I have trying to find how to set the dovecot-sql.conf for using SHA256/512.  I am going to start clean with the stronger format, not migrate from the old MD5.  It seems all I need

Re: Using SHA256/512 for SQL based password

On 2/20/19 9:06 AM, @lbutlr via dovecot wrote: On 20 Feb 2019, at 06:10, Robert Moskowitz via dovecot wrote: libsodium does not help with CentOS7 and Dovecot 2.3: This is what your HTML message looks like here:

Re: Using SHA256/512 for SQL based password

On 20 Feb 2019, at 06:10, Robert Moskowitz via dovecot wrote: > > libsodium does not help with CentOS7 and Dovecot 2.3: This is what your HTML message looks like here:

Re: Using SHA256/512 for SQL based password

On 2/20/19 8:38 AM, Aki Tuomi wrote: On 20 February 2019 15:10 Robert Moskowitz via dovecot wrote: On 2/19/19 1:50 AM, Aki Tuomi via dovecot wrote: On 17.2.2019 10.46, Aki Tuomi via dovecot wrote: On 17 February 2019 at 10:38 Odhiambo Washington via dovecot <

Re: Using SHA256/512 for SQL based password

> On 20 February 2019 15:10 Robert Moskowitz via dovecot > wrote: > > > > > > On 2/19/19 1:50 AM, Aki Tuomi via dovecot wrote: > > > > > > > > > > On 17.2.2019 10.46, Aki Tuomi via dovecot wrote: > > > > > > > > > > > > > > > > > On 17 February 2019 at 10:38 Odhiambo

Re: Using SHA256/512 for SQL based password

On 2/19/19 1:50 AM, Aki Tuomi via dovecot wrote: On 17.2.2019 10.46, Aki Tuomi via dovecot wrote: On 17 February 2019 at 10:38 Odhiambo Washington via dovecot < dovecot@dovecot.org > wrote: On Sun, 17 Feb 2019 at 11:34, Marc Weustink via dovecot <

Re: sieve filter not working

Op 20-2-2019 om 9:30 schreef subin ks via dovecot: I've Dovecot and dovecot-sieve v 2.2.27 installed on a Debian 9.6. I'm trying to set a Sieve filter which will redirect all emails from `info` (i.e. .info) TLD to another email. This is the filter: require ["regex"]; # rule:[test] if

Re: sieve filter not working -- matchtype

Scott, you are right. And I guess it's computed faster too. # rule:[test] if header :matches "from" "*.info" { redirect "su...@domain.com"; } Even a TLD like "*.superinfos" may be included: "*@*.*info*" Greetings Martin On Wed, 2019-02-20 at 08:47 +, Scott M. via dovecot wrote: >

Re: Error sending email from client

On 2/18/19 2:29 PM, Latin Bishop via dovecot wrote: Feb 18 08:26:41 pepino postfix/smtps/smtpd[5328]: warning: unknown smtpd restriction: "permit_ssl_authenticated" Try to change permit_ssl_authenticated to permit_s*a*sl_authenticated (+a) But as Sami said this is a postfix issue and

Re: Using SHA256/512 for SQL based password

On 2/12/19 5:05 PM, Robert Moskowitz via dovecot wrote: I have trying to find how to set the dovecot-sql.conf for using SHA256/512.  I am going to start clean with the stronger format, not migrate from the old MD5.  It seems all I need is: [...] default_pass_scheme = SHAxxx-CRYPT [...] How

Re: sieve filter not working -- wildcard missing

On Wed, 2019-02-20 at 10:37 +0100, Martin Johannes Dauser via dovecot wrote: > On Wed, 2019-02-20 at 10:18 +0100, Martin Johannes Dauser via dovecot > wrote: > > Hi! > > > > You forgot the wildcard '.*' (= Match zero or more instances of any > > single character, except newline) > > > > require

Re: index problems after update

> On 18 February 2019 09:28 Hajo Locke via dovecot wrote: > > > Hello, > > it seems we need a dovecot developers opinion. May be we hit a bug or cant > help ourselves. > > > Core dump with backtrace would help, if possible to acquire. Please refer to

Re: sieve filter not working -- wildcard missing

On Wed, 2019-02-20 at 10:18 +0100, Martin Johannes Dauser via dovecot wrote: > Hi! > > You forgot the wildcard '.*' (= Match zero or more instances of any > single character, except newline) > > require ["regex"]; > # rule:[test] > if header :regex "from" ".*info$" > { >   redirect

Re: sieve filter not working -- wildcard missing

Hi! You forgot the wildcard '.*' (= Match zero or more instances of any single character, except newline) require ["regex"]; # rule:[test] if header :regex "from" ".*info$" {   redirect "su...@domain.com"; } With this rule, you are filtering emails from toplevel domain '*.info' or new

Re: sieve filter not working

Why do you use regex ? You can just use matches: https://p5r.uk/blog/2011/sieve-tutorial.html#matchtype (https://p5r.uk/blog/2011/sieve-tutorial.html#matchtype) On Wed, Feb 20, 2019 at 03:31 AM, subin ks via dovecot wrote: I've Dovecot and dovecot-sieve v 2.2.27 installed on a Debian 9.6. I'm

sieve filter not working

I've Dovecot and dovecot-sieve v 2.2.27 installed on a Debian 9.6. I'm trying to set a Sieve filter which will redirect all emails from `info` (i.e. .info) TLD to another email. This is the filter: require ["regex"]; # rule:[test] if header :regex "from" "info$" { redirect "su...@domain.com"; }