tlug: from popclient to fetchmail

["Eric Standlee" <fwiw3980@example.com>]

On a tip from Karl-Max, I searched for a source copy of popclient to
rebuild...

I changed to fetchmail from popclient.  On the sunsite archive cd's I have,
it was touted as the replacement for popclient.

After fetchmail --version 'ing several times, I finally got my
~/.fetchmailrc where it looked like it would work...  Find that below as
well as the output from a fetchmail -a -L ~/fet.log

I left the lengthy header to the .fetchmailrc file because I figured that
some may not be using fetchmail and yet may still be able to figure out my
errors with that bit of documentation...

You will notice that the problem is being reported in fet.log as a bad
password, but I triple checked and that is definitely the right password
which pon/pppd are using to login with...

SO CLOSE, and yet sooooooooo far....  ARRRRRG!
-----
# fetchmail control file samplE
#
# This file (or one of your own creation, rather) should be located
# in your home directory with the name .fetchmailrc.  Permissions on this
# file may be no greater than -rw-------, or fetchmail will refuse to
# use it.
#
# To see what effect your ~/.fetchmailrc file has, do
#
# fetchmail --version
#
# This will display the fetchmail version number and an explanation
# in English of what the currently set options and defaults mean.
#
# Comments begin with a '#' and extend through the end of the line.
# Blank lines between server entries are ignored.
# Keywords and identifiers are case sensitive.
# When there is a conflict between the command-line arguments and the
# arguments in this file, the command-line arguments take precedence.
#
# Legal keywords are
#   poll                      -- must be followed by a mailserver name
#   skip                      -- must be followed by a mailserver name
#   protocol (or proto)       -- must be followed by a protocol ID
#   uidl
#   port                      -- must be followed by a TCP/IP port number
#   authenticate (or auth)    -- must be followed by an authentication type
#   timeout                   -- must be followed by a numeric timeout value
#   envelope                  -- must be followed by an envelope header name
#   aka                       -- must be followed by one or more server
aliases
#   localdomains              -- must be followed by one or more domain
names
#   interface                 -- must be followed by device/IP address/mask
#   monitor                   -- must be followed by IP address
#
#   username (or user)        -- must be followed by a name
#   is                        -- must be followed by one or more names
#   remotefolder (or remote)  -- must be followed by a filename
#   password (or pass)        -- must be followed by a password string
#   smtphost (or smtp)        -- must be followed by a host name
#   mda                       -- must be followed by an MDA command string
#   preconnect (or pre)       -- must be followed by an initialization
command
#
#   keep
#   flush
#   fetchall
#   rewrite
#   forcecr
#   stripcr
#   dns
#   no keep
#   no flush
#   no fetchall
#   no rewrite
#   no forcecr
#   no stripcr
#   no dns
#   no envelope
#   limit                     -- must be followed by numeric size limit
#   fetchlimit                -- must be followed by numeric msg fetch limit
#   batchlimit                -- must be followed by numeric SMTP batch
limit
#
# Legal protocol identifiers are
#   pop2 (or POP2)
#   pop3 (or POP3)
#   imap (or IMAP)
#   apop (or APOP)
#   rpop (or RPOP)
#   kpop (or KPOP)
#   etrn (or ETRN)
#
# Legal authentication types are
#   login
#   kerberos
#
# Legal global option statements are
#
#   set logfile =  -- must be followed by a string
#   set daemon =  -- must be followed by a number
#
# The noise keywords `and', `with', `has', `wants', and `options' are
ignored
# anywhere in an entry; they can be used to make it resemble English.  The
# punctuation characters `,' `:' `;' are also ignored.
#
# The run control file format is fully described (with more examples) on the
# fetchmail manual page.
#
# This is what the developer's .fetchmailrc looks like:

set daemon 300 # Poll at 5-minute intervals

