search for: deltachat

...than the S= specified >> 2) we could avoid using "S=" for the lookups and count every file >> there, including indexes and mails without S=... if we'd read >> filesizes > > > -- > With best regards, > Max Kostikov > > W: https://kostikov.co | DeltaChat: mk at eprove.net

Hello, Is there any reason why dovecot relies on S= instead of real disk size email takes? 1) compressed mails take less than than the S= specified 2) we could avoid using "S=" for the lookups and count every file there, including indexes and mails without S=... if we'd read filesizes Eample: # ls -l '1567026317.M331058P4751.testing.server.com,S=3086,W=3148:2,S' -rw-------

...ed: read() failed: dot-input stream ends without '.' line (last sent=mail_request (EOL), last recv=mail) The question is it possible to have password encrypted user keys with Dovecot dbsync replication or we found a new bug? -- With best regards, Max Kostikov W: https://kostikov.co | DeltaChat: mk at eprove.net

...> > 1) compressed mails take less than than the S= specified > 2) we could avoid using "S=" for the lookups and count every file > there, including indexes and mails without S=... if we'd read > filesizes -- With best regards, Max Kostikov W: https://kostikov.co | DeltaChat: mk at eprove.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: <https://dovecot.org/pipermail/dovecot/attachments/20200208/03d63359/attachment.sig>

...t;> 2) we could avoid using "S=" for the lookups and count every file >>> there, including indexes and mails without S=... if we'd read >>> filesizes >> >> -- >> With best regards, >> Max Kostikov >> >> W: https://kostikov.co | DeltaChat: mk at eprove.net