we’re using the sandbox tool “mail box cleaner” to delete dead mails from our two mail.boxes. This worked perfectly for some time, but since about 2 weeks it causes trouble.
The agent ist scheduled to run every 6 hours - what it does. But most of the time the agents fails:
11/29/2007 12:07:57 PM AMgr: Start executing agent ‘Mail Box Cleaner’ in ‘Mail Box Cleaner.nsf’ by Executive ‘2’
11/29/2007 12:07:57 PM AMgr: ‘Admin/Domain’ is the agent signer of agent ‘Mail Box Cleaner’ in ‘Mail Box Cleaner.nsf’
11/29/2007 12:07:57 PM AMgr: 'Agent ‘Mail Box Cleaner’ in ‘Mail Box Cleaner.nsf’ will run on behalf of ‘Admin/Domain’
11/29/2007 12:07:57 PM AMgr: Agent ‘Mail Box Cleaner’ in database ‘Mail Box Cleaner.nsf’ signed by ‘Admin/Domain’ is running in Full Administrator mode
11/29/2007 12:08:15 PM AMgr: Agent (‘Mail Box Cleaner’ in ‘Mail Box Cleaner.nsf’) error message: Notes error: Invalid or nonexistent document
I’ve already recreated the mail.boxes what did not solve the problem.
Why are you getting dead mail in your mail.box? You should change the Configuration document so that you don’t get dead mails.
Configuration document,
Router/SMTP tab,
Restrictions and Controls tab,
SMTP Inbound Controls tab,
Inbound Intended Recipients Controls section,
Verify that local domain recipients exist in the Domino Directory field: Set to enabled.
Dead mail is normally mail accepted by the Domin SMTP server, addressed to users in the local domain that doesn’t exist, sent by external users that doesn’t exist. Domino should reject these at the protocol level as Chris Linfoot ( http://chris-linfoot.net/ ) says.
The affected server is our external mail gateway and also used as relay server for some of our customers (who of course are not listed in our directory).
Most of the dead mails are spam mails from faked sender adresses to non-existant users in our (or our customer’s) directory which can’t neither be delivered to a recipient nor be returned to the sender.
You will need some way of identifying your customers, and their IP address is one choice. Then you can setup exceptions to the anti-relay rules in the configuration document.
