fetchmail-users — User questions and discussion

Re: [fetchmail-users] Fetchmail vs. Getmail (from a Fetchmail perspective)

[Rob M. <rob...@gm...>]

On 11/12/06, Stephen Allen <fet...@ro...> wrote:
> Hello,
>
> I currently use Fetchmail, because, well... I do - no other reason.
> However, Fetchmail 6.2.5.5 (running as a daemon)

You're *very* out of date - 6.3.5 is out and a lot of bug fixes have
taken place since the version you're running.

> randomly stops picking up
> messages (with no events in the logfile to indicate why) until I restart
> the daemon when everything then works ok again. So, I am considering
> Getmail instead.

You may find that updating to 6.3 fixes your problem.  Alternatively
the problem may be elsewhere - without any further information it's
impossible to even guess.  Certainly I've never seen fetchmail
silently fail, and I've been running it since mid way through the 5.x
series.

>  From a Fetchmail perspective, what the the Pros/Cons of using each?  I
> don't want to jump out of the frying pan and into the fire!

Never used getmail, and you're asking on a fetchmail list - you're
going to get a very fetchmail centric response :)

> And for ease of administration, I run Fetchmail as root, collecting
> email from all users' POP3 accounts, so I only need one fetchmailrc
> file.  Is this good/bad etc?

Very bad - fetchmail will soon (if it hasn't already) refuse to allow
you to do this.  There is nothing in fetchmail that requires it to be
run as root.  Create an account for it and use this account instead.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[fetchmail-users] Fetchmail vs. Getmail (from a Fetchmail perspective)

[Stephen A. <fet...@ro...>]

Hello,

I currently use Fetchmail, because, well... I do - no other reason. 
However,
Fetchmail 6.2.5.5 (running as a daemon) randomly stops picking up 
messages (with no events in the logfile to indicate why) until I restart 
the daemon when everything then works ok again. So, I am considering 
Getmail instead.

 From a Fetchmail perspective, what the the Pros/Cons of using each?  I 
don't want to jump out of the frying pan and into the fire!

And for ease of administration, I run Fetchmail as root, collecting 
email from all users' POP3 accounts, so I only need one fetchmailrc 
file.  Is this good/bad etc?

Many thanks,
Steve :)

Re: [fetchmail-users] Change message as it is resent?

[Matthias A. <mat...@gm...>]

David Davis <dda...@ya...> writes:

> Matthias Andree <mat...@gm...> wrote:\
>
>     You can use one of the tiny sendmail-to-SMTP clients (too many to list)
>     along with a shell script and use this shell script as "mda" to
>     fetchmail. Adding said header can be done with reformail which ships in
>     Sam Varshavchik's "maildrop" package.
>
> Thanks for the tip.
>
> If I go the "mda" route, my little custom mda needs to be responsible for reliable delivery.   (Right?)  As far as fetchmail is concerned, the mail was
> sent successfully even if the final SMTP server down. Seems tricky.

fetchmail considers the exit code of the mda. == 0 means success, != 0 means failure.

> If I can't do this in fetchmail itself, perhaps an SMTP-to-SMTP
> data-munging proxy is the better route?  Does such a thing exist?

You can't "pull" with SMTP. 

> Also, can fetchmail "walk" all (or a subset of) an account's SMTP
> folders, or do I need to create a separate poll entry for each folder?

Separate poll entries are needed.

-- 
Matthias Andree

Re: [fetchmail-users] fetchmail authorization and socket errors

[Rob M. <rob...@gm...>]

On 11/12/06, wa...@wa... <wa...@wa...> wrote:
>
> wadesmart@wadesmart:~$ fetchmail -v -v --nosyslog
> fetchmail: Old UID list from mail.wadesmart.com: <empty>
> fetchmail: Old UID list from pop.gmail.com: GmailId10e8f455dc54ed32
> GmailId10e8f46fde19d311 GmailId10e8f4a6b0d10d02 GmailId10e8f4c07c89e66b
> GmailId10e8f4cbae005b2d GmailId10e8f50a2d43221f GmailId10e8f510de40d911
> GmailId10e8fba2f4d0afbd GmailId10e944ea0c475421 GmailId10e94e9c6c03b6cf
> GmailId10e97181912529f4 GmailId10e972091000eb30 GmailId10e980bf95a5a4fa
> GmailId10e983449f8df563 GmailId10e9ab926f5343ef GmailId10e9b00b3dad0fb6
> GmailId10e9bed7d19a8626 GmailId10e9c0309b42ef5c GmailId10e9c04dd5a86b35
> GmailId10e9c092922226f4 GmailId10e9c0c26a992b44 GmailId10e9c0dadf5f2fe0
> GmailId10e9c0ea04994f1c GmailId10e9c0fa3e323dc2 GmailId10e9f6b951f259da
> GmailId10ea335d9a13e479 GmailId10ea3e0e4897646a GmailId10ea44e696162f25
> GmailId10ea4db3b637cc45 GmailId10ea4dcf6aa21d7f GmailId10ea4fe434a48145
> GmailId10ea52e9acdb0e3d GmailId10ea618d21705b47 GmailId10ea619a305c10c2
> GmailId10ea61bb993345f8 GmailId10ea61d407b9a142 GmailId10ea61dea9561041
> GmailId10ea620f2165782c GmailId10ea620f81650b88 GmailId10ea90081470a258
> GmailId10eaf7383c9368e6 GmailId10eaf7502bfae592 GmailId10eaf76e0e206de4
> GmailId10eaf78cb2a00772 GmailId10eaf794879f3be8 GmailId10eaf7b934c2a644
> GmailId10eaf7c9163d5361 GmailId10eafbb7ed826299 GmailId10eb4d0364369fcc
> GmailId10eb8a25d8c853b9 GmailId10ec051b29896443 GmailId10ec053235c67f79
> GmailId10ec0560ba6d0641 GmailId10ec058703a84409 GmailId10ec05898d16ef7d
> GmailId10ec05accf51c74c GmailId10ec05bce24bb78e <empty>
> fetchmail: Scratch list of UIDs: <empty>

Can you repost that with the rest of the stuff you cut.  There should
be lots of lines about it's communications with the mail servers.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail authorization and socket errors

[<wa...@wa...>]

