Thanks Mark, your explanations helps me a lot! Daniel! > ----- Original Message ----- > From: "Mark Martinec" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Thursday, November 29, 2007 10:14 PM > Subject: Re: [AMaViS-user] whitelist doubts > > >> Daniel, >> >>> amavisd.conf: >>> @whitelist_sender_maps = >>> read_hash('/var/spool/amavisd/white_sender.lst'), >>> [qw(example.com [EMAIL PROTECTED])], ]; >>> In /var/spool/amavisd/white_sender.lst on entry per line: >>> [EMAIL PROTECTED] works fine! >>> >>> Its possible use especial characters in this .lst file >> >> The syntax of addresses in a file read-in by read_hash is >> the usual rfc2822 syntax of addresses in a mail header, >> special characters (like spaces, %, ", @, comma in a >> mailbox name) should be quoted as per rfc 2822, e.g. >> "some \"weird\" username"@example.com >> but this is rarely needed for normal e-mail addresses. >> >>> like sintaxe in >>> qw(...), and not use qw into de amavisd.conf? Need preced of "\" >>> constructions like: >>> [EMAIL PROTECTED] (names with 3 leters begin with a) >>> .domain.com (fora all users from this domain and >>> subdomains) >>> [EMAIL PROTECTED] (names user*@ >> >> You want to use regular expressions in addresses. >> Within a hash-type lookup table this is not possible, >> but you can use a regexp-type lookup table instead. >> See README.lookups. There is currently no routine >> to read regular expressions from a file and make >> a regexp-type lookup table out of them, you need >> to specify them directly in a configuration file, >> or write a few-line Perl code for such purpose. >> >> >>> .domain.com (fora all users from this domain >>> and subdomains) >> >> For this one you don't need a regexp-type lookup table, >> the above example with read_hash suffices, just put a: >> >> .domain.com >> >> in a line. It implies the domain.com and its subdomains. >> See README.lookups, the section: >> HASH LOOKUPS (associative array lookups) >> >>> 2) >>> There is a amavisdnew web application or gui interface, like webmin >>> module, >>> linuxconf, to configure amavisd? >> >> Not really. There were some attempts with very limited functionality. >> >> Mark >> >> ------------------------------------------------------------------------- >> SF.Net email is sponsored by: The Future of Linux Business White Paper >> from Novell. From the desktop to the data center, Linux is going >> mainstream. Let it simplify your IT future. >> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 >> _______________________________________________ >> 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/ >
------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ 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/
