Community Discussions and Support
Variable Signature Not Fully Functional

[quote user="bfluet"]

Check this setting:  Tools > Options > Outgoing mail > Message formatting > Disable all text styling options (never send styled mail).

[/quote]

Thank you for the suggestion, Brian. But unfortunately, the modification has no effect on the behavior as described previously.

Please note, that by changing the selected signature options to the following

Tools/Options/Outgoing Mail/Signatures/Add this variant of default signature upon message creation, Variant: Internet address, plain content

Pegasus will behave as expected, adding the variable signature to both a new mail message and a new message generated as a reply to a previously received message. So it appears as though the problem at hand is specifically related to the option combination of

/Add this variant of default signature upon message creation, Variant: Internet address, formatted content

Because, as I explained earlier, if the option

/Add this variant of default signature upon message creation,

is omitted, Pegasus will successfully add the formatted variable signature to the new mail message when it is sent to the SMTP server.

Is it possible that there is some erroneous character (e.g. carriage return) being added by the formatted signature that is only being passed during the creation of a new mail message that is disrupting the insertion of the variable signature?

[quote user="bfluet"]<p>Check this setting:  Tools > Options > Outgoing mail > Message formatting > Disable all text styling options (never send styled mail).</p><p>[/quote]</p><p>Thank you for the suggestion, Brian. But unfortunately, the modification has no effect on the behavior as described previously.</p><p>Please note, that by changing the selected signature options to the following</p><blockquote><p><span style="font-size: 10pt;"><strong>Tools/Options/Outgoing Mail/Signatures/Add this variant of default signature upon message creation, Variant: Internet address, <em>plain</em> content</strong></span></p></blockquote><p><span style="font-size: 10pt;">Pegasus will behave as expected, adding the variable signature to both a new mail message and a new message generated as a reply to a previously received message. So it appears as though the problem at hand is specifically related to the option combination of </span></p><blockquote><p><span style="font-size: 10pt;"><strong>/Add this variant of default signature upon message creation, Variant: Internet address, <em>formatted</em> content</strong></span></p></blockquote><p><span style="font-size: 10pt;">Because, as I explained earlier, if the option</span></p><blockquote><p><span style="font-size: 10pt;"><span style="font-size: 10pt;"><strong>/Add this variant of default signature upon message creation,</strong></span></span></p></blockquote><p><span style="font-size: 10pt;"><span style="font-size: 10pt;">is omitted, Pegasus will successfully add the formatted variable signature to the new mail message when it is sent to the SMTP server.</span></span></p><p><span style="font-size: 10pt;">Is it possible that there is some erroneous character (e.g. carriage return) being added by the formatted signature that is only being passed during the creation of a new mail message that is disrupting the insertion of the variable signature?</span></p>

I have been

a long time user of Pegasus and recently installed v 4.6.3 on a machine running

a 64 bit version of Windows 7. Unfortunately the Variable Signature feature

is not fully functional. I say not fully functional because when the options:<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

Tools/Options/Outgoing

Mail/Signatures/Add this variant of default signature upon message creation, Variant:

Internet address, formatted content

is selected,

the program fails to insert the variable signature upon creation of a new message. However, if the additional

option of:

/Add

this variant of default signature upon message creation

is left

unchecked, Pegasus processes the message and properly inserts the variable

signature when it is sent to the SMTP server. In addition, if the options:

/Add

this variant of default signature upon message creation, Variant: Internet

address, plain content

are selected,

Pegasus properly places the Variable Signature in the body of the message

when it is first created, as would be expected.

From this

behavior it would appear that the rquotes.r file has been properly formatted

and that rquotes.pms has been properly compiled by rescom.exe.

text

x

{

"Thought for the

day:\n",

" If we knew what

it was we were doing, it would not be\n",

" called research,

would it?\n",

" -- Albert

Einstein (1879-1955)\n",

};

I believe that

it would further indicate that rquotes.pms currently resides in the correct

folder: e.g. Z:\Pmail\Mail, on my machine.

