Sam Varshavchik wrote:
> Julian Mehnle writes:
12345678901234567890123456789012345678901234567890123456789012345678901234
> > Also, am I right that the various items can be split on /,\s+/, and
> > that this pattern and closing parentheses (")") won't appear in them?
> > Or do I have to handle balanced quotes and brackets/parentheses?
>
> I think that if you see the second physical line in the received header
> begin with whitespace, then a "(", and end with a ")", you can safely
> process everything inside.
>
> Unless your mailbox names include commas you won't see commas in the
> AUTH: part. Theoretically, a remote ident query could come back with
> something that contains commas.
>
> You'll probably need to be a bit smart in parsing this.
Well, the TLS field can certainly contain commas, but as far as I can see
all commas within field values are not followed by whitespace (i.e. ","
but not ", "), so I wonder if I can just split the fields on /,\s+/? Or
can ", " appear within AUTH or IDENT?
But perhaps it would be better overall to create a new (better machine
readable) authentication record type to be put into the control file. I
have never played with the guts of Courier, so if I am to create a patch
for this, it may take a while.
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
