I haven't seen anything about message limit functionality so am curious whether a message limit takes attachments into consideration and how/when the sender is notified.
I have an acquaintance using Pegasus Mail whose message are being blocked when above 10mb in size. He sent me a screenshot of a Pegasus Mail window titled "Cannot add attachment" that says "The attachment you have selected is larger than the maximum size permitted for a single attachment by your system administrator." I assumed it was an ISP limit until I saw the screenshot. I don't know of a setting within PMail the imposes an attachment size limit. The screenshot is of too poor quality to try to include here so I'm hopeful someone recognizes the issue and can explain what is happening.
Hi Brian,
neither I do know any limitation for size of attachment within Pegasus.
I assume his ISP has set that limit. Or is he using Mercury? I don't know any more the settings of a fresh new installation of Mercury, but with Mercury it is possible to set limits on size and lines.
greets Olaf
Thanks for the response Olaf. No Mercury involved. His ISP claims a 25mb limit but messages are being blocked at 10mb. He can send large messages using the web interface of the ISP (Comcast).
He sent me these log entries but I don't recognize the format and haven't heard back from him regarding their source. I don't know what they mean.
18-05-14 23:08 T name@domain.org Attachment Test - 0 <Default> NNYNNY
18-05-14 23:08 M name@domain.org Attachment Test - 0 <Default> NNYNNY
Hi Brian,
[quote]He sent me these log entries but I don't recognize the format and haven't heard back from him regarding their source. I don't know what they mean.
18-05-14 23:08 T name@domain.org Attachment Test - 0 <Default> NNYNNY
18-05-14 23:08 M name@domain.org Attachment Test - 0 <Default> NNYNNY[/quote]
Sometimes I had a file with an explanation ... can't find it any more. All I found is this headerline for SYSLOG.PM
date status to subject CC attachments identity setting extra
and as I remeber settings stands for the six boxes for Confirm Reading, Confirm Delivery, Copy to self, Urgent, Encrypted and Formated (hopefully translated them correctly).
So it seems, he didn't send an attachment. The question is, what avoided it due to a 10MB limit. Is there any virus scanner that may do something like that?
greets Olaf
You should get a copy of Limits.exe which deals with attachments and folders You can a copy from my website: http://www3.telus.net/public/irelam/limits.zip
Sorry there is no help file but the dialog should be self-explaining
Martin
Olaf: Thanks for the SYSLOG.PM pointer. That's a log file I've not paid much attention to.
Martin: Where are the size limits stored that are set by your Limits utility?
I would love to answer your question but the program belongs to David Harris. All I can says it interfaces with Pegasus Mail to examine incoming and outgoing messages.
I suspect it is using the extensions interface of Pegasus Mail to either display a warning or stop the process. The sizing is the user or administrator responsibility. I have no clue as to where the limits are stored, but could poke around to see what gets updated, like for example, pmail.ini
Martin
The interface of limits.exe appears to allow the setting of hard and soft limits on message size and attachment size. I didn't grasp the difference between hard and soft but didn't put much effort into it yet either. I was curious about the storage location only because it would provide a place to look for a size limit specified within Peg. I can try to figure out functionality if it comes to that.
As for the attachment size delivery problem, the internet session log just received indicates the message was accepted for delivery. I'm now wondering if the size limit is on the recipients end. That scenario doesn't seem to fit with the failure message so I'm still pretty clueless.
The ownership labels in the Exe say David Harris. Also I found the registry keys in the program under Software/Pegasus Mail/limits, except when I inspected the Rgistry tere was no such keys ??
When I changed the values, the new values were presented next time I executed the program.
Martin
It sounds like the registry entries are only created by limits.exe and that utility isn't readily available so I doubt this has anything to do with the problem but if he's comfortable with checking the registry I'll have him take a look.
Subkeys of HKCU/Software/Pegasus Mail correct?
Hi guys,
so ... the existence of LIMITS.EXE shows, that it is possible to control the size of attachments with Pegasus via registry. I had a look at my registry and there are now entries that have to do anything with such limits. Even in PMAIL.INI I don't see anything on limits.
And I don't know any configuration entry in Pegasus to control that. The only possibility I know that has to do with size limits are filtering rules. But with filters I don't know anything to produce that error message.
The question is, if the user has such entries in registry (without using LIMITS) and in case how they did get there. If they are present and they are deleted (on closed Pegasus), will Pegasus act as assumed in future?
And as SYSLOG shows, the test mails were sent ... but without any attachment!!!
Greets Olaf
Hi Brian,
had a test with LIMITS.EXE and it seems to be the reason (or the four registry entries under HKCU/Software/Pegasus Mail).
[quote]Pegasus Mail window titled "Cannot add attachment" that says "The attachment you have selected is larger than the maximum size permitted for a single attachment by your system administrator."[/quote]
Sorry - my Pegasus is german and the screenshots show german warning / error window. I'll explain:
This is the WARNING window, which comes up on attaching a file greater than SOFT limit. You may continue and file will be attached or cancel and file will not be attached.
This is the ERROR window, which comes up on attaching a file greater than HARD limit. You may continue and file will NOT be attached. If I translate window title and the first paragraph (not header) of message, it seems to be what user gets in english.
Changes on limits will be activated on closed Pegasus! Simply deleting the four entries in registry on closed Pegasus will set Pegasus to "normal" behavior!
Conclusion: how ever - the user must have set the registry entries for that limits, because they produce exactly these windows with warning or error.
greets Olaf
[quote user="FJR"]so ... the existence of LIMITS.EXE shows, that it is possible to control the size of attachments with Pegasus via registry. I had a look at my registry and there are now entries that have to do anything with such limits. Even in PMAIL.INI I don't see anything on limits.
And I don't know any configuration entry in Pegasus to control that. The only possibility I know that has to do with size limits are filtering rules. But with filters I don't know anything to produce that error message.
The question is, if the user has such entries in registry (without using LIMITS) and in case how they did get there. If they are present and they are deleted (on closed Pegasus), will Pegasus act as assumed in future?[/quote]
That is indeed the question. I've asked my acquaintance to check his registry.
Martin: Do you think running limits.exe with settings at zero is the safest way to undo any limits set in the registry?
[quote user="FJR"]And as SYSLOG shows, the test mails were sent ... but without any attachment!!![/quote]
Received confirmation that messages are being delivered but attachments of +10MB are not included so the issue is specific to attachment size.
I would think that setting values to zero would stop the limit processes. I wonder how one starts the program, I would expect it is done manually.
I am going to write to David to see if he has any official documentation or program source. The original distribution file was just the Exe and manifest files.
In my distant past I do remember some discussions about this utility though.
Martin
BINGO! There are four registry entries in HKCU\Software\Pegasus Mail, one each for hard and soft attachment and message limits.
I just went through my PMail version archives and found limits.exe was distributed in the 4.6x versions. No documentation though.
We now know the where and how of this attachment limit issue.
Olaf,
I just received the email notification of your post made 13 hours ago that contained the screenshot of the large attachment notice. Unfortunately I don't follow the forum. I just react to the email notifications.
You have exactly duplicated the issue and identified the solution. Thank you for your efforts.
Brian
Hi guys,
After some days off I've checked my most favorite forum here [:)] and found this thread where I'm interested in, too. From time to time I get postmaster notifications that one of my users has tried to send a very large e-mail (often of 100 MB and more - no joke) which was of course not processed by our ISP.
And this Limit.exe seems to be a simple way to set a maximum size for attachments including information to the user (soft and hard).
Is this limit.exe also usable in a multi-user environment with only one Pmail installation at a server? Has this limit.exe to be placed into the folder where the pmail executive resides or into the user's mailbox? Has this limits.exe to be executed from each user or only one time by the administrator to set the limits?
Olaf, you have tested it above and the German notification windows look very good. I hope, the registry values for the different limits need not to be set manually with every user.
Thanks
Joerg
