[ExchangeList] User does not exist!
- From: <ChongJa@xxxxxxxxxxxxxxxx>
- To: <exchangelist@xxxxxxxxxxxxx>
- Date: Wed, 22 Mar 2006 10:06:02 -0500
Getting event id 9646. I'm not so much as interested in the event, but
the user it talks about (user37534619) does not exist, and cannot find
him anywhere! This event for this particular user started last Saturday
and has repeated every 30mins. I went through every store on the
particular ex server, do not see this mailbox, searched through AD, LDAP
queries etc.
Mapi session "/O=American Red
Cross/OU=ARCHQ/cn=Recipients/cn=user37534619" exceeded the maximum of
250 objects of type "objtMessage".
________________________________
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Mulholland
Sent: Tuesday, March 21, 2006 5:52 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Blacklisting
It is possible for two mx servers (bad choice of words) mail servers to
be blacklisted on separate grounds in separate physical locations given
the type of mail they might be routing or infected with.
Michael reminded me about SURLB's which may cause an issue but i have
rarely seen it happen.
Greg Mulholland
________________________________
From: exchangelist-bounce@xxxxxxxxxxxxx on behalf of
ChongJa@xxxxxxxxxxxxxxxx
Sent: Wed 22/03/2006 8:05 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Blacklisting
So if this is the case, it is possible for subdomainA to be blacklisted
due to subdomainB's actions?
________________________________
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Mulholland
Sent: Tuesday, March 21, 2006 3:51 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Blacklisting
Greg is right! generally a blacklist service will black list a bank of
ip's depending on how tight they are. Having said that if these MX
servers were setup in mesh topology for backup then it is entirely
possible that the same mails which bounce around MX1 may bounce around
MX2 thus causing the same problem.
Greg
________________________________
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Greg Lara
Sent: Wednesday, March 22, 2006 6:32 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Blacklisting
It's always been my impression that a domain is blacklisted based on
it's IP address. So if west.company.com has an independent MX record,
from a DNS standpoint there would be no association with
east.company.com and therefore no reason for the east domain to be
blacklisted.
Greg Lara
________________________________
From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of
ChongJa@xxxxxxxxxxxxxxxx
Sent: Tuesday, March 21, 2006 2:22 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Blacklisting
Let's say you are east.company.com and you also host MX records for
west.company.com and so forth. If west.company.com was compromised and
get blacklisted, can they potentially get the root domain company.com
blacklisted? I'm thinking each domain is autonomous and only the
individual domains would get blacklisted and not the entire root.
Anybody know for certain? Thanks.
James Chong
ETS Sr. Exchange Engineer
Office: 703.206.7548
Cell: 703.863.1483
chongja@xxxxxxxxxxxxxxxx
Other related posts:
