Am 2005-03-05 11:51:59, schrieb Andreas Pakulat:

> man fetchmailrc, expunge gilt auch f�r POP3 ;-) 

Schon mal den overhead gesehen ?

Mach bei ner 30.000 Message POP3 Box ein "expunge 5" und
Du kannst Dir nen Schu� geben, denn nach jedem "expunge"
macht er ein quit und Du mu�t die Mailbox neu �ffnen...

Guck mal in die RFC's...

Niemand wird Dir "expunge" bei POP3 empfehlen, weil es
einfach nicht f�r POP3 gemacht wurde.

Aus der:

  __( manpage 'fetchmailrc' )___________________________________________
 /
| fetchmail(1)                                         fetchmail(1)

<snip>

|        -e <count> | --expunge <count>
|               (keyword: expunge) Arrange for deletions to be made
|               final after a given number of messages.  Under POP2
|               or POP3,  fetchmail  cannot  make  deletions  final
                   ^^^^              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               without sending QUIT and ending the session -- with
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               this option on, fetchmail will break  a  long  mail
                                          ^^^^^^^^^^^^^^^^^^^^^^^^^
|               retrieval  session into multiple subsessions, send�
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               ing QUIT after each sub-session.  This  is  a  good
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               defense  against line drops on POP3 servers that do
|               not do the equivalent of a QUIT on  hangup.   Under
|               IMAP,  fetchmail normally issues an EXPUNGE command
|               after each deletion in order to force the  deletion
|               to  be  done immediately.  This is safest when your
|               connection to the server is flaky and expensive, as
|               it  avoids  resending  duplicate  mail after a line
|               hit.  However, on large mailboxes the  overhead  of
|               re-indexing after every message can slam the server
|               pretty hard, so if your connection is  reliable  it
|               is  good to do expunges less frequently.  Also note
|               that some servers enforce a delay of a few  seconds
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               after  each  quit,  so fetchmail may not be able to
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               get back in immediately after an expunge -- you may
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|               see  "lock  busy"  errors  if  this happens. If you
|               specify this option  to  an  integer  N,  it  tells
|               fetchmail  to  only  issue  expunges  on  every Nth
|               delete.  An argument of  zero  suppresses  expunges
|               entirely  (so no expunges at all will be done until
|               the end of run).  This option does  not  work  with
|               ETRN or ODMR.

<snip>

|                                                      fetchmail(1)
 \______________________________________________________________________


Also bei POP2/POP3 alles andere als zu empfehlen...

> Andreas

Greetings
Michelle

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

Attachment: signature.pgp
Description: Digital signature

Antwort per Email an