Tags:
create new tag
, view all tags
Gathering information about pop3 servers.

See AboutThesePages.

Contents

pop3 servers are simple

From 30.1.2 Configuring a POP/IMAP server from Rute. As suggested below, see also Chapter 29 of Rute for information about starting pop3 from inetd or xinetd.

POP and IMAP are invoked by inetd or xinetd--see Chapter 29. Except for limiting the range of clients that are allowed to connect (for security reasons), no configuration is required. Client connections authenticate themselves using the normal UNIX login name and password. There are specialized POP and IMAP packages for supporting different mailbox types (like Maildir).

I was going to draw a sketch for a pop3 server (like those on EmailServerSketches), and I probably will, but it may be exceeding simple -- perhaps no more detail than is already shown on some of those sketches, but including only the /var/mail/<username> spools, a box, and remote users (in another box).

I think all I need to say about a pop3 server is something along the lines of:

"If you install and run a pop3 server, it will automagically allow pop3 clients on machines on the LAN to access their mailbox on the server. In general, if they are username01, they will be able to download mail from /var/mail/<username01> after authenticating themselves with their username and password as assigned on the server."

I think a description of imap would be fairly similar, except dealing with the idea that they read (and compose) their mail on the server instead of downloading it to their own machine.

See man ipopd. In man ipopd there is a statement "POP3 does not allow you to specify an alternate folder from the user's default" -- which presumably means that the mail folder must be in the default location, which I assume is /var/mail/<username>. I don't know where that is set, so I don't know if there is an opportunity to change that anywhere (like in the MTA configuration??).

Note: popd is a bash (?) command used in conjunction with pushd to push and pop directories onto a stack in scripts or at the command line. The reason the pop daemon is called ipopd is probably to minimize confusion.

qpopper

  • Free from Eudora
  • Files (mail spools) are presumably in /var/mail based on first resource below.

Some resources:

pop3 and xinetd or inetd

Subject: RE: [expert] Troubles with pop daemon
   Date: Fri, 22 Mar 2002 21:11:18 -0000
   From: "David Stevenson" <u415542@dgssoftware.co.uk>
     To: <expert@linux-mandrake.com>

Put the contents of that script into xinetd.conf, that should be all required. The ip/range should also be allowed to connect in the /etc/hosts.* files.

HTH Dave


Original Message----- From: rbsteffes@wwwPLEASENOSPAM.eq-viatores.org [mailto:rbsteffes@www.eq-viatores.org]On Behalf Of rbsteffes@comcastPLEASENOSPAM.net Sent: 22 March 2002 07:18 To: expert@linux-mandrakePLEASENOSPAM.com Subject: [expert] Troubles with pop daemon

No matter what I do I can't seem to get the pop daemon to work. I'm trying to use ipop3d from the imap package and it seems to work ok, but it doesn't start on boot.

Every help guide says to put some lines into inetd.conf which is conspicuously absent. In xinetd.d I've got an ipop3 script with:

service pop3
{
disable = no
socket_type = stream
wait = no
user = root
server = /usr/sbin/ipop3d
log_on_success += USERID
log_on_failure += USERID
}

In it.

Just typing ipop3d as root lets me type in typical mailbox type commands (user pass list last ...). Telnet to 110 gives connection denied. (Not any more -- maybe I didn't have it running?)

rc.firewall

#!/bin/bash
echo "Enabling Forwarding"
echo ""
echo 1>/proc/sys/net/ipv4/ip_forward

iptables -P INPUT ACCEPT
iptables -F INPUT
iptables -P OUTPUT ACCEPT
iptables -F OUTPUT
iptables -P FORWARD ACCEPT
iptables -F FORWARD

iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j
ACCEPT
iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j
REDIRECT --to-port 3128
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 81 -j
REDIRECT --to-port 3128
iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5900 -j
DNAT --to-destination 192.168.0.1
iptables -t nat -A PREROUTING -i eth1 -p tcp --dport 5800 -j
DNAT --to-destination 192.168.0.1

Contributors

  • RandyKramer - 22 Feb 2002
  • <If you edit this page, add your name here, move this to the next line>

Page Ratings

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r7 - 2002-08-15 - RandyKramer
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by PerlCopyright 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding WikiLearn? WebBottomBar">Send feedback
See TWiki's New Look