More info in Logs

piotrpawlowski

Hello,

Sometimes i recieve errors conected with sending mails via SMTP. Unfortunately in Systelm Logs I can find only info: SMTP Error, and my IP address.

Is it possible to have more information about this error? In example what kind of error, or to which e-mail OST was unable to send message?

Thank you for all information.

Piotr

PRedmond

The code you are looking for is almost certainly this (in include/class.email.php):

$alert=sprintf("Unable to email via %s:%d \n\n%s",$smtp,$smtp,$smtp);

Sys:(LOG_ALERT,'SMTP Error',$alert,false);

Perhaps changing it to

Sys:(LOG_ALERT,'SMTP Error',$alert . "\n " . $to,false);

may be more helpful? This SHOULD print out the email address which was supposed to receive the email.

I am not sure that it is possible to return the actual SMTP error - I don't even know for sure that such an error would be generated...

piotrpawlowski

Hello,

Thank you for this code. I have just implemented it in my OST. Hope it will help me in searching for a error.

But what is strange for me: in this code I can find info 'Unable to email via...' - where this error message will be displayed? I didn't see it in OST.

Thank you for help.

Piotr

piotrpawlowski

Hello,

This modification works great, but I still receive errors when I try send e-mail. I would try to verify where the error occurs. Is it possible to find out it?

Thank you.

Piotr

PRedmond

What is the error you get? The way I find errors is to look at where I THINK they are coming from, and put code like in:

db_query($sql) or die("Yep - this is it");

That way, if there is an error, you know EXACTLY where the errenous code is.

The other way I find the correct code is by searching for it. Most decent text editors (I use Crimson Editor, but there are heaps others) will allow you to search a directory for text - so you can search the entire osTicket directory for "Successfully Deleted", and you get a list of where this is. Then it is a matter of determining which code could be the culprit, and fixing the trouble. Only, it is often easier to find the code, than to make it work perfectly...! ;)