[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: fetchmail troubles



> On Fri, Jul 21, 2000 at 09:02:35AM -0500, Christopher Tessone wrote:
> 
> > Could you perhaps provide a little more information about your
> > fetchmail setup and sendmail configuration?  As for me, I've never had
> 
> A trace of the session (ie, the output of fetchmail -v) would probably
> also be useful.  I'm a bit concerned that you say that the SMTP server
> keeps your mailbox locked when things fail - it shouldn't be touching
> the mailbox until it's got the mail sucessfuly.

As a normal user I type:
	fetchmail -v 2>&1 | tee /tmp/fm.log
to get:

fetchmail: 5.3.3 querying mail.prestonet.com.br (protocol auto) at Fri, 21 Jul 
2000 14:30:10 -0300 (BRT)
fetchmail: 5.3.3 querying mail.prestonet.com.br (protocol IMAP) at Fri, 21 Jul 
2000 14:30:10 -0300 (BRT)
fetchmail: IMAP connection to mail.prestonet.com.br failed: Connection refused
fetchmail: 5.3.3 querying mail.prestonet.com.br (protocol POP3) at Fri, 21 Jul 
2000 14:30:11 -0300 (BRT)
fetchmail: POP3< +OK  <0332.397889D5@mail.prestonet.com.br>
fetchmail: POP3> USER ciccio
fetchmail: POP3< +OK ciccio gets mail here
fetchmail: POP3> PASS *
fetchmail: POP3< +OK you may proceed
fetchmail: POP3> STAT
fetchmail: POP3< +OK 1 3363
fetchmail: POP3> LAST
fetchmail: POP3< -ERR invalid command
fetchmail: invalid command
fetchmail: POP3> UIDL
fetchmail: POP3< +OK Iteration follows
fetchmail: POP3< 1 <20000721192155.A11720@cistron.nl>1a33d
fetchmail: POP3< .
1 message for ciccio at mail.prestonet.com.br (3363 octets).
fetchmail: POP3> LIST
fetchmail: POP3< +OK Iteration follows
fetchmail: POP3< 1 3363
fetchmail: POP3< .
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK 3363 octets
reading message 1 of 1 (3363 octets)
fetchmail: SMTP< 220 baco.haus ESMTP Sendmail 8.9.3/8.9.3/Debian 8.9.3-21; 
Fri, 21 Jul 2000 14:30:22 -0300
fetchmail: SMTP> EHLO localhost
fetchmail: SMTP< 250-baco.haus Hello localhost [127.0.0.1], pleased to meet you
fetchmail: SMTP< 250-EXPN
fetchmail: SMTP< 250-VERB
fetchmail: SMTP< 250-8BITMIME
fetchmail: SMTP< 250-SIZE
fetchmail: SMTP< 250-DSN
fetchmail: SMTP< 250-ONEX
fetchmail: SMTP< 250-ETRN
fetchmail: SMTP< 250-XUSR
fetchmail: SMTP< 250 HELP
fetchmail: SMTP> MAIL FROM:<debian-devel-request@lists.debian.org> SIZE=3363
fetchmail: SMTP< 250 <debian-devel-request@lists.debian.org>... Sender ok
fetchmail: SMTP> RCPT TO:<ciccio@localhost>
fetchmail: SMTP< 250 <ciccio@localhost>... Recipient ok
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 Enter mail, end with "." on a line by itself

Here it stays eternally. Listing the incoming file in
/var/spool/mqueue already showed 32k for the data file. The actual
message is at the beginning, the rest are spaces (or non-printing
characters shown as spaces by less(1)).

The blocking of the SMTP server isn't really strange; I can't leave
this hanging around for ever, so sooner or later I kill fetchmail. As
the access to the mailbox at the ISP's SMTP port is never closed, it
has to wait for a timeout, because it's also possible that someone tries to
get her mail with a modem using brasilian telephone lines. As that is
a windows machine, multiple accesses to the same mailbox are not
allowed (are they on linux?).

I can't tell if the lines
	fetchmail: POP3> LAST
	fetchmail: POP3< -ERR invalid command
	fetchmail: invalid command
where happening before, as usually I included the option -a, and now I
did not. Then it wouldn't show. Can't try again until within at least
half an hour.

Christoph Simon
ciccio@prestonet.com.br




Reply to: