Right. Fetchmail actually gets the mail ok but after the annoying cert messages. I'm just trying to figure out why one machine gets the errors and the other does not. <strange> On Tue, Oct 02, 2007 at 11:38:34AM -0700, Gregory Nowak wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > While it is true that pop3 over ssl runs on tcp 995, there is no need > to check the port in fetchmail. If you tell fetchmail to connect to a > pop3 server, and to use ssl, it automatically knows the port to > connect to on the server is tcp 995. > > Greg > > > On Tue, Oct 02, 2007 at 08:42:27AM -0400, Christopher Moore wrote: > > Steve, > > Iwould also check your gmail port. I think it may use something other than > > port 110 which is the default for fetchmail.\ > > Chris > > > - -- > web site: http://www.romuald.net.eu.org > gpg public key: http://www.romuald.net.eu.org/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > > - -- > Free domains: http://www.eu.org/ or mail dns-manager at EU.org > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFHApAp7s9z/XlyUyARAt1tAJ4hlqAJXX0eT6TpYwExmnc3sGnHKwCgsF31 > Wj+iRkJkri2dMe7onOenpJY= > =OmhO > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- HolmesGrown Solutions The best solutions for the best price! http://holmesgrown.ld.net/
