I can remember receiving disclaimers in 4 languages ... the email itself was about 3 lines ... too bad about 50 followed with disclaimer. Vaguely I remember that it was KPMG who had that setup (correct me if I'm wrong). In some countries email still isn't a legitimate format and so a disclaimer won't make any sense nor has it probably and legal value.
You could check some outbound gateway software that can add disclaimers and add them based on rules. ** Please prefix your subject header with BETA for posts dealing with Exchange 2003 ** -------------------------- Martin Tuip MVP Exchange Exchange 2000 List owner www.exchange-mail.org www.sharepointserver.com [EMAIL PROTECTED] -------------------------- ----- Original Message ----- From: "Midgley, Ian" <[EMAIL PROTECTED]> To: "Exchange Discussions" <[EMAIL PROTECTED]> Sent: Wednesday, June 18, 2003 3:06 PM Subject: RE: Brick level backups > That's not funny !! I'm currently involved in discussions with our legal > team regarding the validity of English language disclaimers on messages > written in various different European languages (we route all our Internet > mail through a single SMTP gateway in the UK). The legal team are pushing to > add disclaimers in each language. > > Just because no-one ever reads disclaimers doesn't mean that they are not > legally applicable - when was the last time you read the MS license > agreement when installing software? And just because I select the other > radio button and click OK doesn't mean that I have read the labels attached > to those actions either. > > I would be interested in Williams disclaimer list if he would be happy to > publish. > > Also, does anyone know of a disclaimer adder that is language aware? > Otherwise I'm going to have to do some funny tricks with SMTP connectors and > routing inside the company. > > -----Original Message----- > From: Tony Hlabse [mailto:[EMAIL PROTECTED] > Sent: 18 June 2003 12:21 > To: Exchange Discussions > Subject: RE: Brick level backups > > > That's ok some company will make a 3rd party app I am sure, that will force > you to read or click ok before you actually get to see the email. Hopefully > that won't happen. Probably has just haven't seen it yet. > > > From: "Randal, Phil" <[EMAIL PROTECTED]> > Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> > To: "Exchange Discussions" <[EMAIL PROTECTED]> > Subject: RE: Brick level backups > Date: Wed, 18 Jun 2003 12:55:46 +0100 > > 1: Nobody ever reads them > > 2: Nobody ever reads them > > 3: People read the message, and forget to read the disclaimer > > 4: go to 1 > > Phil > > --------------------------------------------- > Phil Randal > Network Engineer > Herefordshire Council > Hereford, UK > > > -----Original Message----- > > From: Tony Hlabse [mailto:[EMAIL PROTECTED] > > Sent: 18 June 2003 12:54 > > To: Exchange Discussions > > Subject: RE: Brick level backups > > > > > > You have one like this for disclaimers. I know the basics > > why not. I would > > like to see your reasons of why disclaimers are bad. > > > > > > From: "William Lefkovics" <[EMAIL PROTECTED]> > > Reply-To: "Exchange Discussions" <[EMAIL PROTECTED]> > > To: "Exchange Discussions" <[EMAIL PROTECTED]> > > Subject: RE: Brick level backups > > Date: Wed, 18 Jun 2003 03:19:25 -0700 > > > > I probably should reread this, but thwas my answer to this question > A > year ago - plus an added point. > > Why not to do Brick Level Backups: > > > 1) They take a loooong time. At my last position, the priv.edb on > > several Exchange servers was huge with several mailboxes exceeding > 2GB. > Backup windows of 'July' is not acceptible nor necessary. > > 2) Brick > Level break SIS in the process. At a previous employer we > had an SIS > ratio of 4 (lots of little daily cash spreadsheets and the > like getting > sent to DL's). This means that a BLB backup uses as much > as 4 times the > total tape. Now I need an autoloader to take care of > the boxes of tapes > required each night. > > 3) You can't perform a full server restore to > point of failure with > brick level backups. You have to actually perform > additional full > online backups as well to allow for full disaster > recovery. More > tapes. More time. More money. > > 4) A restore of > several mailboxes from BLB's will cause the store to > grow because of no > SIS. If my SIS ratio is 2 and some disaster leaves > me with only > brick-level, my restore will double the size of the priv. > > 5) The > redundant backups for brick level lower the overall performance > of your > exchange server as backups compete with users for CPU cycles > and disk > reads. It is also additional and unnecessary wear and tear > on tape > drives. > > 6) Brick Level Backups do not backup items in deleted item > retention. > As my users (for email anyway) have always been of the > educated > variety, they know and use deleted item recovery as needed. > > > 7) A restore of a mailbox is seldom needed. (Probably the only > instance > is inadvertant deletion by an administrator in Exchange5.5) > With deleted > item retention set to a reasonable 30 days or so, and > with deleted > mailboxes retained in Exchange2000, brick level backups > fall in the > category of a waste of time and resources. > > 8) Backups should not be a > helpdesk support option. They are a > disaster recovery requirement. With > all that tape and time, the > convenience of having someone restore my > mailbox is so simple I can be > more careless with my email. I can always > get my info restored. The > Potential for user complacency because we can > always restore uses > Valuable IT time and resources. > > 9) Yes, it's > true. For me, I have only done this using ArcServeIT. > Because of comments > here in this and other forums, CA took the > Exchange agent back to the lab > and did some more fixing on it. For me > it was too little too late. > Basically, BLB's are not perfect. Data > is not perfectly recreated through > the restore process. Problems > included header info missing, digitally > signed emails corrupt, > attachments missing. > > 10) Many, many more > reputable and experienced people have shared their > horror stories over > and over in this and other forums and newsgroups. > So much so that I was > relieved to learn in 1998 that it wasn't just me > that felt this way. The > people that have expressed this opinion I > hold in high regard and > certainly owe it to myself to try to > understand why the concensus is for > or against something. > > 11) Microsoft provides the utility ExMerge which > can be used to backup > a single mailbox to .pst if necessary. I use this > as the last step > before deleting a users mailbox after (s)he have left > the company. It > is a simplified, granular alternative for certain > circumstances. > > 12) Exchange2003 allows for a disaster recovery storage > group to allow > Production restores without a recovery server. > > The > above may not all apply to you. > > Would you like to see the list against > the use of 'confidentiality > disclaimers'? > > William > > > > > -----Original Message----- > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of David Lloyd > > Sent: Wednesday, June 18, 2003 2:58 AM > To: Exchange Discussions > > Hi > guys, > I just wanted to know why are brick level backups a bad idea. > I > know why pst > files are. > I can only imagine is that they take forever > to complete, and > not always all > of them. > > Sorry if this has been > discussed before but i do need some > reasoning for my > bosses. > > I > know Ed hate em > > > Thnks > > David > > > CONFIDENTIAL NOTICE > > This communication contains useless information which is > confidential and > > may also be naughty. It is for the exclusive use of the intended > > recipient(s). If you are not the intended recipient please > note that any > > distribution, copying or use of this communication or the > information > in it > is strictly prohibited. If you received this communication in > > error, please > notify us by e-mail or by telephone (020 7770 7000) and > then > delete the > e-mail and any copies of it. > > > > > _________________________________________________________________ > > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > > Web Interface: > > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&t > ext_mode=&lang=english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > The new MSN 8: advanced junk mail protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang > =english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang > =english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > The new MSN 8: advanced junk mail protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: > http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang > =english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > > ********************************************************************** > This e-mail and any files transmitted with it are confidential > to the intended recipient(s). If you have received the e-mail > in error please notify the author by replying to this e-mail > and delete it and all copies from your system. Any unauthorised > disclosure, use, or dissemination, either whole or partial, is > prohibited. Any views or opinions contained in this email are > those of the author and are not necessarily endorsed by The Company, > and The Company cannot be held responsible for any misuse. > The Company does not accept responsibility or liability for any loss > or damage arising in any way from its receipt or use or for any errors > or omissions in its contents, which may arise as a result of its transmission. > This email is covered by The Company Terms and Conditions of Business, > a copy of which can be obtained on request. > ********************************************************************** > ********************************************************************** > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
