Probably Telephone Message does predate both Identities and multiple signatures and that is why it uses INETSIG.P[M|N]S; it was the only signature file. Its a useful shortcut for phone messages in a shared office environment but it would be even better if it respected Identities and their attached signatures!

So not really a bug, more a limited feature set.

When I write & send an email via the Telephone Message extension, the signature used is an old one not related to the identity of the current user. Its not the identity of the <default> either, but it was the signature in use for <default> some time ago. If I send a standard email from the identity in use, I get the signature assigned to that identity as expected. The name of the old signature being wrongly assigned to the Telephone Message does not apear anywhere in pmail.ini.

I checked the signature files in \pmail\mail\<user>. The format is INETSIG<2-9>.P[M|N]S except for the first one, which is just INETSIG.P[M|N]S. Removing (by renaming) this file means Telephone Message includes no signature at all. So it seems Telephone Message uses the signature from INETSIG.P[M|N]S no matter which identity is in use, so I will have to change INETSIG.P[M|N]S to a signature that covers all my email identities (so no phone number of email address) or use no signature at all by removing INETSIG.P[M|N]S.

Anyone else run into this issue?

I believe the first signature set is always used by the telephone message because mine is named "telephone_msg".   I stopped using signatures years ago so must have figured this out sometime before then.

I don't know what the date for the telephone message is at present, but I am unaware of any recent upgrades to it.  It wasoroginally written in BorlandC  and I don't think it was reworked into Microsoft Visual C.

Also I was unaware that it had any support for Identities, but probably defaulted to the first entry.

Martin