--On 4 January 2007 10:06:03 -0700 "Chad Leigh -- Shire.Net LLC"
<chad+exim@???> wrote:
>
> On Dec 30, 2006, at 9:01 AM, John Robinson wrote:
>
>> On 23/12/2006 17:05, Chad Leigh -- Shire.Net LLC wrote:
>>> I believe they are ones for which I am a backup MX host so I accept
>>> them and try to relay them on.
>>
>> You probably ought to look into recipient verification callouts then;
>> most of the time the primary MX will be up and it's a spammer
>> desperately trying to get the mail accepted by using a lower-
>> priority MX
>> instead of the primary MX.
>
> Ok, I had
>
> deny message = unrouteable address
> !verify = recipient
>
> which I just changed to
>
> deny message = unrouteable address
> !verify = recipient/callout=2m,defer_ok,random
>
> I assume the defer_ok is what I want to avoid rejecting valid mail
> that I cannot verify due to the main MX being down for some reason...
RANDOM won't help, since that checks a random local part in the domain that
you're trying to verify. I suspect you thought it would use a random sender
address. You could try use_postmaster, or better, mailfrom=$sender_address
would do the trick - but the latter isn't available for recipient
verification.
Since postmaster@yourdomain might not be permitted to post to the exim
mailing list, you should not be surprised to see the callout fail -
although I don't think the exim.org server checks at that stage.
> However, after I did this, I could not send to the exim list! (I
> also tried without the random).
>
> What am I missing?
>
> Thanks
> Chad
>
>>
>> Cheers,
>>
>> John.
>>
>> --
>> ## List details at http://www.exim.org/mailman/listinfo/exim-users
>> ## Exim details at http://www.exim.org/
>> ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
>
> ---
> Chad Leigh -- Shire.Net LLC
> Your Web App and Email hosting provider
> chad at shire.net
--
Ian Eiloart
IT Services, University of Sussex
