GoDaddy server email issues

Discussion in 'Mail Server Support' started by fearmydesign, Sep 23, 2010.

  1. fearmydesign

    fearmydesign Valued Member

    Joined:
    Feb 12, 2009
    Messages:
    29
    Likes Received:
    0
    We recently purchased a dedicated hosting server with GoDaddy (not sure if this was a really good idea to tell you the truth). After many, many.... many issues with the server, we finally got it stable...kind of.

    Currently our own internal company emails go into SPAM when we send emails to eachother. GoDaddy said we needed to upgrade MailEnable so we did, and Spam Assassin as well and we paid for that as well... I get the feeling that they really don't know and keep making us waste more money. Unfortunately our Spam Filtering on the server wide settings was set to delete all spam... so yes, some emails that were being sent from employees were also being deleted without even making it to the recipients junk folder.

    My Question is, there is a setting called White List on Plesk where I know you can add all the safe email addresses, but this would take forever to do for each individual email. Then there is another setting called Trusted Networks List, and it's asking me for "IP address/mask" - what is this? and would this solve our internal emailing problems at least?

    Thank you and sorry for the length of this thread.

    Regards
     


  2. popowich

    popowich EQ Forum Admin Staff Member

    Joined:
    Aug 12, 2008
    Messages:
    8,983
    Likes Received:
    120
    The trusted networks is likely part of the SpamAssassin configuration too.

    For example in my SpamAssassin I have my smtp relays listed in the trusted networks on my incoming mail servers.

    Only put networks into trusted networks that you operate.

    Here is the official blurb from the SpamAssassin documentation :

     

  3. popowich

    popowich EQ Forum Admin Staff Member

    Joined:
    Aug 12, 2008
    Messages:
    8,983
    Likes Received:
    120
    I think the best answer to your question is to take this one step further.

    SpamAssassin should only be filtering incoming email on port 25.

    Yes, it is a good idea for SpamAssassin to be properly configured, but...

    Your users if using the same server for sending email should be using some flavor of smtp authentication on port 587 that allows them to relay but does not filter their email with SpamAssassin.

    Separating the incoming email and smtp relay services should solve the problem.
     
  4. fearmydesign

    fearmydesign Valued Member

    Joined:
    Feb 12, 2009
    Messages:
    29
    Likes Received:
    0
    We made the decision to actually send our emails through a Linux CentOS server instead. We will just host the website on the Windows server. It just seems much safer and reliable to do this.

    Any thoughts?

    Regards
     
  5. popowich

    popowich EQ Forum Admin Staff Member

    Joined:
    Aug 12, 2008
    Messages:
    8,983
    Likes Received:
    120
    Seems reasonable enough. Helps prevent all of your services from going down at the same time too if they are spread across multiple servers.
     

Want to reply or ask your own question?

It only takes a minute to sign up (and it's free!). Click the orange sign up button to choose a username and then you can ask your own questions on the forum.
Loading...