Date: Wed, 12 Jan 2005 15:37:59 -0500 From: Brian Clapper <brian-freebsd-006@clapper.org> To: freebsd-questions@freebsd.org Subject: Re: smtp pull Message-ID: <200501122037.j0CKbxX6047075@condor.inside.clapper.org> In-Reply-To: <41E5806B.1040806@comcast.net> References: <6FC9F9894A9F8C49A722CF9F2132FC2202E948C5@ms05.mailstreet2003.net> <41E5806B.1040806@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 January, 2005, at 14:54 (-0500)
Kris Maglione <bsdaemon@comcast.net> wrote:
>
> >Maybe fetchmail is what you need? That is what most of dialup users use when they run their own MTA servers.
> >
> >
> >
> Fetchmail uses POP.
It'll do more than just POP. From the man page:
AUTO Tries IMAP, POP3, and POP2 (skipping any of these for
which support has not been compiled in).
POP2 Post Office Protocol 2
POP3 Post Office Protocol 3
APOP Use POP3 with old-fashioned MD5-challenge authentication.
RPOP Use POP3 with RPOP authentication.
KPOP Use POP3 with Kerberos V4 authentication on port 1109.
SDPS Use POP3 with Demon Internet's SDPS extensions.
IMAP IMAP2bis, IMAP4, or IMAP4rev1 (fetchmail autodetects
their capabilities).
ETRN Use the ESMTP ETRN option.
ODMR Use the the On-Demand Mail Relay ESMTP profile.
It seems like the ideal solution for the original poster's needs. It can
pull mail down from the external machine, using any of the above protocols,
and will feed the mail to the internal machine's SMTP server.
Brian Clapper, http://www.clapper.org/bmc/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501122037.j0CKbxX6047075>