SEEN-BY: 39:13/0@amiganet 14/0 15/0 16/0 17/0 24/0 39/0 136/1 .20
140/100
SEEN-BY: 150/200 711/16 901/0
Are this lot ghosts?
Btw: your email with the fidopkt got marked as spam, by my provider:
X-XS4ALL-Spam-Score: 5.822 (*****) DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75 X-XS4ALL-Spam: YES
I had that problem here too, but as I run the mail server I could feed
it into SpamAssassin's sa-learn directly so it knew I wanted fido
packets.
X-XS4ALL-Spam-Score: 5.822 (*****)
DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75 X-XS4ALL-Spam: YES
Hmm, Y2K? I'll look into that, might reduce the spam-score a bit. Otherwise quite a high rating for just some encoded binary.
I reported at my provider but no response jet, so I do it againX-XS4ALL-Spam-Score: 5.822 (*****)
DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75 X-XS4ALL-Spam: YES
because this pkt had the same problem...
The year in the date is spelled as '05' not '2005' and the from line
only contains the email adres not a name between quotes ("). Those
might be things you can change?
X-XS4ALL-Spam-Score: 5.822 (*****)
DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75 X-XS4ALL-Spam: YES
Hmm, Y2K? I'll look into that, might reduce the spam-score a bit. Otherwise quite a high rating for just some encoded binary.
I reported at my provider but no response jet, so I do it againX-XS4ALL-Spam-Score: 5.822 (*****)
DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75 X-XS4ALL-Spam: YES
because this pkt had the same problem...
Can you whitelist the address? Either on their side or yours? The problem is that no matter how well presented the email is (and I accept that it isn't completely correct) it's still a big load of uuencoded or base64 encoded text which looks just like a lot of spam.
I still like Fido for lack of spam and general lack of people posting
huge HTML emails around, but it still affects us :-) (Even worse, I
gate email and news to my BBS!)
The year in the date is spelled as '05' not '2005' and the from line
only contains the email adres not a name between quotes ("). Those
might be things you can change?
Yup, testing on this outbound packet - hopefully enough to lower the score to just under 5..
Amazing; it's about two years since I made any changes to Zeus then
two come along at once. The other was adding timezone support to the
NNTP client, so I can reliably use news from the other side of the
world, as my ISP's server breaks the RFCs..
Btw: your email with the fidopkt got marked as spam, by my provider:
X-XS4ALL-Spam-Score: 5.822 (*****) DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75
X-XS4ALL-Spam: YES
I had to rescue it from my pre-filter backup. I've reported this to
my provider, so they might fix it...
Btw: your email with the fidopkt got marked as spam, by my provider:I had that problem here too, but as I run the mail server I could feed
it into SpamAssassin's sa-learn directly so it knew I wanted fido packets.
X-XS4ALL-Spam-Score: 5.822 (*****)
DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75 X-XS4ALL-Spam: YES
Hmm, Y2K? I'll look into that, might reduce the spam-score a bit. Otherwise quite a high rating for just some encoded binary.
Btw: your email with the fidopkt got marked as spam, by my provider:
X-XS4ALL-Spam-Score: 5.822 (*****)
DATE_SPAMWARE_Y2K,NO_REAL_NAME,UPPERCASE_50_75
X-XS4ALL-Spam: YES
seems like sendmail with mailscanner ? :-)
I had to rescue it from my pre-filter backup. I've reported this to
my provider, so they might fix it...
and change to postfix :-)
PS: why should fido pkt needs email in the first place ?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 371 |
Nodes: | 16 (2 / 14) |
Uptime: | 176:03:44 |
Calls: | 7,915 |
Files: | 12,983 |
Messages: | 5,797,780 |