WINPMAIL.EXE directory: C:\PMAIL\Programs
Home mailbox location: Z:\PMAIL\MAIL
New mailbox location: C:\PMAIL\MAIL\Admin
TMP environment variable: C:\Users\Enxss\AppData\Local\Temp
TEMP environment variable: C:\Users\Enxss\AppData\Local\Temp
 

  Also, I believe that the signature

file itself is properly formatted with the ~! as required.

Enxss

~!

One last observation, although Pegasus will not place the formatted variable signature into the body of a new message, as described above, it will properly place it into the body of a new message that is a reply to a received message.

So given the

above outline, it appears that the issue is confined to placing the variable

signature into the body of a new email (not a reply) solely when the option:

/Add

this variant of default signature upon message creation

is selected

in conjunction with:

Variant:

Internet address, formatted content

I have tried

several variations to the formatting of the signature file, including removing

it and reconstructing it as both formatted and plain text, to no avail.

As I

mentioned previously, I have been a long time user of Pegasus. And until the

recent change to Win 7, 64 bit I had been using Pegasus on a machine running

Win XP, 32 bit. No such issue as is described was every encountered with XP. Am

I overlooking something? Is there, perhaps, a conflict with the 64 bit version

of Win 7 that is causing the partial disabling of the feature? At this point I

am stumped.

BTW, I did

review several posts discussing similar issues before publishing this one, including the following:

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

In it, essentially

the same error was resolved on a Win 7, 64 bit machine by relocating the

rquotes.pms file to the user’s personal mail folder, e.g. C:\Pmail\Mail\<My

Username>\rquotes.pms. I tried it on machine with no such luck.

I have

always enjoyed this feature of Pegasus Mail and would hate to see it lost

simply because of a transition to a 64 bit system. Any thoughts as to how I

may be able to rectify this issue would be greatly appreciated.

