That's a valid concern but you can always be checking
the log every now and then. Plus even without this, it
shouldn't stay broken forever as the user involved
will probably start inquiring about where his/her
email is going and why none is arriving.
The disadvantage of the current all-or-nothing
approach shows up in case when several contributors
create the resulting fetchmailrc file together (let's
say individual users sign up for the fetching
service). Then if one of them makes a mistake, not
just his or her mail gets undelivered, but everybody
else is suddenly cut off as well.
Instead of providing some sort of self-service
environment, under the current design you force some
central authority to monitor and verify all requests
for modifications from individual users.
F
--- "Eric S. Raymond" <esr(_at_)thyrsus(_dot_)com> wrote:
Frantisek Brabec <frb_97(_at_)yahoo(_dot_)com>:
Let's assume my .fetchmailrc file contains several
different servers to be polled. If any one of them
doesn't resolve (e.g., a typo in the name), it
causes
fetchmail to exit and none of the servers gets
polled.
Is it really necessary? Could we just skip the
troubled server and process all the others after
all?
Bad idea. The entry could stay invisibly broken
forever.
--
<a href="http://www.tuxedo.org/~esr/";>Eric S.
Raymond</a>
"As to the species of exercise, I advise the gun.
While this gives
[only] moderate exercise to the body, it gives
boldness, enterprise,
and independence to the mind. Games played with the
ball and others
of that nature, are too violent for the body and
stamp no character on
the mind. Let your gun, therefore, be the constant
companion to your
walks."
-- Thomas Jefferson, writing to his teenaged
nephew.
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/