Page 2 of 2
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 11:14 am
by benningtonr
I only have two black list servers entered, same ones i have in my barracuda spam filter
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 11:55 am
by scottwilkerson
benningtonr wrote:Exchange 2007 Blacklist Status Critical 1h 22m 58s 5/5 2012-05-23 16:08:05 (null)
Exchange Core Services Critical 1h 22m 25s 5/5 2012-05-23 16:07:58 MSExchangeADTopology: Started - MSExchangeAntispamUpdate: Started - MSExchangeEdgeSync: Started - MSExchangeFDS: Started - MSExchangeImap4: Started - MSExchangeIS: Started - MSExchangeMailboxAssistants: Started - MSExchangeMailSubmission: Started - MSExch
My guess is that there are core services in the list that aren't started, can you run the following from the command line
Code: Select all
cd /usr/local/nagios/libexec
./check_nt -H <EXCHANGE_SERVER_IP> -s "<NSCLIENT_PASSWORD>" -p 12489 -v SERVICESTATE -d SHOWALL -l MSExchangeADTopology,MSExchangeAntispamUpdate,MSExchangeEdgeSync,MSExchangeFDS,MSExchangeImap4,MSExchangeIS,MSExchangeMailboxAssistants,MSExchangeMailSubmission,MSExchangeMonangePop3,MSExchangeRepl,MSExchangeSA,MSExchangeSearch,MSExchangeServiceHost,MSExchangeTransport,MSExchangeTransportLogSearch,msftesql-Exchange
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:09 pm
by benningtonr
MSExchangeMonangePop3: Not found
only one not started
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:12 pm
by scottwilkerson
That will do it, if you don't have that service, you can remove it from the list in
Configure -> Core config manager -> Services -> Core Exchange -> Modify
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:15 pm
by benningtonr
I took it out of the configured checks string.
Trying to fix the black list now, any ideas?
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:24 pm
by scottwilkerson
Testing that would be similar, run
Code: Select all
cd /usr/local/nagios/libexec
./check_bl -H <EXCHANGE_SERVER_IP> -B rbl.server.com rbl.server2.com
If you get an error about Can't locate Net/DNS.pm run
then try again
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:27 pm
by benningtonr
I ran this, on a pre-built vm
yum install perl-Net-DNS.i686
got the green check now, can you send me the complete list of BL's so i can re-enter then, I took all of them but two out
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:35 pm
by scottwilkerson
Code: Select all
zen.spamhaus.org bl.spamcop.net dnsbl.ahbl.org dnsbl.njabl.org dnsbl.sorbs.net virbl.dnsbl.bit.nl rbl.efnet.org phishing.rbl.msrbl.net 0spam.fusionzero.com list.dsbl.org multihop.dsbl.org unconfirmed.dsbl.org will-spam-for-food.eu.org blacklist.spambag.org blackholes.brainerd.net blackholes.uceb.org spamsources.dnsbl.info map.spam-rbl.com ns1.unsubscore.com psbl.surriel.com l2.spews.dnsbl.sorbs.net bl.csma.biz sbl.csma.biz dynablock.njabl.org no-more-funn.moensted.dk ubl.unsubscore.com dnsbl-1.uceprotect.net dnsbl-2.uceprotect.net dnsbl-3.uceprotect.net spamguard.leadmon.net opm.blitzed.org bl.spamcannibal.org rbl.schulte.org dnsbl.ahbl.org virbl.dnsbl.bit.nl combined.rbl.msrbl.net
Re: Exchange issues, might be with client
Posted: Wed May 23, 2012 12:39 pm
by benningtonr
awsome,
I now have the complete list and it is working great.
Many thanks