fetchmail-users — User questions and discussion

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Jakob H. <jh...@pl...>]

Thomas Wolff wrote:
>> > or like this:
>> >   mda "formail -s procmail -p"
>> formail is unnecessary here, I think, as fetchmail calls the mda for
>> every single message seperately.
> But fetchmail doesn't generate a "From " line which is needed as a
> message separator in the mailbox. That's why formail is necessary.

Shouldn't that be done by procmail itself? Programs running an MDA
shouldn't care about the local mailbox format. I may be wrong about this,
it's long ago that I used procmail and mbox.

> Whatever the issue, error handling should be reviewed and revised to
> never produce this kind of DoS situation, independent of actual error
> analysis.

If it's a server issue, there's not much fetchmail can do about it. If
it's a fetchmail flaw, you are right of course.

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Thomas W. <to...@to...>]

> > or like this:
> >   mda "formail -s procmail -p"

> formail is unnecessary here, I think, as fetchmail calls the mda for every
> single message seperately.
But fetchmail doesn't generate a "From " line which is needed as a 
message separator in the mailbox. That's why formail is necessary.
Please check; maybe the "/usr/bin/procmail" example under --mda in 
the manual page is misleading here and should be changed as well.
Without formail, I couldn't produce a mailbox that is readable with "mail".

> > access to my other mails, I did not care to retrieve any of those
> > (using the webmail interface) which I should have sent here for bug
> > analysis, sorry.

> The output of fetchmail -v -v would have been a start. This could have
> also been an issue of the pop/imap server.
As I noted before (in a mail that unfortunately didn't make it on the 
list yet as I used the wrong sender address :( ) :
Whatever the issue, error handling should be reviewed and revised to 
never produce this kind of DoS situation, independent of actual error 
analysis.

Best regards,
Thomas

[fetchmail-users] Re: fetchmail gets stuck because of malformed spam

[Sunil S. <sh...@bo...>]

Quoting from Karel Kulhavy's mail on Wed, Oct 26, 2005 at 10:59:30AM +0200:
> I got some malformed spam which causes fetchmail to stop on this spam
> and I am unable to download 162 waiting messages behind this spam.
> 
> This seems to be some kind of fetchmail DoS vulnerability - if someone
> sends this mail to all fetchmail users in the world, they will be pretty
> pissed off to have to log in to remote machine and erase the e-mail by
> hand. And if he sends every hour, they will have to change to a
> different program than fetchmail ;-)

Could you send the output of "fetchmail -v" when the mail gets stuck?

My guess is that the mail gets stuck because fetchmail is unable to
send a bounce message.

-- 
Sunil Shetye.

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Jakob H. <jh...@pl...>]

Tho...@si... wrote:

> In this case, it might rather look like this:
>   mda "formail >> ${MAIL-$HOME/Post/Inbox}"

This is a little dangerous, as there is no locking involved

> or like this:
>   mda "formail -s procmail -p"

formail is unnecessary here, I think, as fetchmail calls the mda for every
single message seperately.

> access to my other mails, I did not care to retrieve any of those
> (using the webmail interface) which I should have sent here for bug
> analysis, sorry.

The output of fetchmail -v -v would have been a start. This could have
also been an issue of the pop/imap server.

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Jakob H. <jh...@pl...>]

Karel Kulhavy wrote:

once again:
>> Please keep list traffic on the list.


> But I have mda option.

No, you don't, as your output of fetchmail -V says:

Messages will be SMTP-forwarded to: localhost (default)

That means that your MTA is used, which is fetchmail's default.
A MDA would procmail, maildrop etc., or Exim itself, but not via smtp.

With "mda" it would say something like

Messages will be delivered with "/usr/sbin/sendmail -i %T"

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Karel K. <cl...@tw...>]

On Thu, Oct 27, 2005 at 12:07:35PM +0200, Tho...@si... wrote:
> Jakob Hirsch wrote:

[...]

> So I don't know either if the malformed parts raised the same problem 
> as it occurred now. But in any case, I think fetchmail error handling 
> should be carefully reviewed for any possible case of aborting the 
> retrieval in order to avoid this DoS situation in the future.

Hehe one could send a malformed e-mail to this mailing list so all
people would get pissed - or write a bot which would send every hour
- that would make the bug to be solved promptly ;-)

CL<
> 
> Kind regards,
> Thomas Wolff

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[<Tho...@si...>]

I wrote:

