Issue with SQL lookups

[Dusan Obradovic]

> On Dec 11, 2018, at 2:12 PM, Fred Smith <amavis45 at brightheadtechnology.com> wrote:
> 
> 
> I'm running amavisd-new 2.11.1 and using SQL for lookups.
> 
> The problem was discovered when large emails were being bounced when there is an SQL entry for the email address that should allow the large mail.
> 
> In general I define a domain default SQL entry for @example.com to cover all email addresses not otherwise defined. For large mails I create, for example, an entry for big.mail at example.com.
> 
> I'm seeing multiple lookups, for email=>"@example.com" and email=>"big.mail at example.com" and amavis is proceeding with the results from the email=>"@example.com" and hence the wrong details.
> 
> I've tried changing the ID order in case the lookup was positionally related. But this made no difference.
> 
> 
> Lookup logs at https://pastebin.com/nRE8C7uH
> 

The first SQL lookup match wins and the results are ordered by users.priority field. Alter big.mail at example.com user to a higher priority.