> -------- Original Message --------
> Subject: Re: [fetchmail-users] fetchmail authorization and socket
> errors
> From: "Rob MacGregor" <rob...@gm...>
> Date: Sat, November 11, 2006 5:32 pm
> To: fetchmail-users <fet...@li...>
>
> On 11/11/06, wa...@wa... <wa...@wa...> wrote:
>
> > > 1) Contents of fetchmailrc (mangle usernames/passwords)
>
> > > 1a) The command line used to call fetchmail
>
> Which is?
>
> > > 2) Output of "fetchmail -v -v --nosyslog"
>
> Stop fetchmail and re-run this
>
> > > 3) Output of "fetchmail -V"
>
> Slightly old, but should be ok
>
> > > 4) Details of your OS, including kernel version
>
> Some version of Linux with 2.6.15 kernel :)> >
>
> > This is the .fetchmailrc
> > # Configuration created Tue Oct 24 12:53:28 2006 by fetchmailconf 1.52
> > $Revision: 4636 $
> > set syslog
> > set postmaster "wadesmart"
> > set no bouncemail
> > set no spambounce
> > set properties ""
> > set daemon 300
> >
> > # setup first email service provider -> WadeSmart
> >         poll mail.wadesmart.com
> >         uidl protocol pop3 auth password
> >         user 'wa...@wa...' there with password 'password' is
> > 'wade' here
> >         no keep
>
> Typo - there is a keyword "nokeep", which is probably what you're after.
>
> > # setup third email service provider -> Gmail
> >         poll pop.gmail.com
> >         uidl port 995 auth password
> >         user 'wad...@gm...' there with password 'password'
> >         keep
> >         no fetchall
> >         ssl sslcertpath /etc/ssl/certs
>
> Looks otherwise ok, but without that "-v -v --nosyslog" run I can't
> say where your problem lies.
>
> --
>                  Please keep list traffic on the list.
>
> Rob MacGregor
>       Whoever fights monsters should see to it that in the process he
>         doesn't become a monster.                  Friedrich Nietzsche
> _______________________________________________
> fetchmail-users mailing list
> fet...@li...
> https://lists.berlios.de/mailman/listinfo/fetchmail-users



wadesmart@wadesmart:~$ fetchmail -v -v --nosyslog
fetchmail: Old UID list from mail.wadesmart.com: <empty>
fetchmail: Old UID list from pop.gmail.com: GmailId10e8f455dc54ed32
GmailId10e8f46fde19d311 GmailId10e8f4a6b0d10d02 GmailId10e8f4c07c89e66b
GmailId10e8f4cbae005b2d GmailId10e8f50a2d43221f GmailId10e8f510de40d911
GmailId10e8fba2f4d0afbd GmailId10e944ea0c475421 GmailId10e94e9c6c03b6cf
GmailId10e97181912529f4 GmailId10e972091000eb30 GmailId10e980bf95a5a4fa
GmailId10e983449f8df563 GmailId10e9ab926f5343ef GmailId10e9b00b3dad0fb6
GmailId10e9bed7d19a8626 GmailId10e9c0309b42ef5c GmailId10e9c04dd5a86b35
GmailId10e9c092922226f4 GmailId10e9c0c26a992b44 GmailId10e9c0dadf5f2fe0
GmailId10e9c0ea04994f1c GmailId10e9c0fa3e323dc2 GmailId10e9f6b951f259da
GmailId10ea335d9a13e479 GmailId10ea3e0e4897646a GmailId10ea44e696162f25
GmailId10ea4db3b637cc45 GmailId10ea4dcf6aa21d7f GmailId10ea4fe434a48145
GmailId10ea52e9acdb0e3d GmailId10ea618d21705b47 GmailId10ea619a305c10c2
GmailId10ea61bb993345f8 GmailId10ea61d407b9a142 GmailId10ea61dea9561041
GmailId10ea620f2165782c GmailId10ea620f81650b88 GmailId10ea90081470a258
GmailId10eaf7383c9368e6 GmailId10eaf7502bfae592 GmailId10eaf76e0e206de4
GmailId10eaf78cb2a00772 GmailId10eaf794879f3be8 GmailId10eaf7b934c2a644
GmailId10eaf7c9163d5361 GmailId10eafbb7ed826299 GmailId10eb4d0364369fcc
GmailId10eb8a25d8c853b9 GmailId10ec051b29896443 GmailId10ec053235c67f79
GmailId10ec0560ba6d0641 GmailId10ec058703a84409 GmailId10ec05898d16ef7d
GmailId10ec05accf51c74c GmailId10ec05bce24bb78e <empty>
fetchmail: Scratch list of UIDs: <empty>


wadesmart@wadesmart:~$ fetchmail -V
This is fetchmail release 6.3.2+NTLM+SDPS+SSL+NLS.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond, Rob F. Funk, Graham
Wilson
Copyright (C) 2005 Matthias Andree, Sunil Shetye
Copyright (C) 2006 Matthias Andree
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and
you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.

Fallback MDA: (none)
Linux wadesmart 2.6.15-27-386 #1 PREEMPT Sat Sep 16 01:51:59 UTC 2006
i686 GNU/Linux
Taking options from command line and /home/wadesmart/.fetchmailrc
Poll interval is 300 seconds
Idfile is /home/wadesmart/.fetchids
Progress messages will be logged via syslog
Fetchmail will forward misaddressed multidrop messages to wadesmart.
Fetchmail will direct error mail to the postmaster.
Options for retrieving from wa...@wa...@mail.wadesmart.com:
  True name of server is mail.wadesmart.com.
  Protocol is POP3 (forcing UIDL use).
  Password authentication will be forced.
  Server nonresponse timeout is 300 seconds (default).
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will not be kept on the server (--keep off).
  Old messages will not be flushed before message retrieval (--flush
off).
  Oversized messages will not be flushed before message retrieval
(--limitflush off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is disabled (stripcr off).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits
off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be kept (dropdelivered off)
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10).
  Messages will be SMTP-forwarded to: localhost (default)
  Single-drop mode: 1 local name recognized.
  No UIDs saved from this host.
Options for retrieving from wad...@gm...@pop.gmail.com:
  True name of server is pop.gmail.com.
  Protocol is auto (forcing UIDL use).
  Password authentication will be forced.
  SSL encrypted sessions enabled.
  Server nonresponse timeout is 300 seconds (default).
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will be kept on the server (--keep on).
  Old messages will not be flushed before message retrieval (--flush
off).
  Oversized messages will not be flushed before message retrieval
(--limitflush off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is disabled (stripcr off).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits
off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be kept (dropdelivered off)
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10).
  Messages will be SMTP-forwarded to: localhost (default)
  Single-drop mode: 1 local name recognized.

Ubuntu 6.06LTS with
wadesmart@wadesmart:~$ uname -r
2.6.15-27-386

fetchmail runs in daemon mode at 300 interval.

wade

Re: [fetchmail-users] fetchmail authorization and socket errors

[<wa...@wa...>]