> But I've actually had similar problems a while ago; fetchmail couldn't 
> get past certain spam mails. I had to use a webmail interface to 
> delete them to get any further. Unfortunately, as I needed quick 
> access to my other mails, I did not care to retrieve any of those 
> (using the webmail interface) which I should have sent here for bug 
> analysis, sorry.
As an additional information I just remembered that I had to use 
the webmail interface because Mozilla Thunderbird was not able to 
retrieve those mails, either, and got stuck the same way, 
when this problem occurred here a few months ago.

Kind regards,
Thomas Wolff

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[<Tho...@si...>]

Jakob Hirsch wrote:

> I personally would always recommend using fetchmail with the mda option
> (for the usual pop/imap retrieval), so you won't have all these smtp
> problems.
> ...
> > What is mda option?
> It means that your mail is not delivered over smtp but to the local
> delivery agent, which (usually) simply drops it in your inbox.
> 
> I use:
> 
> defaults
>   mda "/usr/sbin/sendmail -i %T"
> ...

I have a personal setup that does not (cannot) rely on a working local 
mail environment (the machine is not normally intended for handling mails).
In this case, it might rather look like this:
  mda "formail >> ${MAIL-$HOME/Post/Inbox}"
or like this:
  mda "formail -s procmail -p"

So for me, there is no smtp involved in mail retrieval.
But I've actually had similar problems a while ago; fetchmail couldn't 
get past certain spam mails. I had to use a webmail interface to 
delete them to get any further. Unfortunately, as I needed quick 
access to my other mails, I did not care to retrieve any of those 
(using the webmail interface) which I should have sent here for bug 
analysis, sorry.

So I don't know either if the malformed parts raised the same problem 
as it occurred now. But in any case, I think fetchmail error handling 
should be carefully reviewed for any possible case of aborting the 
retrieval in order to avoid this DoS situation in the future.

Kind regards,
Thomas Wolff

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Jakob H. <jh...@pl...>]

Karel Kulhavy wrote:


Please keep list traffic on the list.

>> I personally would always recommend using fetchmail with the mda option
> What is mda option?


It means that your mail is not delivered over smtp but to the local
delivery agent, which (usually) simply drops it in your inbox.

I use:

defaults
  mda "/usr/sbin/sendmail -i %T"
  is "jh" here

poll imap.web.de proto imap user x pass y fetchall ssl


For more information: man fetchmail

> What is multidrop?

The opposite of single-drop, which you are using.
For more information: man fetchmail

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

[Jakob H. <jh...@pl...>]

Karel Kulhavy wrote:

> reading message cl...@tw...:1 of 162 (765 header octets)
> fetchmail: SMTP error: 501 <agrode@%%DOMAIN%>: domain missing or malformed
> gethostbyname failed for kestrel

Fetchmail should go on retrieving the next message after a 501 from the
smtp server, but it seems to consider the failed gethostbyname() a fatal
error.
Looks more like a misconfiguration on your side. "kestrel" is your
hostname, right?

I personally would always recommend using fetchmail with the mda option
(for the usual pop/imap retrieval), so you won't have all these smtp
problems.
At least as long as you are not using multidrop, but that is not
recommended anyway.

Re: [fetchmail-users] fetchmail gets stuck because of malformed spam

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

On 26/10/05, Karel Kulhavy <cl...@tw...> wrote:
> I got some malformed spam which causes fetchmail to stop on this spam
> and I am unable to download 162 waiting messages behind this spam.
>
> This seems to be some kind of fetchmail DoS vulnerability - if someone
> sends this mail to all fetchmail users in the world, they will be pretty
> pissed off to have to log in to remote machine and erase the e-mail by
> hand. And if he sends every hour, they will have to change to a
> different program than fetchmail ;-)

I've seen a similar problem before, but usually fetchmail will skip
the offending mail and carry on.  One option may be to set 501 as one
of the anti-spam codes.

> don't know how to get IMAP server greeting line

telnet IMAPHOST 143

More useful than the config dump would be the contents of .fetchmailrc
and output of "fetchmail -v -v" for the problem email (along with the
matching log entries from your MTA).

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

[Karel K. <cl...@tw...>]

Here is the poison:

>From agrode@%%DOMAIN%  Tue Oct 25 17:34:28 2005
Return-Path: <agrode@%%DOMAIN%>
Received: from EXTREME-07 (200-102-91-6.smace701.dsl.brasiltelecom.net.br [200.102.91.6] (may be forged))
	by twin.jikos.cz (8.11.6p2/8.11.6) with SMTP id j9PFYRb05150
	for <cl...@tw...>; Tue, 25 Oct 2005 17:34:27 +0200
