I'd turn on mail tracing and see what comes out then. There is a document on diagnosic email issues located here :-
There might be a more up to date guide, so it's worth rummaging around. Generally from the point of turning on trace you can then usually fine the errant email and from there take a look to see if there is anything obvious. A query written against System/message recipients also helps to spot mails that have been sent or have errors. My money would be on a badly formed email signature unless all emails have stopped working.
That was actually an incorrect problem, it appears that we're having problems whereby an an email is sent to an account, this should then auto create a call and move it through to a specific call queue. Getting lots on Object Reference not set to an instance of an object errors
Any further ideas?
Same idea :-) Turn on tracing, specifically for inbound email and see what it reveals in the steps leading up to the attempt to log.
Appreicate the advice so far...I cant see how to turn on Mail Tracing in that document
Is this a quick and easy job?
On your application server, browse to the "Program Files/LANDesk/LANDesk Applications" folder. (Or Program Files (x86) if in 64-bit OS).
In here are a bunch of config files. If the problems are with inbound mail, then open up the Touchpaper.Service.Mail.Inbound.WindowsService.exe.config file (or the SystemTray one if that is how it is running).
Change "Error" to "Trace" in the following line:
<add key="Log Severity" value="Error" />
Save, and restart IIS and the inbound mail service. All inbound mail actions will appear in the Application Event Log. Don't run it this way for very long, as the log will fill up very quickly. Reverse the change to the config and restart the services again.
Ok, thanks for that log level help...It appears that the call is getting processed, however an I cant see an incident being created...In order the events go
Processing Inbox for server name xxxxxx.premierfoods.co.uk, user name Premier Alerts.
Connected to server named: xxxxxxx.premierfoods.co.uk with user name Premier Alerts
Connected to server named: xxxxxxxxx.premierfoods.co.uk with user name Premier Alerts
Creating New Process Alerts
Creating an instance of IncidentManagement.Incident with lifecycle NewProcess6 with template WiproAlert0 for user Joe Ciocci.
Processing mappings for business class IncidentManagement.Incident.
Successfully mapped mail field body to attribute Description with value
test call please delete
Successfully mapped mail field subject to attribute Title with value incident.
New process was created.
There are no further logs for inbound mail after this
From that I would say it was working. Strange. There is an entry in that same config file Paul mentioned called detailed logging. If that is turned to true and you continue to get no errors, I'd check the query you are using to make sure it isn't filtering out the very processes you are trying to find.