[THIN] Re: Mildly OT/ the disclaimer in Exchange 2003 (or not) from 5.5
- From: "Andrew Wood" <andrew.wood@xxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 5 Dec 2005 13:49:31 -0000
Jim,
You're right about the free GFI disclaimer - have used that in the past. And
it has some anti-spam stuff - but I think there's an add-on now from
Microsoft as part of the latest SP to do some of this functionality.
Pay attention to the note in the MS article :-
Note If you use a MAPI client, such as Microsoft Outlook, to send the e-mail
message, the recipient does not receive a modified e-mail message. This is
because the e-mail message that is submitted by using MAPI is not in an SMTP
format when the e-mail message triggers the SMTP transport event. Therefore,
changes that are made by the code of the event are not persisted.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jim Kenzig http://Kenzig.com
Sent: 05 December 2005 13:27
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Mildly OT/ the disclaimer in Exchange 2003 (or not) from
5.5
Actually I sold the site to Techgenix. I am still hosting thethin.net
content on my servers though.
As far as your problem goes,
I've read that GFI has a disclaimer functionality in their demo version that
remains FREE even after it expires. http://www.gfi.com/mes/
Here is how to build your own with visual basic from MS
http://support.microsoft.com/default.aspx?scid=kb;en-us;317327
<http://support.microsoft.com/default.aspx?scid=kb;en-us;317327&Product=exch
2003> &Product=exch2003
Also check out DisclaimIT http://www.netal.com/disclaimit.htm or eXclaimer
http://www.exclaimer.com/
Jim
Jim Strowe <jstrowe@xxxxxxxxxxxxxxxx> wrote:
Alas, trying to upgrade I find that:
1. The 5.5 Exchange version (with the right resource kit plugin) can do a
disclaimer
2. I am still quite surprised that our friends at Microsoft didn't think
that 2003 needed that feature.
So far I found the "create your own sink" DLL script (that only works for
SMTP mail).
I also found the "force all your mail to be SMTP mail. (elsewise the above
choice does not work.
Would that be the solution....i.e. create the stupid DLL since Microsoft
doesn't, and then force all mail via the connector to go SMTP.?
Jim, if you happen to read this... nice revision on the thin page. (spare
time buddy or what? )
Other related posts:
