Files
Mechiel Lukkien 90fe36b568 add mechanism to work around imap client protocol incompatibilities
with a per-account setting to disable imap extensions (capabilities) for
sessions of that account.

prompted by microsoft office 365, which enables the "UIDONLY" extension
(indicating it limits itself to UID-using commands and promising to
refrain from using commands based on message sequence numbers (MSN)),
but then attempts to execute an old fashioned MSN-based "FETCH" command.

users can change the disabled capabilities for their account themselves,
requiring no admin intervention to work around the problems, and without
affecting any other accounts/users of the system. only the account's
imap connections are affected.

we won't implement workarounds based on client "ID", as forbidden by its
RFC.

uidonly-related symptoms reported by FLuX on matrix, thanks!

see issue #388 for more information.
2025-09-29 16:38:37 +02:00

49 lines
939 B
Plaintext

Domains:
mox.example:
LocalpartCaseSensitive: false
Accounts:
mjl:
Domain: mox.example
Destinations:
[email protected]: nil
[email protected]:
Mailbox: Other/Sub1
[email protected]:
Rulesets:
-
VerifiedDomain: test.example
Mailbox: Other/Sub2/SubA
-
VerifiedDomain: list.example
ListAllowDomain: list.example
Mailbox: List
""@mox.example: nil
mó[email protected]: nil
JunkFilter:
Threshold: 0.95
Params:
Twograms: true
MaxPower: 0.1
TopWords: 10
IgnoreWords: 0.1
other:
Domain: mox.example
Destinations:
[email protected]: nil
limit:
Domain: mox.example
Destinations:
[email protected]: nil
QuotaMessageSize: 1
disabled:
Domain: mox.example
LoginDisabled: testing
Destinations:
[email protected]: nil
imapcaps:
Domain: mox.example
Destinations:
[email protected]: nil
IMAPCapabilitiesDisabled:
- UIDONLY