The error is back from our original user.  So moving the PNX files was not a proper / complete fix.

 It worked nicely for almost exactly a week.  Anything to try next?

I created this post in another thread but it got no responses and was buried fast. This is the error I get:

 Delivery has failed on the enclosed message for the following
reasons reported either by the mail delivery system on the mail
relay host or by the local TCP/IP transport module:

   *** Invalid message file - no '$$' signature ***
   WinPMail has encountered a file which is not properly formatted
   for sending via its built-in SMTP transport (valid files start
   with the characters '$$' on a line of their own). This error is
   usually the result of running out of disk space in the volume
   containing your home mailbox. The message cannot be sent.

I am getting this error

message from a few users.  Although they are still able to send mail. 

It's just an annoyance for them really.

The first user has five

1KB .PMO files, but no .PMX, or .PMW in their folder.  There are eight

or so .PNX files though.

Using WinXP, and version 4.5 but this

was first seen in v4.41 for certain.

Thanks for any and all help.

> I created this post in another thread but it got no responses and was buried fast. This is the error I get:
>
>  Delivery has failed on the enclosed message for the following
> reasons reported either by the mail delivery system on the mail
> relay host or by the local TCP/IP transport module:
>
>    *** Invalid message file - no '$' signature ***

This means the the From: address in the "glue" headers file is missing or invalid.  This would happen when a file is being converted from the editable format to the final "glue" headers form.  Here's a sample of a glue headers message sent to the Mercury queue, the form is the same for the Pegasus Mail internal queue.

------------------------   spam.101 ----------------------------
$$ cslaw@indirect.com
tstephen@mtshasta.lmms.lmco.com
support@tstephenson.com

From: swallace@cyberpromo.com (Sanford Wallace)
Organization: Ambulance Chasing, Inc.
To: "Laurence A Canter" <spamford@wilhelp.com>
Date: Fri, 17 Oct 2003 12:55:34 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Test Message
Reply-to: "Taylor Jimenez" <taylor@wilhelp.com>
CC: "Martha S Siegel" <Martha@smartbotpro.net>
Priority: normal
Message-id: <399917090.3123.1066456430@persephone.pmail.gen.nz>
X-mailer: Pegasus Mail for Win32 (v3.12c)

This is a test of the mail servers settings for spammers.

Here's a little text file that you can use to test Mercury/32
or Pegasus Mail.   With Mercury or Mercury/32 you save the
file in the Mercury queue with the 101 extension.  With Pegasus
Mail you save the message in the HOME mail directory with the
PMX file extension.
 
This is a file in "Glue" headers format, the $$ line is the
SMTP MAIL FROM: address, the next two lines are RCPT TO:
addresses and the blank line is the separator from the RFC 2822
message body.  You can delete the Date: or Message-ID line in
the message body, the SMTP relay host is expected to add these
to the file.  Copy and paste the file to Notepad and then save
it with the correct extension it the correct queue.  Modify the
RCPT TO: "Glue" headers to use your own addresses.
---------------------------- cut here ----------------------------





>    WinPMail has encountered a file which is not properly formatted
>    for sending via its built-in SMTP transport (valid files start
>    with the characters '$' on a line of their own). This error is
>    usually the result of running out of disk space in the volume
>    containing your home mailbox. The message cannot be sent.
>
> I am getting this error message from a few users.  Although they are
> still able to send mail.  It's just an annoyance for them really.

> The first user has five 1KB .PMO files, but no .PMX, or .PMW in their folder.  There are eight or so .PNX files though.

Open the files with a ASCII editor and check out the addresses.

> Using WinXP, and version 4.5 but this was first seen in v4.41 for certain.
>  
> Thanks for any and all help.

I'm a little confused with this advice: 

 "This is a file in "Glue" headers format, the $$ line is the
SMTP

MAIL FROM: address, the next two lines are RCPT TO:
addresses and

the blank line is the separator from the RFC 2822
message body.  You

can delete the Date: or Message-ID line in
the message body, the

