[quote user="Greenman"]I don't want to 'test' this as I don't want to break anything. I don't want to risk importing a registry key and something unexpected happening - for example, I don't know if there are other registry entries that Pegasus Mail writes/references to support the generation of the alerts. Some programs hang when entries are missing.[/quote]

Rest assured that HKEY_CURRENT_USER\Software\Pegasus Mail is the only place Pegasus Mail writes its values to, and these are not required for Pegasus Mail to run properly: In fact it recreates them whenever it's relaunched or changes any of them (like the global identity or the user name - in previous versions). They are mainly used for installation purposes and extensions which cannot access any of these data via the internal interface (BearHtml being one of these to date, but this is about to change since David Harris just extended the renderer interface for providing this information: It affects caching of remote image files. IERenderer works around this limitation thanks to my long-standing experiences with doing so in my encryption extensions). Pegasus Mail still keeps its settings in INI-files despite of Microsoft's long-standing recommendations ...

Hi, Folks

I recently installed 4.61 on our network. I have a single installation of Pegasus Mail on a Windows 2008 64bit Storage Server and the clients access their mail (on the same server), via a desktop link to the winpm-32.exe program file.

After installing 4.61 I was very pleased to read about Limits.exe that imposes soft/hard limits on the size of messages/attachments. Although I have set this (15MB soft and 19MB hard for attachments), hard limits are not imposed, nor are alerts displayed for soft limits. I attached a 25MB file to a message and nothing happened.

Does limits only work when the installation is local? Or, am I doing something wrong?

Thanks.

[quote user="Greenman"]Does limits only work when the installation is local? Or, am I doing something wrong?[/quote]

According to the What's new section of Pegasus Mail's online help it works by creating Registry entries which most probably implies that it'll only work if limits.exe has been executed locally.

Thanks, Michael

The next question, of course, is what these settings are and which parts of the registry need to be edited. I can then use Group Policy Preferences to make the registry changes on all the computers in the domain. I would prefer to do it this way rather than using Mercury to set size limits because the user would be notified immediately. If a user is in a hurry, sends a LaRgE message and then quits Pegasus Mail, they will not know the message has exceeded the size limit until later. And that, of course, may be too late.

Cheers!

[quote user="Greenman"]The next question, of course, is what these settings are and which parts of the registry need to be edited.[/quote]

I don't know, but you can easily figure out by using limits.exe on your local machine and checking the modifications below HKEY_CURRENT_USER\Software\Pegasus Mail (I assume it doesn't use HKLM since limits.exe doesn't request admin rights according to the look of its icon on Windows 7).

Thank you.

I ran this command on the server this morning, and have just checked the registry keys you suggested but cannot see anything at all that might relate to this. In fact, the registry keys are rather sparse(which, I suppose, may be why Pegasus Mail crashes/migrations are so easy to deal with on Windows systems).

Cheers!

[quote user="Greenman"]In fact, the registry keys are rather sparse(which, I suppose, may be why Pegasus Mail crashes/migrations are so easy to deal with on Windows systems).[/quote]

... and maybe fail so easily as well: Pegasus Mail's Registry keys are only (re)created on the machine which Pegasus Mail actually runs on, on the server they are more or less useless anyway when running multiple instances based on it.

Haha - anyway - I searched the registry (which I should have done in the first place...) and there they were.

[HKEY_CURRENT_USER\Software\Pegasus Mail]
"MsgSizeSoftLimit"="0"
"MsgSizeHardLimit"="20971520"
"AttmtSizeSoftLimit"="15728640"
"AttmtSizeHardLimit"="19922944"

[HKEY_CLASSES_ROOT\Software\Pegasus Mail]
"MsgSizeSoftLimit"="0"
"MsgSizeHardLimit"="20971520"
"AttmtSizeSoftLimit"="15728640"
"AttmtSizeHardLimit"="19922944"

 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SOFTWARE\Pegasus Mail]
"MsgSizeSoftLimit"="0"
"MsgSizeHardLimit"="20971520"
"AttmtSizeSoftLimit"="15728640"
"AttmtSizeHardLimit"="19922944"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\SOFTWARE\Pegasus Mail]
"MsgSizeSoftLimit"="0"
"MsgSizeHardLimit"="20971520"
"AttmtSizeSoftLimit"="15728640"
"AttmtSizeHardLimit"="19922944"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\SOFTWARE\Pegasus Mail]
"MsgSizeSoftLimit"="0"
"MsgSizeHardLimit"="20971520"
"AttmtSizeSoftLimit"="15728640"
"AttmtSizeHardLimit"="19922944"

[HKEY_USERS\{Administrator}-500\Software\Pegasus Mail]
"MsgSizeSoftLimit"="0"
"MsgSizeHardLimit"="20971520"
"AttmtSizeSoftLimit"="15728640"
"AttmtSizeHardLimit"="19922944"

It's the last one that bothers me - rather than using group policy preferences (I'd have to use the SID's for each user?), can limits.exe be run as a command-line tool so that I can use it in a login script? Would it work considering that Pegasus Mail has not been installed on the clients?

It's no biggy if it can't be done, but it would save our staff some time and reduce my administration time.

Thanks.

[quote user="Greenman"]Haha - anyway - I searched the registry (which I should have done in the first place...) and there they were.

[HKEY_CURRENT_USER\Software\Pegasus Mail][/quote]

Sorry to hear you needed to do this: The above loaction was the one I mentioned in my first reply to this issue ... and all the other ones are simply "copies" of this one as I'm pretty sure Pegasus Mail doesn't write to any other location by itself and it's the way the Registry works, IOW: Windows does the rest (some branches are simply "linked" into others while WOW64 stuff is related to 64-bit machines maintaining a 32-bit and a 64-bit version of the respective branches alongside).

[quote user="Greenman"][HKEY_USERS\{Administrator}-500\Software\Pegasus Mail]

[...]

It's the last one that bothers me - rather than using group policy preferences (I'd have to use the SID's for each user?), can limits.exe be run as a command-line tool so that I can use it in a login script? Would it work considering that Pegasus Mail has not been installed on the clients?[/quote]

I have no idea about any of this, you better contact David Harris himself for getting proper answers. With regard to the Registry key you appear to be referring to see my notes above.

Thanks.

No need to apologise - I should have searched for the keys in the first place. I've been quite busy so was trying to save myself a little time.

I don't want to 'test' this as I don't want to break anything. I don't want to risk importing a registry key and something unexpected happening - for example, I don't know if there are other registry entries that Pegasus Mail writes/references to support the generation of the alerts. Some programs hang when entries are missing.

I'll PM David Harris and reference this thread.

Cheers!