Message-ID: <001401c5d979$885ff56c$0501010a@EXTREME-07>
From: "Floris" <agrode@%%DOMAIN%>
To: cl...@tw...
Subject: You know how it? to work with stable software!          ==Ref:515==
Date: Tue, 25 Oct 2005  13:34:05 -0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0011_01C5D968.C4D24D30"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-IMAPbase: 1130271542 170
X-Keywords:                     
X-UID: 9
Status: RO
Content-Length: 2489
Lines: 61

This is a multi-part message in MIME format.

------=_NextPart_000_0011_01C5D968.C4D24D30
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   0ffice XP - $6o

   other world famous software from name-branded corporations at same
   prices! INTERESTING ?

   then visit the BEST ever OEM store on internet!
   ---
   Why so cheap?

   All the software is OEM- Meaning that you don't get the box and the
   manual with your software. All you will receive is the actual
   software and your unique registration code.

   All the software is in the English language for PC. Our offers
   are unbeatable and we always update our prices to make sure we
   provide you with the best possible offers. Hurry up and place
   your order, because our supplies are limited.

   To unsubscribe click here!

------=_NextPart_000_0011_01C5D968.C4D24D30
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD><BODY bgcolor="#FFFFFF">
<p align="center"><font size="+4"><b><a href="http://VLfI9nf4fgwmx1em2rr5w9rne99r.answerik.com/?mpaMv">0ffice 
  XP - $6o</a></b></font></p>
<p align="center"><b><font color="#FF0000">other world famous software from name-branded 
  corporations at same prices! INTERESTING ?</font></b></p>
<p align="center"><a href="http://fcF9nf4fgwmx1em2rr5w9rne99r.answerik.com/?IMk">then visit the BEST ever OEM store 
  on internet!</a><br>
  ---<br>
  <font size="-2">Why so cheap?</font></p>
<p align="center"><font size="-2">All the software is OEM- Meaning that you don't 
  get the box and the<br>
  manual with your software. All you will receive is the actual<br>
  software and your unique registration code.</font></p>
<p align="center"><font size="-2">All the software is in the English language 
  for PC. Our offers<br>
  are unbeatable and we always update our prices to make sure we<br>
  provide you with the best possible offers. Hurry up and place<br>
  your order, because our supplies are limited.</font></p>
<p align="center">  </p>
<DIV align="center"><FONT face=Arial size=2>To unsubscribe <A href="http://SfHH9nf4fgwmx1em2rr5w9rne99r.answerik.com/dGk?nXd">click here!</FONT></DIV>
</BODY></HTML>


------=_NextPart_000_0011_01C5D968.C4D24D30--

[fetchmail-users] fetchmail gets stuck because of malformed spam

[Karel K. <cl...@tw...>]

I got some malformed spam which causes fetchmail to stop on this spam
and I am unable to download 162 waiting messages behind this spam.

This seems to be some kind of fetchmail DoS vulnerability - if someone
sends this mail to all fetchmail users in the world, they will be pretty
pissed off to have to log in to remote machine and erase the e-mail by
hand. And if he sends every hour, they will have to change to a
different program than fetchmail ;-)

clock@kestrel:~$ fetchmail
162 messages for clock at twin.jikos.cz.
reading message cl...@tw...:1 of 162 (765 header octets) fetchmail: SMTP error: 501 <agrode@%%DOMAIN%>: domain missing or malformed
gethostbyname failed for kestrel

Operating system gentoo linux
GCC 3.3.6
don't know how to get IMAP server greeting line
MDA: ESMTP Exim 4.50
 