&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;I have been a long time user of Pegasus and recently installed v 4.6.3 on a machine running a 64 bit version of Windows 7. Unfortunately the Variable Signature feature is not fully functional. I say not fully functional because when the options:&lt;?xml:namespace prefix = o ns = &quot;urn:schemas-microsoft-com:office:office&quot; /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;Tools/Options/Outgoing Mail/Signatures/Add this variant of default signature upon message creation, Variant: Internet address, formatted content&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;is selected, the program fails to insert the variable signature upon creation of a new message. However, if the additional option of:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;/Add this variant of default signature upon message creation&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;is left unchecked, Pegasus processes the message and properly inserts the variable signature when it is sent to the SMTP server. In addition, if the options:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;/Add this variant of default signature upon message creation, Variant: Internet address, plain content&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;are&amp;nbsp;selected, Pegasus properly places the Variable Signature in the body of the message when it is first created, as would be expected.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;From this behavior it would appear that the rquotes.r file has been properly formatted and that rquotes.pms has been properly compiled by rescom.exe.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;text x&lt;/span&gt;&lt;/strong&gt;&lt;b&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt; &lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;&#039;&gt;{&lt;/span&gt;&lt;/strong&gt; &lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;&#039;&gt;&quot;Thought for the day:\n&quot;,&lt;/span&gt;&lt;/strong&gt; &lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;&#039;&gt;&quot; If we knew what it was we were doing, it would not be\n&quot;,&lt;/span&gt;&lt;/strong&gt; &lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;&#039;&gt;&quot; called research, would it?\n&quot;,&lt;/span&gt;&lt;/strong&gt; &lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;&#039;&gt;&quot; -- Albert Einstein (1879-1955)\n&quot;,&lt;/span&gt;&lt;/strong&gt; &lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;&#039;&gt;}; &lt;/span&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/b&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;I believe that it would further indicate that rquotes.pms currently resides in the correct folder: e.g. Z:\Pmail\Mail, on my machine.&lt;/span&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;strong&gt;WINPMAIL.EXE directory: C:\PMAIL\Programs Home mailbox location: Z:\PMAIL\MAIL New mailbox location: C:\PMAIL\MAIL\Admin TMP environment variable: C:\Users\Enxss\AppData\Local\Temp TEMP environment variable: C:\Users\Enxss\AppData\Local\Temp&lt;/strong&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&amp;nbsp;&lt;/span&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&amp;nbsp;Also, I believe that the signature file itself is properly formatted with the ~! as required.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;Enxss&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;~!&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;One last observation, although Pegasus will not place the formatted&amp;nbsp;variable signature into the body of a new message, as described&amp;nbsp;above, it will properly place it into the body of a new message that is a reply to a received&amp;nbsp;message.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;So given the above outline, it appears that the issue is confined to placing the variable signature into the body of&amp;nbsp;a new&amp;nbsp;email (not a reply) solely when the option:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;/Add this variant of default signature upon message creation&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;is selected in conjunction with:&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;Variant: Internet address, formatted content&lt;/span&gt;&lt;/strong&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;I have tried several variations to the formatting of the signature file, including removing it and reconstructing it as both formatted and plain text, to no avail.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;As I mentioned previously, I have been a long time user of Pegasus. And until the recent change to Win 7, 64 bit I had been using Pegasus on a machine running Win XP, 32 bit. No such issue as is described was every encountered with XP. Am I overlooking something? Is there, perhaps, a conflict with the 64 bit version of Win 7 that is causing the partial disabling of the feature? At this point I am stumped.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;BTW, I did review several posts discussing similar issues before publishing this one, including the following:&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;blockquote&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;&lt;a href=&quot;http://community.pmail.com/forums/thread/25178.aspx&quot;&gt;&lt;font color=&quot;#0000ff&quot;&gt;http://community.pmail.com/forums/thread/25178.aspx&lt;/font&gt;&lt;/a&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;In it, essentially the same error was resolved on a Win 7, 64 bit machine by relocating the rquotes.pms file to the user&rsquo;s personal mail folder, e.g. C:\Pmail\Mail\&amp;lt;My Username&amp;gt;\rquotes.pms. I tried it on machine with no such luck.&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;span style=&#039;font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; font-size: 10pt;&#039;&gt;I have always enjoyed this feature of Pegasus Mail and would hate to see it lost simply because of&amp;nbsp;a transition to a 64 bit system. Any&amp;nbsp;thoughts as to how I may be able to rectify this issue would be greatly appreciated.&lt;o:p&gt;&lt;/o:p&gt;&lt;/span&gt;&lt;/p&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;&lt;font size=&quot;3&quot; face=&quot;Times New Roman&quot;&gt; &lt;/font&gt;

There is something very unusual about the home mail box location you show. What is that and where and why? I'm quite sure, as you also saw in the old post you referenced, that winpm-32 is looking for the .pms file in the default home mail box location which normally is the same as the new mail location c:\pmail\mail\<user> or possibly in c:\pmail\mail only with single user mode install. You can not have both at the same time. You either have single user setup or you have multi user mode setup (the default). What does the current PCONFIG show when you run it. Running it will require use of DosBox application or similar to run the 16bit PCONFIG utility on any 64 bit system. PCONFIG runs ok without any other application layer on 32bit OS systems.

There is something very unusual about the home mail box location you show. What is that and where and why? I&#039;m quite sure, as you also saw in the old post you referenced, that winpm-32 is looking for the .pms file in the default home mail box location which normally is the same as the new mail location c:\pmail\mail\&amp;lt;user&amp;gt; or possibly in c:\pmail\mail only with single user mode install. You can not have both at the same time. You either have single user setup or you have multi user mode setup (the default). What does the current PCONFIG show when you run it. Running it will require use of DosBox application or similar to run the 16bit PCONFIG utility on any 64 bit system. PCONFIG runs ok without any other application layer on 32bit OS systems.

The Home Mailbox location and the New Mailbox Location differ because it was decided to move the Home Mailbox Location to a separate drive for space considerations. This option is explained in the Pegasus Help files in the following section:

Preferences and Settings\General Settings\Mailbox Location

The program was initially installed via the default installation setting of Multi-User. This is why the default New Mailbox Location has the user name of Admin. Although the configuration may appear out of the ordinary to you, I believe that it should pose no conflict with Pegasus. In fact, over the past several years during which this configuration has been used, it has not.

As a result of this configuration, however, the .pms file must be placed in the Home Mailbox Location of Z:\PMail\Mail, which it is. This is the way Pegasus was configured on Win XP, 32 prior to the migration to the Win 7, 64 bit environment, and the Variable Signature feature always worked perfectly. It may be that this configuration is incompatible with a Win 7, 64 bit system for some reason, but I am not sure about that. All other features work perfectly. It is only the Variable Signature that is malfunctioning. And even that is only malfunctioning in one aspect of its performance. Namely, attaching a formatted Variable Signature to a new mail message when the

/Add this variant of default signature upon message creation

option is chosen. And please note, as I indicated previously, such a variable signature is properly inserted into a new mail message when it is a reply to a previously received message. So Pegasus is successfully finding the .pms file and acting on it in all other possible scenarios. Is it possible that Pegasus handles the creation of the two types of messages differently in some way that is effecting the insertion of the variable signature?

BTW, I did try relocating the .pms file to the New Mailbox Location of C:\PMAIL\MAIL\Admin. But this did not work. Nor do I believe that it should have. Also, pconfig.exe confirms the mailbox locations extracted from Pegasus' Help\Info screen, as noted above.

&lt;p&gt;The Home Mailbox location and the New Mailbox Location differ because it was decided to move the Home Mailbox Location to a separate drive for space considerations. This option is explained in the Pegasus Help files in the following section:&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;Preferences and Settings\General Settings\Mailbox Location&lt;/strong&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;The program was initially installed via the default installation setting of Multi-User. This is why the default New Mailbox Location has the user name of Admin. Although the configuration may appear out of the ordinary to you, I believe that it should pose no conflict with Pegasus. In fact, over the past several years during which this configuration has been used, it has not.&lt;/p&gt;&lt;p&gt;As a result of this configuration, however, the .pms file must be placed in the Home Mailbox Location of Z:\PMail\Mail, which it is. This is the way Pegasus was configured on Win XP, 32 prior to the migration to the Win 7, 64 bit environment, and the Variable Signature feature always worked perfectly. It may be that this configuration is incompatible with a Win 7, 64 bit system for some reason, but I am not sure about that. All other features work perfectly. It is only the Variable Signature that is malfunctioning. And even that is only malfunctioning in one aspect of its performance. Namely, attaching a formatted Variable Signature to a new mail message when the&lt;/p&gt;&lt;blockquote&gt;&lt;p&gt;&lt;strong&gt;/Add this variant of default signature upon message creation&lt;/strong&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;option is chosen. And please note, as I indicated previously, such a variable signature is properly inserted into a new mail message when it is a reply to a previously received message. So Pegasus is successfully finding the .pms file and acting on it in all other possible scenarios. Is it possible that Pegasus handles the creation of the two types of messages differently in some way that is effecting the insertion of the variable signature?&lt;/p&gt;&lt;p&gt;BTW, I did try relocating the .pms file to the New Mailbox Location of C:\PMAIL\MAIL\Admin. But this did not work. Nor do I believe that it should have. Also, pconfig.exe confirms the mailbox locations extracted from Pegasus&#039; Help\Info screen, as noted above.&lt;/p&gt;

Check this setting:  Tools > Options > Outgoing mail > Message formatting > Disable all text styling options (never send styled mail).  If enabled it might be blocking the insertion of the formatted content variant. 


&lt;p&gt;Check this setting:&amp;nbsp; Tools &amp;gt; Options &amp;gt; Outgoing mail &amp;gt; Message formatting &amp;gt; Disable all text styling options (never send styled mail).&amp;nbsp; If enabled it might be blocking the insertion of the formatted content variant.&amp;nbsp; &lt;/p&gt;&lt;p&gt; &lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft