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.

[quote user="EricEffern"]

Does anybody have a complete documentation of all the Pegasus Files and especially the structure of Hierarch.PM ?

I found those sources:

http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html
http://wiki.pmail.com/index.php?title=KB:Pegasus_Mail/Structure_of_HIERARCH.PM_File

both lack some inforamtion. eg. Hierarch.PM entries for special folders:

Dokumented is Standard Line, eg. 0,0,"7BB65C2A:0BE9:FOL0266F","2B773879:MT02001_Artes","In"

not documented eg.: 0,0,"WCPL0BDV:1A94:FOL068D8","66E47807:My mailbox","aaAusgangskopien",0,20  (note 2 more items at the end)

Eric

[/quote]

Not sure what the 2nd last item (0) is, but the last one is specifies the sort order in the Folder window.  The lower this number, the higher up in the list that particular folder will appear.  For folders with the same value for this parameter, the sort order is alphabetical - ascending. Some special characters sort before "a" (~ for example).

 Hope this helps.

I looked at the thread but I always clear my New Mail messages out, so it wasn't really of any help (most in there is a handful at a time).  :-(

Ok Michael has solved the problem by analysing the crash dump.

The Problem occurs, when Adobe PDF is set as stnadard printer driver, so I guess that ca be solved !

The thread dealing witn this is here:

http://community.pmail.com/forums/thread/19000.aspx

Thank you very much Michael !!!!

I have been using avast! for a few months now and do not use the mail shield figuring the realtime protection will help with new mail when written to the hd on download. Since Pegasus is safer than most due to Spamhalter / blacklist / blocking of scripts etc thought was the mail scanner would not be called for. YMMV.

[quote user="hogman"]I just got a new system with win 7 64. I've been using Pagasus for years, will it run on win 7 64? [/quote]

Just take into consideration.

Hi Steffan

Will do. Thank you.

I now realise these features are only available with Novell Netware.

Same problem as Mitchell here, so I wanted to say thanks Steffan! :)

- Kim

It sounds like the Live Cycle Designer has a hard coded Mapi32.dll reference, and is not using the correct process to determine which mailer to use. If you are able to experiment in your environment, try the following:

o  In Windows/System32 rename Mapi32.dll to something else (like Mapi32.dllx)

o  Copy Mapipm.dll into Windows/system32

o  Rename Mapipm.dll to Mapi32.dll in windows/system32

o  Try your Submit sequence. Hopefully Pegasus Mail will popup. If so, complain to vendor

o  Check for activity in your Mapipm.log. 

o  Reset your Dll by erasing Mapi32.dll in windows/system32; then rename back in your windows/system32 your Mapi32.dllx to Mapi32.dll

Martin

[quote user="Martin Schnabel"]

Are there any subdirectories in C:\pmail\mail ? Like C:\pmail\mail\admin oder C:\pmail\mail\<YOUR USERNAME> ? If yes, copy rquotes.pms to the subdirectory.

[/quote]

That did it!  Thank you, Martin.  Thank you very much!!

My instructions are now modified as follows:

## -64-bit Windows OS:
## Open DOSBox
## Z:\> mount c c:\PMAIL
## Z:\>c:
## c:\>cd Programs\RESOURCE
## c:\Programs\RESOURCE> rescom rquotes.r
## c:\Programs\RESOURCE> copy rquotes.rsc c:\MAIL\<MY USERNAME>\rquotes.pms
## c:\Programs\RESOURCE>exit
##

Thomas Thanks I will pass this on to our IT admin and hopefully he will look into turning on the long file name support.

A search of this forum using the term "migrate" yielded some specific steps to do just that.  The url is http://community.pmail.com/forums/post/5489.aspx .

Hope this helps!

In two words - client server

Try this link:

Happy reading...