This is fetchmail release 6.2.5.2+RPA+NTLM+SDPS+SSL+INET6+NLS
Fallback MDA: (none)
Linux kestrel 2.6.12-gentoo-r10 #2 Tue Oct 4 10:27:59 CEST 2005 i686 Intel(R) Pentium(R) M processor 1.50GHz GenuineIntel GNU/Linux
Taking options from command line and /home/clock/.fetchmailrc
Idfile is /home/clock/.fetchids
Fetchmail will forward misaddressed multidrop messages to clock.
Options for retrieving from cl...@tw...:
  True name of server is twin.jikos.cz.
  Protocol is IMAP.
  All available authentication methods will be tried.
  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 not be kept on the server (--keep off).
  Old messages will not be flushed before message retrieval (--flush 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(s) recognized.
  No UIDs saved from this host.
Options for retrieving from cl...@at...:
  True name of server is atrey.karlin.mff.cuni.cz.
  Protocol is IMAP.
  All available authentication methods will be tried.
  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 not be kept on the server (--keep off).
  Old messages will not be flushed before message retrieval (--flush 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(s) recognized.
  No UIDs saved from this host.
Options for retrieving from di...@po...:
  True name of server is pop.centrum.cz.
  Protocol is POP3.
  All available authentication methods will be tried.
  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).
  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(s) recognized.
  No UIDs saved from this host.
Options for retrieving from yc...@po...:
  True name of server is pop.centrum.cz.
  Protocol is POP3.
  All available authentication methods will be tried.
  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).
  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(s) recognized.
  No UIDs saved from this host.

Re: [fetchmail-users] fetchmail 6.2.9-rc6 available (yet another candidate...)

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

On Fri, 21 Oct 2005, Thomas Wolff wrote:

> Hello,
> 
> > * fetchmailconf now changes the output file to mode 0600 BEFORE writing to it,
> >   so there is no window where passwords could be read by the world.
> >   Matthias Andree.
> This doesn't sound quite right. The only safe way is to CREATE the 
> file in 600 mode right away. If you just CHANGE to 600 even before writing 
> to it, there IS an unsafe window.
> Try the following:
> touch x
> tail -f x
> 
> Then in another shell:
> chmod -r x
> echo bla >> x
> 
> "bla" will show up in the first window, read by "tail".

Right you are, and thanks for reporting the problem.
(Thanks also to Miloslav Trmac, who also reported the problem.)

Actually, the new script also sets the umask to 077 before opening the
file, so we're doing the right thing, only the NEWS file is off track.

I have uploaded a new version of a security announcement, now at
http://fetchmail.berlios.de/fetchmail-SA-2005-02.txt and will ship it to
pertinent lists shortly.

I have also withdrawn fetchmailconf-1.43.1 and the corresponding patch
from distribution and uploaded fetchmailconf-1.43.2 for users of
fetchmail-6.2.5.2.

Please, further discussion only on fet...@li....

Warning: reply-to is set - take care should you desire to mail me
directly - some mailers require you to manually pick "To Sender Only" or
"Ignore Reply-To."

-- 
Matthias Andree

Re: [fetchmail-users] fetchmail 6.2.9-rc6 available (yet another candidate...)

[Thomas W. <to...@to...>]

Hello,

> * fetchmailconf now changes the output file to mode 0600 BEFORE writing to it,
>   so there is no window where passwords could be read by the world.
>   Matthias Andree.
This doesn't sound quite right. The only safe way is to CREATE the 
file in 600 mode right away. If you just CHANGE to 600 even before writing 
to it, there IS an unsafe window.
Try the following:
touch x
tail -f x

Then in another shell:
chmod -r x
echo bla >> x

"bla" will show up in the first window, read by "tail".

Kind regards,
Thomas Wolff

[fetchmail-users] fetchmail 6.2.9-rc6 available (yet another candidate...)

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

I have just released fetchmail 6.2.9-rc6, yet another release candidate
before 6.3.0, after further fixes to -rc5, became necessary.

- -----------------------------------------------------------------------
Fetchmail needs your support - please consider a donation via:
<https://developer.berlios.de/developer/make_donation.php?user_id=2007>
- -----------------------------------------------------------------------

Changes since -rc5 are:
* fetchmailconf now changes the output file to mode 0600 BEFORE writing to it,
  so there is no window where passwords could be read by the world.
  Matthias Andree.
* Missed --port/--service/--ssl cleanups in the manual. Reminder from Thomas
  Wolff. (MA)
* Complain in POP3 if NTLM/MSN auth is requested but had not been enabled at
  compile time. This configuration mismatch now causes an error message and
  authentication failure. Found by Yves Boisjoly.  Matthias Andree
* fetchmailconf now allows expert users to choose the authorization type and
  also offers MSN and NTLM, suggested by Yves Boisjoly. Matthias Andree
* fetchmailconf now (as of 1.49) writes its version to the comment of the
  saved run control file. Matthias Andree
* Properly shut down SSL connections. Berlios Patch #647 by Arkadiusz
  Miśkiewicz. (MA)
* Global variable cleanup, to fix daemon mode reinitialization problems. Patch
  by Sunil Shetye. (MA)

I seek everyone to test it out, report remaining bugs, update outdated
translations (send your translated .po files to the translation
project's robot, it'll forward your translation to the -devel list) or
send patches for documentation or report inconsistencies (including
formatting!) in the documentation.

The software is available from:
<https://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=7672>
<http://home.pages.de/~mandree/fetchmail/>


Regards,

- -- 
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDWOElvmGDOQUufZURAnEHAKCLG0lXreSui5fw1nqfYGRDihCsHgCfTh0Y
ZGUGQHcBElLVaHfsUNurPOw=
=PejO
-----END PGP SIGNATURE-----

[fetchmail-users] Socket error

[Barsalou <ba...@at...>]

I recently had a similar problem.  One thing to try is to turn off dns
in the fetchmail config.  Also, there might be an issue with ipv6 if you
used the rpms instead of compiling it yourself.

Give it a shot!

Mike B.
-- 
Barsalou <ba...@at...>

Re: [fetchmail-users] RE: Socket Error in Fetchmail!

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

On 13/10/05, deven barhate <red...@gm...> wrote:
> Dear Friends,
>
> I'm using fetchmail-6.2.0-3 and sendmail-8.12 on redhat linux 9.

Please upgrade fetchmail, there are known security problems with
versions before 6.2.5.2.

> fetchmail: socket error while fetching from mail.server.com
> fetchmail: 6.2.5 querying mail.server.com ( protocol POP3) at <date and
> time>: poll completed
> fetchmail Query status=2 (SOCKET)
> fetchmail: sleeping at < date and time>
>
> and fetchmail die.
>
> once again i try to fetch mails it again dies at the same mail. I have to
> delete that mail and then only I can fetch mails untill next socket error
> message comes.
>
> I have to monitor all the time for this error. and delete that perticular
> mail.
>
> Please help me regarding this matter. I searched lot but i only get is the
> posts asking for same problems but not solutions.

The problem relates to comms either with your remote POP server or
your local SMTP server.  You need to check your local mail log to tell
whether it's a problem with your local setup or the remote POP server.

Details on the problem email would be helpful!

--
                 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] RE: Socket Error in Fetchmail!

[deven b. <red...@gm...>]

Dear Friends,
 I'm using fetchmail-6.2.0-3 and sendmail-8.12 on redhat linux 9.
 I can fetch some mails thoroly without any problem but at some point i'm
geting fillowing message-
 fetchmail: socket error while fetching from
mail.server.com<http://mail.server.com/>
fetchmail: 6.2.5 querying mail.server.com <http://mail.server.com/> (
protocol POP3) at <date and time>: poll completed
fetchmail Query status=2 (SOCKET)
fetchmail: sleeping at < date and time>
 and fetchmail die.
 once again i try to fetch mails it again dies at the same mail. I have to
delete that mail and then only I can fetch mails untill next socket error
message comes.
 I have to monitor all the time for this error. and delete that perticular
mail.
 Please help me regarding this matter. I searched lot but i only get is the
posts asking for same problems but not solutions.
 Thanks and Regards,
Deven.

Re: [fetchmail-users] Fetchmail & Merak Mail Server

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

On 11/10/05, Rouven Sacha <rs...@bl...> wrote:
> I have to keep the messages on the server, due to the fact that other
> clients have to have access to these messages as well. And if i do
> understand things right, "fetchall" conflicts with "keep".

Certainly a Bad Idea :-)

> The Debian manpage of fetchmail calls the UIDL code "flaky". Since the
> manpage seems to be outdated (it is pointing to esr's homepage, for
> example): is UIDL still flaky in 6.2.5.2?

I've been running one mail server that polls half a dozen remote
mailboxes (about to jump to a couple of dozen) using UIDL for nearly 3
years now.  I've never had a problem with UIDL support.

Alternatively, put it this way - you have no choice.  You can either
enable UIDL support or try to find another solution that doesn't use
fetchmail :)

--
                 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 & Merak Mail Server

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

Please keep list mail on the list.....

Rouven Sacha wrote:
> Am Montag, den 10.10.2005, 14:43 -0400 schrieb Rob Funk:
> > I've never even heard of Merak Mail Server myself....
>
> http://www.icewarp.com/
>
> > Are you normally checking the mailbox with other clients also?
> > You could try the fetchall option, or the uidl option.  Read about
> > those in the man page.
>
> I have to keep the messages on the server, due to the fact that other
> clients have to have access to these messages as well. And if i do
> understand things right, "fetchall" conflicts with "keep".
>
> The Debian manpage of fetchmail calls the UIDL code "flaky". Since the
> manpage seems to be outdated (it is pointing to esr's homepage, for
> example): is UIDL still flaky in 6.2.5.2?
>
> > We can't see what's wrong from a successful log.  We can only see
> > what's going wrong from an unsuccessful log.
>
> I'm running fetchmail in Debian's debug-run mode right now. I'm going
> to post updates as soon as i get them.

Re: [fetchmail-users] Fetchmail & Merak Mail Server

[Rouven S. <rs...@bl...>]

Am Montag, den 10.10.2005, 14:43 -0400 schrieb Rob Funk:

> I've never even heard of Merak Mail Server myself....

http://www.icewarp.com/ 

> Are you normally checking the mailbox with other clients also?
> You could try the fetchall option, or the uidl option.  Read about 
> those in the man page.

I have to keep the messages on the server, due to the fact that other
clients have to have access to these messages as well. And if i do
understand things right, "fetchall" conflicts with "keep". 

The Debian manpage of fetchmail calls the UIDL code "flaky". Since the
manpage seems to be outdated (it is pointing to esr's homepage, for
example): is UIDL still flaky in 6.2.5.2? 

> We can't see what's wrong from a successful log.  We can only see 
> what's going wrong from an unsuccessful log.

I'm running fetchmail in Debian's debug-run mode right now. I'm going to
post updates as soon as i get them.

-- 
Rouven Sacha | Blinkenlichten GbR | 0174/4220127 | fax: 030/13896249

Re: [fetchmail-users] Fetchmail & Merak Mail Server

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

Rouven Sacha wrote:
> Are there any known issues that affect using fetchmail 6.2.5.2 to pop a
> Merak Mail Server (7.4.5)?

I've never even heard of Merak Mail Server myself....

> I am experiencing problems with fetchmail 
> not recognizing and fetching new messages on that mail server which
> other MUA have no problem at all to see and fetch.

Are you normally checking the mailbox with other clients also?
You could try the fetchall option, or the uidl option.  Read about those 
in the man page.

> I haven't logged a session that fails, yet, and i am hesitating to do
> so since fetchmail outputs quite a lot in verbose mode and the errors
> appear in unpredictable ways.

We can't see what's wrong from a successful log.  We can only see what's 
going wrong from an unsuccessful log.

-- 
==============================|   "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] Fetchmail & Merak Mail Server

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

On 10/10/05, Rouven Sacha <rs...@bl...> wrote:
> Hello List!
>
> Are there any known issues that affect using fetchmail 6.2.5.2 to pop a
> Merak Mail Server (7.4.5)? I am experiencing problems with fetchmail not
> recognizing and fetching new messages on that mail server which other
> MUA have no problem at all to see and fetch.

If you are sharing the mailbox with other mail clients then you MUST
use UIDL support.

--
                 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 & Merak Mail Server

[Rouven S. <rs...@bl...>]

Hello List!

Are there any known issues that affect using fetchmail 6.2.5.2 to pop a
Merak Mail Server (7.4.5)? I am experiencing problems with fetchmail not
recognizing and fetching new messages on that mail server which other
MUA have no problem at all to see and fetch.

fetchmail (debian sarge binary) runs in daemon mode on my site, using
the following config:

set postmaster "postmaster"
set bouncemail
set properties ""

poll mail.domain.tld uidl with proto POP3
user "us...@do..." there with password "password" is user here
options keep

Fetchmails "blindness" disappears when new messages hit that mailbox.

A successfull dialog looks as follows:

fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< APOP
fetchmail: POP3< EXPIRE NEVER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL CRAM-MD5 DIGEST-MD5 LOGIN PLAIN
fetchmail: POP3< .
fetchmail: POP3> AUTH CRAM-MD5
fetchmail: POP3< + PDIwMDUxMDEwMTk0NzM5QG1haWwucm91dGluZy5uZXQ+
fetchmail: POP3>
YW5kcmVhcy5lZ25lckBsb2N6b25lLmRlIDYxMDBmY2MyMjZiNmVmMDM5YjIxYzRiNDNkNDhmYjk1
fetchmail: POP3< +OK 1 messages 10918 octets

I haven't logged a session that fails, yet, and i am hesitating to do so
since fetchmail outputs quite a lot in verbose mode and the errors
appear in unpredictable ways.

Thanks in advance,

Rouven Sacha