Re: ***SPAM*** Re: [SLE] Re: Samba HOWTO
I don't. The subject on my message, as received here shows: "Re: [SLE] Re: Samba HOWTO" That ***SPAM*** is being added elsewhere. Perhaps by your ISP? Brad Bourn wrote:
Why do you put ***SPAM*** on all you emails.
you probably aren't reaching allot of people that use spamassasin and filter out that header.
B-)
On Monday 22 November 2004 09:40 am, you wrote:
Michael W Cocke wrote:
; OS/2 LAN Requester initialization file
[networks]
net1 = NETBEUI$,0,LM10,34,100,14 net2 = TCPBEUI$,1,LM10,34,100,14
Is there any reason why you're running both NetBIOS and NetBIOS over TCP/IP? There's not much need for plain NetBIOS these days, as recent versions of Windows default to, and Linux only supports NetBIOS/IP.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2004-11-22 at 12:42 -0500, James Knott wrote:
I don't. The subject on my message, as received here shows: "Re: [SLE] Re: Samba HOWTO"
That ***SPAM*** is being added elsewhere. Perhaps by your ISP?
Brad Bourn wrote:
Why do you put ***SPAM*** on all you emails.
you probably aren't reaching allot of people that use spamassasin and filter out that header.
I also see that header, but in emails that are answers to James messages - actually, twice this month. And I know it is not my provider, they don't have that service, unless I pay extra. Could the header be generated at SuSE? - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFBorectTMYHG2NR9URAt00AJ96jj3nBKO2O9SH3v+JVvm/jNPiKwCgjTha xf5yiWqZO8k1rZ5o10DKcFU= =y5ND -----END PGP SIGNATURE-----
No, it is spamassasin... for whatever reason. B-) On Monday 22 November 2004 09:07 pm, Carlos E. R. wrote:
The Monday 2004-11-22 at 12:42 -0500, James Knott wrote:
I don't. The subject on my message, as received here shows: "Re: [SLE] Re: Samba HOWTO"
That ***SPAM*** is being added elsewhere. Perhaps by your ISP?
Brad Bourn wrote:
Why do you put ***SPAM*** on all you emails.
you probably aren't reaching allot of people that use spamassasin and filter out that header.
I also see that header, but in emails that are answers to James messages - actually, twice this month. And I know it is not my provider, they don't have that service, unless I pay extra.
Could the header be generated at SuSE?
-- Cheers, Carlos Robinson
The Tuesday 2004-11-23 at 09:39 -0700, Brad Bourn wrote:
No, it is spamassasin...
Not mine. Yes, changing the subject line is one of the spamassassin configurable options; in '/etc/mail/spamassassin/local.cf': # rewrite the Subject: line with ****SPAM**** .* if set to 1 (default=1) rewrite_subject 1 -- Cheers, Carlos Robinson
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2004-11-22 at 12:42 -0500, James Knott wrote:
I don't. The subject on my message, as received here shows: "Re: [SLE] Re: Samba HOWTO"
That ***SPAM*** is being added elsewhere. Perhaps by your ISP?
Brad Bourn wrote:
Why do you put ***SPAM*** on all you emails.
you probably aren't reaching allot of people that use spamassasin and filter out that header.
I also see that header, but in emails that are answers to James messages - actually, twice this month. And I know it is not my provider, they don't have that service, unless I pay extra.
Could the header be generated at SuSE?
If it was, I'd see it on my messages, as they're posted on the list. Do the message headers offer any clues?
participants (3)
-
Brad Bourn -
Carlos E. R. -
James Knott