similar to: Bug: rsync erroneously changes modification time

How exactly does rsync determine that the copy has the incorrect timestamp and not the source file? Does it assume that the copy must be incorrect or are there other criteria that have to be considered? Quoting Kevin Korb via rsync <rsync at lists.samba.org>: > Whenever you use --times (included in --archive) rsync will fix > incorrect time stamps. The only thing --size-only is

Whenever you use --times (included in --archive) rsync will fix incorrect time stamps. The only thing --size-only is doing is keeping the incorrect data instead of replacing it. The purpose of these options is to "fix" a copy done in a way that did not preserve timestamps but the data is known to have not changed. These options allow rsync to correct the incorrect timestamps without

Help? ntfy-mailto.c: In function ?ntfy_mailto_send?: ntfy-mailto.c:505:5: error: too few arguments to function ?smtp_address_create_from_msg_temp? sieve_get_postmaster(senv)); ^ In file included from ./../../../sieve-types.h:5:0, from ./../../../sieve-common.h:7, from ntfy-mailto.c:30: /usr/local/include/dovecot/smtp-address.h:101:5: note:

Pigeonhole download page has links for extdata plugin up to v0.4 but nothing more and no link to the master repository https://pigeonhole.dovecot.org/download.html I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. Thanks for helping ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's

During yum upgrade a couple days ago, I saw this: Cleanup : kernel-3.10.0-229.20.1.el7.x86_64 35/64 warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.softdep: remove failed: No such file or directory warning: file /lib/modules/3.10.0-229.20.1.el7.x86_64/modules.devname: remove failed: No such file

thanks you AKi for alway responding! >> Pigeonhole download page has links for extdata plugin up to v0.4 but >> nothing more and no link to the master repository >> >> https://pigeonhole.dovecot.org/download.html >> >> I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. > > Seems to need v0.5 for it. What are you using it for? For a

I find mailbox_list_index on some doc pages, but not explaination to find what precisely it does? Would someone care to mind explain? Thank you! ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk

Thanks Joseph, Aki, but something missing from upgrade document, where does the dh param file go? I located ssl-parameters.dat so I will put it there. Quoting Joseph Tam <jtam.home at gmail.com>: > On Fri, 22 Jun 2018, Joseph Tam wrote: > >> However, recent advances make this condition obsolete [*] and not >> really safer, so a much faster way to generate a DH key is

Hello, I am using version 2.2.31 (65cde28) on an Ubuntu 16.04 VPS. I am attempting to setup a mail server using a flat file system as an experiment. I am able to send e-mail from external domain names and the messages land in my /var/mail/vmail/domain/user/ directories. I am trying to setup Thunderbird as an MUA using the information I generated on my VPS namely the IMAP server, username

hi sorry if question was asked already. Was reading https://wiki2.dovecot.org/Upgrading/2.3 first I'm confused on diffie hellman parameters file. I never set up ssl-parameters.dat before (should i have? do I have one that was automatically made for me by dovecot?) Do I need to make a fresh dh.pem? The upgrade doc tells how to convert ssl-parameters.dat but how to make a new one? other

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will need this release for Dovecot v2.3.2, because the previous v0.5.1 release will not work. No changes were performed since the release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release

Hello Dovecot users, Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will need this release for Dovecot v2.3.2, because the previous v0.5.1 release will not work. No changes were performed since the release candidate. Much like version 0.4.24 for Dovecot v2.2, this release consists mostly of fixes that accumulated over the last few months. Beyond that, this release

Aki really thanks for reply,, I hope for continue the conversation, >> Do you have advice about Dovecot plugins for mail encryption: >> >> https://wiki2.dovecot.org/Plugins/MailCrypt >> https://0xacab.org/riseuplabs/trees >> >> I like NaCL based encryption but the MailCrypt plugin is better >> because it's maintained by Dovecot developers (is this

Op 30/06/2018 om 07:19 schreef tai74 at vfemail.net: > will you be updating extdata plugin please? Yeah, I'll be giving that a look somewhat soon. Regards, Stephan. > > > Quoting Stephan Bosch <stephan at rename-it.nl>: > >> Hello Dovecot users, >> >> Here's the Pigeonhole release that goes with Dovecot v2.3.2. You will >> need this release

Hai, Do you have advice about Dovecot plugins for mail encryption: https://wiki2.dovecot.org/Plugins/MailCrypt https://0xacab.org/riseuplabs/trees I like NaCL based encryption but the MailCrypt plugin is better because it's maintained by Dovecot developers (is this correct?) Hard to understand MailCrypt docs so may I ask, may I provide per user encryption? I don't like global

On Fri, 22 Jun 2018, Aki Tuomi wrote: >> Do I need to make a fresh dh.pem? The upgrade doc tells how to convert >> ssl-parameters.dat but how to make a new one? > > ... or you can make a fresh one using openssl > gendh 4096 > dh.pem This also works openssl dhparam -out dh.pem 4096 > Note that this will require quite a lot of entropy, so you should > probably

Hai, I found VarExpandCrypt plugin but not sure the usecase? Somewhere is more documentation for it? https://wiki2.dovecot.org/Plugins/VarExpandCrypt ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial

Quoting Alexander Dalloz <ad+lists at uni-x.org>: > Am 23.07.2017 um 17:50 schrieb david.madman2 at vfemail.net: >> My /var/log/mail.log shows: >> >> Jul 22 18:40:48 www dovecot: auth: Error: >> passwd-file(test at domain.com,46.xxx.xxx.xxx,<wZoHUuxU6IAu9j4y>): >> Password data is not valid for scheme SHA256: Input length isn't >> valid

Dear developers, In the rsync's manpage, there is a line describing the "archive mode" option: -a, --archive archive mode; equals -rlptgoD (no -H,-A,-X) Archive mode means that all data is backed up sensibly while the same doesn't apply for all metadata (hence the mentioned -H, -A and -X options). There is another similar "special file system option" as

How do I make rsync ignore and not report or update certain parts of the [l]stat(2) struct or checksum when selecting which items to report or update in a hierarchy? For example, I want to run: rsync -Haxi --delete /hier1/ /hier2/ and have it NOT do anything if say ONLY the modtime differs. Leaving out or in the --times [-t] option from the expansion of -a to -rlptgoD obviously does not do this.