Re: strange email queue issue
- From: mtupker <mtupker@xxxxxxxxx>
- Date: Tue, 4 Nov 2008 15:50:56 -0800 (PST)
On Nov 4, 3:20 pm, Jamestechman <jamestech...@xxxxxxxxx> wrote:
1. When it's in a retry state; what is the reason in the queue viewer?
Are you able to manually telnet to the domain and email to the user?
If not what is the error?
2. Are you up to date on your windows patches? Particular the July DNS
vulnerability patches and the recent out of band security patches? If
not run microsoft update.
3. Your barracuda is that hosted or that is your own MTA? You mean
this has a recipient limitation of 600 users?
James Chong (MVP)
MCITP | EMA; MCSE | M+, S+,
Security+, Project+, ITIL
msexchangetips.blogspot.com
On Nov 4, 3:53 pm, mtupker <mtup...@xxxxxxxxx> wrote:
We have a single exchange 2003 sp2 server for email. We are using the
SMTP option "Use dns to route to each address space on this
connector," for outgoing email.
The problem is we are getting a bottlekneck in some of the smtp
connector queues because of messages in a retry state.
We also have a barracuda spam firewall 300 that can be used as an
outgoing relay. When we use the barracuda in this fasion email is sent
almost immediately. That leads me to believe that there is something
wrong with the way exchange is doing dns lookups for outbound email.
However I'm not sure how to fix this.
We found out about a recipient relay restriction of 600 users on the
barracuda so we cannot use it as an outbound relay.
Anyone have any thoughts on this? Thanks.- Hide quoted text -
- Show quoted text -
There are a more than a few domains this is happening with. Some
emails go through right away and others sit in the retry state. (the
retry emails seems to be stopping processing of other email in the
queue.) The domain that is causing us the most issues is a google apps
domain. I did the nslookup on the mx records and got:
mustangs.mtmercy.edu MX preference = 10, mail exchanger =
aspmx4.googlemail.c
om
mustangs.mtmercy.edu MX preference = 10, mail exchanger =
aspmx3.googlemail.c
om
mustangs.mtmercy.edu MX preference = 10, mail exchanger =
aspmx2.googlemail.c
om
mustangs.mtmercy.edu MX preference = 5, mail exchanger =
alt2.aspmx.l.google.
com
mustangs.mtmercy.edu MX preference = 5, mail exchanger =
alt1.aspmx.l.google.
com
mustangs.mtmercy.edu MX preference = 1, mail exchanger =
aspmx.l.google.com
mustangs.mtmercy.edu MX preference = 10, mail exchanger =
aspmx5.googlemail.c
om
aspmx4.googlemail.com internet address = 66.249.93.27
aspmx5.googlemail.com internet address = 74.125.45.27
1. The additional information area in the queue viewer just says no
additional information avaliable. It always says that for all queues.
That may be another issue that I need to look into. Also I should have
been more specific. The queue isn't in a retry state some of the
emails in the queue are in retry. The queue itself never leaves an
active state. It's probably the same thing but I just thought I should
be a little more specific.
2. I recently installed the latest patches last week actually. :)
3. The barracuda was our MTA until we found out about the 600
recipient limit. Right now only email coming into the campus goes
through the barracuda. It can and was acting as an outbound mta
though. When we use it as such email flows as it should.
I tried a telnet session on port 25 to the two ip addresses returned
by the nslookup above and was greeted by the google email servers.
However if I telnet mustangs.mtmercy.edu 25 from the exchange server I
get an connection failed error. Hmmm. It appears that telnet to port
25 works for other domains and the domain does have a valid MX record.
However there is no A or CNAME dns entry for the domain
mustangs.mtmercy.edu on our internal dns servers which is why the
telnet test is failing.
.
- References:
- strange email queue issue
- From: mtupker
- Re: strange email queue issue
- From: Jamestechman
- strange email queue issue
- Prev by Date: Re: Moving Mailbox to another Storage Group
- Next by Date: Database dismounted without eventid 9689 on exchange 2003 sp2
- Previous by thread: Re: strange email queue issue
- Next by thread: Database dismounted without eventid 9689 on exchange 2003 sp2
- Index(es):
Relevant Pages
|