SMTP relay host is expected to add these
to the file.  Copy and paste

the file to Notepad and then save
it with the correct extension it

the correct queue.  Modify the
RCPT TO: "Glue" headers to use your

own addresses.

...Open the files with a ASCII editor and check out the addresses."

Is this to be done to any email that goes out and results in getting this error?

> I'm a little confused with this advice:
>
>  "This is a file in "Glue" headers format, the $ line is the
> SMTP MAIL FROM: address, the next two lines are RCPT TO:
> addresses and the blank line is the separator from the RFC 2822
> message body.  You can delete the Date: or Message-ID line in
> the message body, the SMTP relay host is expected to add these
> to the file.  Copy and paste the file to Notepad and then save
> it with the correct extension it the correct queue.  Modify the
> RCPT TO: "Glue" headers to use your own addresses.
>
> ...Open the files with a ASCII editor and check out the addresses."
>
> Is this to be done to any email that goes out and results in getting
> this error?

No, the PMW, PMX and PMO files in the users home mail directory.  There is one with a bad format since it's happening when they send mail using the internal mailer and there is no problem when the one's they actually send.  I do not know why it would not should up in their File | Review queued mail.

The .PMO files look nothing like what you displayed.  More like this...

!M:145

!T:12

...

CS:1

RC:0

DC:0

US:0

ending with FL:0

Thats what the PMO files look like.  That user who I stated originally only had 1 of these PMO files now has 5 all filled with text very similar to the above.

This same user still has no PMX files in their PMail | MAIL | "username" folder .  Also zero PMW files.

Anything to try next?

> Thats what the PMO files look like.  That user who I stated originally
> only had 1 of these PMO files now has 5 all filled with text very
> similar to the above.

The PMO file is a saved message file.

> This same user still has no PMX files in their PMail | MAIL | "username" folder .  Also zero PMW files.

The *.PMW looks like this and is a queued message.The first like becomes the $$ MAIL FROM: address of the "Glue" headers.

support@tstephenson., Test Message                 

SY:0
I8:1
TO:support@tstephenson.com
SU:Test Message
RE:tstephensoncom@aol.com
EN:0
CS:1
RC:0
DC:0
UR:0
SS:0
SG:0
MI:1
CE:UTF-8
ID:AOL
ME:0
MF:0
TX:0
EX:0
HP:1
ED:1020 347
RT:1
RX:9JXY153I.PNX
FL:0

The associated PNX file has the data.

If there are no files in the users home mail directory then I can only assume that they have something on their system that creates this bad file when they send the good message.  Virus, worm, filter, etc.  Pegasus Mail is finding a bad file in the queue. 

The user has 10 .PNX files with half of those turning up completely blank in Notepad.  The other half seem to have a ton of encoded text.  With the email contents spread throughout. 

Anything I should do with these PNX files?

Is there any more info I can get to resolve this problem?

Can I delete the troublesome files so the message no longer flaunts itself so often?

[quote user="famme"]

Is there any more info I can get to resolve this problem?

Can I delete the troublesome files so the message no longer flaunts itself so often?

[/quote]

Rather than deleting the files, I would just move them to another folder so you can put any of them back if needed.

Cheers!
Steffan

Fair enough, that sounds like a safer idea.

Are we certain that the .PNX files need to go or be relocated?

[quote user="famme"]

Fair enough, that sounds like a safer idea.

Are we certain that the .PNX files need to go or be relocated?

[/quote]

Certain? No, that's why I suggested moving them. The thing is that these files are in fact email messages. Have a look here http://www.vandenbogaerde.net/han_lkfr.htm, so you know what kind of files we're talking about.

Cheers!
Steffan

Alright I relocated those 10pnx files to another location on Friday April 9, so far none of these bizarre messages have bothered her since then.  I will continue to monitor the situation.

Now my next test is a user with the same error who has 50 PNX files in their mail folder.  I will move these hopefully later today.

Thanks for the help so far Steffan!