~alpine/devel

1

[alpine-devel] Bug in fetchmail-6.3.8-r2

Details
Message ID
<49DCF22E.5070209@jamailca.com>
Sender timestamp
1239216686
DKIM signature
missing
Download raw message
Developers,

When using fetchmail-6.3.8-r2 (the newest available) on alpine-1.7.28.1 
081209, fetchmail does not properly handle the 'fetchall' keyword in a 
fetchmailrc file. It seems to leave "viewed" messages on the remote 
server. However, using the /-a/ command-line option (which, according to 
the man page, is equivalent to 'fetchall') fetchmail gets the "viewed" 
messages as expected. The following are excerpts of the fetchmail 
command output:

#  fetchmail -vv --nosyslog -f /etc/fetchmailrc
...
7 messages for USER@DOMAIN.NET at SERVER.DOMAIN.NET (301242 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 6696
fetchmail: POP3> RETR 1
fetchmail: timeout after 300 seconds waiting for server SERVER.DOMAIN.NET.
fetchmail: socket error while fetching from 
USER@DOMAIN.NET@SERVER.DOMAIN.NET
...
# fetchmail -vv --nosyslog -a -f /etc/fetchmailrc
7 messages for USER@DOMAIN.NET at SERVER.DOMAIN.NET (301242 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 6696
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK 6696 octets
reading message USER@DOMAIN.NET@SERVER.DOMAIN.NET:1 of 7 (6696 octets)
...
fetchmail: SMTP< 250 Ok: queued as 72B855008E
 flushed
fetchmail: POP3> DELE 1
fetchmail: POP3< +OK Marked to be deleted.
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 2606
fetchmail: POP3> RETR 2
fetchmail: POP3< +OK 2606 octets
...[etc. for the rest of the messages]


-aalatchm


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---

Re: [alpine-devel] Bug in fetchmail-6.3.8-r2

Details
Message ID
<49DF9ECD.8070100@jamailca.com>
In-Reply-To
<49DCF22E.5070209@jamailca.com> (view parent)
Sender timestamp
1239391949
DKIM signature
missing
Download raw message
Developers:


aalatchm wrote:
>
> When using fetchmail-6.3.8-r2 (the newest available) on 
> alpine-1.7.28.1 081209, fetchmail does not properly handle the 
> 'fetchall' keyword in a fetchmailrc file. It seems to leave "viewed" 
> messages on the remote server. However, using the /-a/ command-line 
> option (which, according to the man page, is equivalent to 'fetchall') 
> fetchmail gets the "viewed" messages as expected. The following are 
> excerpts of the fetchmail command output:
[snip]

Actually, It turns out that this was not a bug in fetchmail. 
Investigation of the errors and the link 
http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html#R6 
<http://www.catb.org/%7Eesr/fetchmail/fetchmail-FAQ.html#R6> showed that 
the problem was a path-MTU issue which caused the fetchmail to hang. 
Problem has now been solved.


-aalatchm


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Reply to thread Export thread (mbox)