-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-06-06 09:04, Per Jessen wrote:
Anyway, I've tested my setup with a sender address of <@example.com> and it is also let through, but afaict only because something (probably postfix) changes the address to <""@example.com>. If you really want to reject such addresses, I think you need to look at using smtpd_sender_restrictions:check_sender_access A sender_access table to check for <@example.com> could be:
I think he wants it to work :-) He said: ]> I have an application running on a machine that sends status-mails. Unfortunately, it has no means to define a sender address. Instead it uses ]> '@domain-name' (= nothing before the @). I filed a bug-report with the manufacturer. ]> But what make me wonder, postfix _does_ accept the address that is sent and the whole message. Only afterwards the message is bounced, in the ]> log file 127.0.0.1 does this, or at least tries it since there is no real sender-address. I think it's the spam-filter that does this. ]> Shouldn't postfix reject the message immediately when receiving the incomplete sender-address ? Or do I have some configuration error ? Or to fail earlier :-? - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/PIaMACgkQIvFNjefEBxp58gCfX/Kn9+TOmIWP8+2jD6ehDS81 dKcAn0Xq0Ed0IR+Feb0/v0Iv/3A0aivs =Y5/M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org