Do I want the leading dot if we don't accept mail for subdomains?   
(true in all cases so far, and the exceptions are explicitly known...

So with the default setting,
   @domain by itself with Local set to...  that's actually not  
clear.  What value should be in the local field?

   @.domain would permit all subdomains yes?

On Jan 30, 2008, at 8:39 AM, Mark Martinec wrote:
>> Mark?   I was serious when I wrote this.  I've read and reread
>> README.lookups, README.sql, and the sample configuration files and
>> it's really not clear to me how to configure local_domains_map to
>> read the domains from a SQL table.  Nor is it clear what format the
>> return values should be.  Leading dot or not?
>
> In addition to what was said in the thread 'clarify: SQL lookups
> for local domains'...
>
>> Nor is it clear what format the
>> return values should be.  Leading dot or not?
>
> If $sql_lookups_no_at_means_domain is false (default):
>   leading @ and a dot
>
> If $sql_lookups_no_at_means_domain is true:
>   just a leading dot, no @
>
>
> README.lookups:
>
> SQL LOOKUPS
> [...]
>  - lookup for [EMAIL PROTECTED]
>  - lookup for [EMAIL PROTECTED] (only if $recipient_delimiter is '+')
>  - lookup for user+foo (only if domain part is local)
>  - lookup for user     (only local; only if $recipient_delimiter is  
> '+')
>  - lookup for @example.com
>  - lookup for @.example.com
>  - lookup for @.com
>  - lookup for @.       (catchall)
>
>
> RELEASE_NOTES:
>
> - added global configuration variables  
> $sql_lookups_no_at_means_domain and
>   $ldap_lookups_no_at_means_domain, both false by default. They  
> control
>   whether a database mail address field with no '@' character  
> represents
>   a local username, or a domain name. By default (value false) it  
> indicates
>   a username in SQL and LDAP lookups (but represents a domain in  
> hash and
>   acl lookups), so domain names in SQL and LDAP should be specified as
>   '@domain'. Setting these to true will cause 'xxx' to be  
> interpreted as
>   a domain name, just like in hash or acl lookups, which may  
> facilitate
>   interoperability with databases from other applications;
>
> Mark
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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/

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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