|
Solution Search:
|
Related Solutions
Adding Exchange Server 2003 email disclaimers
only. Options include going with a third-party solution, such as DisclaimIt, GFI MailEssentials or eXclaimer, or you can implement an event sink as described in Microsoft Knowledge Base Article 317680, How to add a disclaimer to outgoing SMTP messages in Visual Basic script. Since the event sink option...
More...
Sep 20, 2004
How to add a disclaimer to outgoing SMTP messages in Exchange Server 2003
would have to route messages through another SMTP server. One way of doing this is by implementing an SMTP Connector, and registering the event sink on the SMTP server that serves as a bridgehead for that connector.
There are many third-party applications available that do this job better, including the... More... Jun 21, 2006
Zip and encrypt Microsoft Outlook email attachments
encrypted .ZIP files. This makes it relatively easy for programmers to make use of them.
(It might even be possible to write an Exchange Server event sink to automatically extract and decode the attachments, and match against a password stored somewhere in Active Directory.) As with similar products, your... More... Dec 21, 2006
What event log tracks user access to Exchange Server?
Is there a log that provides the time and date a user logged on to the Exchange server? The Local Security event log will tell you who and when a given user logged on to the Exchange server. The Domain Controller Security event log will tell you who logged on to a specific...
More...
Sep 25, 2007
Virtual memory fragmentation in Exchange
large blocks of memory efficiently. When this happens, your Exchange 2000 or 2003 system may eventually throw a warning or error of Event ID 9582, Event ID 9665 or Event ID 12800:
"The virtual memory necessary to run your Exchange server is fragmented in such a way that performance may be affected. It is... More... Jun 27, 2005
Related Expert Advice
Setting a default mailbox in Exchange 5.5
as a way of ensuring you don't lose valuable messages intended for your Exchange users.
With Exchange 2000 and Exchange 2003 you could theoretically write an event sink to achieve this, though you'd need to have great anti-spam software installed to protect your catchall mailbox from abuse. Microsoft... More... Nov 24, 2004
Exchange event sink scripting error when configuring email disclaimer
I'm trying to add a disclaimer to outgoing SMTP email in Exchange Server. After executing the cscript smtpreg.vbs /setprop 1 onarrival SMTPScriptingHost Sink ScriptName "C:EventSinkScript.vbs" command, the following error message appears:
Binding Display Name Specified... More... Aug 20, 2008
Removing old disclaimers from Exchange Server 2003
Dear Will Schmied: What is the best way to remove disclaimers from Exchange Server 2003 that were added years ago with event sinks from the smtpreg.vbs Event Management Script?
You will need to use the smtpreg.vbs script to remove them. Try using cscript... More... Jun 10, 2009
Generating SMTP notifications in Exchange 2000
me in the right direction. I would have a look at the Exchange Server Software Development Kit (SDK), which you can find here. Specifically, you'll want to look into creating an event sink. You can create a transport event sink that can take action, redirect e-mail, generate new messages, etc., when a new message hits the SMTP...
More...
Sep 10, 2003
Create a 'catch-all' mailbox to receive improperly addressed e-mail
to enable this feature.
A second solution is to create a Catchall mailbox. In Create a "Catchall" mailbox sink for Exchange 2000, Microsoft has instructions for creating an event sink that captures e-mail messages sent to a particular domain, and then direct them to a single mailbox. Now, I realize this is not exactly... More... Mar 5, 2003
|