Manage Email Signatures centrally from your Desktop - For All Users

robert doku

We are having problems deploying signowa. I have searched the forum for solutions, and used the normal debugging processes unsuccessfully.

The signowa.reg contains the following:
"OWAssl"="1"
"OWAfba"="0"
"OWAurl"="webmail.ourcompany.co.uk/exchange"
"Settingsdatabase"="\\\\serversharepath\\sharepath\\settings.mdb"

We are using a "Run As" option with an account with "Received As" rights to the mailstore.

we don't use a proxy server for internal access.

We have an ISA 2400 firewall configured for Basic authentication. The error message seem to suggest that the credentials are passed by the isa server but are not passed to the exchange server which then rejects the credentials:
The error message with "signowa -v" is:

Using the url:
https://webmail.ourcompany.co.uk/exchange
Setting signature for user: rd02
Mailbox name: Robin.Davies
Sending HTTP request to: https://webmail.ourcompany.co.uk/exchange/robin.davies/

The remote server returned an error: <401> Unauthorized.

I though the name resolution from rd02 to Robin.Davies is significant.

Members of our server team are insisting that emailSignature does not support Basic Authentication. Any thoughts on this matter?
_________________
RobD

robert doku · Posted: Thu Jul 03, 2008 2:40 pm Post subject:

I will like to hear from anyone who has implemented emailSignature in a domain with ISA2400 firewall, whether successfully or not. Thanks
_________________
RobD

Bjarne Mess · Posted: Tue Mar 30, 2010 2:44 pm Post subject:

There is never the need to use proxy internally. Please provide the internal address of the Exchange server and not the external and/or force the traffic to stay inside the firewall or proxy server.