Gérald,

Sorry for a late reply.

> One of our clients asked us for Amavisd-new modifications  and we would
> like to have your (users and developpers) comments  on the usefullness
> of the resulting patches for the project, here they are:
>
> 1) addition of a configurable option to allow accentuated characters in
> mail subjects (for faulty clients)  while BadHeader checking is still
> active otherwise

Might be useful, although turning off bad header checks altogether
is not too bad if non-encoded characters in headers are really acceptable.
I'm not opposed to this idea.

Note that accentuated characters in UTF-8 produce quite some binary
gibberish. Eventually these clients producing such invalid header fields
need to be fixed one way or another. If your mailer won't reject them,
some other recipient's mailer will, and users won't stop complaining.

> 2) distinctive logs and quarantine for banned content (banned_extension,
> banned_mimetype etc.)

Could be useful.

> 3) separation of encrypted and signed messages filter with respective
> logs and quarantine

I don't see much use for it, although some customer may see it otherwise.

Btw, the 2.4.0 will have an ability to dynamically switch syslog ident, 
facility and priority, thanks to moving these settings from global settings
to policy-banks. Extending this mechanism might assist in your needs,
if logging different things to separate files would be desired.

> 4) quarantine for the size filter

I don't see much point in accepting a large message, then not delivering
it for being too, large but still preserving it. Size limitation is
meaningful at the MTA level to prevent abuses and provide some sane upper 
limit for disk usage. MTA can do it 'the right way', a huge mail will not 
even be stored to disk. Once we are past this point and message has been 
accepted, the local delivery agent can still bounce it due to quota and size
restrictions on a mailbox. I don't see much point in quarantining large 
messages, these should either be delivered or bounced.

The mail reason why amavisd-new offers size limits is for those few,
which insist on using amavisd-new as a pre-queue content filter
(which is not advised and not really supported - if it works, fine,
otherwise don't complain).

  Mark


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to