email delays: THIS IS A WARNING MESSAGE ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE.

This is normal, there's no need to get nervous about it...

If the message never comes through, then there's a problem, of course. Do you know if these delayed messages eventually reach the intended recipient or if your server times out after a few days?

If you also have other problems, like your mail is being rejected from certain receiving domains and such, you may have to take a look at your DNS records and verify that your sending server/domain is not blacklisted somewhere.
/RID

here is my exim logs for that email address (in this case receiver@domain2.com) they sent to that is being sent back.

2008-03-03 13:02:44 1JWEzl-0006Bl-6X <= sender@domain1.com H=fuse-dedicated-66-117                                                             -238-124.fuse.net (DT3) [66.117.238.124] P=esmtpa A=fixed_login:sender@domain1.com                                                              S=1342659 id=01c401c87d58$ca1384d0$6c01a8c0@DT3 T="subject: Hi Company name"
2008-03-03 13:02:47 1JWEzl-0006Bl-6X => paul <sender2@domain1.com> R=virtual_user T=                                                             virtual_userdelivery
2008-03-03 13:02:48 1JWEzl-0006Bl-6X => receiver@domain2.com R=lookuphost T=r                                                             emote_smtp H=g.mx.mail.yahoo.com [206.190.53.191]
2008-03-03 13:02:48 1JWEzl-0006Bl-6X Completed

2008-03-04 15:48:19 1JWe3f-0000zL-Aw <= receiver@domain2.com H=web54112.mail.                                                             re2.yahoo.com [206.190.39.50] P=smtp S=2087 id=985256.16588.qm@web54112.mail.re2                                                             .yahoo.com T="Re: Omega Processing Merchant Status - Pending  Subject: Hi company name                                                             up"
2008-03-04 15:48:31 1JWe3f-0000zL-Aw => daena <sender@domain1.com> R=virtual_user                                                              T=virtual_userdelivery
2008-03-04 15:48:31 1JWe3f-0000zL-Aw Completed

2008-03-05 07:40:13 1JWsur-0007my-E0 <= sender@domain1.com H=(DT3) [66.117.238.124                                                             ] P=esmtpa A=fixed_login:sender@domain1.com S=2104 id=003001c87ebe$15878c70$6c01a8                                                             c0@DT3 T="RE: Omega Processing Merchant Status - Pending  subject: Hi Company name"
2008-03-05 07:40:55 1JWsur-0007my-E0 == receiver@domain2.com R=lookuphost def                                                             er (-1): host lookup did not complete
2008-03-05 08:05:03 1JWsur-0007my-E0 == receiver@domain2.com R=lookuphost def                                                             er (-1): host lookup did not complete
2008-03-05 09:03:05 1JWsur-0007my-E0 SMTP error from remote mail server after en                                                             d of data: host b.mx.mail.yahoo.com [66.196.97.250]: 451 Message temporarily def                                                             erred - [250]
2008-03-05 09:03:05 1JWsur-0007my-E0 => receiver@domain2.com R=lookuphost T=r                                                             emote_smtp H=d.mx.mail.yahoo.com [216.39.53.2]
2008-03-05 09:03:05 1JWsur-0007my-E0 Completed

2008-03-05 14:41:12 1JWzUG-0007p3-Tm <= receiver@domain2.com H=web54110.mail.                                                             re2.yahoo.com [206.190.37.245] P=smtp S=3097 id=141586.49638.qm@web54110.mail.re                                                             2.yahoo.com T="what is the status for  subject: Hi Company name"
2008-03-05 14:41:26 1JWzUG-0007p3-Tm => daena <sender@domain1.com> R=virtual_user                                                              T=virtual_userdelivery
2008-03-05 14:41:26 1JWzUG-0007p3-Tm Completed

2008-03-05 14:45:59 1JWzYt-00084O-MU <= sender@domain1.com H=fuse-dedicated-66-117                                                             -238-124.fuse.net (DT3) [66.117.238.124] P=esmtpa A=fixed_login:sender@domain1.com                                                              S=3106 id=016901c87ef9$8c366270$6c01a8c0@DT3 T="RE: what is the status for company"
2008-03-05 14:46:00 1JWzYt-00084O-MU => receiver@domain2.com R=lookuphost T=r                                                             emote_smtp H=c.mx.mail.yahoo.com [68.142.237.182]
2008-03-05 14:46:00 1JWzYt-00084O-MU Completed

here's a blacklist list:   we're 216.83.111.0/24
http://www.spamcop.net/w3m?action=map;mask=65535;net=3629318144;sort=ipsort

Are there any other lists we can look at to make sure we're not blacklisted?

Hi allwebnow,

This is what you want to look for :

http://www.completewhois.com/rbl_lookup.htm

This will give you the full list of where you're blacklisted

Let me know if you need more help

Regards,
Richard

Do a DNS Report for the Sender's domain to make sure there are no mis-configurations with Reverse DNS, etc.

www.dnsstuff.com

Ok, i ran a dns report and found 3 yellow warnings which I've been told to take with a grain of salt.  Regardless, my client isn't receiving emails so I need to make sure this is correct and tight.

On dnsreport for this client (http://www.dnsstuff.com/tools/dnsreport.ch?domain=omegap.com ) I get these warnings:

Warning 1. WARN SOA MNAME Check WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: ns0.dnsmadeeasy.com.. However, that server is not listed at the parent servers as one of your NS records! This is legal, but you should be sure that you know what you are doing.  

Now, ns0.allwebnow.com is a vanity of ns0.dnsmadeasy.com.  So, do I need to setup ns records at dnsmadeeasy.com account for their ns?  I use dnsmadeeasy.com for dns failover features.

Warning 2. WARN SOA MINIMUM TTL value WARNING: Your SOA MINIMUM TTL is : 180 seconds. This seems low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.

I don't know if I should raise this or not because it's the failover setting TTL dnsmadeeasy.com told me to set it at so if the server failsover, it only takes about 2mins to recache.  Would this mess up the client's ISP dns and as well cause email or blocking errors?

Warning 3. WARN Mail server host name in greeting WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

omegap.com claims to be host classic31.allwebnow.com [but that host is at 216.83.111.31 (may be cached), not 216.83.111.62]. <br />

I don't even know what to make of this this.  I read on a forum http://forums.theplanet.com/index.php?showtopic=64892 this:

You reporting the incorrect name due to a bad hostname on the server, change your servers hostname also make sure you set your hostname correct in httpd.conf,
I checked httpd.conf and the hostname looks ok.  Also, I don't know where to edit this 3-digit code.

So that's where I'm at with this.

Ok i fixed the first warning through dnsmadeeasy's support...
Warning 1. WARN SOA MNAME Check WARNING: Your SOA (Start of Authority) record states that your master (primary) name server is: ns0.dnsmadeeasy.com.. However, that server is not listed at the parent servers as one of your NS records! This is legal, but you should be sure that you know what you are doing.  
THIS IS FIXED as you can see here:
http://www.dnsstuff.com/tools/dnsreport.ch?domain=omegap.com

The other two warnings I'm still working through.

Ok, warning 2 i've been told to disregard since it is no longer a standard and I still need the ttl low for dns failover purposes in the event it happens.   So that's taken care of.

Warning 2. WARN SOA MINIMUM TTL value WARNING: Your SOA MINIMUM TTL is : 180 seconds. This seems low (unless you are just about to update your DNS). You should consider increasing this value to somewhere between 3600 and 10800. RFC2308 suggests a value of 1-3 hours. This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching.

This has been FIXED!

Only 1 more warning to figure out.

I don't understand where 216.83.111.31/classic31.allwebnow.com is being picked up from.  Is it setup in the EHLO/HELO of your mail server?  I believe this is where your problem lies.

216.83.111.31 is our main shared server's ip in which the hostname classic31.allwebnow.com is apart of.

allwebnow.com and omegap.com are 2 sites that reside on that server 216.83.111.31 with their own dedicated IP addresses ie. omegap.com = 216.83.111.62, allwebnow.com = 216.83.111.58.  These 2 domains also do NOT use the main servers local dns settings but rather dnsmadeeasy's dns services.
ns0.allwebnow.com
ns1.allwebnow.com
ns2.allwebnow.com
ns3.allwebnow.com
ns4.allwebnow.com

So when you send an email out, it comes from 216.83.111.31?

If yes, then DNSStuff (and your email recipients) is (are) looking at that and saying that it does not match what it is expecting, which is 216.83.111.62.  They may reject the email, or subject it to anti-spam measures on that basis.

Here's a header to a fuse email account from my allwebnow.com email account which is on that 216.83.111.31 server.  I replace my real email accounts with email @  :

Return-Path: <email @ allwebnow.com>
Received: from gwin4 ([216.68.8.214]) by dmta2.fuse.net
          (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP
          id <20080307215501.VJGD18758.dmta2.fuse.net@gwin4>
          for <email @ fuse.net>; Fri, 7 Mar 2008 16:55:01 -0500
Return-Path: <email @ allwebnow.com>
X-CBT-Local: fuse.net
X-CNFS-Analysis: v=1.0 c=1 a=n275RSSi7RcA:15 a=0RVjke6HtYMA:10 a=0aCI623mbnRtpNxB93W2qA==:17 a=0qykEaKHAAAA:8 a=NVLfDSTE3Umlio-Z70kA:9 a=AhrQGxENK1m26lhDBzYSd5oecgAA:4 a=ZAhoCFtSTOwA:10 a=RwiNt2JJ6zAA:10 a=LQJLfU0sVpAA:10 a=gJcimI5xSWUA:10 a=SSmOFEACAAAA:8 a=4ZEcvddvKz--V5iQBJYA:9 a=6ZdQCuBIG9a1C3WTm1IA:7 a=0Pt0W-_Zu6ZWw3ATipXFB6ktUcYA:4 a=37WNUvjkh6kA:10
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
Authentication-Results: gwin4 smtp.mail=email @ allwebnow.com; spf=softfail
Received-SPF: softfail (gwin4: transitional domain allwebnow.com does not designate 216.83.111.31 as permitted sender)
Received: from [216.83.111.31] ([216.83.111.31:41934] helo=classic31.allwebnow.com)
      by mx4.fuse.net (envelope-from <email @ allwebnow.com>)
      (ecelerity 2.2.1.28 r()) with ESMTP
      id 0E/76-05345-4B9B1D74; Fri, 07 Mar 2008 16:55:00 -0500
Received: from ev-esr1-72-49-254-161.fuse.net ([72.49.254.161] helo=allwebnow)
      by classic31.allwebnow.com with esmtpa (Exim 4.68)
      (envelope-from <email @ allwebnow.com>)
      id 1JXkWg-0001Sd-DY
      for email @ fuse.net; Fri, 07 Mar 2008 16:54:50 -0500
Reply-To: <email @ allwebnow.com>
From: "Ben Wade" <eamil @ allwebnow.com>
To: <email @ fuse.net>
Subject: test
Date: Fri, 7 Mar 2008 16:54:47 -0500
Organization: All Web Now
Message-ID: <858723372DDD496998F7BE2FAB961612@allwebnow>
MIME-Version: 1.0
Content-Type: multipart/alternative;
      boundary="----=_NextPart_000_000B_01C88073.F4CD51B0"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AciAnduge+ve8iBSTh6s6oscjKkslQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
X-AllWebNow-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 1JXkWg-0001Sd-DY
X-AllWebNow-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-AllWebNow-MailScanner-SpamCheck:
X-AllWebNow-MailScanner-From: email @ allwebnow.com
X-Spam-Status: No
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - classic31.allwebnow.com
X-AntiAbuse: Original Domain - fuse.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - allwebnow.com
X-Antivirus: avast! (VPS 080307-0, 03/07/2008), Inbound message
X-Antivirus-Status: Clean

I noticed the one above says:
Received-SPF: softfail (gwin4: transitional domain allwebnow.com does not designate 216.83.111.31 as permitted sender)

-------------------------
Now here's a header from GMAIL to the fuse account:

Return-Path: <email @ gmail.com>
Received: from gwin1 ([216.68.8.211]) by dmta1.fuse.net
          (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP
          id <20080307220140.SFIN2369.dmta1.fuse.net@gwin1>
          for <email @ fuse.net>; Fri, 7 Mar 2008 17:01:40 -0500
Return-Path: <email @ gmail.com>
X-CBT-Local: fuse.net
X-CNFS-Analysis: v=1.0 c=1 a=nS36O97Bj3wUElCrIrAA:9 a=WSUfejPYnVaDIwHsvJh5HpFP3bwA:4 a=8pNSdTfqQRAA:10
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
Authentication-Results: gwin1 smtp.mail=email @ gmail.com; spf=pass
Received-SPF: pass (gwin1: domain gmail.com designates 209.85.200.173 as permitted sender)
Received: from [209.85.200.173] ([209.85.200.173:49505] helo=wf-out-1314.google.com)
      by mx1.fuse.net (envelope-from <email @ gmail.com>)
      (ecelerity 2.2.1.28 r()) with ESMTP
      id 4A/D8-27932-219B1D74; Fri, 07 Mar 2008 16:52:18 -0500
Received: by wf-out-1314.google.com with SMTP id 23so826319wfg.5
        for <email @ fuse.net>; Fri, 07 Mar 2008 14:01:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
        bh=7AKMIOM9WZiHfV7ocN2hb4M9+ftvBCWAp2o6sKnVFGM=;
        b=BjGVB5Mr/Nq0MGlpI3dmbOr2RHk+4KG+x5rmvWERdU1dOJtkgT5cATCmMFQxUcmrTbnesU9/0LVfXN0DaAQvbL0I5Y9NaZTJz7HiyvBITNAnlsFwQG0hX+H3vTbKomKD9iZZAocvtKalHLd8S5Y2XP55XJJGuae7A3eo4/sjnf4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=qk7vk6LwxK/lDFNK0wtSJ+j20apdnzzqiI21+oHUj21hNCE6PUmXreag9E+efUQe2Z9ZZ+YxiUypPVhz2UChhWgJHNQ0wDwVCJ7lQavahXOy52+U3pSASEmI9VgwZ7o6QXi8Lf1ooUkflNbQdxu4AX8wzLyNNbtgMKk1PNur2P0=
Received: by 10.142.251.9 with SMTP id y9mr1174398wfh.43.1204927299861;
        Fri, 07 Mar 2008 14:01:39 -0800 (PST)
Received: by 10.142.50.3 with HTTP; Fri, 7 Mar 2008 14:01:39 -0800 (PST)
Message-ID: <69e39a140803071401s619cf680m3197f3f5af12542@mail.gmail.com>
Date: Fri, 7 Mar 2008 17:01:39 -0500
From: "Ben Wade" <email @ gmail.com>
To: email @ fuse.net
Subject: test
MIME-Version: 1.0
Content-Type: multipart/alternative;
      boundary="----=_Part_10213_26192672.1204927299844"
X-Antivirus: avast! (VPS 080307-0, 03/07/2008), Inbound message
X-Antivirus-Status: Clean

I noticed this one says:
Received-SPF: pass (gwin1: domain gmail.com designates 209.85.200.173 as permitted sender)

How do I fix this?

"v=spf1 a mx ~all"

You are correct... so I just run that wizard and it will tell me what to put in its place?

Yes

hmm

allwebnow.com's IP address is 216.83.111.58 (sarc12a-216-83-111-58.sniparpa.net).
Does that server send mail from allwebnow.com?
I set it to no cuz it's really sending from 216.83.111.31?

This wizard found 2 names for the MX servers for allwebnow.com: allwebnow.com and sarc12a-216-83-111-58.sniparpa.net. (A single machine may go by more than one hostname. All of them are shown.)
MX servers receive mail for allwebnow.com.
Do they also send mail from allwebnow.com?
I set it to yes?

Do you want to just approve any host
whose name ends in allwebnow.com? (Expensive, unreliable and not recommended)      

I don't know what to set here.  If I set it to no I'm afraid much would be blocked.
 
Do any other servers send mail from allwebnow.com?
Is this where i put classic31.allwebnow.com?

You can describe them by giving "arguments" to the a:, mx:, ip4:, and ptr: mechanisms. mx: takes domain names and approves all the MX servers of these domains. To keep the wizard short we left out ptr:, but it works analogously.

I don't know what to put here.

IP networks can be entered using CIDR notation, eg. 192.0.2.0/24
Is this where i put 216.83.111.31

Could mail from allwebnow.com originate through
servers belonging to some other domain?
If you send mail through your ISP's servers, and the ISP has published an SPF record, name the ISP here.
Most of my shared clients cna use allwebnow.com so I don't know if I should put all their domain names in here.

Do the above lines describe all the hosts
that send mail from allwebnow.com?
I don't know.



I just put stuff in, does this look right?
"v=spf1 mx a:classic31.allwebnow.com mx:allwebnow.com ip4:216.83.111.31 include:omegap.com ?all"

I'm really worried about blocking many of my shared hosting clients if i put this in or mess with this.

>I'm really worried about blocking many of my shared hosting clients if i put this in or mess with this.

Whatever you put in there won't affect any clients unless they are using omegap.com's email address - you are setting this up in omegap.com's domain, so the only way the info can be referenced is by the recipient looking up omegap's details.  So I think you are ok.

>allwebnow.com's IP address is 216.83.111.58 (sarc12a-216-83-111-58.sniparpa.net).
Does that server send mail from allwebnow.com?
I set it to no cuz it's really sending from 216.83.111.31?

I am inclined to agree


>This wizard found 2 names for the MX servers for allwebnow.com: allwebnow.com and sarc12a-216-83-111-58.sniparpa.net. (A single machine may go by more than one hostname. All of them are shown.)
MX servers receive mail for allwebnow.com.
Do they also send mail from allwebnow.com?
I set it to yes?

Snip presumably backs up your email if it fails to find your mail server.  You can set this to No, but there's no harm leaving it at Yes - leave it as yes.

>Do you want to just approve any host
whose name ends in allwebnow.com? (Expensive, unreliable and not recommended)     I don't know what to set here.  If I set it to no I'm afraid much would be blocked.

My brain is about had it for today - I need to think about this one - I think it is ok to set it to No because you are not talking about fred@allwebnow.com, jim@allwebnow.com uncletomcobbley@allwebnow.com, you are being asked whether subdomain fred.allwebnow.com for instance, is going to be sending out mail.  (The answer I suspect I would hear from you, is No).

>You can describe them by giving "arguments" to the a:, mx:, ip4:, and ptr: mechanisms. mx: takes domain names and approves all the MX servers of these domains. To keep the wizard short we left out ptr:, but it works analogously.

I don't know what to put here.

IP networks can be entered using CIDR notation, eg. 192.0.2.0/24
Is this where i put 216.83.111.31

I think these can be left blank

>Could mail from allwebnow.com originate through
servers belonging to some other domain?
If you send mail through your ISP's servers, and the ISP has published an SPF record, name the ISP here.
Most of my shared clients cna use allwebnow.com so I don't know if I should put all their domain names in here.

This is not your client's emails - unless they use omegap.  This is for omegap only.  Do you ever send out email via your service provider?  If so you will need to include that in the wizard.

ok good news.

I sent a test with this string:
"v=spf1 mx a:classic31.allwebnow.com mx:allwebnow.com ?all"

and got this header:

Return-Path: <email @ allwebnow.com>
Received: from gwin4 ([216.68.8.214]) by dmta1.fuse.net
          (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP
          id <20080308053852.MFCZ2369.dmta1.fuse.net@gwin4>
          for <email @fuse.net>; Sat, 8 Mar 2008 00:38:52 -0500
Return-Path: <email @ allwebnow.com>
X-CBT-Local: fuse.net
X-CNFS-Analysis: v=1.0 c=1 a=n275RSSi7RcA:15 a=0RVjke6HtYMA:10 a=0aCI623mbnRtpNxB93W2qA==:17 a=0qykEaKHAAAA:8 a=NVLfDSTE3Umlio-Z70kA:9 a=AhrQGxENK1m26lhDBzYSd5oecgAA:4 a=ZAhoCFtSTOwA:10 a=RwiNt2JJ6zAA:10 a=LQJLfU0sVpAA:10 a=gJcimI5xSWUA:10 a=SSmOFEACAAAA:8 a=4ZEcvddvKz--V5iQBJYA:9 a=6ZdQCuBIG9a1C3WTm1IA:7 a=0Pt0W-_Zu6ZWw3ATipXFB6ktUcYA:4 a=37WNUvjkh6kA:10
X-CM-Score: 0
X-Scanned-by: Cloudmark Authority Engine
Authentication-Results: gwin4 smtp.mail=email @ allwebnow.com; spf=pass
Received-SPF: pass (gwin4: domain allwebnow.com designates 216.83.111.31 as permitted sender)
Received: from [216.83.111.31] ([216.83.111.31:58456] helo=classic31.allwebnow.com)
      by mx4.fuse.net (envelope-from <email @ allwebnow.com>)
      (ecelerity 2.2.1.28 r()) with ESMTP
      id DE/77-05345-C6622D74; Sat, 08 Mar 2008 00:38:52 -0500
Received: from ev-esr1-72-49-254-161.fuse.net ([72.49.254.161] helo=allwebnow)
      by classic31.allwebnow.com with esmtpa (Exim 4.68)
      (envelope-from <email @ allwebnow.com>)
      id 1JXrl7-0008PR-5j
      for email @fuse.net; Sat, 08 Mar 2008 00:38:13 -0500
Reply-To: <email @ allwebnow.com>
From: "Ben Wade" <email @ allwebnow.com>
To: <email @fuse.net>
Subject: test2
Date: Sat, 8 Mar 2008 00:38:04 -0500
Organization: All Web Now
Message-ID: <18DE556967904DE29C0DA03DD414BBE4@allwebnow>
MIME-Version: 1.0
Content-Type: multipart/alternative;
      boundary="----=_NextPart_000_001B_01C880B4.B317F720"
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
Thread-Index: AciA3pR8x6qhsThcTqCOm8JQhjw81Q==
X-AllWebNow-MailScanner-Information: Please contact the ISP for more information
X-MailScanner-ID: 1JXrl7-0008PR-5j
X-AllWebNow-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-AllWebNow-MailScanner-SpamCheck:
X-AllWebNow-MailScanner-From: email @ allwebnow.com
X-Spam-Status: No
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - classic31.allwebnow.com
X-AntiAbuse: Original Domain - fuse.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - allwebnow.com
X-Antivirus: avast! (VPS 080307-0, 03/07/2008), Inbound message
X-Antivirus-Status: Clean

---------

Now I set this in my txt entry for allwebnow.com only.  Do I set the same txt record for omegap.com, or will it be any different?  All of my clients use their own domain name as their send and receive mailserver settings in pop3.

To quote http://www.openspf.org/

Could mail from example.com originate through
servers belonging to some other domain?
If you send mail through your ISP's servers, and the ISP has published an SPF record, name the ISP here.

Presumably you can consider omegap's email as coming from an ISP that has published an SPF record.  Ok, omegap and the ISP may be one entity as far as you, and shared hardware are concerned, but the recipient cannot know that, so I feel that the allwebnow details should go in here.  Also, your clients should do the same with their SPF records too.

After all this investigating and troubleshooting, I found that cpanel had an update a week ago that I didn't know about.  Needless to say, I updated and I think many of these delayed email issues have been fixed from the update.  However, this spf record seems to have definetly enhanced the headers and make them look more legitimate like that of the "big guys" like gmail and hotmail.  Still I've read  alot of bad things about spf online.  So, I have omegap's dns txt record setup like this.. "v=spf1 mx a:classic31.allwebnow.com mx:omegap.com ?all".  I've tested it and I think this is correct.  However, if you think otherwise, let me know if those settings appear as though they could be problamatic to where my client could encounter any email issues that I would not be aware of?  

I haven't checked the record for accuracy - you know your circumstances better than I.  In general terms the only problem likely to arise is that someone has forgotten for example, that a website separate from your system is sending out emails using the omegap domain in the From field.  What would happen there is that the recipient, gmail let's say, looks at the from field (omegap.com), checks the omegap SPF record, finds it doesn't tally with the IP address that the email emanated from, then rejects it because it is not from a known source.

As far as your email server is concerned, I try to cover my backside by archiving sent and received emails and have logging of external transactions set to paranoia level, so that anyone coming to me saying "this message was not received at the other end" I can copy and print the relevant part of the SMTP handshaking, annotate it using less-technical jargon, and hand it to the enquirer, with the offer of working with the recipient's IT department to correct what is generally a mis-config at their end.  In an era where the goalposts move frequently you can't really do any better than this.