fetchmail-users

[fetchmail-users] option -v not working...

[Dave P. <sd...@gm...>]

Hello all.  If this has been posted already, I apologize.

I'm not able to get output to terminal using fetchmail -v

fetchmail executes normally (I think) as the mail is being delivered to
procmail, and from there to my various boxes.  However, I have no
indication as to messages retrieved, skipped, etc.  Where to look?

Cheers, Dave

Re: [fetchmail-users] option -v not working...

[Frederic M. <fre...@wo...>]

Dave Patterson wrote:
> Hello all.  If this has been posted already, I apologize.
>   

I think it has been answered several times and by people more 
knowledgeable than me... :-)

> I'm not able to get output to terminal using fetchmail -v
>
> fetchmail executes normally (I think) as the mail is being delivered to
> procmail, and from there to my various boxes.  However, I have no
> indication as to messages retrieved, skipped, etc.  Where to look?
>   

In my case, when fetchmail runs in daemon mode (-d option), I also 
specify the --syslog option and the outputs are written to 
/var/log/mail.info but it really depends on the configuration of syslog.

Frederic

Re: [fetchmail-users] option -v not working...

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

Dave Patterson <sd...@gm...> writes:

> Hello all.  If this has been posted already, I apologize.
>
> I'm not able to get output to terminal using fetchmail -v

Add --nodetach --nosyslog to the command line.

> fetchmail executes normally (I think) as the mail is being delivered to
> procmail, and from there to my various boxes.  However, I have no
> indication as to messages retrieved, skipped, etc.  Where to look?

Otherwise, syslog (/var/log/mail, /var/log/maillog, or thereabouts).

-- 
Matthias Andree

Re: [fetchmail-users] option -v not working...

[Dave P. <sd...@gm...>]

* Matthias Andree <mat...@gm...> [2006-06-26 09:38:17 +0200]:

 
> Add --nodetach --nosyslog to the command line.
> 
No luck.
> Otherwise, syslog (/var/log/mail, /var/log/maillog, or thereabouts).
> 
None there, either... 

Regards, Dave

Re: [fetchmail-users] option -v not working...

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

Dave Patterson <sd...@gm...> writes:

> * Matthias Andree <mat...@gm...> [2006-06-26 09:38:17 +0200]:
>
>  
>> Add --nodetach --nosyslog to the command line.
>> 
> No luck.
>> Otherwise, syslog (/var/log/mail, /var/log/maillog, or thereabouts).
>> 
> None there, either... 

--logfile (or set logfile) used?

-- 
Matthias Andree

Re: [fetchmail-users] option -v not working...

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

On 6/26/06, Dave Patterson <sd...@gm...> wrote:
> Hello all.  If this has been posted already, I apologize.
>
> I'm not able to get output to terminal using fetchmail -v

Version of fetchmail?

Contents of .fetchmailrc?

Any command line arguments passed to fetchmail (and what are they)?

-- 
                 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] option -v not working...

[Dave P. <sd...@gm...>]

* Rob MacGregor <rob...@gm...> [2006-06-26 10:12:26 +0100]:

 
> Version of fetchmail?
> 
Debian's fetchmail package # 6.3.4-1

('fetchmail -V' or fetchmail --version' results in fetchmail retrieving mail and passing it to Procmail, but the version request is ignored - interesting)

> 
> Any command line arguments passed to fetchmail (and what are they)?
> 
Command line arguments thus far have been '-V'  '--version' '--nodetach
--nosyslog' '-v'

Contents of .fetchmailrc :

<cut>

set syslog
set logfile=~/.fetchmaillog

poll pop.gmail.com with proto POP3 and options no dns 
    user 'XX...@gm...' with pass "XXX"  is 'dave' here options
    ssl 
    mda '/usr/bin/procmail -d %T'

    poll pop.mail.yahoo.com with protocol pop3,
    user XXX there is dave here,
    with password XXX;
    mda '/usr/bin/procmail -d %T'

    poll net1.ji-net.com with protocol pop3,
    user XXX there is dave here,
    with password XXX;
    mda '/usr/bin/procmail -d %T'

    poll 127.0.0.1 port 110 with protocol pop3,
    user 'XXX' with pass "XXX" is
    'dave' here,
    mda '/usr/bin/procmail -d %T

<cut>


Hmmm..

Cheers, Dave

Re: [fetchmail-users] option -v not working...

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

On 6/26/06, Dave Patterson <sd...@gm...> wrote:
>
> Contents of .fetchmailrc :
>
> <cut>
>
> set syslog
> set logfile=~/.fetchmaillog

So, what's in that logfile?

-- 
                 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] option -v not working...

