Benny Pedersen:
[ Charset UTF-8 unsupported, converting... ]
> On 1. jul. 2014 22.00.22 CEST, wie...@porcupine.org wrote:
> >Narcis Garcia:
> >> At this moment I don't want to check manually if an IP is blacklisted
> >or
> >> not (I already had made that exercise).
> >>
> >> I want my Postfix installation presents a REJECTION to me. I'm
> >looking
> >> for a way to send a mail because I want to reach my Postfix and it
> >> REJECTS it due to DNSBL rule.
> >
> >Telnet to 127.0.0.2 port 25 then send mail.
> >
> >THIS MAIL SHOULD BE REJECTED by Postfix because almost every DNSBL
> >uses 127.0.0.2 as a test pattern.
> >
> >This is my final attempt to help you.
>
> For the record here, his postfix might not listen on 127.0.0.2, and 127.0.0.2
> is not a ip, its a result code
>
> Confusing result code and telnet ip
Benny you have no idea what you are talking about.
When a client connects from 127.0.0.2, the Postfix DNSBL client
will make a query, for example, for 2.0.0.127.zen.spamhaus.org.
2.0.0.127.zen.spamhaus.org has address 127.0.0.4
2.0.0.127.zen.spamhaus.org has address 127.0.0.10
2.0.0.127.zen.spamhaus.org has address 127.0.0.2
That can be used to trigger a reject when the client sends mail.
The only glitch is that by default,
telnet 127.0.0.1 smtp
results in
Jul 1 17:09:57 wzv postfix/smtpd[13454]: connect from localhost[127.0.0.1]
But that is easily fixed with "ifconfig lo 127.0.0.2 netmask 255.0.0.0".
Jul 1 17:11:24 wzv postfix/smtpd[13454]: connect from unknown[127.0.0.2]
(and don't forget to reset the lo address to 127.0.0.1).
QED. Now, if the OP were only willing to cooperate he could have
had his answer hours ago.
Wietse
