Stefan,
> I'm talking about subdomains, e.g. my domain is example.com and my
subdomains
> are all domains under example.com, like foo.example.com.
>
> In my 'relay_domains' file I have only: example.com
> because parent_domain_matches_subdomains = relay_domains.
> If I add example.com to my 'relay_domains' file will amavisd then
> recognize the subdomains?
No, subdomains must be listed explicitly - with a leading dot,
e.g. example.com and also .example.com
Documented in README_FILES/README.lookups :
HASH LOOKUPS (associative array lookups)
For arguments to subroutine lookup() of type hash-ref, the argument
is passed to subroutine lookup_hash(), which does a lookup into
a Perl hash.
Hash lookups (e.g. for user+...@sub.example.com) are performed in the
following order:
- lookup for user+...@sub.example.com
- lookup for u...@sub.example.com (only if $recipient_delimiter is '+')
- lookup for user+foo@
- lookup for user@ (only if $recipient_delimiter is '+')
- lookup for sub.example.com
- lookup for .sub.example.com
- lookup for .example.com
- lookup for .com
- lookup for .
The search sequence stops as soon as a match is found, and the value
of the matched entry determines the result.
The domain part is always matched case-insensitively, the localpart
is matched case-sensitively when $localpart_is_case_sensitive
is true (not case-sensitive by default).
A field value undef implies that the next lookup table (if there are more)
is to be tried. In plain words, undef means "this table does not know
the answer, try the next one". Further searching in this table
(for possibly more general defaults) is terminated.
[...]
There is a subroutine read_hash() available for use in amavisd.conf.
It can read keys from a plain text file, and load them into a Perl hash.
Format of the text file: one address per line, anything from '#' to the end
of line is treated as a comment, but '#' within correctly quoted rfc2821
addresses is not treated as a comment (e.g. a hash sign within
"strange # \"foo\" address"@example.com is valid). Leading and trailing
whitespace is discarded, empty lines (containing only whitespace and comment)
are ignored. Addresses are converted from quoted form into internal (raw)
form and inserted as keys into a given hash, with a value of 1 (true).
Each address can have an associated optional value (also known as the
'righthand side' or RHS) separated from the address by whitespace.
An absence of a value implies 1 (true). The $hashref argument is returned
for convenience, so that one can say for example:
$per_recip_whitelist_sender_lookup_tables = {
'.my1.example.com' => read_hash({},'/var/amavis/my1-example-com.wl'),
'.my2.example.com' => read_hash({},'/var/amavis/my2-example-com.wl') }
Mark
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
Please visit http://www.ijs.si/software/amavisd/ regularly
For administrativa requests please send email to rainer at openantivirus dot
org
