I’m using dovecot to provide encrypted IMAP e-mail support for remote clients
and it’s working great. However, I also need to set up a webmail front-end
(Roundcube), which I’m hoping to have use unencrypted IMAP on port 143 (as only
port 993 is available externally).
The problem I’m running int
. This would be much
easier for a script inspecting user home directories, as for now my alternative
is to use the wildcard match to get a list of names, then call dovecot user -f
home for each one to get their home location, which isn’t nearly as nice
=)
- Haravikk
So I’m looking at setting up some house-keeping for my dovecot mailboxes,
specifically deleting messages in trash, spam etc., by deleting Seen messages
older than X days.
In order to protect against the edge case of a user reading a message right
before the deletion task however I’d like to do
> On 28 Jan 2016, at 16:55, Robert Schetterer wrote:
>
> Am 28.01.2016 um 16:51 schrieb Haravikk:
>> I’ve tried sieve, but it can’t set this flag.
>
> imapflags muss be added in 90-sieve.conf
Oh I can set other flags, but \Recent seems to be specifically disallowed in
t
So as part of my daily mailbox maintenance I have the following command:
doveadm expunge -A DELETED
i.e- I’m only expunging messages that have been specifically marked as deleted.
I also only do this *after* running doveadm purge, as this means that there is
at least a 24 hour window be
> On 27 Jan 2016, at 21:55, Axel Luttgens wrote:
>
> Hello Haravikk,
>
> Perhaps could you try to devise an exception based on one (or more) "remote"
> section(s), as in:
>
> remote ip.of.webmail.server {
> ssl_verify_client_cert = n
> On 29 Jan 2016, at 14:29, Timo Sirainen wrote:
>
> \Recent flag is special and you can't add/remove it. It's not even internally
> stored like regular flags.
Are you certain? The following commands seem to work just fine:
doveadm flags add -A ‘\Recent’ OLD UNSEEN
doveadm sea
the settings
in the right parts of master.cf instead of main.cf), allowing me to restrict
client certificate verification to port 587 (I don’t accept port 465) without
interfering with incoming mail server connections on port 25.
> On 29 Jan 2016, at 13:00, Haravikk wrote:
>
>>
this would involve exactly, but if it could avoid the need for
patching it might be a nice way to achieve the same goal.
> On 2 Feb 2016, at 12:44, Timo Sirainen wrote:
>
>
>> On 02 Feb 2016, at 14:19, Timo Sirainen wrote:
>>
>> On 02 Feb 2016, at 13:09, Haravikk
> On 7 Feb 2016, at 02:50, Tom Johnson wrote:
>
> I have some users where I'd like to expunge their mail at different times.
>
> For example, I may have some users who I want to expunge everything from
> every folder at 30 days.
>
> Others where I'd like to expunge everything at 90 days.
>
> On 7 Feb 2016, at 10:17, Haravikk wrote:
>
>
>> On 7 Feb 2016, at 02:50, Tom Johnson wrote:
>>
>> I have some users where I'd like to expunge their mail at different times.
>>
>> For example, I may have some users who I want to expunge
So I have a script for handling my specific archive and expunge needs, but it’d
be nice to be able to track how many messages are being affected.
Currently I’m doing it by firing the same search queries into doveadm search
and counting the lines of the result with wc -l, but that’s not a very pr
Not sure how you’re seeing such a high ratio; I tried the same commands on my
system (thanks for these btw) and my savings from compression are around 5% =D
That said I’m dealing with a much smaller volume (3gb) and I’ve only identified
a half dozen or so attachments that don’t have some kind of
13 matches
Mail list logo
