Thanks Michael, I will do just that - I guess system managers check the Mercury support forum more frequently than the Pegasus one. I was wearing my blinkers and thinking it was just a Pegasus issue.
On his 8th August posting about Pegasus 4.62, Han suggested that David has added control switches to the PEGASUS.INI file as well as (instead of?) the registry switches, in order to manage attachments and message size issues. This is a "Good Idea", because adding registry keys at the user-level can be fiddly for managers of large networks. However, although Han points us at his INI-file sample, this sample does not show any details of the [Limits] section. I could ask Han, but it might be just as quick to ask the community to confirm this and see if anyone is using it successfully yet. I want to nail down the details before I contemplate deploying 4.62.
[quote user="Rammie"]On his 8th August posting about Pegasus 4.62, Han suggested that David has added control switches to the PEGASUS.INI file as well as (instead of?) the registry switches, in order to manage attachments and message size issues. This is a "Good Idea", because adding registry keys at the user-level can be fiddly for managers of large networks. However, although Han points us at his INI-file sample, this sample does not show any details of the [Limits] section. I could ask Han, but it might be just as quick to ask the community to confirm this and see if anyone is using it successfully yet. I want to nail down the details before I contemplate deploying 4.62.[/quote] Doing a simple "limits" search reveals the following thread, e.g.. It might also be a better idea to post your question to the Mercury support forum.
Michael -- IERenderer's Homepage PGP Key ID (RSA 2048): 0xC45D831B S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