> -------- Original Message --------
> Subject: Re: [fetchmail-users] fetchmail authorization and socket
> errors
> From: Gerard Seibert <ge...@se...>
> Date: Sat, November 11, 2006 4:43 pm
> To: fet...@li...
>
> On Saturday November 11, 2006 at 05:04:08 (PM) wade wrote:
>
> > This is the .fetchmailrc
> > # Configuration created Tue Oct 24 12:53:28 2006 by fetchmailconf 1.52
> > $Revision: 4636 $
> > set syslog
> > set postmaster "wadesmart"
> > set no bouncemail
> > set no spambounce
> > set properties ""
> > set daemon 300
> >
> > # setup first email service provider -> WadeSmart
> > 	poll mail.wadesmart.com
> >        	uidl protocol pop3 auth password
> >         user 'wa...@wa...' there with password 'password' is
> > 'wade' here
> >        	no keep
> >
> >
> > # setup third email service provider -> Gmail
> > 	poll pop.gmail.com
> > 	uidl port 995 auth password
> > 	user 'wad...@gm...' there with password 'password'
> > 	keep
> > 	no fetchall
> > 	ssl sslcertpath /etc/ssl/certs
>
>
> I use fetchmail to access numerous accounts, including some 'gmail' ones also.
> My configuration for accessing 'gmail' is slightly different though.
>
> # Configuration created Sun Jul 30 19:38:15 2006 by fetchmailconf 1.52 $Revision: 4740 $
> set logfile "/usr/home/ges/logs/fetchmail.log"
> set postmaster "postmaster"
> set bouncemail
> set spambounce
> set properties ""
> set daemon 900
> poll pop.gmail.com with proto POP3 and options uidl
>     localdomains seibercom.net
>
>  user 'ger...@gm...' there with password 'secret' is
> 'gerard-gmail' here options fetchall forcecr pass8bits ssl mimedecode
>
>
> The only real difference is that I do not give it a specific port number.
> Have you tried removing it and seeing what transpires? Just a suggestion.
>
>
> --
> Gerard
>
> The average housefly lives for one month.
> _______________________________________________
> fetchmail-users mailing list
> fet...@li...
> https://lists.berlios.de/mailman/listinfo/fetchmail-users

11112006 1806 gmt-6

Actually I got those settings from gmail help.
I removed the port number and I still got the error.

Wade

Re: [fetchmail-users] fetchmail authorization and socket errors

[Rob M. <rob...@gm...>]

On 11/11/06, wa...@wa... <wa...@wa...> wrote:

> > 1) Contents of fetchmailrc (mangle usernames/passwords)

> > 1a) The command line used to call fetchmail

Which is?

> > 2) Output of "fetchmail -v -v --nosyslog"

Stop fetchmail and re-run this

> > 3) Output of "fetchmail -V"

Slightly old, but should be ok

> > 4) Details of your OS, including kernel version

Some version of Linux with 2.6.15 kernel :)> >

> This is the .fetchmailrc
> # Configuration created Tue Oct 24 12:53:28 2006 by fetchmailconf 1.52
> $Revision: 4636 $
> set syslog
> set postmaster "wadesmart"
> set no bouncemail
> set no spambounce
> set properties ""
> set daemon 300
>
> # setup first email service provider -> WadeSmart
>         poll mail.wadesmart.com
>         uidl protocol pop3 auth password
>         user 'wa...@wa...' there with password 'password' is
> 'wade' here
>         no keep

Typo - there is a keyword "nokeep", which is probably what you're after.

> # setup third email service provider -> Gmail
>         poll pop.gmail.com
>         uidl port 995 auth password
>         user 'wad...@gm...' there with password 'password'
>         keep
>         no fetchall
>         ssl sslcertpath /etc/ssl/certs

Looks otherwise ok, but without that "-v -v --nosyslog" run I can't
say where your problem lies.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail authorization and socket errors

[Gerard S. <ge...@se...>]

On Saturday November 11, 2006 at 05:04:08 (PM) wade wrote:

> This is the .fetchmailrc
> # Configuration created Tue Oct 24 12:53:28 2006 by fetchmailconf 1.52
> $Revision: 4636 $
> set syslog
> set postmaster "wadesmart"
> set no bouncemail
> set no spambounce
> set properties ""
> set daemon 300
> 
> # setup first email service provider -> WadeSmart
> 	poll mail.wadesmart.com
>        	uidl protocol pop3 auth password
>         user 'wa...@wa...' there with password 'password' is
> 'wade' here
>        	no keep
>        	
> 
> # setup third email service provider -> Gmail
> 	poll pop.gmail.com
> 	uidl port 995 auth password
> 	user 'wad...@gm...' there with password 'password'
> 	keep
> 	no fetchall
> 	ssl sslcertpath /etc/ssl/certs


I use fetchmail to access numerous accounts, including some 'gmail' ones also.
My configuration for accessing 'gmail' is slightly different though.

# Configuration created Sun Jul 30 19:38:15 2006 by fetchmailconf 1.52 $Revision: 4740 $
set logfile "/usr/home/ges/logs/fetchmail.log"
set postmaster "postmaster"
set bouncemail
set spambounce
set properties ""
set daemon 900
poll pop.gmail.com with proto POP3 and options uidl
    localdomains seibercom.net

 user 'ger...@gm...' there with password 'secret' is
'gerard-gmail' here options fetchall forcecr pass8bits ssl mimedecode


The only real difference is that I do not give it a specific port number.
Have you tried removing it and seeing what transpires? Just a suggestion.


-- 
Gerard

The average housefly lives for one month.

Re: [fetchmail-users] fetchmail authorization and socket errors

[<wa...@wa...>]

> -------- Original Message --------
> Subject: Re: [fetchmail-users] fetchmail authorization and socket
> errors
> From: "Rob MacGregor" <rob...@gm...>
> Date: Sat, November 11, 2006 2:28 pm
> To: "fet...@li..."
> <fet...@li...>
> 
> Keep this on the list.
> 
> On 11/11/06, wa...@wa... <wa...@wa...> wrote:
> > 11112006 1316 GMT-6
> >
> > I changed the username but still an error. I checked gmail settings and
> > pop is turned on. I checked the password (many times because I thought
> > that was the problem to) and that isnt it either.
> >
> > But the thing is, it was checking before 1300 on the 9th and after 1300
> > it wasnt.
> 
> Which means that *something* changed.  If it wasn't local (you didn't
> upgrade fetchmail, change anything else on the box
> 
> > Of course, that doesnt say why I cant get mail from my own servers.
> 
> That would the in the dozens of lines you quoted on your first post?
> Look like another auth error suggesting a username/password mismatch.
> 
> To work to the bottom of this I need you to post:
> 
> 1) Contents of fetchmailrc (mangle usernames/passwords)
> 
> 1a) The command line used to call fetchmail
> 
> 2) Output of "fetchmail -v -v --nosyslog"
> 
> 3) Output of "fetchmail -V"
> 
> 4) Details of your OS, including kernel version
> 
> -- 
>                  Please keep list traffic on the list.
> 
> Rob MacGregor
>       Whoever fights monsters should see to it that in the process he
>         doesn't become a monster.                  Friedrich Nietzsche
> _______________________________________________
> fetchmail-users mailing list
> fet...@li...
> https://lists.berlios.de/mailman/listinfo/fetchmail-users

