On 14 Dec 2007 at 16:41, Mariposa Symphony Orchestra wrote: > No router; the computer is directly plugged into the DSL modem.
Unless the router provides NAT IP addresses (i.e., not routable from outside the DSL modem -- this is something that Verizon's DSL modems do now), then this is a rather dangerous configuration, as you're depending on your software firewall to protect you from exploits on the wild Internet. Dropping a $50 broadband router between your PC and DSL modem would vastly improve your inbound security. > And the computer hasn't been ID'd as 'Les.' Then that name is somehow provided by your ISP, and then they are to blame for providing a nonresolvable host name. But, just doing a traceroute to the IP address in your latest email (64.118.115.205), it does a reverse DNS lookup that resolves to 64-118-115-205-rt- broadband-00.broadband.oakhurst.sti.net, which is exactly the same kind of thing as RoadRunner does. I don't know why your SMTP server thinks that the machine with IP address 64.118.115.205 is called "Les". > The oddity to me is that > I only have this problem with the shsu server. It would likely happen with any listserv using graylisting. > And - of course as > you note: indiscriminately so. Some times, no prob; other times: > bingo. I do a rather large amount of e-mailing every day and to a > pretty far-flung number of recipient ISPs....but never (to my obvious > knowledge) experience this sort of tagging elsewhere. The tagging is gone, so maybe it was an erroneous configuration change at SHSU that has been rolled back. Your messages are still getting stamped with the X-Greylist headers, though. > As sidebar: The past problem which I noted between my ISP and AOL > arose from client(s) of STI either having their addresses used as > forged headers by a spammer, or STI clients having their computers > actually be hijacked by a spammer or -- an STI client was an actual > spammer. And consequently, AOL identified the .sti domain as a spam > source and blacklisted the entire domain, or so I discovered: any > e-mail from any STI client was automatically bounced by AOL itself -- > at least that's what I was told. STI is a relatively large server > covering a good chunk of Central California. Thousands of clients > who may have been victimized. Me? Naw. The computer is larded > with anti-spy, anti-viral, anti-bot....you name it, scrupulously kept > up-to-date. You're in a dangerous state connected directly to the Internet. Installing a broadband router is really plug'n'play, about as easy as it gets. > But in any case, David --- I really do appreciate (and enjoy) your > e-tective work. And am more than satisfied to play Watson to your > Holmes. I'm interested in this kind of thing because my own clients occasionally encounter similar problems. If your email messages had the first RECEIVED: header with 64-118-115-205-rt-broadband- 00.broadband.oakhurst.sti.net as the name, then I strongly doubt that your messages would be getting flagged at all. Why they are not, I can't say. -- David W. Fenton http://dfenton.com David Fenton Associates http://dfenton.com/DFA/ _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
