fetchmail authorization failure

[Haines Brown <brownh@hartford-hwp.com>]

I replaced the stock nv driver under Etch with the nVidia proprietary
driver, and logged out and back in. When I did so, fetchmail was no
longer able to get authorization from my mail server. I should note
that it has been months since I've logged out, and the graphics driver
change is probably irrelevant.

Gnus and web browsing work OK. 

Fetchmail reports the error:

  fetchmail: Authorization failure on 
	brownh@hartford-hwp.com@pop.registeredsite.com
  fetchmail: Query status=3 (AUTHFAIL)

It looks to me like fetchmail is sending a garbled address to the mail
server.  However, the ~/.fetchmailrc file is unchanged: 

        poll pop.registeredsite.com
        user "brownh@hartford-hwp.com"

At the time the system ceased working, there was a burst of unusual
reports in my messages log. 

  Oct 25 15:35:42 teufel gconfd (brownh-8670): Failed to send buffer
  Oct 25 15:35:42 teufel last message repeated 3 times
  Oct 25 15:36:10 teufel gconfd (brownh-8670): 
	GConf server is not in use, shutting down.
  Oct 25 15:36:10 teufel gconfd (brownh-8670): Exiting
  Oct 25 15:39:08 teufel gconfd (brownh-19277): 
	starting (version 2.16.1), pid 19277 user 'brownh'
  Oct 25 15:39:08 teufel gconfd (brownh-19277): 
	Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" 
	to a read-only configuration source at position 0
  Oct 25 15:39:08 teufel gconfd (brownh-19277): 
	Resolved address "xml:readwrite:/home/brownh/.gconf" to a 
	writable configuration source at position 1
  Oct 25 15:39:08 teufel gconfd (brownh-19277): 
	Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to 
	a read-only configuration source at position 2
  Oct 25 15:39:08 teufel gconfd (brownh-19277): 
	Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" 
	to a read-only configuration source at position 3
  Oct 25 15:39:08 teufel gconfd (brownh-19277): 
	Resolved address "xml:readonly:/var/lib/gconf/defaults" to a 
	read-only configuration source at position 4
  
The problem here is that I don't use a GNOME (or any) desktop,
although I run a few GNOME applications. I've no idea what's going on
here, but it seems to involve resolving an address. 

-- 
 
       Haines Brown, KB1GRM