11112006 1559 GMT-6

When I hit reply it goes automatically to your name, not the list. Ill
watch that.

This is the .fetchmailrc
# Configuration created Tue Oct 24 12:53:28 2006 by fetchmailconf 1.52
$Revision: 4636 $
set syslog
set postmaster "wadesmart"
set no bouncemail
set no spambounce
set properties ""
set daemon 300

# setup first email service provider -> WadeSmart
	poll mail.wadesmart.com
       	uidl protocol pop3 auth password
        user 'wa...@wa...' there with password 'password' is
'wade' here
       	no keep
       	

# setup third email service provider -> Gmail
	poll pop.gmail.com
	uidl port 995 auth password
	user 'wad...@gm...' there with password 'password'
	keep
	no fetchall
	ssl sslcertpath /etc/ssl/certs

This is fetchmail -v-v-nosyslog:
wadesmart@wadesmart:~$ fetchmail -v -v --nosyslog
fetchmail: Old UID list from mail.wadesmart.com: <empty>
fetchmail: Old UID list from pop.gmail.com: GmailId10e8f455dc54ed32
GmailId10e8f46fde19d311 GmailId10e8f4a6b0d10d02 GmailId10e8f4c07c89e66b
GmailId10e8f4cbae005b2d GmailId10e8f50a2d43221f GmailId10e8f510de40d911
GmailId10e8fba2f4d0afbd GmailId10e944ea0c475421 GmailId10e94e9c6c03b6cf
GmailId10e97181912529f4 GmailId10e972091000eb30 GmailId10e980bf95a5a4fa
GmailId10e983449f8df563 GmailId10e9ab926f5343ef GmailId10e9b00b3dad0fb6
GmailId10e9bed7d19a8626 GmailId10e9c0309b42ef5c GmailId10e9c04dd5a86b35
GmailId10e9c092922226f4 GmailId10e9c0c26a992b44 GmailId10e9c0dadf5f2fe0
GmailId10e9c0ea04994f1c GmailId10e9c0fa3e323dc2 GmailId10e9f6b951f259da
GmailId10ea335d9a13e479 GmailId10ea3e0e4897646a GmailId10ea44e696162f25
GmailId10ea4db3b637cc45 GmailId10ea4dcf6aa21d7f GmailId10ea4fe434a48145
GmailId10ea52e9acdb0e3d GmailId10ea618d21705b47 GmailId10ea619a305c10c2
GmailId10ea61bb993345f8 GmailId10ea61d407b9a142 GmailId10ea61dea9561041
GmailId10ea620f2165782c GmailId10ea620f81650b88 GmailId10ea90081470a258
GmailId10eaf7383c9368e6 GmailId10eaf7502bfae592 GmailId10eaf76e0e206de4
GmailId10eaf78cb2a00772 GmailId10eaf794879f3be8 GmailId10eaf7b934c2a644
GmailId10eaf7c9163d5361 GmailId10eafbb7ed826299 GmailId10eb4d0364369fcc
GmailId10eb8a25d8c853b9 GmailId10ec051b29896443 GmailId10ec053235c67f79
GmailId10ec0560ba6d0641 GmailId10ec058703a84409 GmailId10ec05898d16ef7d
GmailId10ec05accf51c74c GmailId10ec05bce24bb78e <empty>
fetchmail: Scratch list of UIDs: <empty>
fetchmail: can't accept options while a background fetchmail is running.
  

And this is fetchmail -V:
wadesmart@wadesmart:~$ fetchmail -v
fetchmail: can't accept options while a background fetchmail is running.
wadesmart@wadesmart:~$ fetchmail -V
This is fetchmail release 6.3.2+NTLM+SDPS+SSL+NLS.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond, Rob F. Funk, Graham
Wilson
Copyright (C) 2005 Matthias Andree, Sunil Shetye
Copyright (C) 2006 Matthias Andree
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and
you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.

Fallback MDA: (none)
Linux wadesmart 2.6.15-27-386 #1 PREEMPT Sat Sep 16 01:51:59 UTC 2006
i686 GNU/Linux
Taking options from command line and /home/wadesmart/.fetchmailrc
Poll interval is 300 seconds
Idfile is /home/wadesmart/.fetchids
Progress messages will be logged via syslog
Fetchmail will forward misaddressed multidrop messages to wadesmart.
Fetchmail will direct error mail to the postmaster.
Options for retrieving from wa...@wa...@mail.wadesmart.com:
  True name of server is mail.wadesmart.com.
  Protocol is POP3 (forcing UIDL use).
  Password authentication will be forced.
  Server nonresponse timeout is 300 seconds (default).
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will not be kept on the server (--keep off).
  Old messages will not be flushed before message retrieval (--flush
off).
  Oversized messages will not be flushed before message retrieval
(--limitflush off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is disabled (stripcr off).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits
off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be kept (dropdelivered off)
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10).
  Messages will be SMTP-forwarded to: localhost (default)
  Single-drop mode: 1 local name recognized.
  No UIDs saved from this host.
Options for retrieving from wad...@gm...@pop.gmail.com:
  True name of server is pop.gmail.com.
  Protocol is auto (using service 995) (forcing UIDL use).
  Password authentication will be forced.
  SSL encrypted sessions enabled.
  Server nonresponse timeout is 300 seconds (default).
  Default mailbox selected.
  Only new messages will be retrieved (--all off).
  Fetched messages will be kept on the server (--keep on).
  Old messages will not be flushed before message retrieval (--flush
off).
  Oversized messages will not be flushed before message retrieval
(--limitflush off).
  Rewrite of server-local addresses is enabled (--norewrite off).
  Carriage-return stripping is disabled (stripcr off).
  Carriage-return forcing is disabled (forcecr off).
  Interpretation of Content-Transfer-Encoding is enabled (pass8bits
off).
  MIME decoding is disabled (mimedecode off).
  Idle after poll is disabled (idle off).
  Nonempty Status lines will be kept (dropstatus off)
  Delivered-To lines will be kept (dropdelivered off)
  Fetch message size limit is 100 (--fetchsizelimit 100).
  Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10).
  Messages will be SMTP-forwarded to: localhost (default)
  Single-drop mode: 1 local name recognized.


wade

Re: [fetchmail-users] fetchmail authorization and socket errors

[Rob M. <rob...@gm...>]

Keep this on the list.

On 11/11/06, wa...@wa... <wa...@wa...> wrote:
> 11112006 1316 GMT-6
>
> I changed the username but still an error. I checked gmail settings and
> pop is turned on. I checked the password (many times because I thought
> that was the problem to) and that isnt it either.
>
> But the thing is, it was checking before 1300 on the 9th and after 1300
> it wasnt.

Which means that *something* changed.  If it wasn't local (you didn't
upgrade fetchmail, change anything else on the box

> Of course, that doesnt say why I cant get mail from my own servers.

