MaDhAt2r via Exim-users <exim-users@???> (Do 29 Aug 2019 13:21:26 CEST):
>
> Thanks for your reply Julian.
>
> That is what I originally thought. But when I send from an address like
> user@??? and that is a user of the system it goes out. But when I
> send from nouser@??? that is not a user the system, then it gets
> rejected by Exim. I get the following messages:
>
> 2019-08-29 06:14:14.453 [21564] H=(localhost.localdomain)
> [192.168.???.???]:59454 I=[???.???.???.???]:25 sender verify fail for
> <nouser@???>: Unknown user
> 2019-08-29 06:14:14.453 [21564] H=(localhost.localdomain)
> [192.168.???.???]:59454 I=[???.???.???.???]:25 F=<nouser@???>
> rejected RCPT <nouser@???>: Sender verify failed
If you have a near default config, you'll have
require verify = sender
in your ACL. Exim does about `exim -bvs $sender_address`, using the
configured routers to find, if the $sender_address is routable. For
remote domains a simple DNS MX lookup will be done, not more, for local
domains (depending on the config) Exim can even check the existence of
the user (as in your case).
You can disable this line, or limit it to domains that are not local
domains. But that's not wise and is asking for trouble.
You should work hard to have working sender addresses, for bounces,
replies and such stuff. And, to satisfy sender verification. (And while
you can disable sender verification on your host, you can't do so on
mine, and my host may do sender verification including callbacks… and
will finally reject the message, if your hosts is unwilling to accept
RCPT TO: nouser@???.)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
