[quote user="Mike Powell"]I have Pegaus 4.21c installed on a Windows XP computer with two mailboxes established. One is working fine but when I try to change user to get to the other, it hangs up when applying mail filtering rules. Trying to enter directly doesn't work - endless hourglass on the desktop.
The last thing I did was send out two large sound files - approx 15MB each - copied to myself. Was this a mistake?
Yes if there is any server at all along the line that will not accept the encoded 15 MByte files. The messages will be bounced back. In addition a 15 MByte sound file will be closer to 20 MBytes when encoded in a message.
Has it overpowered the system? If so, is there any way of rectifying the situation?
The messages have probably bounced and there is an even larger bounce message in the inbox where both filtering and content control is trying to process. Go to the new mail directory and move (or delete) these huge CNM files and PMail will open normally.
Alternatively I notice a 0kb MAILBOXP.LCK file in the 'problemfiles' folder, which then appears at the top of the list in my C:\PMAIL\MAILl folder each time I try to gain entry. Apologies if this has been posted before - I did check a few other threads which appeared promising that they were about differenct problems. Any advice very welocme.[/quote]
Then are you going to restore the file from tape / backup when the user complains?
Not a good thing.
Best is to educate the users.
Should be easy enough to run a script to check the size of the mailstore and give a warning at 75% of max. When at 95% lock the user out. This is mean, but after one or two times they will comply.
Perl, Python or even vbscript should be able to handle this.
Maybe, but this is not something Pegasus Mail has any control over. It depends a great deal on system administration, a skill which most users do not have. It is better to clearly state that pmail offers no such security than to have people complaining that "Pegasus is broken" because it didn't work for them, or to engender an illusion of security.
> I am trying to use the -j command line option to send emails. If > there is an instance of Pegasus running then the emails are sent > immediately. However if Pegasus is not running the emails are queued > and when I next run it , on exit I am prompted to send the queued > emails. Is this the expected action of Pegasus?
Yes, it you want to send a message immediately then you should use a command line mailer like Blat!.
BLAT http://sourceforge.net/projects/blat
DESCRIPTION:
Blat is a Public Domain Windows NT console utility that sends the contents of a file in an e- mail message using the SMTP protocol. Blat is useful for creating scripts where mail has to be sent automatically (CGI, backups, etc.) To use Blat you must have access to a SMTP server via TCP-IP. Blat uses the a DLL ("gensock" or "gwinsock") from WinVN, the public domain usenet newsreader for windows. Blat can store a default SMTP server address and a default "From:" field in the registry. The server's address can be overriden using the -server flag, and the "From:" address using the -f flag. Input from the console (stdin) can be used instead of a disk file (if the special filename '-' is specified). Blat can also "carbon copy" and "blind carbon copy" the message. Impersonation can be done with the -i flag which puts the value specified in the "From:" line, however when this is done the real senders address is stamped in the "Reply-To:" and "Sender:" lines. This feature can be useful when using the program to send messages from NT users that are not registered on the SMTP host.
Optionally, blat can also attach multiple binary files to your message.
That said, if you are using Mercury/32 to send the mail then there are a number of other options as well.
yes, I restarted Pegasus and even reinstalled it, with transfer of files from the old to the new program. Apparently I also transferred the problem which, as Tom pointed out, was hidden in the queued message. Removing it did the trick. (I use VISTA).
if you notice to above link, this link is incorrect. 13 character in the end of above line in not a html link.
why?
Hard to say what is wrong with the PHP process since I have not seen a MercuryS session log with what you have actually sent to MercuryS. It looks like plain text but I suspect is is not. I can paste this URL into into PMail as unwrapped plain text and send it without any problem on the receiving end at all. I can do this as well with Outlook and Thunderbird. I can also create a link in PMail with this string as send it as an HTML message and it comes through normally. There is something wrong with the string as sent via SMTP to the MercuryS server.
I suspect that one of those characters is not a valid ASCII character. What happens when you select it all an use "Open selection as Hyperlink" in PMail?
Most likely you have a wiring problem (as the only change was replace a switch) in your building, with intermittent connection problems. This will affect software protocols that are poor in recovering from faults, like paradox databases and open imap connections. The only way to catch something like this, is to investigate piece by piece what is happening in each segment of your network.
Edit add: I should have said also, that with Vista you need to open explorer, and make sure explorer reconnects the drive, before you attempt to restart Pegasus Mail.
The window had been manually minimized, i.e. for some reason, lost in the mists of time, I had grabbed the corner of the window and reduced it down to only the header bar. Consequently, although everything indicated the window was there , I couldn't see it. All is well now and I can edit my filter to get rid of even more incoming spam and junk.
[quote user="PhilM"]That trial and error killing lines in hierarch.pm scared me.[/quote]
There's aboslutely nothing to be scared about if you keep a backup, really. And deleting lines (not editing them!) will only get Pegasus Mail to recreate them if it detects folders missing in there.
[quote user="PhilM"] I tried something else, and it worked. I created two new folders, and then looked at the folder info for each, writing down the folder names, folnnnnn.* Then I renamed the new ones (by adding $ to each extention), and renamed the old .pmm and .pmi folders to the new names.[/quote]
The only issue with creating new folders is that filter rules applying to the old ones won't work anymore because Pegasus Mail uses their (unique) internal ID's instead of human readable names, so if there are some you should get into their editor and check for "red lines" indicating missing folders. So you see there's always a "gotcha" ...
I take it then that when sending mail using another identity doesn't pick up these settings, that you have to actually be in the identity for it to work?
Well, I want the **arrival** of a new mail to trigger an action, but I don't want opening "New Mail", containing unread messages, to trigger the action.