defaults
# interface "sl0/10.0.2.15" # SLIRP standard address
# user fwiw3980 is root esstand fetchmail-friends magic-numbers here
# user e-w.standlee is root esstand here
 fetchall

# Use this for production
poll mb.infoweb.ne.jp protocol POP3:
 username fwiw3980 password ********;
# user fwiw3980 is root esstand fetchmail-friends magic-numbers here
 #user e-w.standlee@example.com is root esstand here
 #no dns, aka snark.thyrsus.com thyrsus.com locke.ccil.org ccil.org
 fetchall

# Use this to test POP3
poll pop.netaddress.net with protocol POP3:
 username e-w.standlee password *********;
# user e-w.standlee@example.com is root esstand here
 #no dns, aka snark.thyrsus.com thyrsus.com locke.ccil.org ccil.org
 fetchall

# Use this to test against a different server
#skip pop3.netaxs.com:
# password my_netaxs.password;
-----End of .fetchmailrc
-----fet.log
fetchmail: starting fetchmail 3.9.1 daemon
fetchmail: 3.9.1 querying mb.infoweb.ne.jp (protocol POP3) at Mon Jun 22
18:54:22 1998
fetchmail: POP3< +OK InfoWeb Pop server at mb103.infoweb.or.jp starting.
fetchmail: POP3> USER fwiw3980
fetchmail: POP3< +OK Password required for fwiw3980.
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR Password supplied for "fwiw3980" is incorrect.
fetchmail: protocol error
fetchmail: Authorization failure on fwiw3980@example.com: Unknown
error -1
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Pop sever at mb103.infoweb.or.jp signing off.
fetchmail: authorization error while fetching from mb.infoweb.ne.jp: Unknown
error -1
fetchmail: 3.9.1 querying pop.netaddress.net (protocol POP3) at Mon Jun 22
18:54:33 1998
fetchmail: connecting to host
fetchmail: sleeping at Mon Jun 22 18:54:33 1998
fetchmail: awakened by User defined signal 1
fetchmail: awakened at Mon Jun 22 18:55:13 1998
fetchmail: 3.9.1 querying mb.infoweb.ne.jp (protocol POP3) at Mon Jun 22
18:55:13 1998
fetchmail: POP3< +OK InfoWeb Pop server at mb104.infoweb.or.jp starting.
fetchmail: POP3> USER fwiw3980
fetchmail: POP3< +OK Password required for fwiw3980.
fetchmail: POP3> PASS *
fetchmail: POP3< -ERR Password supplied for "fwiw3980" is incorrect.
fetchmail: protocol error
fetchmail: Authorization failure on fwiw3980@example.com: Unknown
error -1
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Pop sever at mb104.infoweb.or.jp signing off.
fetchmail: authorization error while fetching from mb.infoweb.ne.jp: Unknown
error -1
fetchmail: 3.9.1 querying pop.netaddress.net (protocol POP3) at Mon Jun 22
18:55:24 1998
fetchmail: connecting to host
fetchmail: sleeping at Mon Jun 22 18:55:25 1998
-----End of fet.log

TIA,
Eric S. Standlee
Kashihara-shi <Kintetsu Yamato Yagi>
Nara, Japan
e-w.standlee@example.com

---------------------------------------------------------------
Next Nomikai: 15 May Fri, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next TLUG Meeting: 13 June Sat, Tokyo Station Yaesu gate 12:30
Featuring Stone and Turnbull on .rpm and .deb packages
---------------------------------------------------------------
a word from the sponsor:
TWICS - Japan's First Public-Access Internet System
www.twics.com  info@example.com  Tel:03-3351-5977  Fax:03-3353-6096

--------------------------------------------------------------
Next Nomikai: 17 July, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next Meeting: 8 August, Tokyo Station Yaesu central gate 12:30
*** 20 June: TLUG will be at the Tokyo Linux Fair
http://tlug.linux.or.jp/projects/linux-fair/fair.html
--------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp