I assume you found the answer to the first question, if not simply click on help in Manage Local Users

To automatically run Pegassus for a specific user, add -I username to the shortcut

(thats a capital i)

AVG V10 can be obtained from: http://free.avg.com/us-en/download-avg-anti-virus-free  Please note that the install time is quite long as yet more features have been packaged with the "free" version.

  Virscan.ini needs to be updated to use this new version of AVG

The Virscan.ini CMDLINE= line should be changed from AVG9 to AVG10 so that the new Cmdline looks like:

; For AVG V10 scanner something like:
CmdLine=c:\progra~1\avg\avg10\Avgscanx.exe /SCAN "!f"

Martin

> Thanks for your reply, is this a limitation of pegasus or the IMAP protocol ?

Depends a lot both on the server and the client.  Some servers support more options that others, some clients store a lot more data at the client system.  If you were to cache all of the IMAP4 data via Pegasus Mail then it would be able to search the cache without even being connected to the host.

>  
> I have set up squirrelmail running from our server and connecting up to dovecot and it works fine including the searching of email body
> so I assume squirrelmail is just searching through IMAP. It would be really handy to be able to do the same with pegasus. I guess I cant
> have everything  :)

I my case I find the Squirrelmail gets really slow when the folders get large with most IMAP4 servers, maybe Dovecot is more efficient with server side searching than the UW type IMAP4 servers.

[quote user="Xylvyr"] Since each and every email address has to "behave" like a standalone email when I use the "reply" functions, does that mean that each address will need its own identity? [/quote]

Yes.

[quote user="Xylvyr"] And if so, can all the mail for all the identities still be checked in one sweep? Or just all the mail for one identity at a time?

[/quote]

They can all be checked in one sweep. Have a look at the two options at the bottom of Tools | Internet options | Receiving.

Cheers!

Autofilter is not working on newly created folders as well as the two originally mentioned.

Makes me want to say bad words, right out loud.

Any suggestions?  Is this the only occurrence of this situation?

> I'm cleaning up my hard disk and I've found some old directories with Pegasus FOL*.PMM and PMI files (not my current PM mail directory).
> I'd like to look in them.  I've tried making them Public Folders (under Tools menu) and I've tried adding new mailboxes (under Folders
> menu) with just a little success.  A couple folders appeared in the new mail box.  It seems that there are many more folders in the
> directory which I pointed to.  How can I get Pegasus to look at them?  Deleting the PMI (index?) file doesn't cause a reindex and
> recognition.  Thanks for Pegasus Mail and for this forum; it's great.

These may be copies of folders in you current mailbox and if so they will not show up in the folder list.  Try using the following utility.

PMRestArch - Pegasus Mail Restore Mail Folder Archives:
http://www.lexacorp.com.pg

Usage:
PMRestArch SourceDir DestinationDir

Description:
Pegasus Mail cannot display two mail folders with the same internal ID even if they are in separate mailboxes. Mail folders also have to be Read-Write.
      
This causes problems when trying to view mail folders which have been archived by copying them to backup media.

This utility:

1.  Copies all .PMM and .PMI files in the source directory to the destination directory and renames them as BAKxxxxx.PMM
    and BAKxxxx.PMI.

2.  Ensures that the resulting file is Read/Write.

3.  Creates a different internal unique ID for each file.

Once you have run this program to restore archived folders to a directory you can attach that directory using the Pegasus Mail 'Add mailbox to list' option and access the archived folders in this new mailbox.

Thanks Michael. Greatly appreciated.

At least now I know it's not worth pursuing anymore.  I was beginning to think the way to do it was obvious but I was too clueless to find it.

I have problems forwarding some emails I receive.  My Norton Anti-Virus rejects it by giving "Error 500 5.7.1 Your Email is not using the proper character set.  Please correct this (try setting your mail program to use plain text) and resend"  Is this a problem with Pegasus, Norton or my ISP? 

I suspect the problem is that you are using the wrong character set for the characters in the message and your ISP is telling you to fix it.

[quote user="lyndave"]is this telling me i need to sign onto some site on a browser before i send an email?  which site would that be?  how would the site have anything to do with my email transmission from a different app?[/quote]

This is an error message returned from your email or home page provider's SMTP server which almost certainly provides a web interface for email accounts: Try ...

