efa-project.org

That makes sense but still doesn’t account for the mtalog filling again after being emptied. It’s like the mails are spoiled and keep retrying.

When Exchange rejects the message, eFa should defer the message maybe make a few retries (based on postfix settings), and then fire an undeliverable. Perhaps the defaults are too much for your setup?

What is your postfix configuration for the following?

postconf -d minimal_backoff_time
postconf -d maximal_backoff_time
postconf -d maximal_queue_lifetime
postconf -d bounce_queue_lifetime

Also, have you tried enabling recipient address verification? This would cause eFa to also reject a message when Exchange doesn't have a valid recipient.

http://www.postfix.org/ADDRESS_VERIFICA ... #recipient

shawniverson wrote: ↑21 Oct 2017 11:52 When Exchange rejects the message, eFa should defer the message maybe make a few retries (based on postfix settings), and then fire an undeliverable. Perhaps the defaults are too much for your setup?

What is your postfix configuration for the following?

postconf -d minimal_backoff_time
postconf -d maximal_backoff_time
postconf -d maximal_queue_lifetime
postconf -d bounce_queue_lifetime

Also, have you tried enabling recipient address verification? This would cause eFa to also reject a message when Exchange doesn't have a valid recipient.

http://www.postfix.org/ADDRESS_VERIFICA ... #recipient

Thanks for the reply.
I already have invalid recipients rejection enabled.

I check the values and got:
postconf -d minimal_backoff_time - 300 s
postconf -d maximal_backoff_time - 4000 s
postconf -d maximal_queue_lifetime - 5d
postconf -d bounce_queue_lifetime - 5d

Since yesterday morning there are another 263336 more entries in mtalog dating from 16/10 so I guess that these should start to reduce now they are over the 5 day limit.

Can you think of anything else that could be affecting the SPAM reporting speed? At the moment it is taking me
273 Seconds
4 Refreshes
to submit a message.

Thanks again

Solved -

Gained remote access via the creator of the post
Reviewed the logs
Updated some MailWatch links to reflect proper ports
Executed DB repair
User modified NAT policy as well

Upon the completion of the above, spam submission takes aprox 15 seconds now.

Logs were pointing to a issue with the DB and congestion and approaching httpd timeouts

Thanks for all your help.