On Monday 27 October 2003 12:45 pm, Jerry A! wrote:

On Mon, Oct 27, 2003 at 12:29:56PM -0500, E.F.Maurer wrote: : I just switched to comcast from sprynet and can't get fetchmail to set up : correctly. Has anyone got this to work? : : I'm using mail.comcast.net as the pop server : port 110

What does a 'fetchmail -v <pop-server>' yield? The verbose, debug information will go a long way in diagnosing the problem.

framau@VMXLinux:~> fetchmail -v mail.comcast.net fetchmail: 6.2.1 querying mail.comcast.net (protocol auto) at Mon 27 Oct 2003 12:48:45 PM EST: poll started fetchmail: 6.2.1 querying mail.comcast.net (protocol IMAP) at Mon 27 Oct 2003 12:48:45 PM EST: poll started and it freezes, or never responds. I wonder why imap is in there? I started over, and it worked... poll mail.comcast.net with proto POP3 user 'efmaurer' there with password '+' is 'framau' here options fetchall But in fetchmailconf it couldn't probe server for supported protocols. I wonder why? Thanks.

Am Montag, 27. Oktober 2003 18:29 schrieb E.F.Maurer:

I just switched to comcast from sprynet and can't get fetchmail to set up correctly. Has anyone got this to work?

I'm using mail.comcast.net as the pop server port 110

I can receive through kmail but fetchmail never completes when i test it

here's my fetchmailrc

# Configuration created Mon Oct 27 12:06:35 2003 by fetchmailconf set postmaster "framau" set bouncemail set no spambounce set properties "" poll pop.sprynet.com with proto APOP user 'nebbish@sprynet.com' there with password '*' is 'framau' here options fetchall

poll mail.comcast.net user 'efmaurer' there with password '*' options fetchall

Please login as the user which has the .fetchmailrc in his home and run: $ fetchmail -vv without other argumnents. What happens? -- Andreas

On Monday 27 October 2003 1:05 pm, Jerry A! wrote:

On Mon, Oct 27, 2003 at 12:57:08PM -0500, E.F.Maurer wrote: : On Monday 27 October 2003 12:45 pm, Jerry A! wrote: : > On Mon, Oct 27, 2003 at 12:29:56PM -0500, E.F.Maurer wrote: : > : I just switched to comcast from sprynet and can't get fetchmail to : > : set up correctly. Has anyone got this to work? : > : : > : I'm using mail.comcast.net as the pop server : > : port 110 : > : > What does a 'fetchmail -v <pop-server>' yield? The verbose, debug : > information will go a long way in diagnosing the problem. : : framau@VMXLinux:~> fetchmail -v mail.comcast.net : fetchmail: 6.2.1 querying mail.comcast.net (protocol auto) at Mon 27 Oct : 2003 12:48:45 PM EST: poll started : fetchmail: 6.2.1 querying mail.comcast.net (protocol IMAP) at Mon 27 Oct : 2003 12:48:45 PM EST: poll started : : and it freezes, or never responds. : I wonder why imap is in there? : : I started over, and it worked... : : poll mail.comcast.net with proto POP3

---------------------------------------^ Shouldn't there be a colon at the end of the line? It looks as though it's looping through until it finds a protocol that it likes.

Here's the output of fetchmail -v ... framau@VMXLinux:~> fetchmail -v mail.comcast.net fetchmail: 6.2.1 querying mail.comcast.net (protocol POP3) at Mon 27 Oct 2003 02:57:31 PM EST: poll started fetchmail: POP3< +OK (rwcrpxc51) Maillennium POP3/PROXY server #39 fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< EXPIRE NEVER fetchmail: POP3< IMPLEMENTATION Maillennium/PROXY V04.61c++ [12-Jun-03] cpu_spar fetchmail: POP3< c.os_solaris_bsd.comp_gnu fetchmail: POP3< LOGIN-DELAY 0 fetchmail: POP3< PIPELINING fetchmail: POP3< RESP-CODES fetchmail: POP3< STLS fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< USER fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation fetchmail: Warning: server certificate verification: self signed certificate in certificate chain fetchmail: Warning: server certificate verification: self signed certificate in certificate chain fetchmail: Issuer Organization: RSA Data Security, Inc. fetchmail: Unknown Issuer CommonName fetchmail: Server CommonName: mail.comcast.net fetchmail: mail.comcast.net key fingerprint: 86:4B:ED:3A:64:CE:70:D4:56:C1:DE:57:C6:92:AC:19 fetchmail: Warning: server certificate verification: self signed certificate in certificate chain fetchmail: POP3> USER efmaurer fetchmail: POP3< +OK fetchmail: POP3> PASS fetchmail: POP3< +OK ready fetchmail: POP3> STAT fetchmail: POP3< +OK 0 0 fetchmail: No mail for efmaurer at mail.comcast.net fetchmail: POP3> QUIT fetchmail: POP3< +OK comcast.net fetchmail: 6.2.1 querying mail.comcast.net (protocol POP3) at Mon 27 Oct 2003 02:57:35 PM EST: poll completed fetchmail: normal termination, status 1 Should I add a ":" after POP3 ? none of my other entries had one. I'll check the fetchmailrc man or help. Thanks E.F.Maurer

On Monday 27 October 2003 7:40 pm, Carlos E. R. wrote:

The 03.10.27 at 15:01, E.F.Maurer wrote:

...

fetchmail: No mail for efmaurer at mail.comcast.net fetchmail: POP3> QUIT fetchmail: POP3< +OK comcast.net fetchmail: 6.2.1 querying mail.comcast.net (protocol POP3) at Mon 27 Oct 2003 02:57:35 PM EST: poll completed fetchmail: normal termination, status 1

I knew that carlos, the problem was from before. I was told I might need a colon or it would try imap and the other protocols.

Simply there is no new mail in that server.

...

Should I add a ":" after POP3 ?

What for?

...

none of my other entries had one.

Me neither.

-- Cheers, Carlos Robinson

-- E.F.Maurer using SuSE 8.2

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 27 Oct 2003 12:29:56 -0500 "E.F.Maurer" wrote:

I just switched to comcast from sprynet and can't get fetchmail to set up correctly. Has anyone got this to work?

I'm using mail.comcast.net as the pop server port 110

I can receive through kmail but fetchmail never completes when i test it

here's my fetchmailrc

# Configuration created Mon Oct 27 12:06:35 2003 by fetchmailconf set postmaster "framau" set bouncemail set no spambounce set properties "" poll pop.sprynet.com with proto APOP user 'nebbish@sprynet.com' there with password '*' is 'framau' here options fetchall

poll mail.comcast.net user 'efmaurer' there with password '*' options fetchall With respect to all the other answers, here is my poll command for comcast. Note the ssl. I checked the logs and it works with no problems. I run it in daemon mode.

poll mail.comcast.net with proto POP3 user <user> is <user> pass <password> fetchall ssl - -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/oPNC+wA+1cUGHqkRArrjAJ0U4Daa7U9UunOtGRj09cnXAVEUfwCfTJw5 w1Htc8gLWuWIICDnPaEXvYU= =ExbF -----END PGP SIGNATURE-----

The Thursday 2003-10-30 at 07:27 -0500, E.F.Maurer wrote:

I got it working before this, but just added the ssl which makes me feel a little better. Did you set this up manually or did you use fetchmailconf? I'm still kinda confused as to why fetchmailconf couldn't probe the server for the right protocol or mailbox format. Because of this my .fetchmailrc had no protocol so it tried all of them making it seem like it crashed, it was slower than dialup.

I don't remember now fetchmailconf (I do it manually), but I'm running it right now to check. It has improved! On the protocol section, you see that the default is "auto": this will set the configuration file to "auto". There is a "probe for supported protocols" as well, but seeing your original configuration file, I think you left it as "auto". In fact, the configuration file I have just created using fetchmailconf is very similar to yours. Now, what happens in auto mode? I explained this before (2003-10-23), but you didn't notice. I'll explain now with more details: The fetchmail programs tries to connect to the IMAP port (143). If it gets a response, ie, it is open, it tries to use IMAP - this is shown as happening in the logs you posted here. And it will try till timeout: that is, five full minutes. It is not stuck, it is waiting. You could have set a lower timeout on the config (expert mode). After those 5 minutes of waiting, it will try the next protocol, pop3 (notice that it is a different port, 110), and even pop2 (port 109). Who is the culprit here? Surely, your ISP, because they left the 110th port open, and did not put a configured server on it. Shame on them, but it has happened to me before. -- Cheers, Carlos Robinson

The Saturday 2003-11-01 at 08:10 -0500, E.F.Maurer wrote:

Thanks Carlos. Sorry i missed your first post. I changed isp's and was changing my email addresses, and subscribing and unsubscribing until I got it all setup the way i wanted it, it probably fell through the cracks. i just started a new job, with comcast, I'll just have to ask about why the port for imap is left open.

See? You can use this to demonstrate to your employer why linux is good for testing providers :-p

I guess i got impatient when i thought it stalled, I was expecting it to be faster than dialup, well it is now.

It happened to me previously, and I investigated; I like to log debug info for email. So, when I saw you your log, I knew.

Thanks again.

Welcome! -- Cheers, Carlos Robinson