That would the in the dozens of lines you quoted on your first post?
Look like another auth error suggesting a username/password mismatch.

To work to the bottom of this I need you to post:

1) Contents of fetchmailrc (mangle usernames/passwords)

1a) The command line used to call fetchmail

2) Output of "fetchmail -v -v --nosyslog"

3) Output of "fetchmail -V"

4) Details of your OS, including kernel version

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail authorization and socket errors

[Rob M. <rob...@gm...>]

Please don't crosspost to multiple lists - pick a list and stick with it.

On 11/11/06, wa...@wa... <wa...@wa...> wrote:
>
> Nov 11 12:47:17 wadesmart fetchmail[13871]: Unknown login or
> authentication error on wad...@gm...@gmail-pop.l.google.com
> Nov 11 12:47:17 wadesmart fetchmail[13871]: socket error while fetching
> from wad...@gm...@pop.gmail.com

Check your gmail password and account.  The password you have in the
fetchmail config file is not the password that's set on the account
(or you've disabled POP access).

Also, with gmail you only need your username, not the full address (or
at least that's been my experience, YMMV).

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-users] fetchmail authorization and socket errors

[<wa...@wa...>]

11112006 1258 GMT-6

I rebooted and then ran fetchmail -c to generate a mail.info and
mail.err log.
This is from mail.info:
Nov 11 07:52:14 wadesmart dovecot: imap-login: Login: user=<wadesmart>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Nov 11 11:06:40 wadesmart postfix/master[4815]: terminating on signal 15
Nov 11 11:06:40 wadesmart dovecot: Killed with signal 15
Nov 11 11:10:05 wadesmart postfix/master[4816]: daemon started --
version 2.2.10, configuration /etc/postfix
Nov 11 11:10:06 wadesmart dovecot: Dovecot v1.0.beta3 starting up
Nov 11 11:10:06 wadesmart dovecot: Generating Diffie-Hellman parameters
for the first time. This may take a while..
Nov 11 11:10:22 wadesmart dovecot: ssl-build-param: SSL parameters
regeneration completed
Nov 11 12:20:53 wadesmart dovecot: imap-login: Login: user=<wadesmart>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Nov 11 12:47:16 wadesmart fetchmail[13871]: 450 messages for
wa...@wa... at mail.wadesmart.com (4990589 octets).
Nov 11 12:47:17 wadesmart fetchmail[13871]: Unknown login or
authentication error on wad...@gm...@gmail-pop.l.google.com
Nov 11 12:47:17 wadesmart fetchmail[13871]: socket error while fetching
from wad...@gm...@pop.gmail.com
Nov 11 12:47:18 wadesmart fetchmail[13871]: 67 messages (57 seen) for
wad...@gm... at pop.gmail.com (7398134 octets).

and from mail.err
Nov 11 12:47:17 wadesmart fetchmail[13871]: Unknown login or
authentication error on wad...@gm...@gmail-pop.l.google.com
Nov 11 12:47:17 wadesmart fetchmail[13871]: socket error while fetching
from wad...@gm...@pop.gmail.com

wade

> -------- Original Message --------
> Subject: fetchmail authorization and socket errors
> From: wa...@wa...
> Date: Sat, November 11, 2006 10:53 am
> To: Ubuntu Users <ubu...@li...>, Ubuntu Yahoo Groups
> <ubu...@ya...>
>
> 11112006 1047 GMT-6
>
> I have traced my mail problems down (with help) to fetchmail errors.
>
> This is from mail.info log:
>
>   * Just before here I noticed that gweather applet wasnt working and
> would not update automatically or manually.
>   * And then I rebooted.
>
> Nov  9 11:30:40 wadesmart fetchmail[7668]: Unknown login or
> authentication error on wad...@gm...@gmail-pop.l.google.com
> Nov  9 11:30:40 wadesmart fetchmail[7668]: socket error while fetching
> from wad...@gm...@pop.gmail.com
> Nov  9 11:30:43 wadesmart fetchmail[7668]: 57 messages (57 seen) for
> wad...@gm... at pop.gmail.com (6345985 octets).
> Nov  9 11:35:44 wadesmart fetchmail[7668]: Unknown login or
> authentication error on wad...@gm...@gmail-pop.l.google.com
> Nov  9 11:35:44 wadesmart fetchmail[7668]: socket error while fetching
> from wad...@gm...@pop.gmail.com
> Nov  9 11:35:47 wadesmart fetchmail[7668]: 57 messages (57 seen) for
> wad...@gm... at pop.gmail.com (6345985 octets).
> Nov  9 11:39:18 wadesmart postfix/master[23958]: terminating on signal
> 15
> Nov  9 11:39:18 wadesmart dovecot: Killed with signal 15
> Nov  9 11:40:55 wadesmart postfix/master[4816]: daemon started --
> version 2.2.10, configuration /etc/postfix
> Nov  9 11:40:55 wadesmart dovecot: Dovecot v1.0.beta3 starting up
> Nov  9 11:40:55 wadesmart dovecot: Generating Diffie-Hellman parameters
> for the first time. This may take a while..
> Nov  9 11:41:01 wadesmart dovecot: ssl-build-param: SSL parameters
> regeneration completed
> Nov  9 12:02:40 wadesmart dovecot: imap-login: Login: user=<wadesmart>,
> method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
> Nov  9 13:45:16 wadesmart postfix/master[4816]: terminating on signal 15
> Nov  9 13:45:16 wadesmart dovecot: Killed with signal 15
> Nov  9 13:48:02 wadesmart postfix/master[4815]: daemon started --
> version 2.2.10, configuration /etc/postfix
> Nov  9 13:48:03 wadesmart dovecot: Dovecot v1.0.beta3 starting up
> Nov  9 13:48:03 wadesmart dovecot: Generating Diffie-Hellman parameters
> for the first time. This may take a while..
> Nov  9 13:48:43 wadesmart dovecot: imap-login: Login: user=<wadesmart>,
> method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
> Nov  9 13:48:48 wadesmart dovecot: ssl-build-param: SSL parameters
> regeneration completed
> Nov  9 13:51:46 wadesmart fetchmail[5739]: starting fetchmail 6.3.2
> daemon
> Nov  9 13:51:46 wadesmart fetchmail[5739]: Server certificate
> verification error: self signed certificate
> Nov  9 13:51:48 wadesmart fetchmail[5739]: Authorization failure on
> wadesmart@wadesmart
> Nov  9 13:51:48 wadesmart dovecot: imap-login: Aborted login:
> user=<wadesmart>, method=PLAIN, rip=127.0.1.1, lip=127.0.1.1, TLS
> Nov  9 13:51:48 wadesmart fetchmail[5739]: Query status=3 (AUTHFAIL)
> Nov  9 13:56:48 wadesmart fetchmail[5739]: Server certificate
> verification error: self signed certificate
> Nov  9 13:56:51 wadesmart fetchmail[5739]: Authorization failure on
> wadesmart@wadesmart
> Nov  9 13:56:51 wadesmart dovecot: imap-login: Aborted login:
> user=<wadesmart>, method=PLAIN, rip=127.0.1.1, lip=127.0.1.1, TLS
> Nov  9 13:56:51 wadesmart fetchmail[5739]: Query status=3 (AUTHFAIL)
> Nov  9 13:58:26 wadesmart fetchmail[5739]: terminated with signal 15
> Nov  9 13:58:30 wadesmart fetchmail[6394]: 55 messages for
> wa...@wa... at mail.wadesmart.com (387691 octets).
>
> So I see two errors: socket errors when connecting to gmail and then
> authorization errors on my own system.
> What would cause this and what can I now do about it?
>
> wade
>
>
> --
> ubuntu-users mailing list
> ubu...@li...
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Re: [fetchmail-users] fetchmail no longer getting mail

[Nico G. <ni...@ng...>]

Hi,
* wa...@wa... <wa...@wa...> [2006-11-11 15:34]:
> 11112006 0732 GMT-6
> 
> Day before yesterday I noticed that my mail wasn't being checked. And
> then I noticed that gweather applet also wouldn't connect. But I am
> still on the net so I don't think its a connectivity issue.
> 
> I just setup my system with fetchmail/postfix/dovecot to get mail.
> I have stopped fetchmail and the restarted it but that didn't get it to
> connect.
> It was working fine and then literally, it wasn't.
> 
> What could I troubleshoot?

debug output?
Kind regards
Nico
-- 
Nico Golde - http://www.ngolde.de
JAB: ni...@ja... - GPG: 0x73647CFF
Forget about that mouse with 3/4/5 buttons,
gimme a keyboard with 103/104/105 keys!

[fetchmail-users] fetchmail no longer getting mail

[<wa...@wa...>]

11112006 0732 GMT-6

Day before yesterday I noticed that my mail wasn't being checked. And
then I noticed that gweather applet also wouldn't connect. But I am
still on the net so I don't think its a connectivity issue.

I just setup my system with fetchmail/postfix/dovecot to get mail.
I have stopped fetchmail and the restarted it but that didn't get it to
connect.
It was working fine and then literally, it wasn't.

What could I troubleshoot?

wade

Re: [fetchmail-users] (no subject)

[Rob M. <rob...@gm...>]

On 11/11/06, wa...@wa... <wa...@wa...> wrote:
> 11112006 0732 GMT-6
>
> Day before yesterday I noticed that my mail wasn't being checked. And
> then I noticed that gweather applet also wouldn't connect. But I am
> still on the net so I don't think its a connectivity issue.
>
> I just setup my system with fetchmail/postfix/dovecot to get mail.
> I have stopped fetchmail and the restarted it but that didn't get it to
> connect.
> It was working fine and then literally, it wasn't.
>
> What could I troubleshoot?

Good question.  You say absolutely nothing about your setup that would
help direct you, however:

1) Check your mail log.  If you've configured fetchmail to use syslog
this will be the same as your postfix server.  Otherwise it'll be
somewhere else.

