[reposted from the Pegasus support forum, in the hope of targetting more system managers]
On his 8th August posting (on his own website) 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 to his INI-file sample, this sample does not currently 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.
<DIV>[reposted from the Pegasus support forum, in the hope of targetting more system managers]&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>On his 8th August posting (on his own website) 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&nbsp;to his INI-file sample, this sample does not currently 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.</DIV>