All Archives / aussie-isp / 2005-08
<<< Date >>>
Permanent Link
Date: Fri, 05 Aug 2005 03:19:55 +1000
From: Reid
To: Paul Raj Khangure
Cc: Oz-ISP Mailing list
Message-Id: <1123175995.3108.9.camel@dragonslair.au00.com>
In-Reply-To: <20050804021319.GA22601@she-bitch.digitaljunkie.net>
References: <20050804021319.GA22601@she-bitch.digitaljunkie.net>
Subject: Re: [Oz-ISP] Domain Hosting Companies - Spam Relaying
No followups recorded.

On Thu, 2005-08-04 at 10:13 +0800, Paul Raj Khangure wrote:
> A question for the ISP community in general, with relevant company names
> removed.
>
> A domain hosting company offers a service to paying clients, whereby any
> email sent to u s e r n a m e @ c l i e n t - d o m a i n . c o m . a u is forwarded through to
> u s e r n a m e @ i s p . c o m . a u
>
> Said company has a large number of clients, who forward to a
> particular ISP
> ISP.com.au's mail servers notice that over half the mail coming from
> the hosting company's MX servers is SPAM, and blacklist said servers.
> Those servers aren't originating the spam as such, but they are relaying
> it.

Wouldn't it make sense to block that spam before it hit your server,
rather than pass it on to others?  

> Does the domain hosting company have any responsibility to not relay
> spam? After all, their clients are paying for all the email to be
> forwarded.

Domain hosting company would be better off not forwarding, and offering
pop3 access, further Domain hosting company's clients would be better
off with a service that blocked the "over 50%" of traffic that is crap.

> Does the ISP have to put up with said spam, instead of just blacklisting
> the servers, and suggesting that affected clients change domain hosting
> company?

No. Get a clue!


--
Reid <r e i d . h a l l @ a u 0 0 . c o m

----
email "unsubscribe aussie-isp" to m a j o r d o m o @ a u s s i e . n e t to be removed.

<<< Date >>>
This page was automatically generated, based on a complete record of postings made to the nominated list. Copyright issues, blame or gratitude belongs to the entity that wrote the content.