[quote user="edg"]Our Office setup has the Pegasus mail binaries installed in a common shared folder on the network, with individual users having their mail message (and .ini's etc) files in their own private folder elsewhere.

My question is in regards  to installing this control. If I do so, will it automatically replace bearhtml and configure the IE control for all users? Or is there a way to configure it to be enabled on a per user basis?[/quote]

This is partly due to the format of the message store.

A new version of the store is in the pipe-line, and hopefully these sorts of problems will be history.

Would someone let me know to whom to send these.  I have them renamed to .cxx and zipped.  The archive is 8712 bytes.

Send them to either tech-support@pmail.gen.nz or techsupp@tstephenson.com and they'll get to the test group.  FWIW, the filtering on the subject crash with a subject exceeding the SMTP line length limits has already been passed to the test group and David Harris.

Easiest way would be to set it up on a mail server and just parse the queued mail and output to the lpt port.

VBscript and ASP have commands to handle an email message.  You can access the headers, body, etc pretty easy.

It'd just work in the background as new mail came in and send it to the printer continuously.

Most email clients would not be set up to print like this.

Brian,

     This posting sent on to team.

Martin

SUCCESS!

THANKS!

I've used Pegasus for a couple of days now and it seems to be fixed. I set both addresses to be the exact same and all seems to work. [+o(] Hope it continues.

Thanks so much, IDW, for the help! I appreciate your time.

[quote user="DanT"]

The list of messages, at least in the Preview mode, have the headers "From", "Subject", "Date/Time" and "Size".  Which of these headers is in bold?  If something other than "Date/Time" is bolded try clicking on that header.

Hope this helps, but if I'm way off I apologize for wasting your time.

[/quote]

 Information of any type is no waste of time. Thanks for taking yours to post. I checked the headers and the 'From" header was bold . I clicked on the Date/Time and the messages went into chronological order. AHA! I was sorting alphabetically (I guess?) instead of chronologically.

 That fixed it and also annoys me a bit because I've used Pegasus for years and didn't know that or at least didn't remember it.

 Thanks for the information. It fixed the problem! [:D]

Robert

aderoy, many thanks for replying.

Your suggestion allowed me to sort this out very quickly.

Cheers! 

> Does anybody have a detailed desciption of the binary setup of the *.PMI and *.PMM files for this file ?

This is an old description but it's valid except for some flags that are not material to your problem.  Over 90% of the time this reindexing problem is caused by something else accessing the mailbox files when Pegasus Mail is trying to write to a file. The first things that come to mind are multiple access to a single mailbox and anti-virus software doing on-open checking.

Folders:

A Pegasus Mail 2.2 folder consists of two files. The master file has the extension .PMM: it has a 128-byte header of which the first 50 bytes are the long name of the folder, the remainder being reserved. Following the header is the text of all the messages in the folder, separated by ^Z characters (ASCII 26). Some of the messages stored in the folder may in fact be deleted  there is no way of determining this without consulting the record matching the message in the .PMI index file for the folder.

The other file has the extension .PMI, and consists of a
representation of the message using a structure called an IMESSAGE, shown below in its C language definition (note that all integer values in the file are stored in Intel word order  Pegasus Mail for the Macintosh does whatever conversion is necessary for its Motorola processor as it loads each entry from the index):

typedef struct
{
unsigned long flags;
unsigned long fpos; /* Offset in master file */
WORD msg_number; /* Msg ordinal position */
char fname; /* Unused in folders */
char from [30]; /* Sender of message */
char subject [36]; /* Guess what this is */
char date [20]; /* Reduced form of date */
long mtime; /* See below */
long fsize; /* Bytes in this message */
} IMESSAGE;

flags is a bitmap of message characteristics, using the following values:

0x1 The message has Pegasus Mail-style attachments
0x2 The message is a uuencoded file transmission
0x4 The message is encrypted
0x80 The message has been read
0x2000 Sender requests confirmation of reading
0x20000L The message is a copy to self
0x40000L The message has been deleted
0x80000L The message is in a MIME transmission format
0x100000L A reply has been sent for this message
0x200000L The message has been forwarded to another user
0x400000L The message is urgent (never seen in folders)
0x800000L The message contains BinHex-encoded enclosures
0x1000000L The message originates from an MHS system
0x2000000L The message originates from an SMTP system.
0x4000000L The message has annotations.
0x8000000L The message contains enclosures

All other values are reserved - do not use them.

The mtime field is a crude calculation of the number of seconds since Jan 1 1990, used only for sorting purposes. It is not intended to be accurate merely "near enough".

The fsize field can be larger than the actual size of the message, but in no circumstance should it be less - this will cause Pegasus Mail to crash.