Am Mittwoch, 27. August 2003 08:09 schrieb Luca Berra:
> On Wed, Aug 27, 2003 at 07:26:40AM +0200, Martin Fahrendorf wrote:
> >Am Montag, 25. August 2003 22:20 schrieb Buchan Milne:
> >> /^Content-(Type|Disposition):.*(file)?name=.*\.(asd|bat|chm|cmd|dll|exe|
> >>hlp
> >>
> >>|hta|jse|lnk|ocx|pif|scr|shb|shm|shs|vb|vbe|vbs|vbx|vxd|wsf|wsh)/REJECT
> >>
> >> Sorry, we do not accept .${3} file types.
> >> (all on one line)
> >
> >With postfix this is not header_checks but mime_header_checks.
>
> mime_header_checks defaults to $header_checks in postfix 2.0
> and i still think is useful to have all those checks in one place.

jep, that's right. I have header and mime_header in different files.

...

> >And, like the chroot stuff, there are many users who will be lost, if they
> > do a little change and nothing is working any more. And the body_* and
> > header_
>
> dunno 'bout the chroot: it is well documented and if users do changes
> when they have no clue they will get it wrong with or without chroot.

Jeah, it is well documentated; but how many people do you know reading 
docimentations? They claim that this and that is not self-explaining and are 
lamment about the missing function (I read the postfix mailinglist since 
about four years and it is full of this and that does not work -- the answer 
often ist: disable chroot).

I can handle the chroot stuff very well, but I know (almost) how it works.

>
> >check stuff can not be bypassed.
>
> what do you mean 'can not be bypassed', postconf is your friend.

you can not define a user x for which postfix does not use the check_* stuff. 
You can enable it for every user or not. That do i mean with bypass.

>
> regards,
> L.

Martin
-- 
------------------------------------------------------------
H E L I X Gesellschaft f�r Software & Engineering mbH
------------------------------------------------------------
Hanauer Landstrasse 52              Telefon (069) 4789 35-30
D-60314 Frankfurt am Main           Telefax (069) 4789 35-44
------------------------------------------------------------
http://www.helix-gmbh.net                [EMAIL PROTECTED]
------------------------------------------------------------

Attachment: pgp00000.pgp
Description: signature

Reply via email to