On Fri, 2008-03-28 at 10:17 -0700, Les wrote:
> On Fri, 2008-03-28 at 09:35 -0700, Craig White wrote:
> > On Fri, 2008-03-28 at 08:29 -0700, Les wrote:
> > > >
> > > But is 99.99% delivery sufficient? I receive more than 150 emails per
> > > day (ones that I am interested in), and every few days I need to receive
> > > certain emails about customer relations and ongoing projects. 99.99
> > > percent means I would miss one every 66 days. If the one that I miss
> > > cost me a contract, it might not matter whether I received the rest or
> > > not. Currently I have to parse through the junk mail locally and
> > > remotely about once a week. the ISP junk folder often has more than
> > > 1200 emails in it. THe local one about 30. This adds about 1/2 day of
> > > overhead every week to recapture what should have come through.
> > > Personally I think the world needs to eliminate spam, or at least make
> > > every effort to seriously reduce it.
> > ----
> > but your example completely misses the point.
> > the 'Junk' directory is a result of some type of agent parsing accepted
> > e-mail, scoring it and redirecting it based on a score.
> > The point of greylisting is always about (or virtually always...depends
> > upon various implementations anyway) sender/recipient/smtp server
> > 'tuples' and 'Temporary Failure' /SMTP result codes 450 and whether the
> > sender attempts redelivery.
> > http://www.greylisting.org/
> > I would suggest that rather than prove the argument about the problems
> > with greylisting, you have proven the opposite because if you can lop
> > approximately 70% of that junk mail off the top via greylisting, you
> > wouldn't have to look through so much 'junk' to find the false positives
> > that inevitably occur with any type of spam scoring system.
> > Craig
> I cannot argue the value of greylisting. But efficiency is in the eye
> of the beholder. My time is limited. My work valuable, and my customer
> correspondence is dictated by my customer, not my email policy. I am at
> the mercy of the ISP here, and the customer. Yet I am the one who
> suffers loss, not the ISP, not the customer who will find someone to do
> his work. Yet you as the web person thinks this is effective. I cannot
> speak to school systems, only professional uses. Time is money and lost
> opportunity is even more valuable, resulting in loss that cannot be
> measured, yet ultimately may determine the success or failure of my
> I would like to take this thought "out of the box". The methods
> currently in place, grey listing, parsing for key words, and other
> simplistic means, while effective at reducing traffic are not really the
> desired solution by users, who would like 100% success in getting their
> desired email. And while I cannot spout statistics about loss, I know
> it happens from personal experience. The question at hand is how to
> avoid even more loss. It is a quality issue, and today the quality
> standard is not 99.99%, it is 99.9999% (six nines or six sigma) in most
> industries. To say that 99.99 is good enough is the path for GM and
> Ford, not Toyota and Nissan. Think of it that way. So how do we
> improve by two decades of quality in this "war" against spam?
greylisting is just one of a lot of tools available to the mail server
administrator - all of them are calibrated to minimize the junk mail
delivered to the end users and of course minimizing delivery failures
and false positive scoring by various mechanisms.
End users of course are the ones ultimately affected and you seemingly
want to open an end user discussion about a server level
technology...please don't as it won't provide clarity to anyone.
If you are losing e-mails, evaluate the filtering system that you use at
end user level and discuss the methodologies employed by your mail
provider with them.
Running GNOME in fully updated F8 on a dual-core x86_64. When I log in,
several apps or applets produce pop-up error boxes with the following
An error occurred while loading or saving configuration
information for <applet>. Some of your configuration settings
may not work properly.
Clicking the "details" button produces one to several occurrences of the
Adding client to server's list failed, CORBA error:
This started a while back, and it would occur on the first login after
boot, but subsequent logins would work fine. More recently, it's
started happening on every login. The applets that produce the error
vary, but they include
- Power Manager
- Evolution's calendar/alarm app
Anybody have a clue what's going on? Which component should I BZ?
Clemson University Math Sciences
mjs AT clemson DOT edu
i've been pruning my "downloads" disk,
rather drastically, and not making a dent.
today some more, less drastic but still
hefty, same result.
revisited du- checked it twice - three
times- yup, it reports one directory at
800+ gb- on a 400gb disk!
fsck (forced) failed to report any problems,
there don't seem to be any symlinks,
and the sub-direcory sizes are sane...
any ideas welcome, and appreciated.
: Do What Thou Wilt :
: Shall Be :
: The Whole of The Law :
I go to the official bluez-utils web site and their documentation page
basically says "You don't want to look at our docs, they suck.".
I go to the official bluetooth web site and their documentation either
tells me why I ought to be making bluetooth devices or talks about
radio spectrum and communications layers.
Where is the web page that explains to a human what the gibberish
in the hcid.conf man page actually means?
All I'm trying to do is arrange for my bluetooth keyboard (which definitely
works with manual poking and prodding) to work automatically once
my fedora 8 system has booted. Seems like it ought to be a simple task :-).
After a clean install of fc8, a full yum update, I then add freshrpms and install dvdrip. I then setup a project, rip the dvd, but the preview fails. I have searched their forum and found some issues but it seems non apply, there is no actual error other then that the file isn't created?
Anyone know what could be wrong?
Can any one, point me to a Howto that explains how to use the new
Firewire stack in F7/8,
I'm trying to get my Mini DV camera to work with via Firewire, actually
was hoping to use the Camara with ZoneMinder.
08:08.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
IEEE-1394a-2000 Controller (PHY/Link)
firewire_ohci 19137 0
firewire_core 36353 1 firewire_ohci
crc_itu_t 5953 1 firewire_core
However, no devices in /dev/fwX appear to be created ?
dvgrab does not see a device connected:
Error: no camera exists
I checked the fedora documentation, but could not find any docs on the
BTW: I'm using kernel 220.127.116.11-7.fc8PAE
There is a feature on X windows when used in Fedora-7 that allowed
you to zoom the desktop in and out using ctrl-alt-plus and ctrl-alt-minus.
This feature does not work with the Fedora-8 version of X windows. This
feture does not even work with the same xorg.conf file that was used with
This is show stopper for us. Our vision impaired users are screaming bloody
murder about not being able to use this feature with Fedora-8. We have
had to install Fedora-7 in place of Fedora-8 on those systems, and we will
have to do this Fedora-7 install on all of our servers in order to have
all systems using the same distribution version of Linux.
We understand a change to the Xorg software was made to the Fedora-8
version to accommodate users of multiple displays. This change apparently
broke the Zoom feature and on the Fedora-8 distribution the Zoom feature
was disabled. Apparently there is a patch to the X windows server that
can be used to re-enable the Zoom feature, but there appears to be no
information available that documents how you get this patch and implement
We will be testing Fedora-9 when it is released to see if the Zoom feature
has been fixed. Otherwise, we will continue to use Fedora-7 as long as we
can until an alternative software distribution can be found, Our having
to use Fedora-7 over Fedora-8 puts a real crimp in our development effort.
William M. Perkins E-mail - wmp(a)grnwood.net
The Greenwood UNIX Systems Administration
Reston, Virginia (Solaris, Linux, HP-UX)
-----BEGIN PGP SIGNED MESSAGE-----
It seems that using bengali itrans in scim kills scim with a seg fault....
Anybody has such an experience?
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 44 55 35 61
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----