MonitorWare Knowledge Base

Hello, we are using Winsyslog 4.2 und i chose the option to let winsyslog send an email to my adress, when something happens.
But emails sent by winsyslog are not delivered.

I got an Mailserver, and this one works, because i tested it in outlook express, and it worked fine, emails were delivered.

relay auth is managed over the senders emailadress, so if the sender exists, no further auth is necessary.

this is the log file i get, when activating full logging and provocating some error:


StartupServices is processing service "Default Syslog Listener".
Create CInfoSourceSyslog Object
RegKey: SOFTWARE\Adiscon\WinSyslog\Services\IS1
CInfoSourceSyslog: Loading config!
Port: 514
New InfoSource started!
InfoSource 0x00aa4958 running.
Waking up worker thread.
CQueManList::WorkerThread() woke up.
CRuleList::ApplyRules() Check Filter Condition: Begin
Check Filter Condition: Conditions all OK, Filter fires!
CActionListEntry::CallAction, ID 1001
in CActionSendSyslog::doAction()
CSyslogClient::SetSyslogAddOrigSource: "10.87.70.10"
Target 127.0.0.1 - 0100007f set
out CActionSendSyslog::doAction()
CActionListEntry::CallAction, ID 1003
CActionListEntry::CallAction, ID 1008
CActionListEntry::CallAction, ID 1002
CWinSock::CWinSock(int af, int type, int protocol)
Error Message set: 'Invalid Hostname'
Error while applying an action - skipping this action. Error is 'Invalid Hostname'.
matching.
DELETEFIRSTENTRY: 00000000 - pTail
CQueManList::WorkerThread() woke up.
Waking up worker thread.
CQueManList::WorkerThread() woke up.
CRuleList::ApplyRules() Check Filter Condition: Begin
Check Filter Condition: Conditions all OK, Filter fires!
CActionListEntry::CallAction, ID 1001
in CActionSendSyslog::doAction()
CSyslogClient::SetSyslogAddOrigSource: "10.87.70.10"
Target 127.0.0.1 - 0100007f set
out CActionSendSyslog::doAction()
CActionListEntry::CallAction, ID 1003
CActionListEntry::CallAction, ID 1008
CActionListEntry::CallAction, ID 1002
CActionSendEmail: Send Message
CActionSendEmail: GetResponseStatus did not respond with Status 250
Error Message set: 'Error talking to smtp-server - END OF MAIL'
Error while applying an action - skipping this action. Error is 'Error talking to smtp-server - END OF MAIL'.
matching.
DELETEFIRSTENTRY: 00000000 - pTail
CQueManList::WorkerThread() woke up.
Waking up worker thread.
CQueManList::WorkerThread() woke up.
CRuleList::ApplyRules() Check Filter Condition: Begin
Check Filter Condition: Conditions all OK, Filter fires!
CActionListEntry::CallAction, ID 1001
in CActionSendSyslog::doAction()
CSyslogClient::SetSyslogAddOrigSource: "10.87.70.10"
Target 127.0.0.1 - 0100007f set
out CActionSendSyslog::doAction()
CActionListEntry::CallAction, ID 1003
CActionListEntry::CallAction, ID 1008
CActionListEntry::CallAction, ID 1002
CActionSendEmail: Send Message
CActionSendEmail: GetResponseStatus did not respond with Status 250
Error Message set: 'Error talking to smtp-server - END OF MAIL'
Error while applying an action - skipping this action. Error is 'Error talking to smtp-server - END OF MAIL'.
matching.
DELETEFIRSTENTRY: 00000000 - pTail
CQueManList::WorkerThread() woke up.
in stop loop, service id 0, pointer 0x00aa4910.
Waking up worker thread.
CQueManList::WorkerThread() woke up.
QueMan: Stop Message - Terminating...
DELETEFIRSTENTRY: 00000000 - pTail
Cancel thread 0x00aa3e50...
Worker Thread FINISHED!


has anyone an idea how to fix this? or are there questions i might answer to help in this case?

thanks in advance,

Alex

Alex,

many thanks for contacting Adiscon support.

I have reviewed the log and think I have noticed the one of the problem causes. Look, it says:

"Error while applying an action - skipping this action. Error is 'Invalid Hostname'. "

So it looks like the configured mail server is not a valid name or at least not DNS resolvable. I suggest that you check this.

Other than that, we have a second cause, which was fixed with the 4.2 SP1 version that went out right yesterday.

You can visit

http://www.winsyslog.com/odl.asp

to download the 4.2SP1 version. This version fixes an issue where mail can no longer be send after there was an error during session setup. You log reveals that this might also be a problem in your case.

I hope this answers your question. Please do not hesitate to contact us at any time if we can be of any further assistance.

Best regards,
Rainer Gerhards
Adiscon