fetchmail-users — User questions and discussion

Re: [fetchmail-users] query state=2 (SOCKET)

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

"Roberto Meyer" <rob...@gm...> writes:

> 2006/9/13, Rob MacGregor <rob...@gm...>:
>
>> On 9/12/06, Roberto Meyer <rob...@gm...> wrote:
>> >
>> > Still having problems with it, I decided to put tcpdump in action. The
>> > problem is I don't really know much about it. I read the man pages and
>> > understood a little about flags, etc. but don't know a lot of tcp/ip.
>> >
>> > I've attached the output of two connections triggered at the same time
>> > for two different users through cron jobs. One of them was successful,
>> > the other one failed with a socket, status=2 result.
>> >
>> > The command I issued was:
>> > "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"
>> >
>> > I've attached the 'text' version of it which I rescued through
>> > "tcpdump -r /tmp/tcpdump.raw"
>>
>> Separating the 2 is, sadly, not possible.  If you could capture one
>> working run and one failed run then I *may* be able to help work out
>> what's going wrong.  It would help to have the binary pcap of the
>> failed run, though obviously you'd need to change passwords
>> immediately afterwards (or before and after) for security reasons.
>
> Finally I got a couple of errors with single connections.

Please update fetchmail (newer versions have fewer bugs and better error
reporting) and if the problem persists, run:

env LC_ALL=C fetchmail -vvv --nodetach --nosyslog -d0

to obtain a more detailed log. However, it still looks like the problem
is outside fetchmail to me.

-- 
Matthias Andree

Re: [fetchmail-users] query state=2 (SOCKET)

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

On 9/13/06, Roberto Meyer <rob...@gm...> wrote:
>
> Finally I got a couple of errors with single connections.
>
> I've attached a .tgz file with the logs of fetchmail and tcpdump at
> the moment of the errors, and both logs for a well done connection
> too.

A quick scan of the logs show what I'd expect for a networking
problem.  I'll have a look at the text outputs from tcpdump later,
though a quick scan doesn't show anything obvious right now.

> "cat /proc/sys/net/ipv4/tcp_ecn" returns "0" (zero)

Ok, so ECN isn't on so can't be the source of the problem (which is a
confirmation of what I already suspected).

> "ifconfig eth0" returns:
>
> eth0    Link encap:Ethernet  HWaddr 11:50:24:64:09:BE
>           inet addr:201.65.9.43  Bcast:201.65.9.255  Mask:255.255.255.224
>                                                    ^^^^^^^^^^^^^^^^
> I noticed here broadcast address is wrong... could this be hurting
> packets or fetchmail connections? It should be 201.65.9.63 because of
> the netmask...

Well, that won't matter to fetchmail.  It'll only matter when
something does a broadcast (like DHCP).

> Thanx a lot for your help.

So far, everything seems to point to intermittent network problems
somewhere in the path from your host to the remote POP server.  It
could be that the other software doesn't report these errors, or it
could be that something about the network topology means they take a
different route...

Once I've had the time to take a better look at the tcpdump output
I'll get back to you.

-- 
                 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] query state=2 (SOCKET)

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

2006/9/13, Rob MacGregor <rob...@gm...>:

> On 9/12/06, Roberto Meyer <rob...@gm...> wrote:
> >
> > Still having problems with it, I decided to put tcpdump in action. The
> > problem is I don't really know much about it. I read the man pages and
> > understood a little about flags, etc. but don't know a lot of tcp/ip.
> >
> > I've attached the output of two connections triggered at the same time
> > for two different users through cron jobs. One of them was successful,
> > the other one failed with a socket, status=2 result.
> >
> > The command I issued was:
> > "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"
> >
> > I've attached the 'text' version of it which I rescued through
> > "tcpdump -r /tmp/tcpdump.raw"
>
> Separating the 2 is, sadly, not possible.  If you could capture one
> working run and one failed run then I *may* be able to help work out
> what's going wrong.  It would help to have the binary pcap of the
> failed run, though obviously you'd need to change passwords
> immediately afterwards (or before and after) for security reasons.

