On Sat, 22 Jan 2000 18:57:10 +0100 , listy-dyskusyjne Krzysztof Dabrowski writes:
>
> >relaying. What control mechanism are you using? SMTP after POP is pretty
> >easy, and I think there's stuff already on the qmail web site implementing
> >it.
>
> There is atleast one smtp client from redmond that never does POP before
> SMTP if there is something to send prefering to do POP after SMTP :).
> Because of that we (large ISP with roaming customers) can not use it.
Actually, we (a large ISP with roaming customers)
do just fine -- we just make it clear when you sign
up that you must POP before sending mail, unless
you are using one of our dial-ups.
> The right thing is to use SMTP AUTH but the only patch available leaves
> much things to improve.
> POP before smtp also stinks because you have to recreate an "allowed IP's
> list" after every POP connection and this also is performace killer.
Not necessarily: I hacked open-smtp to touch a
(per-IP) file whenever someone authed from a roaming
IP. I then placed an extra command in the qmail-smtpd
pipeline that would check the timestamp on this
file, and if it was "young" enough, set RELAYCLIENT.
So far, no performance problems -- and it even works
on clusters of mail relays, if you share the set of
files via NFS.
--
Chris Mikkelson | Setting delivery schedules is easy enough using the
[EMAIL PROTECTED] | I Ching, astrology, psychic hotlines, or any of the
| well-known scatomantic and necromantic methodologies.
| Meeting your prophetic deadlines, though, is another
| bowl of entrails. -- Stan Kelly-Bootle
