Hi Mike,
On Wed, 26 Jun 2002 22:07:49 -0500, you wrote:

> My colleague was told by her ISP that it was because they
> "blacklisted" certain domains. Since I have my own domain
> (harlos.net), I had a hard time understanding why I would be included
> with the likes of Hotmail etc. I don't do any spamming or mass
> mailings.

If the mail server that is reporting to be from your domain is on the black
list, then they'll probably ignore you.  Or if you host your domain from a
DSL/Dialup connection for example, you may find that you have been caught in a
block that matches the whole section.  Or even if you are sending mail from a
blacklisted block, and not necessarily have anything to do with your domain
[harlos.net].

> I phoned their tech support, and was told that they block emails that
> are sent via a relay (?SMTP relay). I'm afraid that my technical
> knowledge does not enable me to fully understand or explain this.

An open relay (which is what they are often referring to) is a poorly configured
mail server that allows anbody the ability to send mail via it, even people that
are not supposed to.  These often get exploited for the pure and simple use of
spam.  Most of the time, they rely on external sources to do the work, they just
do a lookup on it (see http://www.ordb.org or http://mail-abuse.org).


> I use the SMTP server at my service provider, ATT Canada:
> outbox.attcanada.ca

Maybe you might want to take a look http://www.ordb.org and do a lookup on
there, see if it's listed.  If so, you may want to contact your ISP, and notify
them, although ordb.org does notify the poorly configured server's admin to let
them know of the issue.

> I suppose that because my email address [EMAIL PROTECTED] does not match
> my ISP's domain, it is considered to be relayed?

I highly doubt they'd do that, otherwise a lot of mail aliases would never work.
Take for example your ISP... I'm sure they run several other domains on the same
servers.  If random ISPs decided to start blocking mail because the sending name
doesn't match the real name from what it's being sent from... then a lot of mail
would be rejected.  You also get the issue as well with major companies such as
uu.net who provide line/server services to companies who then sell on their
services to end users.  All the uu.net dialup accounts have <some
location>.<some ip>.uu.net or in that kind of format.  For any mail to work in
the above case, you'd have to have a uu.net email address, which is not the
case, the sub-provider often issues one under their domain.

> In any case, that was their explanation... I didn't suspect that it
> was a TB! issue.

I don't personally think it is a TB issue itself... more of an issue with the
ISP setup.  I find it unusual to believe that a client would drop a connection
to just one ISP... but it does appear the the afflicted ISP is doing some form
of filtering, and dropping the X-Mailer that matches TB!.  What really needs to
happen, is some direct contact with the actual people that run the server, and
not some tech support representative.  In most ISP cases, the tech support
representative doesn't have that kind of information.

-- 
Jonathan Angliss
([EMAIL PROTECTED])

________________________________________________________
Current Ver: 1.60q
FAQ        : http://faq.thebat.dutaint.com 
Unsubscribe: mailto:[EMAIL PROTECTED]
Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Bug Reports: https://www.ritlabs.com/bt/

Reply via email to