On Wed, 10 Sep 2003 22:08:04 +0100
"Alberto" <alberto(_at_)bersol(_dot_)fadlan(_dot_)com> uttered:
I don't know if your problem is the same of mine. My fetchmail version
is 6.2.2-3.
Please, paste here your log and the incorrect header for compare it.
This is *I believe* what was causing the problem, but I have yet to
determine if it is something added by my ISP or lists.sourceforge.net.
X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact
helpdesk(_at_)ITBE(_dot_)utwente(_dot_)nl for more information.
X-UTwente-MailScanner:
Found to be clean X-Spam-Score: -1.0 (-)
X-Spam-Report: -1.0/5.0
The original message has been attached along with this report, so
you can recognize or block similar mail in future.
See: //spamassassin.org/tag/ for more details.
Content: On Wed, 10 Sep 2003 00:20:40 +0200 mess-mate wrote: :
Hi,: did you install rox on a debian system ? : If so, how did
you; I can't: ( : A+ : mess-mate After we added both the apt sources
from the rox webpage and the one suggested by Marcin Juszkiewicz running
"apt-get install rox" just worked (although with a slightly outdated
shared-mime-info version if I remember correctly). [...]
Content: (-1.00 points, 5 required)
IN_REP_TO (-0.5 points) Has a In-Reply-To header
REFERENCES (-0.5 points) Has a valid-looking References header
I don't believe it is my ISP, as they claim they use something called
"Brightmail', but it is entirely possible that Brightmail uses
Spamassassin.
On the other hand, this tag only appears in mail from
lists.sourceforge.net.
All I know *for sure* is that patching Fetchmail 6.2.4 fixed the
problem.
I am not sure what you mean by "log".
--
JoeHill
Registered Linux user #282046
Homepage: www.orderinchaos.org
+++++++++++++++++++++++++++
Waste not fresh tears over old griefs.
-- Euripides