‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:05 PM, Aki Tuomi
wrote:
> Did you add sufficient flags to rsync to retain file mtime and ctime? These
> are used to determine the mail saved date.
>
> Aki
I have been using "rsync -av". As far as I know the "-a or --archive"
> On 17 Mar 2020, at 17.27, mabi wrote:
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 3:57 PM, Sami Ketola
> wrote:
>
>> Since you were migrating dovecot->dovecot I would have just used Dsync.
>
> Thanks for the hint about dsync. It seems quite complex to setup and to
On Tue, 17 Mar 2020 at 15:47, Sami Ketola wrote:
>
>
>
> > On 17 Mar 2020, at 16.42, Philip Colmer wrote:
> >
> > doveadm fetch -u local-finance-support "mailbox date.saved" UID 37
> >
> > mailbox: INBOX
> > date.saved: 2020-03-17 14:34:12
> >
> > Why on earth is dovecot showing today's date for
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 3:26 PM, Sami Ketola wrote:
> So your rsync did not preserve mail object ctimes. Dovecot uses that for
> internal date if correct value is not in dovecot.index.cache.
Oh I see, so that's quite unfortunate that rsync does not preserve
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 3:57 PM, Sami Ketola wrote:
> Since you were migrating dovecot->dovecot I would have just used Dsync.
Thanks for the hint about dsync. It seems quite complex to setup and to use.
Isn't there an easier method? What about tar'ing the
> On 17 Mar 2020, at 16.42, Philip Colmer wrote:
>
> doveadm fetch -u local-finance-support "mailbox date.saved" UID 37
>
> mailbox: INBOX
> date.saved: 2020-03-17 14:34:12
>
> Why on earth is dovecot showing today's date for that message? What
> have I misunderstood or misconfigured?
> On 17 Mar 2020, at 16.43, mabi wrote:
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 3:26 PM, Sami Ketola
> wrote:
>
>> So your rsync did not preserve mail object ctimes. Dovecot uses that for
>> internal date if correct value is not in dovecot.index.cache.
>
> Oh I
dovecot 2.2.33.2 (d6601f4ec) on Ubuntu 18.04
The recent announcement that expunge is going to be deprecated and
that autoexpunge should be used instead reminded me that my recent
switch over to autoexpunge is not working.
There has been an active discussion today about getting expunge
working so
> On 17/03/2020 13:44 mabi wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 11:46 AM, Aki Tuomi
> wrote:
>
> > Try`doveadm -Dv expunge -u username\\@domain.com mailbox INBOX savedbefore
> > 90`
> >
> > It might give insight what goes wrong.
>
> Here would be
> On 17/03/2020 13:55 mabi wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 12:45 PM, Aki Tuomi
> wrote:
>
>
> > `doveadm search -u username@domain.com mailbox INBOX savedbefore 90`
> >
> > return any mails?
>
> No it does not return any mails, although
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 2:00 PM, Aki Tuomi
wrote:
> `sudo doveadm search -u admin\\@domain.tld HEADER MESSAGE-ID
> "sawh8n6hdrb...@mgw.subdom.domain.tld"`
Ah yes, I had to remove the "user" part of course... Thanks!
After running this command, the only
> On 17 Mar 2020, at 15.40, mabi wrote:
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 2:18 PM, Aki Tuomi
> wrote:
>
>> So doveadm fetch -u admin\\@domain.tld "mailbox date.saved" UID 130863
>>
>> Aki
>
> This is the ouput:
>
> mailbox: INBOX
> date.saved: 2020-01-16
> On 17/03/2020 12:42 mabi wrote:
>
>
> Hello,
>
> I have migrated my mailbox server from Dovecot 2.1.7 (Debian 7) to Dovecot
> 2.3.4 (Debian 10) and have a crontab setup in root to daily delete all mails
> in the INBOX of a specific user which are older than 90 days like this:
>
>
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 11:46 AM, Aki Tuomi
wrote:
> Try`doveadm -Dv expunge -u username\\@domain.com mailbox INBOX savedbefore 90`
>
> It might give insight what goes wrong.
Here would be the output but I still can't see where the problem is:
Debug:
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 12:45 PM, Aki Tuomi
wrote:
> `doveadm search -u username@domain.com mailbox INBOX savedbefore 90`
>
> return any mails?
No it does not return any mails, although there are mails older than 90 days in
the INBOX.
> How did you do
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:10 PM, mabi wrote:
> I have been using "rsync -av". As far as I know the "-a or --archive"
> parameter should preserve almost everything, at least the rsync man page says
> that.
If that is of any help I did a "stat" on one of the
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:19 PM, Aki Tuomi
wrote:
> Can you try`doveadm fetch -u user date.saved UID mail-uid` To see if it
> matches this?
How can I find out the "mail-uid" of this specific message? Is that the
"Message-ID" header of that particular mail?
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 2:18 PM, Aki Tuomi
wrote:
> So doveadm fetch -u admin\\@domain.tld "mailbox date.saved" UID 130863
>
> Aki
This is the ouput:
mailbox: INBOX
date.saved: 2020-01-16 18:21:53
I think that might be the date where I have done the
> On 17/03/2020 14:15 mabi wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 1:10 PM, mabi wrote:
>
> > I have been using "rsync -av". As far as I know the "-a or --archive"
> > parameter should preserve almost everything, at least the rsync man page
> > says
Hello,
I have migrated my mailbox server from Dovecot 2.1.7 (Debian 7) to Dovecot
2.3.4 (Debian 10) and have a crontab setup in root to daily delete all mails in
the INBOX of a specific user which are older than 90 days like this:
/usr/bin/doveadm expunge -u username\@domain.com mailbox INBOX
> On 17/03/2020 14:32 mabi wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 1:19 PM, Aki Tuomi
> wrote:
>
> > Can you try`doveadm fetch -u user date.saved UID mail-uid` To see if it
> > matches this?
>
> How can I find out the "mail-uid" of this specific
> On 17/03/2020 14:52 mabi wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 1:38 PM, Aki Tuomi
> wrote:
>
> > If you have message-id you can use
> >
> > `doveadm search -u user HEADER MESSAGE-ID "messageid"` to find out the UID.
>
> I tried the following
‐‐‐ Original Message ‐‐‐
On Tuesday, March 17, 2020 1:38 PM, Aki Tuomi
wrote:
> If you have message-id you can use
>
> `doveadm search -u user HEADER MESSAGE-ID "messageid"` to find out the UID.
I tried the following command:
sudo doveadm search -u user admin\@domain.tld HEADER
> On 17/03/2020 15:16 mabi wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Tuesday, March 17, 2020 2:00 PM, Aki Tuomi
> wrote:
>
> > `sudo doveadm search -u admin\\@domain.tld HEADER MESSAGE-ID
> > "sawh8n6hdrb...@mgw.subdom.domain.tld"`
>
> Ah yes, I had to remove the "user" part of
With these planned changes, you mention they will be removed from
'core', so is the intention to allow more of these legacy plugins to
more to their own repo's for those that might still want to use them?
Eg, more in the the path of plug-in architecture? Just curious for
clarity.
Oh, and
Hello Rupert,
Note the following - using X.509 certificates is an excellent idea for
preventing password guessing, but you need to realize one very important
thing before switching to X.509 certificate authentication. In TLSv<=1.2
the TLS handshake leaks the client X.509 certificate. Simply start
> Password schemes: HMAC-MD5, RPA, SKEY, PLAIN-MD4, LANMAN, NTLM, SMD5
The web is flooded with plain text passwords and hashed passwords harvested
from hacked servers.
Dovecot stores passwords with the same scheme used for client authentication.
Therefore, we use crammd5/hmac-md5. It does not
Those plugins can be resurrected with simple `git revert`.
Are you planning on open sourcing your client id authetication plugin?
Aki
On 18/03/2020 01:44 Michael Peddemors <
mich...@linuxmagic.com> wrote:
On 18/03/2020 00:06 Rupert Gallagher wrote:
> Password schemes: HMAC-MD5, RPA, SKEY, PLAIN-MD4, LANMAN, NTLM, SMD5
The web is flooded with plain text passwords and hashed passwords harvested from hacked servers.
Dovecot
On 17/03/20 7:50 pm, Aki Tuomi wrote:
Dovecot is now a nearly 20 year old product, and during that time it has
accumulated many different features and plugins in its core repository.
We are starting to gradually remove some of these parts, which are unused,
untested or deprecated.
We will
Hi!
Dovecot is now a nearly 20 year old product, and during that time it has
accumulated many different features and plugins in its core repository.
We are starting to gradually remove some of these parts, which are unused,
untested or deprecated.
We will provide advance notification before
I haven’t seen this term on the mailing list for a while. I don’t know
if you’re tracking this somewhere, in any case I’m curious if you are
still planning to add support for SMTPUTF8.
Cheers,
Hi!
Dovecot is now a nearly 20 year old product, and during that time it has
accumulated many different features and plugins in its core repository.
We are starting to gradually remove some of these parts, which are unused,
untested or deprecated.
We will provide advance notification before
33 matches
Mail list logo
