Manage Email Signatures Centrally - For All Users

Bjarne Mess

This will only happen when upgrading to version 4.8.7 and you are using another data source than Active Directory.

The reason for this is performance improvements where reuse of data don't automatically show up in this version.

Please follow these simple steps to get it working again.

Open the Data Source Manager and select your data source. Save the data source after having verified it and selected your table for identification again.

You might need to expand field 'custom_str3' in table 'General', but the Cockpit will inform about that.

After you now run sign.exe, your RTF and TEXT signatures are working again.
_________________
</Bjarne> | Test Email Signature | Showcase |

John Martin · Posted: Wed Nov 07, 2007 10:44 am Post subject: Same problem, not fixed for me

I'm on release 4.9.1 and see the same issue when using a contact database other than AD. Resetting the database doesn't help.

Any other ideas? This seems to be the last step in our evaluation process and it's holding back our deployment.

Bjarne Mess · Posted: Wed Nov 07, 2007 11:59 am Post subject:

Which database are you using?

Please try to delete the last field in the rtf signature as they are usually causing trouble. Especially if you see a square at the end of the code or something like that.

John Martin · Posted: Wed Nov 07, 2007 12:04 pm Post subject:

>> What database?

SQL 2005

>> Please try to delete the last field in the rtf signature

Done many, many iterations already with the RTF and Plain text. Spaces, linebreaks and hard-coded text are all coming through just fine. Only the database values are not.

Here's the RTF code that's failing right now:

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fcharset0 Tahoma;}}
{\*\generator Msftedit 5.41.15.1507;}\viewkind4\uc1\pard\b\f0\fs17 ((fullname))\b0 $$NULL(title)$$VALUE(, ((title)) )$$\par
McGlinchey Stafford PLLC\par
$$NULL(direct)$$VALUE(Direct: ((direct)) )$$\par
$$NULL(mobile)$$VALUE(Cell: ((mobile)) )$$\par
$$NULL(fax)$$VALUE(Fax: ((fax)) )$$\par
$$NULL(email)$$VALUE(Email: ((email)) )$$ \par
\par
((address))\par
((csz))\par
$$NULL(maddress)$$VALUE(\par
((maddress))\par
)$$$$NULL(mcsz)$$VALUE( ((mcsz))\par
\pard )$$\fs17
}

BTW, it previews just fine. The issue is it won't deploy.

All I get in the deployed signature is the "McGlinchey Stafford PLLC" text and a bunch of linebreaks and spaces.

John Martin · Posted: Wed Nov 07, 2007 12:17 pm Post subject:

I'm using your default Access settings database.

The custom_str5 field is TEXT with a current length of 250.

TEXT fields have a maximum of 255.

Can I change it to MEMO?

Bjarne Mess · Posted: Wed Nov 07, 2007 12:19 pm Post subject:

Yes please try to do that.

John Martin · Posted: Wed Nov 07, 2007 3:44 pm Post subject:

Thanks to Jesper Frier... database field names are case sensitive in RTF and TEXT when accessed by SIGN.EXE. All other cases (HTML and also PREVIEW for all types) are not case-sensitive.

I synched the case of all my field names and, viola, it's working.

Bjarne Mess · Posted: Wed Nov 07, 2007 3:50 pm Post subject:

I'm glad you got it to work now.

Thanks,
Bjarne

Jesper Frier

Thank you for your patience John!

I shall take this issue to the feature request and see if we can avoid this issue another time.

Cheers
Jesper