2) Try a mail check in verbose mode: "fetchmail -c --nosyslog -v -v"

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[fetchmail-users] (no subject)

[<wa...@wa...>]

11112006 0732 GMT-6

Day before yesterday I noticed that my mail wasn't being checked. And
then I noticed that gweather applet also wouldn't connect. But I am
still on the net so I don't think its a connectivity issue.

I just setup my system with fetchmail/postfix/dovecot to get mail.
I have stopped fetchmail and the restarted it but that didn't get it to
connect.
It was working fine and then literally, it wasn't.

What could I troubleshoot?

wade

Re: [fetchmail-users] Change message as it is resent?

[David D. <dda...@ya...>]

Matthias Andree <mat...@gm...> wrote:\
   
You can use one of the tiny sendmail-to-SMTP clients (too many to list)
along with a shell script and use this shell script as "mda" to
fetchmail. Adding said header can be done with reformail which ships in
Sam Varshavchik's "maildrop" package.

Thanks for the tip.

If I go the "mda" route, my little custom mda needs to be responsible for reliable delivery.   (Right?)  As far as fetchmail is concerned, the mail was sent successfully even if the final SMTP server down. Seems tricky.

If I can't do this in fetchmail itself, perhaps an SMTP-to-SMTP data-munging proxy  is the better route?  Does such a thing exist?

Also, can fetchmail "walk" all (or a subset of) an account's SMTP folders, or do I need to create a separate poll entry for each folder?

Thanks,
David

 
---------------------------------
Everyone is raving about the all-new Yahoo! Mail.

Re: [fetchmail-users] Change message as it is resent?

[Matthias A. <mat...@gm...>]

David Davis <dda...@ya...> writes:

> Does fetchmail have anyway to modify the email that it
> retrieves/resends?

Not something that you could script - you'll have to hook up your own
scripts.

> For instance, I need to move messages from an IMAP server to a POP server via
> SMTP. (Don't ask.)
>
> Anyway, the messages on the IMAP server are in folders, and I need someway to
> tell the POP client from where the message originated.  (Need to add a prefix
> to the the subject line, and add an internal 'x-orig-folder:' header)

You can use one of the tiny sendmail-to-SMTP clients (too many to list)
along with a shell script and use this shell script as "mda" to
fetchmail. Adding said header can be done with reformail which ships in
Sam Varshavchik's "maildrop" package.

HTH,

-- 
Matthias Andree

[fetchmail-users] Change message as it is resent?

[David D. <dda...@ya...>]

Hello,
 
 Does fetchmail have anyway to modify the email that it retrieves/resends?
 
 For instance, I need to move messages from an IMAP server to a POP server via SMTP. (Don't ask.)
 
 Anyway, the messages on the IMAP server are in folders, and I need someway to tell the POP client from where the message originated.  (Need to add a prefix to the the subject line, and add an internal 'x-orig-folder:' header)
 
 Can this be done with fetchmail?
 
 Thanks,
 David
 
 
---------------------------------
Want to start your own business? Learn how on Yahoo! Small Business.

Re: [fetchmail-users] Fetchmail Error Message

[Gerard S. <ge...@se...>]

On Monday November 06, 2006 at 12:39:21 (PM) cron wrote:

> On Sun, Nov 05, 2006 at 03:28:34PM -0500, Gerard Seibert wrote:
> > FreeBSD 6.1 STABLE
> > Postfix-2.4-20061019
> > Fetchmail release 6.3.5+RPA+SDPS+SSL+OPIE+NLS.
> > 
> > I have just updated to the latest version of Fetchmail. Prior to this
> > update, Fetchmail had run flawlessly. Unfortunately, it now appears to
> > be suffering some problems.
> > 
> > This is a truncated version of my /var/log/maillog:
> > 
> > Nov  5 00:01:28 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4441 octets).
> > Nov  5 00:01:29 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4441 octets) (log message incomplete)
> > Nov  5 00:01:29 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
> 
> you can't connect to postfix
> try another mda in fetchmai and see if it works


