Re: Reporting problem (found problem: COMCAST)

"Jim" <[email protected]> wrote:.
> (quoting me)
> >
> > Hi, Jim.
> >
> > I noticed the same thing today.  Seems all my submissions
> > since July 4th have been eaten by the comcast mailserver.
> >
> > Fortunately the outgoing filtering seems to be on their
> > server and not at the router.  I set OE to use one of the
> > spamcop MXs as its smtp server for an OE "Account" and a
> > submission from that user got through.
> >
> > Fast.  Flakey (2% packet loss).  Costly ($60/mo).  Rude.
> >
> > I'll try again with my other mail-handling ISPs tomorrow.
> >
> > d.
> >
> >
> I had about 12 emails from/to comcast about them blocking outgoing emails
determined to be spam.
>    They kept saying they do not block outgoing email.  On one of their
last emails they had me
> go to Comcast Web Mail and submit the spam.  It was even blocked there.
They kept asking me to
> go to online chat to try to solve the problem.  In frustration I just gave
up.  Another problem
> in dealing with Comcast  by email is that you do not get a service number
so every email is
> handle by a different person.
>
> It also made no difference if the spam was in the body of the email or as
an attachment, it was
> still block.


I repeated your test and found I was able to forward
either one or two *CLEAN* email attachments through
the comcast mailserver with no trouble.

If I forward a message known to contain a virus, though,
nothing comes through.  The message isn't rejected on
submission and doesn't generate any error message but
is silently killed.

Comcast accepts mail submissions from its customers with
no authentication beyond the IP.


My other mail-handling ISP, geekisp (www.geekisp.net)
does forward the messages, even if spammy or infected,
after renaming the infected attachment and prepending
a virus notification on  the subject line.

GeekISP requires encryption and authentication and
supports IMAP.  I really like 'em.

duncan.