On Wed, Dec 3, 2008 at 9:07 AM, Mark Komarinski <[EMAIL PROTECTED]> wrote:
>
I'm amused that I have apparently become an HTML tag. ;-)
-- Ben
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhl
On 12/02/2008 11:34 PM, Dan Miller wrote:
> Every time I received these emails, all I had running was Linux with a
> customized iptables script, so chances of a virus are virtually nil.
>
Just because you don't have viruses doesn't mean that a misconfiguration
of your MTA* will cause you to b
I've had similar experience. I don't think Comcast can tell the
difference between a joe-job and real spam.
I gave up pestering them and am just sending all outgoing email through
a VPN to one of our servers in Manchester.
--Bruce
Dan Miller wrote:
> I've called Comcast (when I had them) before
I've called Comcast (when I had them) before on this very issue. Ask for
the security department, and then start asking for evidence. Since their
email states (and they state on the phone) that they closed the port
because it looked like you were spamming and have a virus.
I would always ask fo
Many thanks to everyone who's replied so far!
Yes, I was aware that there is a very serious spam issue both
within Comcast and overall on the Internet. I'd been using the Port 25
configuration since I started with Comcast over 5 years ago (after I
got married and moved down here to sunny South Flo
I would like to have seen Comcast do this in some more gentle way. In my case,
I got the message that I was a spammer last March. I was helping with
communications right before my daughter's school play. Just days before the
show, when we were making last minute tweaks to the schedule, BAM! My
On Tue, Dec 2, 2008 at 9:41 AM, Bayard Coolidge <[EMAIL PROTECTED]> wrote:
> ... considered a spammer and/or that I had a security problem caused by
> a virus/bot.
> ... I'm wondering what their real agenda is...
Making money, of course. But they're trying to increase their money
by blocking sp
On 12/02/2008 09:41 AM, Bayard Coolidge wrote:
I got a nastygram from Comcast in my normal e-mail inbox this morning,
warning me that I was considered a spammer and/or that I had a security
problem caused by a virus/bot.
The recommended fix apparently is to move my outbound SMTP to Port 587,
whi
On Tue, Dec 2, 2008 at 10:09 AM, Charlie Farinella <
[EMAIL PROTECTED]> wrote:
> I had the same thing happen to me. In my case they blocked outgoing
> mail from my wife's account only, even though all of my computers go
> out through the same router.
>
> I also followed their instructions and hav
On Tuesday 02 December 2008, Bayard Coolidge wrote:
> I got a nastygram from Comcast in my normal e-mail inbox this morning,
> warning me that I was considered a spammer and/or that I had a
security
> problem caused by a virus/bot.
>
> The recommended fix apparently is to move my outbound SMTP to
I got a nastygram from Comcast in my normal e-mail inbox this morning,
warning me that I was considered a spammer and/or that I had a security
problem caused by a virus/bot.
The recommended fix apparently is to move my outbound SMTP to Port 587,
which I have now done.
But, considering that I'm ru
11 matches
Mail list logo
