I know this thread is several years old but...

I was also using headers.dll, headers.fff & headers.pm successfully until recently (inside the last year).

However I am now running 4.70 and no headers from headers.pm appear in outgoing emails.

I can see the headers DLL in extensions manager and reporting is set to 4. 

Does this DLL not work under new versions of Pegasus?

I am familiar with the customs header facility and also the recently used list, so its easy to include a header without re-typing.

However its also far to easy to forget to include a custom header - the setting is not sticky. 

Hello,

am I the only who has problems with GRT's Headers extension? It does not seem to work anymore for me since Pegasus v4.51.

[quote user="rogers"]

Hello,

am I the only who has problems with GRT's Headers extension? It does not seem to work anymore for me since Pegasus v4.51.

[/quote]

This feature is built in into the progam for a long time AFAIK. When you write a message, in the special pane you can add headers either by using previous ones or create a new one. When it's a reply the original  X- headers are shown there as well.

[quote user="Han v.d. Bogaerde"]

This feature is built in into the progam for a long time AFAIK. When you write a message, in the special pane you can add headers either by using previous ones or create a new one. When it's a reply the original  X- headers are shown there as well.[/quote]

It's not the same, because one has to add additional headers for each new message again. The "Headers extension" did this automatically.

[quote user="rogers"]

The "Headers extension" did this automatically.

[/quote]

Do you see that the headers.dll as a Loading Extension in System Messages?

The extension functions correctly with v4.52

Note:
 System message reporting level must be 4 (or 5) at:

Tools > Options | User interface > Reporting/logging | System messages, and logging

Sorry for the late reply, did not see the answer.

The extension is loaded. The PM-file in my mailbox-dir is like before (the "..." are placeholders):