Re: Warning message

On May 4, 2018, at 15:41, for...@mehl-family.fr wrote: > I don't find where is the problem. Did you check line 39 of /etc/dovecot/conf.d/90-quota.conf? -- My main job is trying to come up with new and innovative and effective ways to reject even more mail. I'm up to about 97% now.

Re: expiring mail from root's Maildirs?

Can you use a set record= for root? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 On 5/4/18, 8:50 PM, "dovecot on behalf of LuKreme"

Re: expiring mail from root's Maildirs?

On May 4, 2018, at 16:07, Benny Pedersen wrote: > > outgoing mail should not be stored into root uid 0 And yet it is. > root: some-other-unix-login Root has been aliased for decades. This has no impact on where and how mutt stores the mail it sends as root out of root’s

Re: expiring mail from root's Maildirs?

LuKreme skrev den 2018-05-04 20:40: Alias the local 'root' user to another account. This is best practice anyway... +1 For incoming mail the root user is aliased, but mail sent from cron via mutt is saved in root's home folder (was in /root/sent but I did get mutt to save it in

Re: Warning message

for...@mehl-family.fr skrev den 2018-05-04 23:41: _STATUS=SENT (DELIVERED VIA DOVECOT SERVICE (DOVECONF: WARNING: /ETC/DOVECOT/CONF.D/90-QUOTA.CONF LINE 39: GLOBAL SETTING MAIL_PLUGINS WON'T CHAN._ what is the content of that line ? It is just a warning, the e-mail was delivered. its

Warning message

Hi, In my maillog I see this warning message at every reception of e-mail: _STATUS=SENT (DELIVERED VIA DOVECOT SERVICE (DOVECONF: WARNING: /ETC/DOVECOT/CONF.D/90-QUOTA.CONF LINE 39: GLOBAL SETTING MAIL_PLUGINS WON'T CHAN._ It is just a warning, the e-mail was delivered. I don't find

Re: expiring mail from root's Maildirs?

On May 4, 2018, at 10:28, Tanstaafl wrote: > On Fri May 04 2018 10:59:22 GMT-0400 (Eastern Standard Time), LuKreme > wrote: >> The mail is crontab mail that is sent out to users via mutt. What would be >> the "right” way to do this? (The cron tasks

Re: v2.2.36 release candidate released

Hello Timo, > Am 30.04.2018 um 16:11 schrieb Timo Sirainen : > > https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz > https://dovecot.org/releases/2.2/rc/dovecot-2.2.36.rc1.tar.gz.sig > > v2.2.36 is hopefully going to be the last v2.2.x release. Please test this RC >

Re: expiring mail from root's Maildirs?

On Fri May 04 2018 10:59:22 GMT-0400 (Eastern Standard Time), LuKreme wrote: > The mail is crontab mail that is sent out to users via mutt. What would be > the "right” way to do this? (The cron tasks run as root because they are > scanning system logs on behalf of certain

Re: expiring mail from root's Maildirs?

(Sorry about previous mail) > On May 4, 2018, at 07:45, Aki Tuomi wrote: > Dovecot has hardcoded root prevention. For delivery, too. So dovecot cannot expire, reindex, clean, repair, etc root mail? The mail is crontab mail that is sent out to users via mutt. What would be

Re: expiring mail from root's Maildirs?

Dovecot has hardcoded root prevention. For delivery, too. ---Aki TuomiDovecot oy Original message From: "@lbutlr" Date: 04/05/2018 15:24 (GMT+02:00) To: dovecot Subject: expiring mail from root's Maildirs? I would like to delete old

expiring mail from root's Maildirs?

I would like to delete old mail from root's sent mailbox but doveadm throws errors when I try to do this, not wanting to process root's mail at all (I am running the commands as root, naturally) # doveadm expunge -u root mailbox Sent SENTBEFORE 1-Apr-2018 doveadm(root): Error: Invalid settings

Re: Bug: Dovecot index loosing sync with FTS despite "fts_autoindex = yes"

 Bump. Can someone from dovecot dev team please respond something to my problem ? I've provided all the possible information, and if not please tell me. Or do you only provide support for your own FTS solution bundled with the paid version of dovecot-pro ? If so, you should clearly state it in the

Re: dovecot fts hangs on search

Hello Could you plese 1. send the full output of doveconf -n 2. Check the SOLR logs for any errors 3. Describe your dovecot architecture, ie. if you are running a single backend or a more complex configuration. 4. Provide a backtrace of the core dump using the instructions on