I am having issues with --addfile working for Office 2013 clients. It works fine for 2010 but in 2013 the image is linked to a local directory on the senders PC which results in a broken image. We had a much older version of ADOLSIGN (2.0.0) and I downloaded the lastest version to test it. If I run it in a CMD prompt on a 2013 client I get a "No profile information is found" message. This message does not appear for 2010 clients.
- Solutions
- Support
- Frequently Asked Questions
- Documentation
- Videos
- Itefix Labs
- User Forum Archive (2005 - 2016)
- Online store
- Login
Trial version supports up to Office 2010.
I purchased a new license and downloaded the latest version. I'm still having issues with the images partly due to the fact that the directory structure changed and it doesn't look like the new instructions reflect this. Everything seems to be in new folders (bin, dll, doc and lib) so I'm not sure how to rework the script and where to put all of the files. I previously had everything (adolsign.exe, htm files, images) in one directory and my script was the following:
\\server\shared\templates\adolsign.exe --signature mobile -newdefault mobile --addfile logo.png --addfile bar.gif
Now I have the following file struture:
Root Folder
>BIN Folder >> adolsign.exe, makensis.exe, cpfworkrt folder
>DLL Folder
>DOC >> contains shortcut with script
>LIB Folder
>images-directory folder >> logo.png, bar.gif
In the root folder I have my .htm files for the templates. My new script is:
\\server\shared\templates\bin\adolsign.exe --signature mobile -newdefault mobile --addfile images-directory
The signature appears to work but the images appear broken when i send emails to any one.
Try
\\server\shared\templates\bin\adolsign.exe --signature \\server\shared\templates\mobile -newdefault mobile --addfile \\server\shared\templates\images-directory
Same result. I can see the image when I first create the email but it breaks after the email has been sent.
This is an expected behaviour: If you send an html signature with an image link to a local image file in signatures directory, it will not work on the destination as it lacks the same directory structure. You need to create signatures using images available independent of local resources. An http link for global availability or a network file for availability in your internal network. Alternatively, you may consider to send rtf signtures as they contains image information inside.
This only breaks with Office 2013 AND it worked previously before I upgraded to the current version.
There are no changes regarding copying files in the newest version. It seems to be related to Office 2013 itself.