similar to: expiring mail from root's Maildirs?

On May 4, 2018, at 10:28, Tanstaafl <tanstaafl at libertytrek.org> wrote: > On Fri May 04 2018 10:59:22 GMT-0400 (Eastern Standard Time), LuKreme > <kremels at kreme.com> 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

On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote: > >> And yet it is. > > in muttrc you miss ~ or $(HOME)/something No. >> 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 crontab. > > root user can read mail files for all unix users, thats your fail, maybe

(Sorry about previous mail) > On May 4, 2018, at 07:45, Aki Tuomi <aki.tuomi at dovecot.fi> 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 the "right? way to do this? (The cron tasks run as root because they are scanning

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 /root/Maildir/.Sent/ instead. outgoing mail should not be stored into

> On 05 May 2018 at 20:14 "@lbutlr" <kremels at kreme.com> wrote: > > > On 2018-05-05 (06:52 MDT), Benny Pedersen <me at junc.eu> wrote: > > > >> And yet it is. > > > > in muttrc you miss ~ or $(HOME)/something > > No. > > >> Root has been aliased for decades. This has no impact on where and how > >> mutt

What happens if you put the following in /root/.muttrc: Set record='/file/to/put/mail/in' ? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx at gmail.com US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 ?On 5/5/18, 12:15 PM, "dovecot on behalf of @lbutlr" <dovecot-bounces at dovecot.org on behalf of

On May 4, 2018, at 16:07, Benny Pedersen <me at junc.eu> 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 crontab. -- My main job is trying to come up with new and innovative and effective ways to

On Fri May 04 2018 10:59:22 GMT-0400 (Eastern Standard Time), LuKreme <kremels at kreme.com> 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 users and those scans cannot be run as the user.) Alias the local 'root' user to

> And yet it is. in muttrc you miss ~ or $(HOME)/something >> 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 crontab. root user can read mail files for all unix users, thats your fail, maybe crontab miss $(HOME) where it matters, but if it have and you start mutt as root

On 2018-05-05 (11:19 MDT), Larry Rosenman <larryrtx at gmail.com> wrote: > > What happens if you put the following in /root/.muttrc: > Set record='/file/to/put/mail/in' I get a mail still owned by root. -- May you live in interesting times

Hi, i am running basically this from cron: /usr/bin/doveadm -v expunge -u * mailbox INBOX.Spam SENTBEFORE 90d /usr/bin/doveadm -v expunge -u * mailbox INBOX.Trash SENTBEFORE 90d /usr/bin/doveadm -v expunge -u * mailbox INBOX.Junk SENTBEFORE 90d Now i am experiencing that the first line e.g. expunging INBOX.Spam returns the error code 68. No syslog/Output whatsoever. I tried running with -vvv -D

Hi Aki, On Wed, Sep 06, 2017 at 11:26:30AM +0300, Aki Tuomi wrote: > On 05.09.2017 14:39, Florian Lohoff wrote: > > Hi, > > i am running basically this from cron: > > > > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Spam SENTBEFORE 90d > > /usr/bin/doveadm -v expunge -u * mailbox INBOX.Trash SENTBEFORE 90d > > /usr/bin/doveadm -v expunge -u * mailbox

Affected product: Dovecot IMAP Server Internal reference: DOV-5320 Vulnerability type: Improper Access Control (CWE-284) Vulnerable version: 2.2 Vulnerable component: submission Report confidence: Confirmed Solution status: Fixed in main Researcher credits: Julian Brook (julezman) Vendor notification: 2022-05-06 CVE reference: CVE-2022-30550 CVSS: 6.8

Affected product: Dovecot IMAP Server Internal reference: DOV-5320 Vulnerability type: Improper Access Control (CWE-284) Vulnerable version: 2.2 Vulnerable component: submission Report confidence: Confirmed Solution status: Fixed in main Researcher credits: Julian Brook (julezman) Vendor notification: 2022-05-06 CVE reference: CVE-2022-30550 CVSS: 6.8

Thank you, Sami. I've made that change. Regards Philip On Mon, 17 Feb 2020 at 10:50, Sami Ketola <Sami.Ketola at open-xchange.com> wrote: > Hi, > > how about switching to use autoexpunge? > > https://wiki.dovecot.org/MailboxSettings > > Sami > > > On 17 Feb 2020, at 11.01, Philip Colmer <philip.colmer at linaro.org> wrote: > > We're

is there a way to run this command but with exception to not delete the FLAGGED email? doveadm expunge -u user at email.com mailbox Inbox SENTBEFORE 90d -- Sent from: http://dovecot.2317879.n4.nabble.com/

Hi, Sorry for the delay in replying. Been having a few mail problems ironically! Gmail smtp server stopped working! On 23/09/2019 4:13 PM, Bernd Petrovitsch via dovecot wrote: > It's not directly a solution within dovecot but "fail2ban" exists. Yes, I have fail2ban, but that bans based on IP address. And most mail password attacks these days are distributed, and although

We're using dovecot on a help desk ticketing system. The system doesn't perform any cleanup of IMAP mailboxes so we have a regular cronjob doing this: /usr/bin/doveadm flags add -A '\Deleted' SEEN SENTBEFORE 12w && /usr/bin/doveadm expunge -A DELETED MAILBOX '*' Recently, doveadm has been reporting this: doveadm(nobody): Error: User initialization failed:

Hi, im wondering if it's possible to store old messages in a compressed mdbox on alternate storage. The main storage is uncompressed mdbox. I tried something like: doveadm -Dv -o "plugin/zlib_save=gz" altmove -u testuser sentbefore 8d Could someone tell me if it's possible and give me a hint how this can be done? I tried this with dovecot-2.2 Claus

Hi all, I have some questions about hardlinks, alternate storage and compression. I already scanned the list for related information and I have an idea of how things works, but I would like to have a definite answer. System spec: - CentOS 6.6 x64 - dovecot-2.0.9-8.el6_6.4.x86_64 RPM package/version - sdbox mail store 1) About hardlinks: when sending the same message to two different