|
|
|
|
|
|
|
|
Applies To: Models 1000, 2000, 3000
A mail queue that is rapidly increasing in the amount of messages can be related to one of the following reasons:
Problem: Mail looping, duplicate entries exist in Default Mail Relay and Mail Routing
Solution: Remove the entry listed in Default Mail Relay and leave blank
Problem: Mail looping, Accepting mail for a domain and the Mail Route specified in ePrism points to an MX record that points back to ePrism. This can happen when there are a large number of domain names for the company.
Problem:Internal mail servers exposed on the Internet (Port 25) set to deliver to a smart host (ePrism) and ePrism is set to route mail to the internal mail server
Solution: Disable access to the internal mail server
Internal mail server fails to respond on Port 25 and ePrism queues the messages, due to server maintenance or capacity issues
Firewalls must have Port 25 open for ePrism to accept AND send e-mail. Check the Mail Transport logs for 'Connection Refused'
Internal mail server is configured to accept a limited amount of SMTP connections
Internal mail server forwarding mail to ePrism must be able to resolve the hostname or NETBIOS name for ePrism
DNS, external or internal, is not available and/or configured improperly. i.e. hostname points to two A records, however only one A record responds. Verify using Host Name Lookups in Status & Utility for ePrism
A mail queue that sometimes increases and decreases in the amount of messages, but generally fluctuates around a specific number can be related to one of the following reasons:
Network Interface Settings are set correctly to full duplex, half duplex or auto-negotiate
MTU settings are set to 576 by default on ePrism. This is a rare occurrence and should only be considered as a last option
Remote mail server times out due to RFC1644. Contact Technical Support for assistance
An increase in mailer-daemon messages caused by messages designated to unknown recipients with forged, non-existent return addresses. ePrism can be configured to automatically remove these messages on an hourly basis in Delivery Settings under Mail Delivery. Deleting mailer-daemon messages does not affect normal undeliverable mail.
Accepting mail for non-existent domain names where Internal servers have not been configured to handle
Internal mail server is configured to send all messages with unresolved recipients back to ePrism
Mail server configured as an open relay available on the Internet and sending mail to a smart host (ePrism)
