From: Nicolas Riendeau (no email)
Date: Wed Aug 11 2004 - 19:08:38 EDT
Hi Mr Venema!
Wietse Venema wrote:
> Victor Duchovni:
>
>>>What is a robust solution? Ideally the MTA operator simply specifies
>>>a text file without any MIME crap, and Postfix does the right thing.
>>
>>The text file if not MIME encoded cannot specify its character-set,
>>so this would be a separate configuration parameter:
>>
>> bounce_template_file = /etc/postfix/bounce_template
>> bounce_template_charset = us-ascii
>
>
> That is worse than having to specify it in the "sorry" file.
Why? These parameters are mostly "set & forget", once you set these to the proper
values you don't need to mess with them again.
> I'm thinking that only aneasy to use solution will be useful.
I'm not saying that to you they might seem simpler but to an inexperienced
admin, I'm not sure what you are proposing is simpler.
> This is the simplest possible template file. It contains only
> text and no MIME information.
>
> +----------
> |bla bla bla bla bla
> |la bla bla bla bla
> |blah bla bla bla bla
> |la bla bla bla bla
> +----------
>
> It is's all 7bit, slap on default headers, transform into
> quoted-printable and deliver:
>
> +----------
> |Content-Type: text/plain
> |Content-Transfer-Encoding: quoted-printable
> |
> |bla bla bla bla bla
> |la bla bla bla bla
> |blah bla bla bla bla
> |la bla bla bla bla
> +----------
With the charset set value specified as a main.cf parameter, if it is not set this
is what would be produced minus the "Content-Transfer-Encoding: quoted-printable" which
would not be necessary I believe.
>
> If it's not 7bit, the MTA operator has to supply charset info.
>
> Here's a template file with 8-bit content:
>
> +----------
> |Content-Type: ignored/ignored; charset=STUFF; ignored...
> |[other headers will be ignored]
This syntax might be a little too complex for inexperienced admins.
This would alos require parsing the template file (and not simply substuting the content of
the macros by the appropriate values) and might limit the kind of validation we could do on
them.
What do we do if they are missing?
As I said above setting them (charset) in main.cf would mostly be a "set & forget" operation, once you
set them you don't need to mess with them again and it would be possible to do more validations
based on them.
One such validation could be to reject the template if it contains 8-bit data and no charset, etc...
Let me know...
Nick
|
|
|