PureMessage for UNIX: how to troubleshoot a “socket_map_lookup(pmxbl)” error in the system maillog
How to troubleshoot a "socket_map_lookup(pmxbl)" error in the system maillog for PureMessage for Unix, version 5.2.1 and higher.
You may find the following errors in the system maillog and PureMessage pmx_log.
From the system maillog:
<time stamp> mail sendmail[<pid>]: <message id>: SYSERR(root): socket_map_lookup(pmxbl): failed to read length parameter of reply
From the PureMessage pmx_log:
0 <time stamp> [<pid>,pmx-blockerd] Error reading from MTA: Connection timed out
What to do
- Verify whether, or not, the
FEATURE(`delay_checks')feature is used in the sendmail configuration file. Check the /opt/pmx/sendmail/etc/mail/sendmail.mc file if using PureMessage-Sendmail. - If so, remove this feature, because this is an unsupported feature that we do not ship with PureMessage-Sendmail.
- Restart sendmail afterwards.
If you would like to allow certain senders and/or recipients, before blocking messages based on relay IP addresses, then you should implement the 'Message is from blocked IP' test in your policy.
If the FEATURE(`delay_checks') feature is not used, then please contact Technical Support by sending a Support Request. We may ask you for your sendmail configuration file and your system maillog to troubleshoot further.
If you need more information or guidance, then please contact technical support.
- Article ID: 26856
- Created: 28 Jun 2007
- Last updated: 6 Oct 2008
