[Date Prev][Date Next]
Jeroen Vriesman <firstname.lastname@example.org> writes:
> I have a qmail schema which has:
> attributetype ( 188.8.131.52.4.1.79184.108.40.206.1 NAME 'qmailUID'
> DESC 'UID of the user on the mailsystem'
> EQUALITY integerMatch
> SYNTAX 220.127.116.11.4.1.1418.104.22.168.36
..121.1.36 defines Numeric String (RFC 2252) so integerMatch fails. One
way is to change integerMatch to numericStringMatch (as you did), the
other to change Syntax to ..121.1.27
As you wrote there are more problems in qmail.schema:
> ... it stops complaining, but complains about the next one:
> attributetype ( 22.214.171.124.4.1.79126.96.36.199.3 NAME 'mailMessageStore'
> DESC 'Path to the maildir/mbox on the mail system'
> EQUALITY caseExactIA5Match
> SYNTAX 188.8.131.52.4.1.14184.108.40.206.15
If you change SYNTAX to ..121.26 it will pass the schemacheck.
> Why is that, adn should I just change the qmail.schema?
The reasons are that the EQUALITY-rules doesn't match the typedefs
For our use we changed the schema so it passes the schemachecks. A
slightly modified qmail.schema which passes the schemacheck can be found
- From: Jeroen Vriesman <email@example.com>