cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1236
Views
0
Helpful
3
Replies

ESA SMTP Call-Ahead logs

llomjaria
Level 1
Level 1

Hello,

Can you please tell where can I find logs for SMTP Call-Ahead?

Thanks

1 Accepted Solution

Accepted Solutions

UdupiKrishna
Cisco Employee
Cisco Employee

SMTP Call-ahead is not a separate log or subscription thats available. By default mail logs will generate lines when SMTP call ahead fails, however if you would like more detailed information, you can change the logging level of mail_logs to debug and whenever ESA initiates a SMTP call ahead request, information will be logged.

Though I would recommend not to keep the logging level at debug all the time.

View solution in original post

3 Replies 3

srigovi2
Cisco Employee
Cisco Employee

Hi llomjaria ,

 

To view the SMTP Call Ahead logs on your ESA, you can follow these steps:


1. Log in to your ESA using SSH or console access.
2. Enter the following command to enable the SMTP Call Ahead logs:
esa(config)# logging mail call-ahead`

3. Enter the following command to view the logs:
esa# show logging mail call-ahead`


This will display the SMTP Call Ahead logs on your ESA. If you want to save the logs to a file, you can use the following command:
esa# show logging mail call-ahead > call-ahead.log`

This will save the logs to a file named "call-ahead.log" in the root directory of your ESA. I hope this will help you .

 

Thanks ,

G.Srinivasan

 

Hi G.Srinivasan,

Thanks for the reply!

When I log in into ESA using SSH I do not have "esa(config)#" this prompt and the command is rejected: Unknown command or missing feature key: logging

 

UdupiKrishna
Cisco Employee
Cisco Employee

SMTP Call-ahead is not a separate log or subscription thats available. By default mail logs will generate lines when SMTP call ahead fails, however if you would like more detailed information, you can change the logging level of mail_logs to debug and whenever ESA initiates a SMTP call ahead request, information will be logged.

Though I would recommend not to keep the logging level at debug all the time.