I sent this in a reply to the latest beta announcement, but it probably should be its own thread. Original message follows:
This may be late, but here are some issues I have with the beta and with our expected improvements in the product.
First, the push-pins are no longer in the interface. We use these to keep the Proxy Content Manager available on the first page since we are always going directly to that. Can these be put back in? Why do we always access the PCM, you may ask? It because of issues with the SMTP proxy.
1) SMTP proxy doesn't allow exim configuration on when frozen messages are removed, etc. Every day or so we have around 10K messages in the frozen state, and we have yet to reach the default of 7 days to see if the stmp proxy ever removes undeliverable messages/bounces/etc. We are always forced to delete regularly throughout the day to have a usuable interface to inspect messages. This leads to 2...
2) We need to inspect messages since virus quarantine places all such messages in the SMTP_ERR queue with all other frozen messages. Its not reasonable to search for viruses in such a queue to see if we need to forward/reject. We cannot reject off hand since on many occassions a virus reject from one client serviced by ASL caused a loop when it was sent to another client under the protection of the same ASL server. Load would spike heavily on the machine for quite some time and we need to switch back to quarantine to solve the problem
The real answer is to have a new target for anti-virus smtp proxying. That would be to strip the virus and still forward the message. Right now, pass is not useful since the virus stays intact in the message. Preferably, a special reject message should be sent with the original headers to the to: and from: headers so that both sides are aware of the original message containing a virus. Maintaining the virus in the message serves neither party in practical use, as most of these messages are caught or looped back again and again without the parties being aware of it.
