Oracle exchange messaging MTA troubleshooting
Oracle messaging exchange MTA troubleshooting:
* The approach to troubleshooting MTA issues is to track the message in mail.log_current file, enable debugging for the problematic channel (will require MTA restart) and stop/start channels to hold message in queue or view the messages already queued. Debug channel log file records the full SMTP dialogue/handshake.
* Enable message ID in logs by adding 'LOG_MESSAGE_ID=1' in option.dat file
* Channels can be manually run by job controller by running the command :
imsimta submit channel
e.g imsimta submit tcp_local
Channel logging can be enabled by adding slave_debug and master_debug channel options in imta.cnf file.
* Channels can be stopped and started to trap a message in channel queues. Messages are queued to the next channel queue directory.
* SMTP server processes are started by dispatcher. Max simultaneous connection limit is equal to MAX_PROCS * MAX_CONNS settings in dispatcher configuration file. Dispatcher should be able to create a hidden socket file in /tmp directory for successful startup.
* Looping messages are held as .HELD files.
* Postmaster address must be present on an MTA system. Message loops are detected through RECEIVED header lines in message headers. Removal of RECEIVED headers can cause failure in loop detection. Loop detection are caused by server not recognising its variant name or user forwarding error etc. Messaging software should correctly handle notification emails by adding empty envelope From: address. Message can be held due to user or domain status of hold
* SMTP protocol only supports ASCII 7-bit characters. 8-bit characters must be encoded
* Test user sieve filter with command, imsimta test -rewrite -debug -filter user@domain. Filter errors can result in message delivery failure to a particular recipient.
* Job controller is in-memory database.
* MTA makes up of job controller (which run channel jobs) and dispatcher (which creates and manages smtp server processes).
* imsimta cnbuild compiles configuration into an image.
Useful commands:
imsimta process To verify MTA processes including dispatcher and job controller
imsimta submit To manually run a channel through job controller
imsimta qm stop/start channel To start or stop a channel
imsimta cache -view To view queue cache used by job controller
imsimta cache -sync To force synchronisation of in-memory cache with on disk queues
imsimta test -rewrite To validate MTA configuration without sending emails
* The approach to troubleshooting MTA issues is to track the message in mail.log_current file, enable debugging for the problematic channel (will require MTA restart) and stop/start channels to hold message in queue or view the messages already queued. Debug channel log file records the full SMTP dialogue/handshake.
* Enable message ID in logs by adding 'LOG_MESSAGE_ID=1' in option.dat file
* Channels can be manually run by job controller by running the command :
imsimta submit channel
e.g imsimta submit tcp_local
Channel logging can be enabled by adding slave_debug and master_debug channel options in imta.cnf file.
* Channels can be stopped and started to trap a message in channel queues. Messages are queued to the next channel queue directory.
* SMTP server processes are started by dispatcher. Max simultaneous connection limit is equal to MAX_PROCS * MAX_CONNS settings in dispatcher configuration file. Dispatcher should be able to create a hidden socket file in /tmp directory for successful startup.
* Looping messages are held as .HELD files.
* Postmaster address must be present on an MTA system. Message loops are detected through RECEIVED header lines in message headers. Removal of RECEIVED headers can cause failure in loop detection. Loop detection are caused by server not recognising its variant name or user forwarding error etc. Messaging software should correctly handle notification emails by adding empty envelope From: address. Message can be held due to user or domain status of hold
* SMTP protocol only supports ASCII 7-bit characters. 8-bit characters must be encoded
* Test user sieve filter with command, imsimta test -rewrite -debug -filter user@domain. Filter errors can result in message delivery failure to a particular recipient.
* Job controller is in-memory database.
* MTA makes up of job controller (which run channel jobs) and dispatcher (which creates and manages smtp server processes).
* imsimta cnbuild compiles configuration into an image.
Useful commands:
imsimta process To verify MTA processes including dispatcher and job controller
imsimta submit To manually run a channel through job controller
imsimta qm stop/start channel To start or stop a channel
imsimta cache -view To view queue cache used by job controller
imsimta cache -sync To force synchronisation of in-memory cache with on disk queues
imsimta test -rewrite To validate MTA configuration without sending emails
posted by Usman Wahid at
5:28 PM
0 Comments:
Post a Comment
<< Home