Outgoing email treated as spam

Our domain and exchange is run on SBS 2003. All email accounts are hosted at the exchange. Whenever anyone sends out an email from this domain to a new recipient, the recipient system seems to regard it as spam. As far as i can see the domain (dgslex.ca) is not blacklisted. I have tried sending out directly from the server and via a smarthost (the ISP's smtp server - smtp10.bellnet.ca) however nothing seems to make a difference. The web site (www.dgslex.ca) is hosted elsewhere and the static IP to which it is attached is blacklisted in some places - I don't know if this can cause a problem. Any help would be greatly appreciated.
m28298Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Matt1705Commented:
Is a response received from the emails and if so, what does it say?
0
the_b1ackfoxCIOCommented:
How are you getting an indication that the email is being treated as spam?  Lets start from there and work out way to a fix.
0
m28298Author Commented:
There is no response. This email was sent to a gmail account and arrived in the spam folder rather than the inbox, i have included the text shown when "Show original" is selected... (The SBS SMTP server is currently set to send out via smarthost - smtp10.bellnet.ca)
                                                                                                                                                                                                                                                           
Delivered-To: dmarshment@gmail.com
Received: by 10.150.148.3 with SMTP id v3cs130121ybd;
        Wed, 30 Jan 2008 19:01:58 -0800 (PST)
Received: by 10.35.106.1 with SMTP id i1mr1681174pym.62.1201748518340;
        Wed, 30 Jan 2008 19:01:58 -0800 (PST)
Return-Path: <mparent@dgslex.ca>
Received: from tomts27-srv.bellnexxia.net (tomts27.bellnexxia.net [209.226.175.101])
        by mx.google.com with ESMTP id n63si3435744pyh.8.2008.01.30.19.01.56;
        Wed, 30 Jan 2008 19:01:58 -0800 (PST)
Received-SPF: pass (google.com: domain of mparent@dgslex.ca designates 209.226.175.101 as permitted sender) client-ip=209.226.175.101;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of mparent@dgslex.ca designates 209.226.175.101 as permitted sender) smtp.mail=mparent@dgslex.ca
Received: from toip37-bus.srvr.bell.ca ([67.69.240.38])
          by tomts27-srv.bellnexxia.net
          (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP
          id <20080131030155.ZBMP24647.tomts27-srv.bellnexxia.net@toip37-bus.srvr.bell.ca>
          for <dmarshment@gmail.com>; Wed, 30 Jan 2008 22:01:55 -0500
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAE5ulEdGNs21/2dsb2JhbACBV4EYqC0
Received: from mtrlpq02-1177996725.sdsl.bell.ca (HELO mail.dgslex.ca) ([70.54.205.181])
  by toip37-bus.srvr.bell.ca with ESMTP; 30 Jan 2008 22:01:54 -0500
Subject: trying again
Date: Wed, 30 Jan 2008 22:01:43 -0500
Message-ID: <8314A81B6514C14A9538331F66BD3C46068488@dgs-server.dgslex.local>
X-MS-Has-Attach:
MIME-Version: 1.0
Content-Type: multipart/alternative;
      boundary="----_=_NextPart_001_01C863B5.9C1BA7B4"
X-MS-TNEF-Correlator:
Thread-Topic: trying again
Thread-Index: AchjtZvOONaY159JQjW+0JTfU8tdyg==
From: "Administration Dionne Gertler Schulze" <mparent@dgslex.ca>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
To: <dmarshment@gmail.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C863B5.9C1BA7B4
Content-Type: text/plain;
      charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

and again...

------_=_NextPart_001_01C863B5.9C1BA7B4
Content-Type: text/html;
      charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16587" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D431230103-31012008>and =
again...</SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C863B5.9C1BA7B4--

0
Webinar: Miercom Evaluates Wi-Fi Security

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom how WatchGuard's Wi-Fi security stacks up against the competition in our upcoming webinar!

the_b1ackfoxCIOCommented:
does your smart host have a reverse lookup ptr in DNs setup for it?
0
m28298Author Commented:
sorry b1ackfox, you have passed the limit of my comprehension with your question. Where do I check this - The DNS for the domain held by the webhosts (with an MX record pointing at our SBS server), the DNS setup on our SBS server or would this be held by the ISP? - again - sorry for being thick.
0
the_b1ackfoxCIOCommented:
ur not being thick...  here is how the problem breaks down...  If you are sending email to a smart host, and it is being reported as spam, you should be on the phone with the service provider asking them to fix the issue.  Fact of the matter is that mail being sent out from your system is getting to where it needs to go, so something is making it look suspicious.  If your domain is not blacklisted, then either the config from the service provider of the smart host is setup incorrectly, OR some mail that has come from the ip address of the service provider has been flagged as spam...  either way, the service provider should be doing the foot work to clear this up...  you job is clear... give em hell until they get it fixed...
0
m28298Author Commented:
the service provider is bell canada - so anything is possible! however I use the same smtp server for many domestic email accounts and commercial domains hosted by the service provider using POP/SMTP based email accounts without a problem. yet when I send out email from an SBS hosted domain via this ISP I have the problem. Is this because they need to create the "reverse lookup ptr in DNs" you mentioned? if so what do I ask for (because Bell Canada's customer service is not great).- Or is this something I can do?
0
the_b1ackfoxCIOCommented:
If other accounts are not acting the same way, it isn't a reverse ptr issue, but it is still a configuration issue.  I will be back in about 30 minutes or so (commute home)
0
m28298Author Commented:
i have just run the email and internet connect wizard specifying my isp's smtp server - thus creating a smtp connector rather than a smart host - no change. I will be on the phone to bell in the morning. I now retire with a horible sinking feeling - staring into the abyss that is BellCanada's customer service. Thanks for your help.
0
m28298Author Commented:
I had to upgrade my internet service to one that permits a reverse dns lookup.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.