Thank you. You figured it out.

 I have several identities set up. A few months ago, I deleted the SMTP outgoing host for the <default> identity. I no longer needed that identity so I thought I was making it simple on myself by deleting the no longer used SMTP outgoing e-mail section of that identity. That must have been when my problems started. After reading your suggestion, to check all my SMTP setups to ensure they are valid, I knew exactly what it was. I never figured Pegasus would use my <default> identity to forward the mail, I assumed it would use which ever identity I had active.

I am using Pegasus mail v4.41 for win32.

I use a filter rule to forward every message that I receive in my inbox to another e-mail address.

This feature use to work fine, when I would receive a message, Pegasus would follow the trigger

rule I had set up and would forward the email automatically.

Now for some reason, when I get a new inbox e-mail, Pegasus will put the forward into my

Que manager, under the 'type' column, it says 'Final Form'. Once in here, Pegasus can not or will not send the email out. 

Even when I manually hit the 'send queued mail' button. It just sits there until I delete it.

I have looked for and have not found 0 byte pmo,pmx or pww files in my mailbox folder.

The only 0 byte files I have are: NB.pm#, junk.pmk and IMAP.pm

Thank you for any help.

I've got more questions that answers.  If the message is in "Final form" it should be the complete RFC 2822 message body with 'glue' headers.  This should be a PMX file.  Could you show us a copy of the headers of the message in the queue?  FWIW, a message in 'glue' headers format looks like

?? <MAIL FROM: address>
<RCPT TO: address>
<RCPT TO: address>
<BLANK LINE>
<RFC 2822 message body>

 If the message is not in the proper format it will be ignored when you hit the send.

Thanks for your assistance.

I found the .PMX file from the message in the queue.

This is how I ran the test. I sent myself an email from web based Gmail to my @att.net (uses Pegasus).

Pegasus received the e-mail, and followed the rule and tried to forward the e-mail at the @MMS.USCC.NET, but instead of sending, it was put in my queue

 I could not find the <rcpt to: xxx@xxx.com> headers in the message. But I think this is what you requested to see:

$$ xxxxxxxxx@att.net
T xxxxxxxxxx@MMS.USCC.NET

Resent-from: "masked" <xxxxxxxxx@att.net>
Resent-to: xxxxxxxxxx@MMS.USCC.NET
Resent-date: Tue, 08 Jul 2008 11:10:29 -0500
X-Apparently-To: xxxxxxxxxx@att.net via 69.147.85.101; Tue, 08 Jul 2008 09:10:30 -0700
X-Originating-IP: [204.127.208.81]
Authentication-Results: mta110.sbc.mail.re3.yahoo.com  from=gmail.com; domainkeys=pass (ok)
Received: from 204.127.208.81  (EHLO sccwmxc01.att.net) (204.127.208.81)
  by mta110.sbc.mail.re3.yahoo.com with SMTP; Tue, 08 Jul 2008 09:10:30 -0700
Received: from rv-out-0506.google.com ([209.85.198.224])
          by att.net (sccwmxc01) with SMTP
          id <20080708161030s0100hkekde>; Tue, 8 Jul 2008 16:10:30 +0000
X-Originating-IP: [209.85.198.224]
Received: by rv-out-0506.google.com with SMTP id k40so2771211rvb.11
        for <xxxxxxxxx@att.net>; Tue, 08 Jul 2008 09:10:29 -0700 (PDT)


Received: by 10.140.201.1 with SMTP id y1mr3303367rvf.246.1215533429439;
        Tue, 08 Jul 2008 09:10:29 -0700 (PDT)
Received: by 10.141.106.8 with HTTP; Tue, 8 Jul 2008 09:10:28 -0700 (PDT)
Message-ID: <4dbfdsbdfbdfbdfbdfbrse4ge4edrsdrgdrgd6@mail.gmail.com>
Date: Tue, 8 Jul 2008 11:10:28 -0500
From: "xxxxxx" <xxxxxxxx@gmail.com>
To: xxxxxxxx@att.net
Subject: test
MIME-Version: 1.0
Content-Type: multipart/alternative;
    boundary="----=_Part_24669_30597471.1215533429430"
X-PM-PLACEHOLDER:                                          .

------=_Part_24669_30597471.1215533429430
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

test

------=_Part_24669_30597471.1215533429430
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

test<br>

------=_Part_24669_30597471.1215533429430--
 

Looks good to me if there is no blank space between the received lines in the actual file you are looking at. Now I do not know why this is not sent if you can send other messages using the same built-in  mailer interface.

You are correct, when I look at the actual .PMX file, there are no blank spaces between the received lines.

Still, it will not send the queued message.

When I type a new message that goes in my queue, is says 'Ready To Send' under the 'type' column.

When Pegasus uses the rule to forward a message, the 'type' column says 'Final Form' . When Pegasus sends the queue, it will send the 'Ready To Send but not the 'Final Form'. I could not find much information on what Final Form means. If I could figure out why Pegasus now tags my forwarded rule e-mail 'Final Form' I might be able to correct it

 I tried a re-install of Pegasus on another computer, following the instructions for moving over my mail and settings files. It did not correct, error must be in my configuration / .INI file.

Do you have any knowledge of what 'Final Form' means? I searched Pegasus support and could not come up with much.

Thanks!

[quote user="center1212"]

You are correct, when I look at the actual .PMX file, there are no blank spaces between the received lines.

Still, it will not send the queued message.

When I type a new message that goes in my queue, is says 'Ready To Send' under the 'type' column.

When Pegasus uses the rule to forward a message, the 'type' column says 'Final Form' . When Pegasus sends the queue, it will send the 'Ready To Send but not the 'Final Form'. I could not find much information on what Final Form means. If I could figure out why Pegasus now tags my forwarded rule e-mail 'Final Form' I might be able to correct it

Final form just means that the queued message has already been converted from the editable form in the queue.  This always happens when you send the mail via the built-in mailer.   It will also remain in the queue if you try to send and there is an SMTP failure at send time.  You may have noted when there was only one message in the queue when you sent a message that it immediately turns to 2 for a few seconds when  both the editable and final form of the message is in the queue.  Fixing it is another problem since this message appears to be in the correct format but it might be having problems being sent if it was sent via a second identity and SMTP server.

I'd check out all of my SMTP setups to ensure that they are all valid.

 I tried a re-install of Pegasus on another computer, following the instructions for moving over my mail and settings files. It did not correct, error must be in my configuration / .INI file.

Do you have any knowledge of what 'Final Form' means? I searched Pegasus support and could not come up with much.

Thanks!