----- Original Message -----
From: "Gabriel Ambuehl" <[EMAIL PROTECTED]>
To: "Einar Bordewich" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, October 05, 2001 6:50 AM
Subject: Re[2]: per user rbl patch for vpopmail
> > telnet 127.0.0.2 25
>
> THAT is probably the problem:
> On my FreeBSD box, I first must add an alias for lo0:
> #ifconfig lo0 alias 127.0.0.2
> then I can do
> #telnet -s 127.0.0.2 localhost smtp
>
> (-s instructs telnet to use source address 127.0.0.2 and connect to
> localhost)
Nope. I can ping 127.0.0.2, the logs tells me that I connect to 127.0.0.2.
If you saw the mailheader I included, the IP address was from 127.0.0.2. Has
to be something else.
@400000003bbd577806dde194 tcpserver: status: 1/40
@400000003bbd577806e0102c tcpserver: pid 2666 from 127.0.0.2
@400000003bbd57780705b0fc tcpserver: ok 2666 :127.0.0.2:25
:127.0.0.2:root:45322
@400000003bbd577c16fffe2c tcpserver: end 2666 status 0
@400000003bbd577c1700159c tcpserver: status: 0/40
Here I've used telnet -b 127.0.0.2 hellriser.bordewich.net 25 with no luck.
I don't have the -s option, but I guess my -b option is similar:
-b hostalias
Uses bind(2) on the local socket to bind it to an aliased
address
(see ifconfig(8) and the ``alias'' specifier) or to the address
of another interface than the one naturally chosen by
connect(2).
This can be useful when connecting to services which use IP
ad
dresses for authentication and reconfiguration of the server is
undesirable (or impossible).
Anyway, according the the mailheader, I've connected to
hellriser.bordewich.net from 127.0.0.2 as root. This should be enough to
trigger your trap, right?
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 17384 invoked by uid 508); 5 Oct 2001 06:51:44 -0000
Received: from unknown (HELO test) ([EMAIL PROTECTED])
by hellriser.bordewich.net with SMTP; 5 Oct 2001 06:51:44 -0000
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject: test10
SSIA
I must say that I kind of agree with Bill Shupp on the question regarding to
delivery.
What I think could be a good idea, is using your solution together with
delivery to a SPAM maildir, that can be accessed through imap or sqwebmail.
My experience (against RSS, ORBS, DUL, RBL) with users and the lists, is
that they prefere to have the mail delivered, but not in the regular INBOX.
We have been running a solution where we have received the e-mails, but put
it on hold for 48 hours, informing the sender and receipt of this, before
delivering.
Your solution I think should be configurable of which lists you want to
check against, and of course use of several list. Since this solution allows
the "blocked server mail" into the queue, you even might consider returning
an notice about the server beeing listed as blocked, but only if envelope
sender and sender equals. This should of course be a switch to
disable/enable.
m2c
--
--------------------------------------------
IDG New Media Einar Bordewich
Development Manager Phone: +47 2336 1420
E-Mail: eibo(at)newmedia.no
Lat: 59.91144 N Lon: 10.76097 E
--------------------------------------------
