On 1/16/06, Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote:
>
> On Jan 15, 2006, at 7:28 AM, Dave Rolsky wrote:
>
> > On Sun, 15 Jan 2006, Peter J. Holzer wrote:
> >
> >>> One thing that would make this nicer would be if the server knew
> >>> what IP
> >>> addresses it is listening on. Unfortunately, this information is not
> >>> passed from the daemon-running script into the main code.
> >>
> >> How are you running qpsmtpd? The local IP address should be available
> >> in $self->qp->connection->local_ip (and also in $ENV{TCPLOCALIP},
> >> but I
> >> guess this is deprecated).
> >
> > That's the local address for the current connection, not all local
> > addresses that qpsmtpd is listening on.
>
> Does it matter in this case?
>
> Isn't it relatively unlikely that spamware/a virus/other junkmailer
> would forge not the IP it's connecting to or some random IP but one
> of the other IPs on the same box?
> - ask
We use the firewall for this. Our email server sits on the firewall
(gateway as well), and has two NIC's. The outside NIC has a firewall
entry saying it cannot receive any ip in the range 192.168.* (as well
as 127.*). So forged ip's never get in. forged names do though.
-Andy
