On Thu, Mar 19/98, Paul Mansfield <paulm@???> wrote:
>
> I have sender_verify on and sender_verify_fixup, and I have rewrite rules
> in the configure file for
>
> *@something.net $1@???
>
> where the MX records for something.net point to the machine so that it will
> forward the mail from fred@??? to fred@???
>
> If I connect to the machine and say
> helo <whatever>
> mail from: fred@???
> rcpt to: <anybody>
> data
> ...
> . (end)
>
> then it says
> "451 rejected: temporarily unable to verify sender address (try again later)
> <fred@???>"
>
Something.net has to have a valid mx if you are using sender_verify.
> I tried adding something.net into the local_domains to see if this would fix
> the problem, and saw
> "550 rejected: unknown local-part in sender <fred@???>"
>
This looks like you have receiver_verify turned on too. That's probably
not a good idea for a relay machine doing rewriting.
> Is this a bug, a feature, or have I missed something out to do this?
>
> I know that the domain <something.net> is truly valid, and the primary
> is authoritave, and that the exim host has a working resolver and
> everything looks all fine and dandy.
>
what does exim -bv user@??? say?
> If I remove "sender_verify" and "sender_verify_fixup" from the configure,
> then the forwarding works.
>
> JohnH, a contributor here saw my use of the rewrite rules to do aliasing,
> which I admit it a bit of a kluge... I only two different types of rules like:
> *@fred.net $1@???
> *@bert.net al@???
>
> so maybe this would solve my problem.
>
--
Artificial Intelligence stands no chance against Natural Stupidity.
GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
--
*** Exim information can be found at
http://www.exim.org/ ***