[Dave P. <sd...@gm...>]

* Rob MacGregor <rob...@gm...> [2006-06-26 17:57:10 +0100]:

> So, what's in that logfile?
> 
dave@davescrunch:~$ cat .fetchmaillog
dave@davescrunch:~$

--
Cheers,

  Dave 

Re: [fetchmail-users] option -v not working...

[Dave P. <sd...@gm...>]

* Rob MacGregor <rob...@gm...> [2006-06-26 17:57:10 +0100]:

> On 6/26/06, Dave Patterson <sd...@gm...> wrote:
> >
> >Contents of .fetchmailrc :
> >
> ><cut>
> >
> >set syslog
> >set logfile=~/.fetchmaillog
> 
Removed 'set syslog', edited 'set logfile' line to read:

set logfile = /home/dave/.fetchmaillog

All good now.  Thanks for your time.  I'll go crawl back under my rock.

-- 
Cheers,

  Dave 

Re: [fetchmail-users] option -v not working...

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

Dave Patterson <sd...@gm...> writes:

> * Rob MacGregor <rob...@gm...> [2006-06-26 17:57:10 +0100]:
>
>> On 6/26/06, Dave Patterson <sd...@gm...> wrote:
>> >
>> >Contents of .fetchmailrc :
>> >
>> ><cut>
>> >
>> >set syslog
>> >set logfile=~/.fetchmaillog
>> 
> Removed 'set syslog', edited 'set logfile' line to read:
>
> set logfile = /home/dave/.fetchmaillog
>
> All good now.  Thanks for your time.  I'll go crawl back under my rock.

Hang on - this means that fetchmail was utterly confused because it
couldn't open the literal ~ directory? And handle --version improperly?
Looks a bit odd -- and --nodetach is supposed to override --logfile
<scratches head>

I think I'll play with this a bit more before 6.3.5 and see if there's
something to make fetchmail better behaved.

I've put this onto my TODO.txt.

Thanks for sharing the details!

-- 
Matthias Andree

Re: [fetchmail-users] option -v not working...

[Dave P. <sd...@gm...>]

* Matthias Andree <mat...@gm...> [2006-06-28 02:53:30 +0200]:


> Hang on - this means that fetchmail was utterly confused because it
> couldn't open the literal ~ directory? And handle --version improperly?
> Looks a bit odd -- and --nodetach is supposed to override --logfile
> <scratches head>
> 
Oh.  I was thinking that it tried to write to syslog (which I don't allow
userspace to do) first, and reporting instead went to /dev/null due to
system config.  Let me play with a couple settings here and I'll get back
to list. 

-- 
Cheers,

  Dave 

Re: [fetchmail-users] option -v not working...

[Dave P. <sd...@gm...>]

* Dave Patterson <sd...@gm...> [2006-06-28 08:58:29 +0700]:


> Let me play with a couple settings here and I'll get back
> to list. 
Ok, here it is:

set syslog DOES send status report to /var/log/mail.log, file cannot be read by
normal user, this setting cannot be overriden by command line option
--nodetach

set logfile MUST be given the full path to logfile
(/home/dave/.fetchmaillog) NOT ~/.fetchmaillog or the .fetchmailrc line
'set logfile' is ignored and status is printed to screen.  This option CAN
be overridden by the option --nodetach

'set syslog' line before 'set logfile' line in .fetchmailrc has the effect
of using 'set syslog' first, the second option ignored... (as most .rc files
are executed top to bottom in common usage)

-- 
Cheers,

  Dave