mail delivery problems / MX record issue?

[Brad Knowles]

At 1:54 PM +0000 6/5/01, Roger Rabbit wrote:

>  The web server is an offsite machine, hosting probably dozens of
>  web sites and is something I don't have any control over.
>  If there's anything I can ask them (hostway.com) to do that wouldn't
>  affect their other users, please let me know.
>  The other thought I had was to point the top-level domain to our mail
>  server and only assign www.epcom.com to the web server.  But then
>  that would prevent people from accessing the web page via
>  http://epcom.com/.

	That still wouldn't stop spammers from using it.

	If you can't get the web hosting company to turn off the mail 
server listening on port 25, you're screwed.  Unless you want to 
refuse all mail coming to your mail servers from the web hosting 
machine, there's simply no way you can stop them.


	Oh, and please don't use "NOSPAM" garbage in your return address. 
The newsgroup you posted this message to is gatewayed to a mailing 
list, and having this garbage in your address is anti-social and 
makes it more difficult for people to reply to you with the kind of 
information you've requested.

	Moreover, all address scanning tools I know of are intelligent 
enough to remove all "NOSPAM" type tags I've ever seen, so it doesn't 
do any good anyway.

-- 
Brad Knowles, <brad.knowles at skynet.be>

/*        efdtt.c  Author:  Charles M. Hannum <root at ihack.net>          */
/*       Represented as 1045 digit prime number by Phil Carmody         */
/*     Prime as DNS cname chain by Roy Arends and Walter Belgers        */
/*                                                                      */
/*     Usage is:  cat title-key scrambled.vob | efdtt >clear.vob        */
/*   where title-key = "153 2 8 105 225" or other similar 5-byte key    */

dig decss.friet.org|perl -ne'if(/^x/){s/[x.]//g;print pack(H124,$_)}'