Finally I got a couple of errors with single connections.

I've attached a .tgz file with the logs of fetchmail and tcpdump at
the moment of the errors, and both logs for a well done connection
too.


> Can you provide the output of "ifconfig eth0" (feel free to mangle MAC
> and IP addresses) and "cat /proc/sys/net/ipv4/tcp_ecn"?

"cat /proc/sys/net/ipv4/tcp_ecn" returns "0" (zero)

"ifconfig eth0" returns:

eth0    Link encap:Ethernet  HWaddr 11:50:24:64:09:BE
          inet addr:201.65.9.43  Bcast:201.65.9.255  Mask:255.255.255.224
                                                   ^^^^^^^^^^^^^^^^
I noticed here broadcast address is wrong... could this be hurting
packets or fetchmail connections? It should be 201.65.9.63 because of
the netmask...

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1240552 errors:34 dropped:0 overruns:0 frame:34
          TX packets:636714 errors:0 dropped:0 overruns:0 carrier:105
          collisions:0 txqueuelen:1000
          RX bytes:397976183 (379.5 MiB)  TX bytes:78105812 (74.4 MiB)
          Interrupt:14 Base address:0xdc00

Carrier error were due to a cable unplug a week ago.

As far as I checked, frame errors don't seem to be directly related to
fetchmail problems.

I'll change broadcast setup, though I didn't write it in
/etc/init.d/interfaces, I only specified address, network and
gateway... I'm surprised Linux didn't calculate it well...

Thanx a lot for your help.

-- 
Roberto

Re: [fetchmail-users] query state=2 (SOCKET)

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

On 9/12/06, Roberto Meyer <rob...@gm...> wrote:
>
> Still having problems with it, I decided to put tcpdump in action. The
> problem is I don't really know much about it. I read the man pages and
> understood a little about flags, etc. but don't know a lot of tcp/ip.
>
> I've attached the output of two connections triggered at the same time
> for two different users through cron jobs. One of them was successful,
> the other one failed with a socket, status=2 result.
>
> The command I issued was:
> "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"
>
> I've attached the 'text' version of it which I rescued through
> "tcpdump -r /tmp/tcpdump.raw"

Separating the 2 is, sadly, not possible.  If you could capture one
working run and one failed run then I *may* be able to help work out
what's going wrong.  It would help to have the binary pcap of the
failed run, though obviously you'd need to change passwords
immediately afterwards (or before and after) for security reasons.

I still think you'll get some information from a simple telnet.  That
at least will confirm that it's not fetchmail that's at fault.  Worth
noting that things like ECN can cause problems with remote mail
servers.

Can you provide the output of "ifconfig eth0" (feel free to mangle MAC
and IP addresses) and "cat /proc/sys/net/ipv4/tcp_ecn"?

-- 
                 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] query state=2 (SOCKET)

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

2006/9/12, Rob MacGregor <rob...@gm...>:

> On 9/11/06, Roberto Meyer <rob...@gm...> wrote:
> > Hi,
> >
> > I translated the error message in the subject of this mail from
> > spanish, I don't know if it shows exactly like this in other systems.
> The error relates to fetchmail being unable to communicate with the
> remote server.  This is almost always a network issue.

[snip]

Still having problems with it, I decided to put tcpdump in action. The
problem is I don't really know much about it. I read the man pages and
understood a little about flags, etc. but don't know a lot of tcp/ip.

I've attached the output of two connections triggered at the same time
for two different users through cron jobs. One of them was successful,
the other one failed with a socket, status=2 result.

The command I issued was:
"tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"

I've attached the 'text' version of it which I rescued through
"tcpdump -r /tmp/tcpdump.raw"

I know this is a bit off-topic but as this thread started with
fetchmail maybe someone knows help:

TIA,

PD: the mail server is only one and always the same, at least it
resolves always to a single IP.

-- 
Roberto

Re: [fetchmail-users] query state=2 (SOCKET)

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

