If the entire DRAC system is not working correctly, it's possible to test each of the components separately to determine which one is at fault.
If you are using a recent version of the Berkeley db package, you can use the db_dump command to look at the authorization map, something like this:
$ db_dump -p /etc/mail/dracd.db format=print type=btree bt_minkey=2 db_pagesize=512 HEADER=END 188.8.131.52 921984419 184.108.40.206 220.127.116.11 921983897 18.104.22.168 921984520 $
This utility doesn't exist with db version 1.85, but you can at least use sendmail to look up entries in the map:
$ /usr/lib/sendmail -bt ADDRESS TEST MODE (ruleset 3 NOT automatically invoked) Enter [ruleset] [address] ] /map drac 22.214.171.124 map_lookup: drac (126.96.36.199) returns 921984419 (0) ]
You can use the testing utility included with DRAC to add entries to the authorization map, like this:
$ ./testing localhost 188.8.131.52 $
An entry for 184.108.40.206 should then appear in the authorization map, and remain there until the daemon expires it. If your POP/IMAP servers are on a different host, you should run the testing utility there. In this case, your dracd.allow file must be set up to allow updates from that host.
To test relay authorization and rejection in sendmail, you need to simulate the conditions that would exist for specific SMTP peers and destination addresses and see how sendmail reacts to them. Claus A▀mann has already set up a nice set of instructions for this at his Debugging Web Page.
If everything else tests out correctly, but authorization requests from your POP/IMAP server are not appearing in the authorization map, then something must be wrong with the way you modified your POP/IMAP server. Check the server's error logs for details.