Mailscanner converting HTML messages with FORM tags
David Lee
t.d.lee at DURHAM.AC.UK
Fri Oct 24 19:33:32 IST 2003
On Fri, 24 Oct 2003, Kevin Spicer wrote:
> On Fri, 2003-10-24 at 18:27, Lancaster, David Matthew wrote:
>
> Quoting David Lee <t.d.lee at DURHAM.AC.UK>:
>
> > > > > >Allow Form Tags = { yes | convert | no}
> > > > > >Allow Object Codebase Tags = { yes | convert | no}
> > > > > >Allow IFrame Tags = { yes | convert | no}
> > > > > >
>
> I have one criticism of that - it would break existing configurations
> (where one has Allow xxxx Tags = yes, Convert Dangerous HTML to text =
> yes for example). Julian usually goes to pains to ensure that changes
> maintain the existing behaviour for existing setting wherever possible.
>
> I would think a better solution (from this point of view) would be to
> extend the options for Convert Dangerous HTML to Text to include
> keywords e.g.
>
> yes
> objectcodebase
> iframe
> form
> no
>
> and maintain the existing behavior for Allow xxx Tags. You could allow
> multiple keywords on the line, for example
>
> Convert Dangerous HTML to Text = iframe objectcodebase
>
> And keep 'yes' as a synonym for 'objectcodebase iframe form' with 'no'
> or no values maintaining the existing behaviour for 'no'.
Thanks, Kevin.
My original email was written with enthusiastic zeal. The "cold light of
day" this morning brought me similar realisations to the points you raise
(maintaining compatibility of the "conf" file) and defining the
interactions for my (supposedly) "cleverer" ideas about conversion types
(convert-tag v. convert-all).
I certainly agree about the principle of the importance of "conf"-file
maintenance across releases. And I think I tend to agree with your
revision of the detail.
Any other comments, anyone?
--
: David Lee I.T. Service :
: Systems Programmer Computer Centre :
: University of Durham :
: http://www.dur.ac.uk/t.d.lee/ South Road :
: Durham :
: Phone: +44 191 334 2752 U.K. :
More information about the MailScanner
mailing list