On Sat, 25 Aug 2007 at 13:42 -0700, [EMAIL PROTECTED] confabulated:
Duane Hill wrote:
On Sat, 25 Aug 2007 at 13:08 -0700, [EMAIL PROTECTED] confabulated:
Further, how does check_sender_mx_access differ from Sender Address
Verification (SAV)? (where SAV is an INCREDIBLY bad idea, and a blight
upon the internet)
(meaning: if check_sender_mx_access is just the postfix name for SAV, then
we not only shouldn't avoid techniques that break check_sender_mx_access,
we should all openly adopt techniques that break check_sender_mx_access as
a means to further remove the SAV blight from the internet)
Unfortunately, John, it's not SAV. It's an access table used against the MX
hosts for the MAIL FROM.
So, it's a table stored in the local postfix instance, that says which
addresses are valid mail-froms?
No. Here's from the docs:
"Search the specified access(5) database for the MX hosts for the MAIL
FROM address, and execute the corresponding action."
How does that collide with a remote MX being bogus? It seems like the
problem isn't that the remote MX is bogus, the problem would be that the
local postfix admin is entering a value into said table.
What happens if the remote MX is within a private IP range? Should I
accept that message, knowing fully, the recipient would never be able to
respond?
-------
_|_
(_| |