I have already corrected the problem. It seems that the new version of
Fetchmail treats IPv6 differently than the older version. I simply
disabled IPv6 on my system and the problem went away. There is no reason
to use IPv6 presently anyway. It really only exists in a lab.

The developers of Fetchmail might want to investigate this further
though.

-- 
Gerard

Re: [fetchmail-users] Fetchmail Error Message

[<cr...@zm...>]

On Sun, Nov 05, 2006 at 03:28:34PM -0500, Gerard Seibert wrote:
> FreeBSD 6.1 STABLE
> Postfix-2.4-20061019
> Fetchmail release 6.3.5+RPA+SDPS+SSL+OPIE+NLS.
> 
> I have just updated to the latest version of Fetchmail. Prior to this
> update, Fetchmail had run flawlessly. Unfortunately, it now appears to
> be suffering some problems.
> 
> This is a truncated version of my /var/log/maillog:
> 
> Nov  5 00:01:28 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4441 octets).
> Nov  5 00:01:29 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4441 octets) (log message incomplete)
> Nov  5 00:01:29 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.

you can't connect to postfix
try another mda in fetchmai and see if it works

Re: [fetchmail-users] Fetchmail Error Message

[Gerard S. <ge...@se...>]

On Sunday November 05, 2006 at 04:17:43 (PM) Rob MacGregor wrote:

> Looks like you've got "localhost" resolving via IPv6 but your SMTP
> server isn't listening on IPv6 (and you really only needed to post one
> copy of the error :>).
> 
> You'll want to either configure postfix to listen on IPv6 or give
> fetchmail a hostname that only has an IPv4 address.
> 
> This may only have come to light as a result of some of the IPv6 fixes
> mentioned in the fetchmail change log.


OK, I will disable IPv6 support, reboot the system and see what
transpires. I don't need it anyway. I just never bothered to turn it off.

Thanks!

-- 
Gerard

Re: [fetchmail-users] Fetchmail Error Message

[Rob M. <rob...@gm...>]

On 11/5/06, Gerard Seibert <ge...@se...> wrote:
> FreeBSD 6.1 STABLE
> Postfix-2.4-20061019
> Fetchmail release 6.3.5+RPA+SDPS+SSL+OPIE+NLS.
>
> I have just updated to the latest version of Fetchmail. Prior to this
> update, Fetchmail had run flawlessly. Unfortunately, it now appears to
> be suffering some problems.
>
> This is a truncated version of my /var/log/maillog:
>
> Nov  5 00:01:28 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4441 octets).
> Nov  5 00:01:29 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4441 octets) (log message incomplete)
> Nov  5 00:01:29 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
<---SNIP--->
> It does not appear that I am losing any mail. However, all of the
> accounts are not setup as of yet. Once the system is fully functional, I
> cannot afford to have any problems.
>
> As I previously stated, I never experienced any problems with the older
> version of Fetchmail. Since that is the only thing that I have updated
> in a few weeks, this problem has to be related to that update.

Looks like you've got "localhost" resolving via IPv6 but your SMTP
server isn't listening on IPv6 (and you really only needed to post one
copy of the error :>).

You'll want to either configure postfix to listen on IPv6 or give
fetchmail a hostname that only has an IPv4 address.

This may only have come to light as a result of some of the IPv6 fixes
mentioned in the fetchmail change log.

-- 
                 Please keep list traffic on the list.

Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

[fetchmail-users] Fetchmail Error Message

[Gerard S. <ge...@se...>]

FreeBSD 6.1 STABLE
Postfix-2.4-20061019
Fetchmail release 6.3.5+RPA+SDPS+SSL+OPIE+NLS.

I have just updated to the latest version of Fetchmail. Prior to this
update, Fetchmail had run flawlessly. Unfortunately, it now appears to
be suffering some problems.

This is a truncated version of my /var/log/maillog:

