Manage Email Signatures centrally from your Desktop - For All Users

jontheeye · Posted: Wed Nov 12, 2008 5:47 pm Post subject: signowa and mailbox names

Hi

I have a problem with signowa, when I tried to deploy it for the administrator it all worked fine. However, changing to a real user didn't work.
Some how the "mailbox name" and the "login name" have got mixed up.

This is what signowa said:

----------------
C:\emailsignature\signowa>SignOWA.exe -v
Using the url: https://mydomain.co.uk/exchange/
Setting signature for user: CNC_CHRIS
Mailbox name: chris
Sending HTTP request to: https://mydomain.co.uk/exchange/chris/
The remote server returned an error: (404) Not Found.
----------------

Clearly the "mailbox name" is wrong, it should be "cnc_chris".

Does the account login name have to be their first name?

Thanks
Jon

jontheeye · Posted: Thu Nov 13, 2008 12:13 pm Post subject:

I have a workaround for this issue, but it is very limiting and I now have another problem.

Our end-users log in as <code>_firstname. Where the code is something we issue.

So mike @ IBM would log in as ibm_mike, where as their primary email address would be mike@ibm.com.

Signowa seems to think the "mailbox name" is mike, where as it should see it as "ibm_mike". I am not sure in the context of Exchange server why the mailbox name isn't the account name. Problem is the end user won't want recipients to see their login name in their emails. So for my user, I changed their primary email address to cnc_chris@thedomain.co.uk.

And the the new problem is a "440 Login Timeout", which comes up instantly.

signowa.exe -v returns:

Using the url: https://mydomain.co.uk/exchange/
Setting signature for user: CNC_CHRIS
Mailbox name: cnc_chris
Sending HTTP request to: https://mydomain.co.uk/exchange/cnc_chris/
The remote server returned an error: (440) Login Timeout.

If I switch back to my administrator user - it works.

Any help aprreciated.
Jon

Bjarne Mess · Posted: Thu Nov 13, 2008 4:36 pm Post subject:

Signowa runs throug all users in the database, so I believe that it you meet a 'chris' it will try to look him up in Exchange to find the Exchange path for the user.

When you say you switch back to the admin user, do you actuaslly mean that you run signowa as another user, or do you in both cases run signowa with the right credentials every time?

Thanks,
Bjarne

jontheeye · Posted: Thu Nov 13, 2008 5:22 pm Post subject:

Hi Bjarne

Thanks for looking at this.

I am doing this all on the live Exchange server
I am editing the OWAUsers key, "ADMINISTRATOR, CNC_CHRIS"
SignOWA works fine for Administrator, not for the actual user I want it to work for.
I am logging in as the user and running sign.exe (from the cockpit menu) then signowa, to try and make it deploy.

Have I got something wrong in the sequence?
Jon

Bjarne Mess · Posted: Thu Nov 13, 2008 9:08 pm Post subject:

Please try to do the following:

Log on as administrator, and make sure that signowa works for you. Please also make sure that 'settingsdatabase' is pointing to the correct database.

The users signowa will walk through are the users in the lgdaUsers table. Now - as logged on ad amin - and run sigowa -v. Doesn't it deploy to OWA now?

Cheers

jontheeye · Posted: Wed Nov 19, 2008 3:49 pm Post subject:

Hi Bjarne

"mailbox name" is the problem. I don't know why, but it looks like it has to be the username part of the default email address.

I *have* managed to get it to deploy if the login name and "mailbox name" are the same.

Here is the output from signowa.exe -v (I have changed the url)
----------------------
C:\emailsignature\signowa>signowa -v
Using the url: https://mail.co.uk/exchange/
Setting signature for user: CNC_MIKE
Mailbox name: mike.jennings
Sending HTTP request to: https://mail.co.uk/exchange/mike.jennings/
The remote server returned an error: (404) Not Found.
-----------------------

This is really irratating as it prevents us from purchasing it.
Jon

Jakob Christensen · Posted: Wed Nov 19, 2008 7:18 pm Post subject:

SignOWA uses the global catalog for Active Directory to find the mail box name. In your example it locates the user having SAMAccountName = "CNC_MIKE" in AD and retrieves "mike.jennings" from the "mail" attribute in AD.

Kind regards, Jakob.

witwicki · Quite a regular Joined: 03 Jun 2009 Posts: 14 Location: UK

My mailbox names are the same as the SAMaccount name,

How can i get this to work at the moment signOWA.exe is returning the first part of mail attribute and it dosnt match the mailbox name

Thanks

Adam Witwicki

Bjarne Mess · Posted: Mon Jun 29, 2009 11:29 am Post subject:

Please make sure that WEBDAV is enabled on the website and Exchange Server. Also please make sure that you are using the latest version of the dll and exe (currently 3.3.2.1)

Does that work for you?

Thanks, Bjarne

witwicki · Quite a regular Joined: 03 Jun 2009 Posts: 14 Location: UK

Hello,

I check my webdav settings, they were set to prohibited, I have now allowed webdav and the signatures are applied correctly.

Thanks
Adam