Date: Sat, 6 Feb 1999 00:52:17 -0500 From: Chris Johnson <cjohnson@palomine.net> To: Troy Settle <rewt@i-Plus.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: dummy-pop3 server Message-ID: <19990206005217.A17917@palomine.net> In-Reply-To: <19990205192155.A16042@palomine.net>; from Chris Johnson on Fri, Feb 05, 1999 at 07:21:55PM -0500 References: <Pine.GSU.4.05.9901252229490.27237-100000@www.ainet.com> <Pine.BSF.3.96.990205183451.20442A-100000@Radford.i-Plus.net> <19990205192155.A16042@palomine.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 05, 1999 at 07:21:55PM -0500, Chris Johnson wrote: > On Fri, Feb 05, 1999 at 06:37:54PM -0500, Troy Settle wrote: > > > > On Mon, 25 Jan 1999, Joseph M. Scott wrote: > > > > > > > > On Tue, 26 Jan 1999, Leif Neland wrote: > > > > > > > I'm looking for a dummy pop3-server, which can authorize anybody, and just > > > > send a single message: 'Hey dummy, we have moved the pop3-server; don't > > > > use this ip-adress, use the name: "mail.our.domain" instead.' > > > > > > You could also forward all pop3 traffic to the new machine. It's > > > probably unlikely that the people checking their email will ever get the " > > > the pop server is now at : whatever_ip", though this may depend largely on > > > the mail client. > > > > > > > > > I'm trying to redirect port 110 traffic to the appropriate host. I had > > thought that running a simple script to telnet over would do the trick, > > but at least one MUA doesn't seem to like it much (works great by telnet). > > > > Anyways, I looked at the man page for ipfw(8), and tried to figure out > > that divert thing, but it makes no sense in the context of the man page. > > Can anyone shed some light on this? > > > > Or, if anyone has a perl or C proggy that just opens a transparent socket > > to another host, I'd appreciate it. > > There's a simple way to do it. First, install two ports: > /usr/ports/sysutils/ucspi-tcp and /usr/ports/net/netcat. Then, on the old host, > run (as root): > > tcpserver 0 110 nc newhost.com 110 & > > where newhost.com is the name of the new POP host. That's all there is to it! > Connections to port 110 on the old host will be connected to port 110 on the > new host. To follow up my own post, it's easier than that. I don't make much use of inetd so I didn't think of it, but you can install just the netcat port and stick this in /etc/inetd.conf: pop3 stream tcp nowait nobody /usr/local/bin/nc nc name.of.new.host 110 Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990206005217.A17917>