It's a problem with GMail's spam filters and they are *not* optional. There is a lot of discussion about it on the GMail lists. It isn't the LUG messages, specifically, that are snagged, and I'd only be speculating why some are marked and most are not (GMail techs won't discuss the criteria, for obvious reasons). But I really don't think it's because of HTML -- so many people use that that it isn't a reliable identifier.

It's a good reminder, though, that if people find they are missing parts of conversations on the LUG, to check the spam folder -- whether you're using GMail or your ISP has filters.

At the risk of beating a dead horse, I think if the LUG messages were configured to only include the LUG email address, and not the sender's personal address, it might make a difference. The other lists that I am on that do *not* include the personal address on the "From" line -- or include a LIST header, don't end up in the spam folder.

Kirsten Bowman wrote:
Kris:

I also get a fair amount of LUG mail in my spam folder both on my computer
and in my ISP's spam folder.  Sometimes I pull them out and read them;
sometimes I don't.  Do you know the cause?

Perhaps this is a good time to remind listers (yet again) to send in plain
text--or chance ending up in the spam box with no replies.

Kirsten

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kris
Sent: Friday, September 12, 2008 2:07 PM
To: [email protected]
Subject: Re: [LegacyUG] fake messages from Geoff


Some ISPs do a pretty good job of blocking stuff like that.  After
reading Ron's message, I found them.  GMail did a pretty good job of
snagging them.  Unfortunately, I also found quite a few other messages
from the LUG in there, too -- legitimate ones.  :-)



Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/[email protected]/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Reply via email to