Re: fetchmail not communicating with exim.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
A long time ago, in a galaxy far, far way, someone said...
> I'm working on it. Just recompiled my kernel the other day to support
> firewalling but haven't had time to work on the iptables and other
> configuration issues.
I find it easier to configure exim to listen only on 127.0.0.1 (with the
"local_interfaces" setting) - it's all fetchmail needs - than fudge with
firewalling.
Much cleaner that way, I think. But that's just me :)
> @home is way too broad in their description of "server". I understand
> that their intent is to limit bandwidth since it is a shared resource
> but their one-size-fits-all policy is ridiculous.
Tell me about it. Why doesn't anyone consider special cases like
hobbyists any more? I would willingly pay a small premium to be able to
run "servers" as a private person.
> They would not go for it. They were especially not helpful after I, point
> blank, told them that their policy only served to conserve bandwidth for
> use by teenagers pirating software, stolen music and porn. Hmmm...maybe
> I shouldn't have told them that, huh? :)
:)
Back to your problem with fetchmail: would it help to see a working
config?
My exim.conf is at http://tux.creighton.edu/~pbrutsch/exim.conf
This is my .fetchmailrc:
set postmaster "phil"
poll <mailserver> with proto POP3
user "<pop3username>" there with password "<pop3passwd>" is phil here
I put a fetchmail entry in my crontab to check my email every 5 mins.
- --
- ----------------------------------------------------------------------
Phil Brutsche pbrutsch@tux.creighton.edu
GPG fingerprint: 9BF9 D84C 37D0 4FA7 1F2D 7E5E FD94 D264 50DE 1CFC
GPG key id: 50DE1CFC
GPG public key: http://tux.creighton.edu/~pbrutsch/gpg-public-key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6HcVC/ZTSZFDeHPwRAvdLAKCHJY6EVB5XjkLjVAKSNUbkWiqO1QCgjae5
ArRjLmmnyoCaYBnPXn3EZZw=
=Sj40
-----END PGP SIGNATURE-----
Reply to: