I've been mucking with the same problem. The best I've come up with is
similar. I run two poppers, one on an alternate port that only accepts
apop. Then at the firewall, we block all traffic to 110, except to port
forward 110 requests to an alternate port on specific pop hosts. This
makes it nice and easy for users, they do not have to configure their
mail clients to pop from an alternate port. As an aside, I also tried
running standalone poppers bound to different interfaces (ip addresses
actually) on the same machine (still port 110). This worked until
simultaneous requests came in and then standalone daemon that was trying
to run would die (duh). - no good - So what I did then, was run one
popper one 110 and one on an alternate port, then used the rdr directive
in ipnat to forward 110 requests on a specific interface (hme1)to 109.
This did work, but not all my servers have dual NICs. I tried using
Solaris's virtual interface option to ifconfig, but the syntax (hme0:1)
blew chunks in the ipnat configuration... etc... Much easier to do at
the firewall.
-Joel
Admin Mailing Lists wrote:
>
> run qpopper as 2 different services/2 differe ports (1 for apop, 1 for
> pop) and use tcpwrappers against both services?
> maybe not the best way, but an option
>
> -Tony
> .-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
> Anthony J. Biacco Network Administrator/Engineer
> [EMAIL PROTECTED] Intergrafix Internet Services
>
> "Dream as if you'll live forever, live as if you'll die today"
> http://www.asteroid-b612.org http://www.intergrafix.net
> .-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
>
> On Mon, 16 Oct 2000, Sebastian Enders wrote:
>
> > Hello,
> >
> > perhaps anybody can help me!
> >
> > I want to patch qpopper, so that he only allows POP from a special IP range, for
>example
> > 192.168.*.*, from anybody else he should only allow APOP.
> >
> > the qpopper feature -p 3 is waht i want, put this feature only allows POP from
>localhost.
> > Now i want to ahve a patch which changes localhost in an IP Address range such sa
> > 192.168.*.*
> >
> > I have looked up the source code, but i could not find it, where I have to make
>these
> > changes!
> >
> > Anybody an idea?
> > Would be very very nice!
> >
> > Thanks a lot,
> >
> > Best regards,
> >
> > Sebastian Enders
> >
> >
> >
> > Mit freundlichen Gruessen,
> > Ihr COMVOS Team
> >
> > Sebastian Enders
> >
> > ---------------------------------------------------------------------------
> > Sebastian Enders [EMAIL PROTECTED]
> > Internet, Administration
> > 0621 / 17891-18
> > ---------------------------------------------------------------------------
> > COMVOS online medien GmbH http://www.comvos.de/
> > Mannheim, Germany Tel:0621/17891 -0
> > ---------------------------------------------------------------------------
> >