Nov  5 00:01:28 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4441 octets).
Nov  5 00:01:29 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4441 octets) (log message incomplete)
Nov  5 00:01:29 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 00:16:43 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (6285 octets).
Nov  5 00:16:43 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (6285 octets) (log message incomplete)
Nov  5 00:16:43 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 00:47:11 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (5580 octets).
Nov  5 00:47:11 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (5580 octets) (log message incomplete)
Nov  5 00:47:11 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 01:02:26 scorpio fetchmail[734]: 3 messages for ge...@se... at pop.gmail.com (13809 octets).
Nov  5 01:02:26 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 3 (4207 octets) (log message incomplete)
Nov  5 01:02:26 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 01:17:42 scorpio fetchmail[734]: 3 messages for ge...@se... at pop.gmail.com (13385 octets).
Nov  5 01:17:42 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 3 (5074 octets) (log message incomplete)
Nov  5 01:17:42 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 01:17:52 scorpio fetchmail[734]: 1 message for bee...@sp... at pop.spamcop.net (2679 octets).
Nov  5 01:17:52 scorpio fetchmail[734]: reading message bee...@sp...@pop.spamcop.net:1 of 1 (2679 octets) (log message incomplete)
Nov  5 01:17:52 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 01:17:53 scorpio fetchmail[734]: 1 message for gerard-seibert at mail.comcast.net (25369 octets).
Nov  5 01:17:53 scorpio fetchmail[734]: reading message ger...@ma...:1 of 1 (25369 octets) (log message incomplete)
Nov  5 01:17:53 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 01:32:58 scorpio fetchmail[734]: 3 messages for ge...@se... at pop.gmail.com (13104 octets).
Nov  5 01:32:59 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 3 (4710 octets) (log message incomplete)
Nov  5 01:32:59 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 01:33:11 scorpio fetchmail[734]: 1 message for bee...@sp... at pop.spamcop.net (2682 octets).
Nov  5 01:33:11 scorpio fetchmail[734]: reading message bee...@sp...@pop.spamcop.net:1 of 1 (2682 octets) (log message incomplete)
Nov  5 01:33:11 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 02:18:43 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (3063 octets).
Nov  5 02:18:44 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (3063 octets) (log message incomplete)
Nov  5 02:18:44 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 02:33:58 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (10698 octets).
Nov  5 02:33:59 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (5862 octets) (log message incomplete)
Nov  5 02:33:59 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 02:49:13 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4368 octets).
Nov  5 02:49:14 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4368 octets) (log message incomplete)
Nov  5 02:49:14 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 03:19:48 scorpio fetchmail[734]: 1 message for gerard-seibert at mail.comcast.net (53903 octets).
Nov  5 03:19:48 scorpio fetchmail[734]: reading message ger...@ma...:1 of 1 (53903 octets) (log message incomplete)
Nov  5 03:19:48 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 03:35:56 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (3871 octets).
Nov  5 03:35:57 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (3871 octets) (log message incomplete)
Nov  5 03:35:57 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 03:36:05 scorpio fetchmail[734]: 1 message for gerard-seibert at mail.comcast.net (19008 octets).
Nov  5 03:36:05 scorpio fetchmail[734]: reading message ger...@ma...:1 of 1 (19008 octets) (log message incomplete)
Nov  5 03:36:05 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 03:51:11 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (9056 octets).
Nov  5 03:51:12 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (9056 octets) (log message incomplete)
Nov  5 03:51:12 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 04:06:26 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4897 octets).
Nov  5 04:06:26 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4897 octets) (log message incomplete)
Nov  5 04:06:26 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 04:21:41 scorpio fetchmail[734]: 4 messages for ge...@se... at pop.gmail.com (19228 octets).
Nov  5 04:21:41 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 4 (5159 octets) (log message incomplete)
Nov  5 04:21:41 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 04:21:45 scorpio fetchmail[734]: 4 messages for ger...@gm... at pop.gmail.com (19278 octets).
Nov  5 04:21:45 scorpio fetchmail[734]: reading message ger...@gm...@gmail-pop.l.google.com:1 of 4 (5171 octets) (log message incomplete)
Nov  5 04:21:45 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 04:36:59 scorpio fetchmail[734]: 1 message for ger...@gm... at pop.gmail.com (5227 octets).
Nov  5 04:36:59 scorpio fetchmail[734]: reading message ger...@gm...@gmail-pop.l.google.com:1 of 1 (5227 octets) (log message incomplete)
Nov  5 04:36:59 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 05:07:24 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (8169 octets).
Nov  5 05:07:25 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (3921 octets) (log message incomplete)
Nov  5 05:07:25 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 05:22:40 scorpio fetchmail[734]: 5 messages for ge...@se... at pop.gmail.com (19922 octets).
Nov  5 05:22:40 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 5 (5131 octets) (log message incomplete)
Nov  5 05:22:40 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 05:37:57 scorpio fetchmail[734]: 4 messages for ge...@se... at pop.gmail.com (17748 octets).
Nov  5 05:37:57 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 4 (3556 octets) (log message incomplete)
Nov  5 05:37:57 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 05:53:13 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (9826 octets).
Nov  5 05:53:14 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (4913 octets) (log message incomplete)
Nov  5 05:53:14 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 06:08:28 scorpio fetchmail[734]: 5 messages for ge...@se... at pop.gmail.com (23260 octets).
Nov  5 06:08:28 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 5 (2371 octets) (log message incomplete)
Nov  5 06:08:28 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 06:23:45 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (17912 octets).
Nov  5 06:23:46 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (4209 octets) (log message incomplete)
Nov  5 06:23:46 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 06:39:00 scorpio fetchmail[734]: 3 messages for ge...@se... at pop.gmail.com (11760 octets).
Nov  5 06:39:01 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 3 (3766 octets) (log message incomplete)
Nov  5 06:39:01 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 06:54:18 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (9014 octets).
Nov  5 06:54:19 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (4093 octets) (log message incomplete)
Nov  5 06:54:19 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:09:33 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (56827 octets).
Nov  5 07:09:34 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (56827 octets) (log message incomplete)
Nov  5 07:09:34 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:24:48 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4189 octets).
Nov  5 07:24:48 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4189 octets) (log message incomplete)
Nov  5 07:24:48 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:24:56 scorpio fetchmail[734]: 1 message for bee...@sp... at pop.spamcop.net (3328 octets).
Nov  5 07:24:57 scorpio fetchmail[734]: reading message bee...@sp...@pop.spamcop.net:1 of 1 (3328 octets) (log message incomplete)
Nov  5 07:24:57 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:40:04 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (6122 octets).
Nov  5 07:40:05 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (6122 octets) (log message incomplete)
Nov  5 07:40:05 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:40:13 scorpio fetchmail[734]: 1 message for bee...@sp... at pop.spamcop.net (3638 octets).
Nov  5 07:40:13 scorpio fetchmail[734]: reading message bee...@sp...@pop.spamcop.net:1 of 1 (3638 octets) (log message incomplete)
Nov  5 07:40:13 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:56:20 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (7768 octets).
Nov  5 07:56:20 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (4798 octets) (log message incomplete)
Nov  5 07:56:20 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 07:56:28 scorpio fetchmail[734]: 1 message for bee...@sp... at pop.spamcop.net (3542 octets).
Nov  5 07:56:28 scorpio fetchmail[734]: reading message bee...@sp...@pop.spamcop.net:1 of 1 (3542 octets) (log message incomplete)
Nov  5 07:56:28 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 08:11:36 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (5639 octets).
Nov  5 08:11:36 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (2187 octets) (log message incomplete)
Nov  5 08:11:36 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 08:26:53 scorpio fetchmail[734]: 1 message for ge...@se... at pop.gmail.com (4127 octets).
Nov  5 08:26:54 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 1 (4127 octets) (log message incomplete)
Nov  5 08:26:54 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 08:42:12 scorpio fetchmail[734]: 2 messages for ge...@se... at pop.gmail.com (8244 octets).
Nov  5 08:42:13 scorpio fetchmail[734]: reading message ge...@se...@gmail-pop.l.google.com:1 of 2 (3922 octets) (log message incomplete)
Nov  5 08:42:13 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.
--
Nov  5 08:42:22 scorpio fetchmail[734]: 5 messages for gerard-seibert at mail.comcast.net (23670 octets).
Nov  5 08:42:22 scorpio fetchmail[734]: reading message ger...@ma...:1 of 5 (5275 octets) (log message incomplete)
Nov  5 08:42:22 scorpio fetchmail[734]: connection to localhost:smtp [::1/25] failed: Connection refused.


It does not appear that I am losing any mail. However, all of the
accounts are not setup as of yet. Once the system is fully functional, I
cannot afford to have any problems.

As I previously stated, I never experienced any problems with the older
version of Fetchmail. Since that is the only thing that I have updated
in a few weeks, this problem has to be related to that update.


-- 
Gerard
ge...@se...


Ah, SASL, the dark side of authentication it is.
Yes, tempting, easy - but ultimately destroy you it will!
But fear the path of misconfiguration, you should!

Re: [fetchmail-users] Script to check all user accounts

[Net C. <net...@gm...>]

On 11/2/06, Matthias Andree <mat...@gm...> wrote:
>
> "Rob MacGregor" <rob...@gm...> writes:
>
> > I've a vague memory somebody posted something to the list a while
> > back.  If there isn't anything I could probably knock something out
> > over the weekend - it's not terribly complicated.
>
> Check the start script Simon Barner wrote for the FreeBSD port - it
> relies on FreeBSD's rcNG (rc_subr) though.
>
>
Will check out the archives today and see if I can find something. Thanks
for you the help.