Upgrade to 3.2.2 and sieve
Hi all,
I'm having trouble upgrading version 3.0.13 to 3.2.2. I am running two
systems, one of them is a replica. I upgraded on the replica first and
had issues with "intermediate" mailboxes being created which seems to be
expected if I read the release notes right.
Now I'm seeing errors on the replica when users update their script on
the master, they do this via horde's ingo module. On the replica I get
errors like
sieve_rebuild: [path to script] parse failed: script errors:#015#012line
5: header 'resent-from': not a valid header for an address test
These lines are generated by ingo when entering whitelist addresses and
3.2.2 doesn't like them
if address :all :comparator "i;ascii-casemap" :is ["From", "Sender",
"Resent-From"] "thisaddr...@ourdomain.xyz" {
I'm not familiar with the sieve specification, is this a problem in
cyrus or should ingo handle things differently ?
Regards,
Stephan
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Upgrade to 3.2.2 and sieve
Stephan écrivait (wrote) : > sieve_rebuild: [path to script] parse failed: script errors:#015#012line > 5: header 'resent-from': not a valid header for an address test I had the same error with a 2.5 to 3.0 migration. Corrected with 'rfc3028_strict: 0' : rfc3028_strict: 1 If enabled, Sieve will be strict (per RFC 3028) with regards to which headers are allowed to be used in address and envelope tests. This means that only those headers which are defined to contain addresses will be allowed in address tests and only "to" and "from" will be allowed in envelope tests. When disabled, ANY grammatically correct header will be allowed. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Newly arrived mail is marked as "read"
I'm in the process of testing the upgrade from a CentOS 6 box running 2.3.16 to a CentOS 8 box running 3.0.7. The upgrade has been less troublesome than expected, but I'm seeing a strange problem with newly received mail being marked as "read" even though they have not been opened by the client. This is the case for both mail sent locally as well as mail received externally (Gmail). Can anyone point me in the right direction on where to look to fix this? Thanks. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Upgrade to 3.2.2 and sieve
Am 26.06.20 um 14:18 schrieb Jean Charles Delépine: Stephan écrivait (wrote) : sieve_rebuild: [path to script] parse failed: script errors:#015#012line 5: header 'resent-from': not a valid header for an address test I had the same error with a 2.5 to 3.0 migration. Corrected with 'rfc3028_strict: 0' : rfc3028_strict: 1 If enabled, Sieve will be strict (per RFC 3028) with regards to which headers are allowed to be used in address and envelope tests. This means that only those headers which are defined to contain addresses will be allowed in address tests and only "to" and "from" will be allowed in envelope tests. When disabled, ANY grammatically correct header will be allowed. Thank you ! rfc3028_strict was enabled here in 3.0.13 and the scripts were accepted so I guess it must be one of the sieve bug fixes and features mentioned in the 3.2 release notes. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