On 9/11/06, Roberto Meyer <rob...@gm...> wrote:
> Hi,
>
> I translated the error message in the subject of this mail from
> spanish, I don't know if it shows exactly like this in other systems.
>
> I'm running processes for each user from crontabs. I get error
> messages, not always, not always from the same user's cron job. I'm
> running Debian Sarge with fetchmail: 6.2.5.

Please update to 6.3 (though it probably won't help this particular case).

> I'm stuck. I've tried IMAP and POP3 and didn't find much difference.
> Fetchmail is connecting to Courier-IMAP or/and Courier-POP.

The error relates to fetchmail being unable to communicate with the
remote server.  This is almost always a network issue.

> fetchmail: 6.2.5 interrogando a mail.mydomain.com (protocolo POP3) en lun 11 s
>  iniciada
> fetchmail: error `socket' recibiendo de mail.mydomain.com
> fetchmail: 6.2.5 interrogando mail.mydomain.com (protocolo POP3) en lun 11 sep
> erminada
> fetchmail: Estado de la consulta=2 (SOCKET)
> fetchmail: terminación normal, estado 2
<---SNIP--->
> I'll appreciate any help. TIA,

One test you can try is to see if "telnet mail.mydomain.com 110" works
consistently.  You may find that you've got a number of remote
mailservers and one of them is causing this problem.

Without real domain names for the ISP it's hard to say more.

-- 
                 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] query state=2 (SOCKET)

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

Hi,

I translated the error message in the subject of this mail from
spanish, I don't know if it shows exactly like this in other systems.

I'm running processes for each user from crontabs. I get error
messages, not always, not always from the same user's cron job. I'm
running Debian Sarge with fetchmail: 6.2.5.

I'm stuck. I've tried IMAP and POP3 and didn't find much difference.
Fetchmail is connecting to Courier-IMAP or/and Courier-POP.

Each user has a .fetchmailrc which looks like this:
poll mail.mydomain.com
        protocol POP3
        user "us...@my..."
        pass "pass"
        smtpaddress "mydomain.com"

Each user's cron job (8 at this time) is set to:
*/5 * * * *     fetchmail -vvv 1>> fe.log 2>&1

where fe.log is a log file at user's home directory.

Here the error I found at many fe.log:

fetchmail: 6.2.5 interrogando a mail.mydomain.com (protocolo POP3) en lun 11 s
 iniciada
fetchmail: error `socket' recibiendo de mail.mydomain.com
fetchmail: 6.2.5 interrogando mail.mydomain.com (protocolo POP3) en lun 11 sep
erminada
fetchmail: Estado de la consulta=2 (SOCKET)
fetchmail: terminación normal, estado 2


As a plus, people at this organization is downloading mail using
something calles "mail diamond" for Winbug without problem :-(

I'll appreciate any help. TIA,

-- 
Roberto

Re: [fetchmail-users] Questions FETCHMAIL-DAEMON & qvirtual

[Neil W. <ne...@dc...>]

Thanks Matthias,

> Any only halfway recent fetchmail version will use an empty envelope
> sender address, avoiding that problem.

Thanks, I've upgraded it and it's now sending them from a blank address, so it's working.

>> So I somehow need to be able to add qvirtual for each domain that the
>> multi drop mailbox supports.
> 
> Not at this time I'm afraid - send patches - or even better tell them to
> stop doing that nonsense. 

Ok, I'll see what I can do.'

Thanks again Matthias!

Neil

-- 
This email and all contents are subject to the following disclaimer:
http://www.dcdata.co.za/emaildisclaimer.html

Re: [fetchmail-users] Fetchmail homepage?

[Neil W. <ne...@dc...>]

Rob Funk wrote:
> Neil Wilson wrote:
>>
>> Has the site been moved, or is it just temporarily down?
> 
> Must have been temporary, because it looks fine to me right now.
> 
It's working again now, so must have been a temp problem.
I know berlios was doing an upgrade on the 6th Sept so maybe this has something to do with it.

Thanks!

-- 
This email and all contents are subject to the following disclaimer:
http://www.dcdata.co.za/emaildisclaimer.html

Re: [fetchmail-users] Fetchmail homepage?

[Rob F. <rf...@fu...>]

Neil Wilson wrote:
> I tried to go to the fetchmail homepage http://fetchmail.berlios.de/ and
> got the following.
>
> Gone
> The requested resource
> /
> is no longer available on this server and there is no forwarding
> address. Please remove all references to this resource. Apache/1.3.27
> Server at fetchmail.berlios.de Port 80
>
>
> Has the site been moved, or is it just temporarily down?

Must have been temporary, because it looks fine to me right now.

-- 
==============================|   "A microscope locked in on one point
 Rob Funk <rf...@fu...> |Never sees what kind of room that it's in"
 http://www.funknet.net/rfunk |    -- Chris Mars, "Stuck in Rewind"

[fetchmail-users] Fetchmail homepage?

[Neil W. <ne...@dc...>]

I tried to go to the fetchmail homepage http://fetchmail.berlios.de/ and got the following.

Gone
The requested resource
/
is no longer available on this server and there is no forwarding address. Please remove all references to this resource.
Apache/1.3.27 Server at fetchmail.berlios.de Port 80


Has the site been moved, or is it just temporarily down?

Thanks.

Neil

-- 
This email and all contents are subject to the following disclaimer:
http://www.dcdata.co.za/emaildisclaimer.html

Re: [fetchmail-users] Questions FETCHMAIL-DAEMON & qvirtual

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

Neil Wilson <ne...@dc...> writes:

> Hi guys,
>
> I have two questions regarding fetchmail.
>
> The first one is...
>
> One of our ISP's SMTP servers is discarding all mail that comes from FETCHMAIL-DAEMON@domain so miss-addressed bounced messages aren't getting back to the 
> original senders.

Any only halfway recent fetchmail version will use an empty envelope
sender address, avoiding that problem.

> Is there a way to change the address that fetchmail bounces mail
>from(the sender address of the bounced message) instead of
>FETCHMAIL-DAEMON?

No.

> My next questions is...
>
> I have a client who collects email from a multi-drop mailbox with a local domain of domain1.co.za
> EG: user bla with password "blabla" is * here
>
> At the moment I'm using "envelope To:" as the envelope, but I'd like to use "Delivered-To:" because the mail is originating from a qmail server and mail from 
> mailing lists etc.(Bcc'd) mail is bouncing.
>
> The qmail server adds on a dom...@do... so I'd like to use qvirtual "domain1.co.za-" part, but the problem is that the mailbox has multiple 
> domains attached to it.
>
> eg: localdomains: domain1.co.za domain2.co.za domain3.co.za
>
> So I somehow need to be able to add qvirtual for each domain that the
> multi drop mailbox supports.

Not at this time I'm afraid - send patches - or even better tell them to
stop doing that nonsense.

-- 
Matthias Andree

Re: [fetchmail-users] Questions FETCHMAIL-DAEMON & qvirtual

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

On 9/6/06, Neil Wilson <ne...@dc...> wrote:
> Hi guys,
>
> I have two questions regarding fetchmail.
>
> The first one is...
>
> One of our ISP's SMTP servers is discarding all mail that comes from FETCHMAIL-DAEMON@domain so miss-addressed bounced messages aren't getting back to the
> original senders.
>
> Is there a way to change the address that fetchmail bounces mail from(the sender address of the bounced message) instead of FETCHMAIL-DAEMON?

Only by changing the source AFAIK.  To be honest I'd approach the ISP
and ask them what they're playing at.

-- 
                 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] Questions FETCHMAIL-DAEMON & qvirtual

[Neil W. <ne...@dc...>]

Hi guys,

I have two questions regarding fetchmail.

The first one is...

One of our ISP's SMTP servers is discarding all mail that comes from FETCHMAIL-DAEMON@domain so miss-addressed bounced messages aren't getting back to the 
original senders.

Is there a way to change the address that fetchmail bounces mail from(the sender address of the bounced message) instead of FETCHMAIL-DAEMON?

My next questions is...

I have a client who collects email from a multi-drop mailbox with a local domain of domain1.co.za
EG: user bla with password "blabla" is * here

At the moment I'm using "envelope To:" as the envelope, but I'd like to use "Delivered-To:" because the mail is originating from a qmail server and mail from 
mailing lists etc.(Bcc'd) mail is bouncing.

The qmail server adds on a dom...@do... so I'd like to use qvirtual "domain1.co.za-" part, but the problem is that the mailbox has multiple 
domains attached to it.

eg: localdomains: domain1.co.za domain2.co.za domain3.co.za

So I somehow need to be able to add qvirtual for each domain that the multi drop mailbox supports.

Any ideas, or examples of how this can be done?
Can this be done?

Any help will be greatly appreciated.

Regards

Neil Wilson

Powered by Linux, driven by passion!

-- 
This email and all contents are subject to the following disclaimer:
http://www.dcdata.co.za/emaildisclaimer.html

Re: [fetchmail-users] no mail

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

On 9/3/06, Helge <hel...@mo...> wrote:
> cat /var/log/exim4/mainlog | grep 1GJy2M-0002hg-Sh
> 2006-09-03 21:53:46 1GJy2M-0002hg-Sh <= hel...@mo...
> H=localhost (helge.monet.no) [127.0.0.1] P=esmtp S=2388
> id=44F...@mo...
> 2006-09-03 21:53:47 1GJy2M-0002hg-Sh => hel...@mo...
> <helge@localhost> R=dnslookup_relay_to_domains T=remote_smtp
> H=mail.monet.no [62.128.239.20]
> 2006-09-03 21:53:47 1GJy2M-0002hg-Sh Completed
>
> I am sorry but I don't se any clues here; any tips?

You really need to ask on the Exim list - here I only offer help on
fetchmail.  However at a rough guess exim is seeing that the mail is
for @monet.no, doing the DNS lookup and forwarding the mail.  You need
to stop Exim from doing that.

It may be simply that you need to define "localhost" as being a local
mail domain, that may be enough to stop Exim from doing whatever it's
doing (at a guess, trawling the headers for a valid address).

> By the way: I dont see how it is possible to send a reply, and not only
> a new thread  all the time?

That's down to your mail client (Thunderbird), simply hit "Reply To
All" then remove the non-list address(es).

-- 
                 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 mail

[Helge <hel...@mo...>]

Rob MacGregor wrote:
> Given the lack of errors from fetchmail I'd say it's most likely that
> exim is incorrectly handling the email.  Without any logs from exim
> though it's hard to be 100% certain.
>
>   
Here is what I get if I run:
cat /var/log/exim4/mainlog | grep 1GJy2M-0002hg-Sh
2006-09-03 21:53:46 1GJy2M-0002hg-Sh <= hel...@mo... 
H=localhost (helge.monet.no) [127.0.0.1] P=esmtp S=2388 
id=44F...@mo...
2006-09-03 21:53:47 1GJy2M-0002hg-Sh => hel...@mo... 
<helge@localhost> R=dnslookup_relay_to_domains T=remote_smtp 
H=mail.monet.no [62.128.239.20]
2006-09-03 21:53:47 1GJy2M-0002hg-Sh Completed

I am sorry but I don't se any clues here; any tips?

By the way: I dont see how it is possible to send a reply, and not only 
a new thread  all the time?

-- 
Helge Opsjøn

[fetchmail-users] [Fwd: Re: No mail]

[Helge <hel...@mo...>]

-- 
Helge Opsjøn

Re: [fetchmail-users] No mail

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

On 9/2/06, Helge <hel...@mo...> wrote:
> I am using fetchmail 6.3.4-5 together with exim4 4.63-3, on a Debian
> system. I have problems with getting e-mail from my ISP's server.
> fetchmail --nosyslog -v gives:
> fetchmail: 6.3.4 querying mail.monet.no (protocol POP3) at søn
> 03-09-2006 00:14:13 CEST: poll started
> fetchmail: POP3< +OK Hello there.
> fetchmail: POP3> CAPA
<---SNIP--->
> fetchmail: normal termination, status 0

Poll looks good, fetchmail collects email and delivers it to your
local SMTP server.

> Every time I run fetchmail, the e-mails are returned back again to the
> server, and doubles.
>
> Can anybody see any clues her to solve my problem? Is this a fetchmail
> or a exim4-problem?

Given the lack of errors from fetchmail I'd say it's most likely that
exim is incorrectly handling the email.  Without any logs from exim
though it's hard to be 100% certain.

-- 
                 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 mail

[Helge <hel...@mo...>]

I am using fetchmail 6.3.4-5 together with exim4 4.63-3, on a Debian 
system. I have problems with getting e-mail from my ISP's server.
fetchmail --nosyslog -v gives:
fetchmail: 6.3.4 querying mail.monet.no (protocol POP3) at søn 
03-09-2006 00:14:13 CEST: poll started
fetchmail: POP3< +OK Hello there.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Here's what I can do:
fetchmail: POP3< STLS
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< LOGIN-DELAY 10
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION Courier Mail Server
fetchmail: POP3< .
fetchmail: POP3> STLS
fetchmail: POP3< +OK Begin SSL/TLS negotiation now.
fetchmail: Repoll immediately on hop...@ma...
fetchmail: POP3< +OK Hello there.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Here's what I can do:
fetchmail: POP3< STLS
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< LOGIN-DELAY 10
fetchmail: POP3< PIPELINING
fetchmail: POP3< UIDL
fetchmail: POP3< IMPLEMENTATION Courier Mail Server
fetchmail: POP3< .
fetchmail: POP3> USER myself
fetchmail: POP3< +OK Password required.
fetchmail: POP3> PASS *
fetchmail: POP3< +OK logged in.
fetchmail: POP3> STAT
fetchmail: POP3< +OK 1 689
1 message for hopsjo01 at mail.monet.no (689 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 689
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK 689 octets follow.
reading message my...@ma...:1 of 1 (689 octets)
fetchmail: SMTP< 220 helge.monet.no ESMTP Exim 4.63 Sun, 03 Sep 2006 
00:14:14 +0200
fetchmail: SMTP> EHLO helge.monet.no
fetchmail: SMTP< 250-helge.monet.no Hello localhost [127.0.0.1]
fetchmail: SMTP< 250-SIZE 52428800
fetchmail: SMTP< 250-PIPELINING
fetchmail: SMTP< 250 HELP
fetchmail: SMTP> MAIL FROM:<hel...@mo...> SIZE=689
fetchmail: SMTP< 250 OK
fetchmail: SMTP> RCPT TO:<helge@localhost>
fetchmail: SMTP< 250 Accepted
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself
#*****fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 OK id=1GJdkk-0001vb-9p
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Bye-bye.
fetchmail: SMTP> QUIT
fetchmail: SMTP< 221 helge.monet.no closing connection
fetchmail: 6.3.4 querying mail.monet.no (protocol POP3) at søn 
03-09-2006 00:14:14 CEST: poll completed
fetchmail: normal termination, status 0

# Configuration created Sat Sep  2 23:35:40 2006 by fetchmailconf 1.52 
$Revision: 4740 $
set postmaster "helge@localhost"
set bouncemail
set no spambounce
set properties ""
poll mail.monet.no with proto pop3
       user 'myself' there with password '*****' is 'helge' here options 
keep fetchall

Every time I run fetchmail, the e-mails are returned back again to the 
server, and doubles.

Can anybody see any clues her to solve my problem? Is this a fetchmail 
or a exim4-problem?


-- 
Helge Opsjøn

Re: [fetchmail-users] confused about system wide and private setups

[Michelle K. <lin...@fr...>]

Hello Matthias,

Am 2006-08-20 12:34:42, schrieb Matthias Andree:

> That doesn't mean they've included fixes for the other bugs I've worked
> on for 6.3.X, or that we should be supporting it, though I don't recall
> interval bug fixes offhand either.

...but backporting of the Sid version 6.3.4-4 to Sarge is easy.

AFAIK is it allready on <bpo>

Greetings
    Michelle Konzack
    Systemadministrator
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/6/61925193    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: [fetchmail-users] confused about system wide and private setups

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

"Rob MacGregor" <rob...@gm...> writes:

> Also, I only run Fetchmail on FreeBSD these days (though I can test on
> an old Mandrake 9.1 box), which makes helping people with startup
> issues on other platforms all but impossible.

I've seen various run scripts (old and new FreeBSD, Debian, SUSE Linux
10.0) and they are mutually vastly different.

SUSE are quite retro, they are *still* running fetchmail as root, but
they also use --fetchall as a default and thus circumvent quite a few
troubles with b0rked servers.

Debian run fetchmail 6.3.X (in testing) in its own "fetchmail" account
by default, FreeBSD can either do that, or it has recently gained a
means to spawn one fetchmail process per user.

-- 
Matthias Andree

Re: [fetchmail-users] confused about system wide and private setups

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

On 8/20/06, Matthias Andree <mat...@gm...> wrote:
> That doesn't mean they've included fixes for the other bugs I've worked
> on for 6.3.X, or that we should be supporting it, though I don't recall
> interval bug fixes offhand either.
>
> OTOH, Rob MacGregor does the voluntary (and usually excellent) support
> work on the lists, if he has no desire to keep an eye on 6.2.5
> compatibility, that's more than just fine with me.

Thanks :)  Given how useful I find fetchmail it's good to be able to
do something in support.

I no longer have 6.2.x (or older!) to hand which makes it hard to
provide any real support or assistance.  Fortunately very little has
changed WRT configuration so it's possible to help out with config
issues.  Problems relating to running it however...

Also, I only run Fetchmail on FreeBSD these days (though I can test on
an old Mandrake 9.1 box), which makes helping people with startup
issues on other platforms all but impossible.

-- 
                 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] confused about system wide and private setups

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

Rob Funk <rf...@fu...> writes:

> Rob MacGregor wrote:
>> On 8/19/06, Bob Meier <or...@gm...> wrote:
>> > Hi:
>> >
>> >  I'm using Debian Sarge with fetchmail version 6.2.5-12sarge4.
>>
>> You should be on 6.3.4
>
> Not necessarily.  Debian sarge (stable) has patched 6.2.5 to fix the 
> security problems there.

That doesn't mean they've included fixes for the other bugs I've worked
on for 6.3.X, or that we should be supporting it, though I don't recall
interval bug fixes offhand either.

OTOH, Rob MacGregor does the voluntary (and usually excellent) support
work on the lists, if he has no desire to keep an eye on 6.2.5
compatibility, that's more than just fine with me.

Note however that Debian has its own system of starting fetchmail (of
which I know little WRT the 6.2.X days).

-- 
Matthias Andree

Re: [fetchmail-users] confused about system wide and private setups

[Rob F. <rf...@fu...>]

Rob MacGregor wrote:
> On 8/19/06, Bob Meier <or...@gm...> wrote:
> > Hi:
> >
> >  I'm using Debian Sarge with fetchmail version 6.2.5-12sarge4.
>
> You should be on 6.3.4

Not necessarily.  Debian sarge (stable) has patched 6.2.5 to fix the 
security problems there.

-- 
==============================|   "A microscope locked in on one point
 Rob Funk <rf...@fu...> |Never sees what kind of room that it's in"
 http://www.funknet.net/rfunk |    -- Chris Mars, "Stuck in Rewind"

Re: [fetchmail-users] confused about system wide and private setups

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

On 8/19/06, Bob Meier <or...@gm...> wrote:
> Hi:
>
>  I'm using Debian Sarge with fetchmail version 6.2.5-12sarge4.

You should be on 6.3.4

>  How may setup fetchmail to download mail at different intervals for some
> users?

Provide different interval options:

poll pop.isp1.net user first password firspw interval 1
poll pop.isp2.com user second password secondpw interval 2

That would poll pop.isp1.net every run and pop.isp2.com every second.

>  I didn't understand if I can mix system wide fetchmailrc with private or
> personal .fetchmailrcs for _some_ users.

Yes, you can though you don't have to.

>  If I create .fetchmailrcs, which process runs it? Do I have to create cron
> jobs for this users?

You would need to either run a daemon as those users or use cron to
schedule the runs.

-- 
                 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