Results 1 to 10 of 10
  1. #1
    Join Date
    Sep 2003
    Posts
    32

  2. #2
    Please check your Mail server relay settings. You may want to run relay test from http://www.abuse.net/relay.html. As far as I know you can't restrict the From Address to any user. But the original point is to deny such users to use your mail server to send mails and for this you need to check relay thing.

  3. #3
    If it is not sent from your server, don't bother. There's nothing you can do nor stop it.

    Most likely the spam are sent from many trojaned machines worldwide. So tracking the sending machines usually is a waste of energy and of course talking to ISPs is not the most fun thing.

    Just ride it out
    Like us on Facebook to qualify for discounts!
    http://www.sprintserve.net
    Offering: | Internap FCP Bandwidth! | Rebootless Kernel Updates! | Magento Optimized Hosting | Wordpress Hosting |
    Services: | Managed Multiple Cores 64bit Servers | Server Management |

  4. #4
    Join Date
    Apr 2004
    Location
    San Jose
    Posts
    902
    It's not particularly useful yet, but it won't hurt to set up SPF and Microsoft "Caller ID for Mail" TXT records for your domain. Then AOL, Hotmail, and few others will refuse the mail in the first place, knowing it's not from you.

  5. #5
    What is "SPF and Microsoft "Caller ID for Mail" TXT records for your domain". Can you please it and let me know how to configure them.

  6. #6
    Join Date
    Apr 2004
    Location
    San Jose
    Posts
    902
    Do a google search on "caller id for mail", and "spf mail".

    They specifiy DNS TXT records you can publish so that mail receivers can verify that mail claiming to be from your domain comes from an IP you say is one of your email servers.

  7. #7
    Join Date
    Jun 2003
    Posts
    673
    http://www.microsoft.com/mscorp/twc/..._callerid.mspx

    XML in TXT records? Idiotic. Use SPF instead. (Still won't accomplish anything at this point.)

  8. #8
    Join Date
    Mar 2004
    Location
    Vancouver Island, BC
    Posts
    173
    I've found that SPF might work, at least when I've added it to domains undergoing a current "joe job" by the spammers that they stop using it quite quickly once the SPF records exist.
    Dynanet Network Services - 206-607-9075
    We Do Hosting - Established May 2001
    http://www.dynanet.ca/

  9. #9
    Join Date
    Jun 2003
    Posts
    673
    Hmm... Well, the spammers that are forging my domain name are a bit more persistent than that. I've had SPF records up for probably half a year now, and the bounces keep on coming. :/

  10. #10
    Join Date
    Mar 2004
    Location
    Vancouver Island, BC
    Posts
    173
    If you use a default catch-all then try disabling that until the flood slows some, that can help too as then some remote MTA's will refuse to accept from the spammer.

    Basically you need to make it as difficult as possible for the spammer to send using your domain name, having SPF and no default catch-all means there's more of a chance their garbage will get blocked and they are less likely to use your domain then

    But there will always be one I'm sure.
    Dynanet Network Services - 206-607-9075
    We Do Hosting - Established May 2001
    http://www.dynanet.ca/

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •