Hello Exchange Experts,
We have noticed a decline in the speed that e-mails are being delivered out of our exchange server lately.
Sometimes up to 4 - 5 hours later to known good e-mail addresses that we use daily.
We have also had bounce backs from @yahoo.com e-mail addresses as well. (these come and go sometimes they work and sometimes they don't)
Each morning I "pause" the Virtual SMTP port on the Server for about 1 hour to purge the Delivery Queue.
Trying to free up some Server resources ( Dual 2.3 Ghz CPU's / 8GB Memory / RAID 5 with approx 45 GB HDD free space)
I have scanned the questions on these boards and have found similar issues but no absolute resolutions.
My situation is a single Exchange 2000 SP3 in a medium size company.
I have verified that RDNS is configured through DNSReports with the following issues on the "mail" tab from DNSReports
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.
mail.premiumware.com claims to be non-existent host exchange.TPE.PREMIUMWARE.C
OM: <br /> 220 exchange.TPE.PREMIUMWARE.C
OM Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at Mon, 4 Aug 2008 14:33:03 -0500 <br />
PASS Acceptance of NULL <> sender OK: All of your mailservers accept mail from "<>". You are required (RFC1123 5.2.9) to receive this type of mail (which includes reject/bounce messages and return receipts).
PASS Open relay test OK: All of your mailservers appear to be closed to relaying. This is not a thorough check, you can get a thorough one here.
PASS Acceptance of postmaster address OK: All of your mailservers accept mail to email@example.com
(as required by RFC822 6.3, RFC1123 5.2.7, and RFC2821 4.5.1).
PASS Acceptance of abuse address OK: All of your mailservers accept mail to firstname.lastname@example.org.
mail.premiumware.com OK: 550 5.7.1 Unable to relay for Not.abuse.see.www.DNSreport.com.from.IP.18.104.22.168@DNSreport.com
WARN SPF record Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
I have since setup the SPF record on our DNS Server.
Still e-mails are slow to be delivered we have also been experiencing some delays to the inetrnet connections across our network as well.
We use McAfee Groupshield on the Exchange Server and McAfee Virus Scan on the workstations and all are updated automatically and have current DATS and Engines installed.
Need more expertise / help to track this issue down before it starts to affect out client relationships.
Thanks in advance for your time and attention,