Re: [SLE] Re: ***ARGG*** Re: [SLE] Re: Samba HOWTO]

I deleted the SP*M word from the header on the message I sent to the list, in hopes people would respond to to the new topic. I checked my SuSE-Linux folder and find no record of it having been posted to the list though it is in my outgoing record file. Perhaps the copy you. I have _no clue_ why only you would have received the message as the ougoing record shows the To field as "suse-linux-e" without your email in the To or the Cc list. Demon email software (what would one expect from emails handled by daemons?). You can see from the headers below that it really was sent to the list, but seems to have been filtered out from list content: "special". Dunno why my messages would seem to get sent to you personally but not get to list. Just plain weird. but if my message (included below) isn't getting to the list, it might have to be forwarded by someone else, though it seems it had to get to the list in order to get to you, since your email isn't mentioned in the To,Cc, or Bcc field in the record file (the Bcc entries are kept in a "sent" mail folder and are deleted by "sendmail" as it goes out). I was just trying to clean up the header and respond to the orginal poster's question. All of these messages with SP*M in the header line are getting filtered into my SPAM folder that eventually gets used as learning material for spamassassin...(after I manually try to weed out non-spam such as this entire thread -- this being a prime example as to why I don't use spamassassin's autolearn feature). I'd prefer my spam-filter _not_ start thinking that things with SLE in the header and to the suse-linux-e mailing list have a higher Bayes probability of being SP*M. -linda p.s. I am deliberately "Cc"ing you on this one so you should, theoretically, get two copies -- the one directly to you and the one sent through the list. Sorry for any confusions in my attempt to unconfuse the message string. James Knott wrote:

Don Parris wrote:

...

I don't see anything unusual. Just out of curiosity, did you delete the ***SPAM*** bit from your subject header when sending to me? Also, I don't see that in any thread on the list but this one.

Don

I didn't change the subject. When it left here, it still had ***SPAM*** in it. It got into the thread subject, because someone else was getting messages marked that way, and he then replied with it still in the subject. Apparently the problem was caused by spamassassin, at his ISP. It has since been corrected.

--- Begin Original Message ---

From suse@tlinx.org Wed Nov 24 15:28:46 2004 -0800Message-ID: <41A50376.50103@tlinx.org> Date: Wed, 24 Nov 2004 13:56:06 -0800 From: "Linda A. W." User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: suse-linux-e@suse.com Subject: Re: [SLE] Samba "HowTo" References: <419CC9FA.15EF0B48@dev.nul> <200411231040.40045.brad@summitrd.com> <41A376A6.3040900@rogers.com> <200411240103.10327.webdev@matheteuo.org> In-Reply-To: <200411240103.10327.webdev@matheteuo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Status: RO X-Status: X-Keywords: X-UID: 996

Some people need to start editing their Subject lines and remove the spamassassin "junkmail" tag. Having the tag in the header could easily have some people's Bayes filters raising the spam score. As for how it got started...hey, just the caps "[SLE]" in the header adds to the statistical chance of it getting marked spam...CAPS in the header...then with HOWTO also all caps in the header....double "Re:" might get flagged as "weird". Anyway -- maybe the discussion on it being spam should goto the "spamassassin-talk@lists.sourceforge.net" list and the SuSE related questions about the HOWTO could go to the suse-linus-e@suse.com list? I know I missed the original post that started this, and I can't find it in my SuSE-Linux folder (likely because it expired/was too old). The earliest post I found had this in it:

...

http://en.tldp.org/HOWTO/SMB-HOWTO.html was last updated

April 2000,

....

and asked about updating the "howto" from V2 to V3 I don't know what you were looking for, exactly, but samba documentation is on the samba.org site. The doc index is at http://us4.samba.org/samba/docs/man/ . There is also an official V3 HOWTO listed on the index page located at http://us4.samba.org/samba/docs/man/Samba-HOWTO-Collection/index.html . Perhaps this answers the original question -- though I might point out that questions about Samba Howto's from "en.tldp.org" don't exactly sound like a SuSE related question. FYI, there are specific Samba related discussion groups listed at http://lists.samba.org/mailman/ with archives at http://us4.samba.org/samba/archives.html .

From my perspective, I don't like having to fish SuSE postings out of my Spam folder and make sure they end up in my "despam" folder so when I run sa-learn to teach SA what is spam/ham, it doesn't start thinking that SuSE posts are spam...SA is dumb enough as it is -- it seems to classify alot moreemail as spam than Thunderbird's own spam marker, though it might be simply a case that SA errs on side of false positives while Tbird err's on side of false negatives...

In any event -- please _try_ to get the subject's a bit more like "right", so as not to confuse silly sorting rules that look for SA-tags in the Subject field to decide if something has been marked as Spam by SA. I normally wouldn't think that something with "***SPAM***" in the header would be a normal non-spam discussion especially if I was a dumb computer filter that just separates out SA tagged spam into a Spam folder... ;-) Hope any of this helps -- and doesn't offend...not meant to be offensive, merely clarifying.... Tnx, -linda Don Parris wrote:

On Tuesday 23 November 2004 12:43, James Knott wrote:

...

Brad Bourn wrote:

...

I know it is my ISP running spamassasin with a auto-rules update that tags it based on your name and / or email

they have already marked you as an exception.

My mother often said I was exceptional. ;-)

Incidentally, I see the spam heading also.

---- end original message ---