Re: Distribution lists

[James Rankin]

That is actually a fine idea

2009/7/13 Kurt Buff 

> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
> > +1
> >
> >
> >
> > You have given them the recommendation and they have decided. Let it go,
> > move on and ignore the emails in the future. You may be sick of them but
> > management is not. Yet.
> >
> >
> >
> >
> >
> >
> >
> > From: Matt Moore [mailto:mattmoore...@hotmail.com]
> > Sent: Monday, July 13, 2009 11:22 AM
> > To: MS-Exchange Admin Issues
> > Subject: RE: Distribution lists
> >
> >
> >
> > In that case my advice is to turn a blind eye and let those execs worry
> > about it.  If it’s un-monitored, it’s just that.  No worries.
> >
> > M
> >
> >
> >
> > 
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Monday, July 13, 2009 7:20 AM
> > To: MS-Exchange Admin Issues
> > Subject: Re: Distribution lists
> >
> >
> >
> > I would if I could, but I can't. Not until some idiot sends something
> that
> > gets on one of the exec team's nerves. Just wondering if there was any
> other
> > way I could spare myself some pain.
> >
> > I know the old adage about technological solutions to behavioural
> problems,
> > though, it has never rung truer
> >
> > 2009/7/13 Matt Moore 
> >
> > Limit access to a chosen few and all the spam goes away.
> >
> > M
> >
> >
> >
> > 
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Monday, July 13, 2009 7:07 AM
> >
> > To: MS-Exchange Admin Issues
> > Subject: Distribution lists
> >
> >
> >
> > Afternoon Exchange gurus
> >
> > Is it possible to have the "All Staff" distribution list (or any other,
> > really) set up so that when an email is sent to it, it goes to an
> > administrator for approval first? I am sick of getting emails that say
> > "there is a salesman selling cards in reception" and when someone spammed
> > the DL with a hoax that was well-documented on snopes.com, I ended up
> > getting a reprimand from my boss about being harsh to users. I only
> > threatened to remove her ability to send to the DL. Sheesh. I know that
> we
> > shouldn't give all users the ability to send to it, but I doubt I am
> going
> > to shift my boss's boss's stance on this one.
> >
> > Any other pointers would be also gratefully received, I am not much of an
> > Exchange bod.
> >
> > TIA,
> >
> >
> > JRR
> >
> > --
> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> > the machine wrong figures, will the right answers come out?' I am not
> able
> > rightly to apprehend the kind of confusion of ideas that could provoke
> such
> > a question."
> >
> > http://raythestray.blogspot.com
> >
> > Checked by AVG - www.avg.com
> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> > 17:56:00
> >
> >
> > --
> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> > the machine wrong figures, will the right answers come out?' I am not
> able
> > rightly to apprehend the kind of confusion of ideas that could provoke
> such
> > a question."
> >
> > http://raythestray.blogspot.com
> >
> > Checked by AVG - www.avg.com
> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> > 17:56:00
>
>
>


-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

http://raythestray.blogspot.com

RE: E-mail address display question

[Sobey, Richard A]

This could be an issue with Outlook knowing the cached entry for the old 
display name. Try deleting it from your autocomplete list.

If you've  resolved this already, I wasn't here, right.

From: bounce-8596460-8066...@lyris.sunbelt-software.com 
[mailto:bounce-8596460-8066...@lyris.sunbelt-software.com] On Behalf Of Joe 
Heaton
Sent: 13 July 2009 19:26
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

Ok, so I did that change, and if I'm looking through the GAL, it shows 
correctly, but when I sent a test e-mail as that account, it still displayed 
incorrectly in my Inbox.

Joe Heaton
Employment Training Panel

From: Carl Houseman [mailto:c.house...@gmail.com]
Sent: Monday, July 13, 2009 11:09 AM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

Change the "display name" to whatever you want.

Carl

From: Joe Heaton [mailto:jhea...@etp.ca.gov]
Sent: Monday, July 13, 2009 1:54 PM
To: MS-Exchange Admin Issues
Subject: E-mail address display question

Is it possible to display three names in the From section?

I see mine, and most everyone's as Firstname Lastname.  I need to have one 
account here display as First Second Last.  How can I do this?

Joe Heaton
AISA
Employment Training Panel
1100 J Street, 4th Floor
Sacramento, CA  95814
(916) 327-5276
jhea...@etp.ca.gov

RE: Distribution lists

[Carl Houseman]

Think it through.  If you do it from somebody's machine who would have been
allowed to use the DL, such as an executive, it doesn't help at all.   Not
to mention, it will probably be found out that it was keyboard-jacking, and
not employee abuse of the DL, and the result will be mandated
password-protected screen savers throughout.

 

Carl

 

From: James Rankin [mailto:kz2...@googlemail.com] 
Sent: Tuesday, July 14, 2009 3:47 AM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

 

That is actually a fine idea

2009/7/13 Kurt Buff 

This is an easy fix.

Find (or compose) a silly email on someone else's non-attended,
non-screensavered machine, and send it to the all users list.

One of my favorites is to announce candy or cookies at the victim's desk.

Be sure to wipe up for fingerprints afterward, if you happen to do it
to an executive, though.

Heh.


On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
wrote:
> +1
>
>
>
> You have given them the recommendation and they have decided. Let it go,
> move on and ignore the emails in the future. You may be sick of them but
> management is not. Yet.
>
>
>
>
>
>
>
> From: Matt Moore [mailto:mattmoore...@hotmail.com]
> Sent: Monday, July 13, 2009 11:22 AM
> To: MS-Exchange Admin Issues
> Subject: RE: Distribution lists
>
>
>
> In that case my advice is to turn a blind eye and let those execs worry
> about it.  If it's un-monitored, it's just that.  No worries.
>
> M
>
>
>
> 
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Monday, July 13, 2009 7:20 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> I would if I could, but I can't. Not until some idiot sends something that
> gets on one of the exec team's nerves. Just wondering if there was any
other
> way I could spare myself some pain.
>
> I know the old adage about technological solutions to behavioural
problems,
> though, it has never rung truer
>
> 2009/7/13 Matt Moore 
>
> Limit access to a chosen few and all the spam goes away.
>
> M
>
>
>
> 
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Monday, July 13, 2009 7:07 AM
>
> To: MS-Exchange Admin Issues
> Subject: Distribution lists
>
>
>
> Afternoon Exchange gurus
>
> Is it possible to have the "All Staff" distribution list (or any other,
> really) set up so that when an email is sent to it, it goes to an
> administrator for approval first? I am sick of getting emails that say
> "there is a salesman selling cards in reception" and when someone spammed
> the DL with a hoax that was well-documented on snopes.com, I ended up
> getting a reprimand from my boss about being harsh to users. I only
> threatened to remove her ability to send to the DL. Sheesh. I know that we
> shouldn't give all users the ability to send to it, but I doubt I am going
> to shift my boss's boss's stance on this one.
>
> Any other pointers would be also gratefully received, I am not much of an
> Exchange bod.
>
> TIA,
>
>
> JRR
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke
such
> a question."
>
> http://raythestray.blogspot.com
>
> Checked by AVG - www.avg.com
> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> 17:56:00
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke
such
> a question."
>
> http://raythestray.blogspot.com
>
> Checked by AVG - www.avg.com
> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> 17:56:00






-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

http://raythestray.blogspot.com

Re: Distribution lists

[James Rankin]

I wasn't actually being serious. I just neglected to attach the prerequisite
smiley

2009/7/14 Carl Houseman 

>  Think it through.  If you do it from somebody's machine who would have
> been allowed to use the DL, such as an executive, it doesn't help at all.
> Not to mention, it will probably be found out that it was keyboard-jacking,
> and not employee abuse of the DL, and the result will be mandated
> password-protected screen savers throughout.
>
>
>
> Carl
>
>
>
> *From:* James Rankin [mailto:kz2...@googlemail.com]
> *Sent:* Tuesday, July 14, 2009 3:47 AM
>
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Distribution lists
>
>
>
> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
> > +1
> >
> >
> >
> > You have given them the recommendation and they have decided. Let it go,
> > move on and ignore the emails in the future. You may be sick of them but
> > management is not. Yet.
> >
> >
> >
> >
> >
> >
> >
> > From: Matt Moore [mailto:mattmoore...@hotmail.com]
> > Sent: Monday, July 13, 2009 11:22 AM
> > To: MS-Exchange Admin Issues
> > Subject: RE: Distribution lists
> >
> >
> >
> > In that case my advice is to turn a blind eye and let those execs worry
> > about it.  If it’s un-monitored, it’s just that.  No worries.
> >
> > M
> >
> >
> >
> > 
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Monday, July 13, 2009 7:20 AM
> > To: MS-Exchange Admin Issues
> > Subject: Re: Distribution lists
> >
> >
> >
> > I would if I could, but I can't. Not until some idiot sends something
> that
> > gets on one of the exec team's nerves. Just wondering if there was any
> other
> > way I could spare myself some pain.
> >
> > I know the old adage about technological solutions to behavioural
> problems,
> > though, it has never rung truer
> >
> > 2009/7/13 Matt Moore 
> >
> > Limit access to a chosen few and all the spam goes away.
> >
> > M
> >
> >
> >
> > 
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Monday, July 13, 2009 7:07 AM
> >
> > To: MS-Exchange Admin Issues
> > Subject: Distribution lists
> >
> >
> >
> > Afternoon Exchange gurus
> >
> > Is it possible to have the "All Staff" distribution list (or any other,
> > really) set up so that when an email is sent to it, it goes to an
> > administrator for approval first? I am sick of getting emails that say
> > "there is a salesman selling cards in reception" and when someone spammed
> > the DL with a hoax that was well-documented on snopes.com, I ended up
> > getting a reprimand from my boss about being harsh to users. I only
> > threatened to remove her ability to send to the DL. Sheesh. I know that
> we
> > shouldn't give all users the ability to send to it, but I doubt I am
> going
> > to shift my boss's boss's stance on this one.
> >
> > Any other pointers would be also gratefully received, I am not much of an
> > Exchange bod.
> >
> > TIA,
> >
> >
> > JRR
> >
> > --
> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> > the machine wrong figures, will the right answers come out?' I am not
> able
> > rightly to apprehend the kind of confusion of ideas that could provoke
> such
> > a question."
> >
> > http://raythestray.blogspot.com
> >
> > Checked by AVG - www.avg.com
> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> > 17:56:00
> >
> >
> > --
> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> > the machine wrong figures, will the right answers come out?' I am not
> able
> > rightly to apprehend the kind of confusion of ideas that could provoke
> such
> > a question."
> >
> > http://raythestray.blogspot.com
> >
> > Checked by AVG - www.avg.com
> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> > 17:56:00
>
>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke such
> a question."
>
> http://raythestray.blogspot.com
>



-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

http://raythestray.blogspot.com

Re: Distribution lists

[Kevin Lundy]

We do that within my IT department.  If you leave the  IT department without
locking your computer, anyone else is free to send an email from your
computer to the whole department announcing it is your privilage to bring
doughnuts/bagels/cookies the next day.  Doesn't matter if you are only
stepping out for 30 seconds.  Your screen better be locked.  It forms good
habits.  I don't believe we have had a "violation" in well over a year.  But
we have a new help desk employee, I'm sure he'll get nabbed :)

On Mon, Jul 13, 2009 at 1:30 PM, Kurt Buff  wrote:

> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
> > +1
> >
> >
> >
> > You have given them the recommendation and they have decided. Let it go,
> > move on and ignore the emails in the future. You may be sick of them but
> > management is not. Yet.
> >
> >
> >
> >
> >
> >
> >
> > From: Matt Moore [mailto:mattmoore...@hotmail.com]
> > Sent: Monday, July 13, 2009 11:22 AM
> > To: MS-Exchange Admin Issues
> > Subject: RE: Distribution lists
> >
> >
> >
> > In that case my advice is to turn a blind eye and let those execs worry
> > about it.  If it’s un-monitored, it’s just that.  No worries.
> >
> > M
> >
> >
> >
> > 
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Monday, July 13, 2009 7:20 AM
> > To: MS-Exchange Admin Issues
> > Subject: Re: Distribution lists
> >
> >
> >
> > I would if I could, but I can't. Not until some idiot sends something
> that
> > gets on one of the exec team's nerves. Just wondering if there was any
> other
> > way I could spare myself some pain.
> >
> > I know the old adage about technological solutions to behavioural
> problems,
> > though, it has never rung truer
> >
> > 2009/7/13 Matt Moore 
> >
> > Limit access to a chosen few and all the spam goes away.
> >
> > M
> >
> >
> >
> > 
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Monday, July 13, 2009 7:07 AM
> >
> > To: MS-Exchange Admin Issues
> > Subject: Distribution lists
> >
> >
> >
> > Afternoon Exchange gurus
> >
> > Is it possible to have the "All Staff" distribution list (or any other,
> > really) set up so that when an email is sent to it, it goes to an
> > administrator for approval first? I am sick of getting emails that say
> > "there is a salesman selling cards in reception" and when someone spammed
> > the DL with a hoax that was well-documented on snopes.com, I ended up
> > getting a reprimand from my boss about being harsh to users. I only
> > threatened to remove her ability to send to the DL. Sheesh. I know that
> we
> > shouldn't give all users the ability to send to it, but I doubt I am
> going
> > to shift my boss's boss's stance on this one.
> >
> > Any other pointers would be also gratefully received, I am not much of an
> > Exchange bod.
> >
> > TIA,
> >
> >
> > JRR
> >
> > --
> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> > the machine wrong figures, will the right answers come out?' I am not
> able
> > rightly to apprehend the kind of confusion of ideas that could provoke
> such
> > a question."
> >
> > http://raythestray.blogspot.com
> >
> > Checked by AVG - www.avg.com
> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> > 17:56:00
> >
> >
> > --
> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> > the machine wrong figures, will the right answers come out?' I am not
> able
> > rightly to apprehend the kind of confusion of ideas that could provoke
> such
> > a question."
> >
> > http://raythestray.blogspot.com
> >
> > Checked by AVG - www.avg.com
> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
> > 17:56:00
>
>
>

Re: Distribution lists

[Eric Woodford]

Had a manager who loved to send "I Like Cake" from anyone's unlocked PC (at
least in the IT dept). Taught my co-workers to lock their PCs.

On Tue, Jul 14, 2009 at 12:46 AM, James Rankin wrote:

> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
>> This is an easy fix.
>>
>> Find (or compose) a silly email on someone else's non-attended,
>> non-screensavered machine, and send it to the all users list.
>>
>> One of my favorites is to announce candy or cookies at the victim's desk.
>>
>> Be sure to wipe up for fingerprints afterward, if you happen to do it
>> to an executive, though.
>>
>> Heh.
>>
>> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
>> wrote:
>> > +1
>> >
>> >
>> >
>> > You have given them the recommendation and they have decided. Let it go,
>> > move on and ignore the emails in the future. You may be sick of them but
>> > management is not. Yet.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> > Sent: Monday, July 13, 2009 11:22 AM
>> > To: MS-Exchange Admin Issues
>> > Subject: RE: Distribution lists
>> >
>> >
>> >
>> > In that case my advice is to turn a blind eye and let those execs worry
>> > about it.  If it’s un-monitored, it’s just that.  No worries.
>> >
>> > M
>> >
>> >
>> >
>> > 
>> >
>> > From: James Rankin [mailto:kz2...@googlemail.com]
>> > Sent: Monday, July 13, 2009 7:20 AM
>> > To: MS-Exchange Admin Issues
>> > Subject: Re: Distribution lists
>> >
>> >
>> >
>> > I would if I could, but I can't. Not until some idiot sends something
>> that
>> > gets on one of the exec team's nerves. Just wondering if there was any
>> other
>> > way I could spare myself some pain.
>> >
>> > I know the old adage about technological solutions to behavioural
>> problems,
>> > though, it has never rung truer
>> >
>> > 2009/7/13 Matt Moore 
>> >
>> > Limit access to a chosen few and all the spam goes away.
>> >
>> > M
>> >
>> >
>> >
>> > 
>> >
>> > From: James Rankin [mailto:kz2...@googlemail.com]
>> > Sent: Monday, July 13, 2009 7:07 AM
>> >
>> > To: MS-Exchange Admin Issues
>> > Subject: Distribution lists
>> >
>> >
>> >
>> > Afternoon Exchange gurus
>> >
>> > Is it possible to have the "All Staff" distribution list (or any other,
>> > really) set up so that when an email is sent to it, it goes to an
>> > administrator for approval first? I am sick of getting emails that say
>> > "there is a salesman selling cards in reception" and when someone
>> spammed
>> > the DL with a hoax that was well-documented on snopes.com, I ended up
>> > getting a reprimand from my boss about being harsh to users. I only
>> > threatened to remove her ability to send to the DL. Sheesh. I know that
>> we
>> > shouldn't give all users the ability to send to it, but I doubt I am
>> going
>> > to shift my boss's boss's stance on this one.
>> >
>> > Any other pointers would be also gratefully received, I am not much of
>> an
>> > Exchange bod.
>> >
>> > TIA,
>> >
>> >
>> > JRR
>> >
>> > --
>> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
>> into
>> > the machine wrong figures, will the right answers come out?' I am not
>> able
>> > rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> > a question."
>> >
>> > http://raythestray.blogspot.com
>> >
>> > Checked by AVG - www.avg.com
>> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
>> 07/12/09
>> > 17:56:00
>> >
>> >
>> > --
>> > "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
>> into
>> > the machine wrong figures, will the right answers come out?' I am not
>> able
>> > rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> > a question."
>> >
>> > http://raythestray.blogspot.com
>> >
>> > Checked by AVG - www.avg.com
>> > Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
>> 07/12/09
>> > 17:56:00
>>
>>
>>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke such
> a question."
>
> http://raythestray.blogspot.com
>

RE: Distribution lists

[PRamatowski]

Unlocked pc?  That's a themeing.  As attachments are banned,

Step 1 - Put the following into notepad.
Step 2 - Save as whatever.theme,
Step 3 - Profit!

; Copyright © Microsoft Corp. 1995-2001

[Theme]
displayna...@themeui.dll,-2016

; My Computer
[CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\DefaultIcon]
DefaultValue=%WinDir%explorer.exe,0

; My Documents
[CLSID\{450D8FBA-AD25-11D0-98A8-0800361B1103}\DefaultIcon]
DefaultValue=%WinDir%SYSTEM32\mydocs.dll,0

; My Network Places
[CLSID\{208D2C60-3AEA-1069-A2D7-08002B30309D}\DefaultIcon]
DefaultValue=%WinDir%SYSTEM32\shell32.dll,17

; Recycle Bin
[CLSID\{645FF040-5081-101B-9F08-00AA002F954E}\DefaultIcon]
full=%WinDir%SYSTEM32\shell32.dll,32
empty=%WinDir%SYSTEM32\shell32.dll,31



[Control Panel\Colors]
ActiveTitle=0 0 0
Background=255 255 0
Hilight=0 0 0
HilightText=255 255 255
TitleText=255 255 255
Window=255 255 0
WindowText=0 0 0
Scrollbar=255 128 128
InactiveTitle=255 0 0
Menu=255 255 255
WindowFrame=255 255 255
MenuText=0 0 0
ActiveBorder=255 0 0
InactiveBorder=255 0 0
AppWorkspace=255 0 0
ButtonFace=255 0 0
ButtonShadow=170 0 0
GrayText=192 192 192
ButtonText=255 255 255
InactiveTitleText=255 255 255
ButtonHilight=255 128 128
ButtonDkShadow=255 255 255
ButtonLight=255 0 0
InfoText=255 255 0
InfoWindow=0 0 0
GradientActiveTitle=0 0 255


[Control Panel\Cursors]
Arrow=
Help=
AppStarting=
Wait=
NWPen=
No=
SizeNS=
SizeWE=
Crosshair=
IBeam=
SizeNWSE=
SizeNESW=
SizeAll=
UpArrow=
DefaultValue=Windows default
defaultvalue.m...@themeui.dll,-2043

[Control Panel\Desktop]
Wallpaper=
TileWallpaper=0
WallpaperStyle=2
Pattern=
ScreenSaveActive=0

[Control Panel\Desktop\WindowMetrics]

[Metrics]
IconMetrics=76 0 0 0 139 0 0 0 139 0 0 0 1 0 0 0 245 255 255 255 0 0 0 0 0 0 0 
0 0 0 0 0 144 1 0 0 0 0 0 0 0 0 0 0 84 97 104 111 109 97 0 119 0 0 7 0 0 0 0 0 
216 31 7 0 28 52 1 1 216 31 7 0 176 36 1 1 
NonclientMetrics=84 1 0 0 1 0 0 0 16 0 0 0 16 0 0 0 18 0 0 0 18 0 0 0 245 255 
255 255 0 0 0 0 0 0 0 0 0 0 0 0 188 2 0 0 0 0 0 0 0 0 0 0 84 97 104 111 109 97 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12 0 0 0 15 0 0 0 245 255 
255 255 0 0 0 0 0 0 0 0 0 0 0 0 188 2 0 0 0 0 0 0 0 0 0 0 84 97 104 111 109 97 
0 0 80 37 11 0 0 0 0 0 140 221 6 0 227 115 247 119 2 40 11 0 7 0 0 0 18 0 0 0 
18 0 0 0 245 255 255 255 0 0 0 0 0 0 0 0 0 0 0 0 144 1 0 0 0 0 0 0 0 0 0 0 84 
97 104 111 109 97 0 0 0 0 0 0 60 222 6 0 50 71 252 119 120 1 7 0 76 73 252 119 
8 6 7 0 245 255 255 255 0 0 0 0 0 0 0 0 0 0 0 0 144 1 0 0 0 0 0 0 0 0 0 0 84 97 
104 111 109 97 0 119 0 0 7 0 120 1 7 0 120 1 7 0 40 37 11 0 120 1 7 0 120 1 7 0 
245 255 255 255 0 0 0 0 0 0 0 0 0 0 0 0 144 1 0 0 0 0 0 0 0 0 0 0 84 97 104 111 
109 97 0 0 92 1 0 0 136 4 0 0 40 37 1 1 0 0 7 0 184 221 6 0 46 75 232 119 
captionfo...@themeui.dll,-2037
smcaptionfo...@themeui.dll,-2038
menufo...@themeui.dll,-2039
statusfo...@themeui.dll,-2040
messagefo...@themeui.dll,-2041
iconfo...@themeui.dll,-2042

[boot]
SCRNSAVE.EXE=%WinDir%\System32\logon.scr


[MasterThemeSelector]
MTSM=DABJDKT
ThemeColorBPP=4




From: Kevin Lundy [mailto:klu...@gmail.com] 
Sent: Tuesday, July 14, 2009 8:43 AM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

We do that within my IT department.  If you leave the  IT department without 
locking your computer, anyone else is free to send an email from your computer 
to the whole department announcing it is your privilage to bring 
doughnuts/bagels/cookies the next day.  Doesn't matter if you are only stepping 
out for 30 seconds.  Your screen better be locked.  It forms good habits.  I 
don't believe we have had a "violation" in well over a year.  But we have a new 
help desk employee, I'm sure he'll get nabbed :)

RE: E-mail address display question

[Joe Heaton]

Yep, just needed a little more patience.  Works properly now.

 

Thanks guys,

 

Joe Heaton

Employment Training Panel

 

From: Carl Houseman [mailto:c.house...@gmail.com] 
Sent: Monday, July 13, 2009 7:49 PM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

 

Was the user logged in when their display name was changed?

And if so, did the user logout and login before sending the test e-mail?

And what about today?  Same/different?  Waiting up to 2 hours solves
many issues such as this.

 

Carl

 

From: Joe Heaton [mailto:jhea...@etp.ca.gov] 
Sent: Monday, July 13, 2009 2:26 PM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

 

Ok, so I did that change, and if I'm looking through the GAL, it shows
correctly, but when I sent a test e-mail as that account, it still
displayed incorrectly in my Inbox.

 

Joe Heaton

Employment Training Panel

 

From: Carl Houseman [mailto:c.house...@gmail.com] 
Sent: Monday, July 13, 2009 11:09 AM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

 

Change the "display name" to whatever you want.

 

Carl

 

From: Joe Heaton [mailto:jhea...@etp.ca.gov] 
Sent: Monday, July 13, 2009 1:54 PM
To: MS-Exchange Admin Issues
Subject: E-mail address display question

 

Is it possible to display three names in the From section?

 

I see mine, and most everyone's as Firstname Lastname.  I need to have
one account here display as First Second Last.  How can I do this?

 

Joe Heaton

AISA

Employment Training Panel

1100 J Street, 4th Floor

Sacramento, CA  95814

(916) 327-5276

jhea...@etp.ca.gov

 

Re: E-mail address display question

[Jonathan Link]

That tends to solve as many problems as an end user rebot does,  
patience, that is.

Painstakingly sent from my iPhone.

On Jul 14, 2009, at 10:34 AM, "Joe Heaton"  wrote:

> Yep, just needed a little more patience.  Works properly now.
>
>
>
> Thanks guys,
>
>
>
> Joe Heaton
>
> Employment Training Panel
>
>
>
> From: Carl Houseman [mailto:c.house...@gmail.com]
> Sent: Monday, July 13, 2009 7:49 PM
> To: MS-Exchange Admin Issues
> Subject: RE: E-mail address display question
>
>
>
> Was the user logged in when their display name was changed?
>
> And if so, did the user logout and login before sending the test e- 
> mail?
>
> And what about today?  Same/different?  Waiting up to 2 hours solves  
> many issues such as this.
>
>
>
> Carl
>
>
>
> From: Joe Heaton [mailto:jhea...@etp.ca.gov]
> Sent: Monday, July 13, 2009 2:26 PM
> To: MS-Exchange Admin Issues
> Subject: RE: E-mail address display question
>
>
>
> Ok, so I did that change, and if I’m looking through the GAL, it sho 
> ws correctly, but when I sent a test e-mail as that account, it stil 
> l displayed incorrectly in my Inbox.
>
>
>
> Joe Heaton
>
> Employment Training Panel
>
>
>
> From: Carl Houseman [mailto:c.house...@gmail.com]
> Sent: Monday, July 13, 2009 11:09 AM
> To: MS-Exchange Admin Issues
> Subject: RE: E-mail address display question
>
>
>
> Change the "display name" to whatever you want.
>
>
>
> Carl
>
>
>
> From: Joe Heaton [mailto:jhea...@etp.ca.gov]
> Sent: Monday, July 13, 2009 1:54 PM
> To: MS-Exchange Admin Issues
> Subject: E-mail address display question
>
>
>
> Is it possible to display three names in the From section?
>
>
>
> I see mine, and most everyone’s as Firstname Lastname.  I need to ha 
> ve one account here display as First Second Last.  How can I do this?
>
>
>
> Joe Heaton
>
> AISA
>
> Employment Training Panel
>
> 1100 J Street, 4th Floor
>
> Sacramento, CA  95814
>
> (916) 327-5276
>
> jhea...@etp.ca.gov
>
>

Add encryption to internal email

[Bob Fronk]

We are being told we must encrypt internal mail between certain users.  We are 
using a 3rd party encryption service for sending mail externally, but this, in 
my opinion, is not a good solution for internal users.

Is it difficult to setup Exchange (2003) and Outlook (2007) to encrypt internal 
mail?

I am starting my online research, but also wanted to get input and pointers to 
good articles from those that have been down this road.

Thanks for your input.

--
Bob

RE: E-mail address display question

[Michael B. Smith]

Right.

http://theessentialexchange.com/blogs/michael/archive/2008/01/18/Exchange-Server-Caches.aspx


From: Carl Houseman [c.house...@gmail.com]
Sent: Monday, July 13, 2009 10:48 PM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

Was the user logged in when their display name was changed?
And if so, did the user logout and login before sending the test e-mail?
And what about today?  Same/different?  Waiting up to 2 hours solves many 
issues such as this.

Carl

From: Joe Heaton [mailto:jhea...@etp.ca.gov]
Sent: Monday, July 13, 2009 2:26 PM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

Ok, so I did that change, and if I’m looking through the GAL, it shows 
correctly, but when I sent a test e-mail as that account, it still displayed 
incorrectly in my Inbox.

Joe Heaton
Employment Training Panel

From: Carl Houseman [mailto:c.house...@gmail.com]
Sent: Monday, July 13, 2009 11:09 AM
To: MS-Exchange Admin Issues
Subject: RE: E-mail address display question

Change the "display name" to whatever you want.

Carl

From: Joe Heaton [mailto:jhea...@etp.ca.gov]
Sent: Monday, July 13, 2009 1:54 PM
To: MS-Exchange Admin Issues
Subject: E-mail address display question

Is it possible to display three names in the From section?

I see mine, and most everyone’s as Firstname Lastname.  I need to have one 
account here display as First Second Last.  How can I do this?

Joe Heaton
AISA
Employment Training Panel
1100 J Street, 4th Floor
Sacramento, CA  95814
(916) 327-5276
jhea...@etp.ca.gov

RE: Add encryption to internal email

[Michael B. Smith]

Upgrade to Exchange 2007+. The entire mail process is encrypted.

You can encrypt the path to Exchange from Outlook by checking the box in the 
Exchange profile that requires it. But you can't encrypt Exchange to Exchange 
transfers in Exchange 2003.


From: Bob Fronk [...@btrfronk.com]
Sent: Tuesday, July 14, 2009 10:56 AM
To: MS-Exchange Admin Issues
Subject: Add encryption to internal email

We are being told we must encrypt internal mail between certain users.  We are 
using a 3rd party encryption service for sending mail externally, but this, in 
my opinion, is not a good solution for internal users.

Is it difficult to setup Exchange (2003) and Outlook (2007) to encrypt internal 
mail?

I am starting my online research, but also wanted to get input and pointers to 
good articles from those that have been down this road.

Thanks for your input.

--
Bob

RE: Add encryption to internal email

[Bob Fronk]

Thanks... the article I just read pretty much lead me down that path too.

So if I understand what you are saying and what I am reading, out of the box 
with Exchange 2007, an email created in Outlook and sent to an internal user 
(with Outlook), the message is encrypted the entire time?

--
Bob Fronk
P Please print only as needed.





From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, July 14, 2009 11:06 AM
To: MS-Exchange Admin Issues
Subject: RE: Add encryption to internal email

Upgrade to Exchange 2007+. The entire mail process is encrypted.

You can encrypt the path to Exchange from Outlook by checking the box in the 
Exchange profile that requires it. But you can't encrypt Exchange to Exchange 
transfers in Exchange 2003.


From: Bob Fronk [...@btrfronk.com]
Sent: Tuesday, July 14, 2009 10:56 AM
To: MS-Exchange Admin Issues
Subject: Add encryption to internal email
We are being told we must encrypt internal mail between certain users.  We are 
using a 3rd party encryption service for sending mail externally, but this, in 
my opinion, is not a good solution for internal users.

Is it difficult to setup Exchange (2003) and Outlook (2007) to encrypt internal 
mail?

I am starting my online research, but also wanted to get input and pointers to 
good articles from those that have been down this road.

Thanks for your input.

--
Bob

Send As From Public Folder

[Carol Fee]

E2K3 SP2 fully patched
W2K3 Enterprise SP2 fully patched
Single domain/forest
All of a sudden, no one is able to Send As one and only one particular
Public Folder.  This includes users who have permissions and who were
previously able to do so.  Users are still able to do this from other
Public Folders according to the permissions for each.  There have been
no configuration changes to either the server or the Public Folder in
question.
Any ideas 
 
 


Carol Fee
Network Administrator
617-338-0623
c...@massbar.org
 

 

  
   Massachusetts Bar Association
   20 West Street
   Boston, MA 02111-1204
   (617) 338-0500
 
<>

RE: Add encryption to internal email

[Michael B. Smith]

That is correct. End-to-end secure transport of internal email was a primary 
design goal for Exchange 2007.

It's also available for external partners using either TLS (Internet standard 
for secure email) or for any other partner using Exchange 2007 or above 
(Microsoft extension to create secure SMTP sessions).


From: Bob Fronk [...@btrfronk.com]
Sent: Tuesday, July 14, 2009 11:22 AM
To: MS-Exchange Admin Issues
Subject: RE: Add encryption to internal email

Thanks… the article I just read pretty much lead me down that path too.

So if I understand what you are saying and what I am reading, out of the box 
with Exchange 2007, an email created in Outlook and sent to an internal user 
(with Outlook), the message is encrypted the entire time?

--
Bob Fronk
P Please print only as needed.





From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, July 14, 2009 11:06 AM
To: MS-Exchange Admin Issues
Subject: RE: Add encryption to internal email

Upgrade to Exchange 2007+. The entire mail process is encrypted.

You can encrypt the path to Exchange from Outlook by checking the box in the 
Exchange profile that requires it. But you can't encrypt Exchange to Exchange 
transfers in Exchange 2003.


From: Bob Fronk [...@btrfronk.com]
Sent: Tuesday, July 14, 2009 10:56 AM
To: MS-Exchange Admin Issues
Subject: Add encryption to internal email
We are being told we must encrypt internal mail between certain users.  We are 
using a 3rd party encryption service for sending mail externally, but this, in 
my opinion, is not a good solution for internal users.

Is it difficult to setup Exchange (2003) and Outlook (2007) to encrypt internal 
mail?

I am starting my online research, but also wanted to get input and pointers to 
good articles from those that have been down this road.

Thanks for your input.

--
Bob

Re: Changing Subject Line Limits

[Micheal Espinola Jr]

I know this doesnt answer your question, but I'd submit that subject
lines that long are an issue on many levels - and that doesnt just
apply to using Outlook.

Readability of such long subject line is difficult if not impossible
for many mail readers.  The long text should be in the message body.

--
ME2



On Mon, Jul 13, 2009 at 2:47 PM, Rimmel, Carl wrote:
> From what I have found, these messages are using the UTF-8 character set and
> are being BASE64 coded (somewhere along the way).  Using trial and error I
> was able to discover that anytime the BASE64 subject line exceeds 255
> characters, it is truncated by Outlook (thus the 3 dots at the end) and then
> it becomes illegible and cannot be decoded by Outlook.
>
>
>
> Is there a way to expand the character limit in Outlook to allow a subject
> line that is longer than 255 characters?
>
>
>
> Thanks,
>
>
>
> Carl Rimmel
>
> ==
> CONFIDENTIALITY NOTICE: This email contains information from the sender that
> may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected
> from disclosure. This email is intended for use only by the person or entity
> to whom it is addressed. If you are not the intended recipient, any use,
> disclosure, copying, distribution, printing, or any action taken in reliance
> on the contents of this email, is strictly prohibited. If you received this
> email in error, please contact the sending party by reply email, delete the
> email from your computer system and shred any paper copies.
>
> Note to Patients: There are a number of risks you should consider before
> using e-mail to communicate with us. See our Privacy Policy and Henry Ford
> My Health at www.henryford.com for more detailed information. If you do not
> believe that our policy gives you the privacy and security protection you
> need, do not send e-mail or Internet communications to us.
>
> ==
>

RE: Hub Server

[Michael B. Smith]

Dude - you SO need to be running OpsMgr with the latest Exchange Management 
Pack.

You would've had an alert about this when it first happened and never would've 
experienced the problem to begin with. :-P

I do know a consultant or two who happens to specialize in Exchange and 
OpsMgr :-)

Regards,

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
My blog: http://TheEssentialExchange.com/blogs/michael
Monitoring Exchange w/OpsMgr now available http://snurl.com/45ppf

From: KevinM [kev...@wlkmmas.org]
Sent: Monday, July 13, 2009 5:37 PM
To: MS-Exchange Admin Issues
Subject: RE: Hub Server

Never mind..

The answer was run get-transportagent  showed that the transport rules agent 
was disabled for some reason. Turning it back on fixed the issue.

~Kevinm WLKMMAS– This message is Certified Swine Flu Free
My life http://www.hedonists.ca

From: KevinM [mailto:kev...@wlkmmas.org]
Sent: Monday, July 13, 2009 2:35 PM
To: MS-Exchange Admin Issues
Subject: Hub Server

I have Exchange 2007 org XIN, with Servers on Mars, and Earth.  I create a 
transport Rule that should be org wide. The Rule works on the Earth server but 
not the Mars server. Outside of latency why is this? I have a hub server in 
both sites that shows the correct rules.

I looked at this thing and it was pretty but it did not tell what to look at.
http://www.microsoft.com/downloads/details.aspx?familyid=612F811D-2953-4C08-945E-833C17150083&displaylang=en

~Kevinm WLKMMAS– This message is Certified Swine Flu Free
My life http://www.hedonists.ca

RE: Hub Server

[Sobey, Richard A]

I'll bite..what's his name? :)

From: bounce-8597709-8066...@lyris.sunbelt-software.com 
[mailto:bounce-8597709-8066...@lyris.sunbelt-software.com] On Behalf Of Michael 
B. Smith
Sent: 14 July 2009 16:34
To: MS-Exchange Admin Issues
Subject: RE: Hub Server

Dude - you SO need to be running OpsMgr with the latest Exchange Management 
Pack.

You would've had an alert about this when it first happened and never would've 
experienced the problem to begin with. :-P

I do know a consultant or two who happens to specialize in Exchange and 
OpsMgr :-)

Regards,

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
My blog: http://TheEssentialExchange.com/blogs/michael
Monitoring Exchange w/OpsMgr now available http://snurl.com/45ppf

From: KevinM [kev...@wlkmmas.org]
Sent: Monday, July 13, 2009 5:37 PM
To: MS-Exchange Admin Issues
Subject: RE: Hub Server
Never mind..

The answer was run get-transportagent  showed that the transport rules agent 
was disabled for some reason. Turning it back on fixed the issue.

~Kevinm WLKMMAS- This message is Certified Swine Flu Free
My life http://www.hedonists.ca

From: KevinM [mailto:kev...@wlkmmas.org]
Sent: Monday, July 13, 2009 2:35 PM
To: MS-Exchange Admin Issues
Subject: Hub Server

I have Exchange 2007 org XIN, with Servers on Mars, and Earth.  I create a 
transport Rule that should be org wide. The Rule works on the Earth server but 
not the Mars server. Outside of latency why is this? I have a hub server in 
both sites that shows the correct rules.

I looked at this thing and it was pretty but it did not tell what to look at.
http://www.microsoft.com/downloads/details.aspx?familyid=612F811D-2953-4C08-945E-833C17150083&displaylang=en

~Kevinm WLKMMAS- This message is Certified Swine Flu Free
My life http://www.hedonists.ca

RE: another Calendar Question

[Michael B. Smith]

Another very worthwhile question to ask is whether you have any Macintosh 
computers with Entourage involved in your environment. If so, not only are 
these types of problems known, they are well documented by RIM.


From: Doug Gallimore [doug.gallim...@match.com]
Sent: Monday, July 13, 2009 4:52 PM
To: MS-Exchange Admin Issues
Subject: RE: another Calendar Question

David,

I agree that delegate users probably shouldn't be on cached mode, but strongly 
urge you to read this article about BES and Exchange before you change all your 
community to NON-cached mode.

http://crackberry.com/blackberry-slowness-exchange-environment

A lot of the exchange latency that can cause issues with message delivery to 
blackberry devices can be attributed to not properly sizing your exchange 
servers vs.  your blackberry servers or NOT using cached mode.

Food for thought.
Douglas

From: David.Ricci [mailto:david.ri...@hwinstitute.com]
Sent: Monday, July 13, 2009 1:59 PM
To: MS-Exchange Admin Issues
Subject: RE: another Calendar Question

Thank you and yes I am patched on Bes 4.1.6 now.

I am changing people to non cached mode.




David

SERVICE. INNOVATION. RESULTS.

From: Knoch, James W [mailto:james.kn...@intergraph.com]
Sent: Monday, July 13, 2009 11:53 AM
To: MS-Exchange Admin Issues
Subject: RE: another Calendar Question

Do you have a Blackberry server?  If so what version, what service pack, etc?  
There was some calendar issues with earlier versions of 4.1.

Also, are your exec admin team delegates and get copied on the exec meeting 
requests?  If so, how many of them are in Cached Mode?  If the admin team 
accepts/rejects a meeting request, it won't sync until their client does a 
Send/Receive (from my testing experience).  Also, I have seen cases where 
something wouldn't get published or conflict.  Also, they would also cause 
"Tentative" meeting requests.  I had to change most of our admins to Online 
Mode in order to fix most of the problems (mainly with Resource Accounts).

James

From: David.Ricci [mailto:david.ri...@hwinstitute.com]
Sent: Monday, July 13, 2009 9:37 AM
To: MS-Exchange Admin Issues
Subject: another Calendar Question

The problem will not go away.  Disappearing or duplicating calendar entries.

I have Exchange 2003 sp2 and I feel should be patched.

I do have an exec admin team that watch 10 execs calendars.  I thought maybe 
there was a limit to how many people should look at or something to that affect.

Thank you for any advice.



David

RE: Hub Server

[Michael B. Smith]

My bad. That was intended to be a personal message to Kevin we go WAY back.


From: Sobey, Richard A [r.so...@imperial.ac.uk]
Sent: Tuesday, July 14, 2009 11:45 AM
To: MS-Exchange Admin Issues
Subject: RE: Hub Server

I’ll bite..what’s his name? :)

From: bounce-8597709-8066...@lyris.sunbelt-software.com 
[mailto:bounce-8597709-8066...@lyris.sunbelt-software.com] On Behalf Of Michael 
B. Smith
Sent: 14 July 2009 16:34
To: MS-Exchange Admin Issues
Subject: RE: Hub Server

Dude - you SO need to be running OpsMgr with the latest Exchange Management 
Pack.

You would've had an alert about this when it first happened and never would've 
experienced the problem to begin with. :-P

I do know a consultant or two who happens to specialize in Exchange and 
OpsMgr :-)

Regards,

Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP
My blog: http://TheEssentialExchange.com/blogs/michael
Monitoring Exchange w/OpsMgr now available http://snurl.com/45ppf

From: KevinM [kev...@wlkmmas.org]
Sent: Monday, July 13, 2009 5:37 PM
To: MS-Exchange Admin Issues
Subject: RE: Hub Server
Never mind..

The answer was run get-transportagent  showed that the transport rules agent 
was disabled for some reason. Turning it back on fixed the issue.

~Kevinm WLKMMAS– This message is Certified Swine Flu Free
My life http://www.hedonists.ca

From: KevinM [mailto:kev...@wlkmmas.org]
Sent: Monday, July 13, 2009 2:35 PM
To: MS-Exchange Admin Issues
Subject: Hub Server

I have Exchange 2007 org XIN, with Servers on Mars, and Earth.  I create a 
transport Rule that should be org wide. The Rule works on the Earth server but 
not the Mars server. Outside of latency why is this? I have a hub server in 
both sites that shows the correct rules.

I looked at this thing and it was pretty but it did not tell what to look at.
http://www.microsoft.com/downloads/details.aspx?familyid=612F811D-2953-4C08-945E-833C17150083&displaylang=en

~Kevinm WLKMMAS– This message is Certified Swine Flu Free
My life http://www.hedonists.ca

RE: Changing Subject Line Limits

[Michael B. Smith]

I'm not aware of any way to meeting the OP's request.

That being said, I don't know why Exchange would limit a text field to less 
than 1,024 characters. Have you examined the SMTP log to ensure that this is an 
Exchange issue?


From: Micheal Espinola Jr [michealespin...@gmail.com]
Sent: Tuesday, July 14, 2009 11:32 AM
To: MS-Exchange Admin Issues
Subject: Re: Changing Subject Line Limits

I know this doesnt answer your question, but I'd submit that subject
lines that long are an issue on many levels - and that doesnt just
apply to using Outlook.

Readability of such long subject line is difficult if not impossible
for many mail readers.  The long text should be in the message body.

--
ME2



On Mon, Jul 13, 2009 at 2:47 PM, Rimmel, Carl wrote:
> From what I have found, these messages are using the UTF-8 character set and
> are being BASE64 coded (somewhere along the way).  Using trial and error I
> was able to discover that anytime the BASE64 subject line exceeds 255
> characters, it is truncated by Outlook (thus the 3 dots at the end) and then
> it becomes illegible and cannot be decoded by Outlook.
>
>
>
> Is there a way to expand the character limit in Outlook to allow a subject
> line that is longer than 255 characters?
>
>
>
> Thanks,
>
>
>
> Carl Rimmel
>
> ==
> CONFIDENTIALITY NOTICE: This email contains information from the sender that
> may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected
> from disclosure. This email is intended for use only by the person or entity
> to whom it is addressed. If you are not the intended recipient, any use,
> disclosure, copying, distribution, printing, or any action taken in reliance
> on the contents of this email, is strictly prohibited. If you received this
> email in error, please contact the sending party by reply email, delete the
> email from your computer system and shred any paper copies.
>
> Note to Patients: There are a number of risks you should consider before
> using e-mail to communicate with us. See our Privacy Policy and Henry Ford
> My Health at www.henryford.com for more detailed information. If you do not
> believe that our policy gives you the privacy and security protection you
> need, do not send e-mail or Internet communications to us.
>
> ==
>

Re: Distribution lists

[Kurt Buff]

And that's a bad thing?

If you do it from an executive's PC, you get either or both of a
lockdown of the DL and locking screensavers.

If you do it from your least favorite non-executive's machine you get the same.

Seems like a win for you no matter what.

On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
> Think it through.  If you do it from somebody's machine who would have been
> allowed to use the DL, such as an executive, it doesn't help at all.   Not
> to mention, it will probably be found out that it was keyboard-jacking, and
> not employee abuse of the DL, and the result will be mandated
> password-protected screen savers throughout.
>
>
>
> Carl
>
>
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Tuesday, July 14, 2009 3:47 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
>> +1
>>
>>
>>
>> You have given them the recommendation and they have decided. Let it go,
>> move on and ignore the emails in the future. You may be sick of them but
>> management is not. Yet.
>>
>>
>>
>>
>>
>>
>>
>> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> Sent: Monday, July 13, 2009 11:22 AM
>> To: MS-Exchange Admin Issues
>> Subject: RE: Distribution lists
>>
>>
>>
>> In that case my advice is to turn a blind eye and let those execs worry
>> about it.  If it’s un-monitored, it’s just that.  No worries.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:20 AM
>> To: MS-Exchange Admin Issues
>> Subject: Re: Distribution lists
>>
>>
>>
>> I would if I could, but I can't. Not until some idiot sends something that
>> gets on one of the exec team's nerves. Just wondering if there was any
>> other
>> way I could spare myself some pain.
>>
>> I know the old adage about technological solutions to behavioural
>> problems,
>> though, it has never rung truer
>>
>> 2009/7/13 Matt Moore 
>>
>> Limit access to a chosen few and all the spam goes away.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:07 AM
>>
>> To: MS-Exchange Admin Issues
>> Subject: Distribution lists
>>
>>
>>
>> Afternoon Exchange gurus
>>
>> Is it possible to have the "All Staff" distribution list (or any other,
>> really) set up so that when an email is sent to it, it goes to an
>> administrator for approval first? I am sick of getting emails that say
>> "there is a salesman selling cards in reception" and when someone spammed
>> the DL with a hoax that was well-documented on snopes.com, I ended up
>> getting a reprimand from my boss about being harsh to users. I only
>> threatened to remove her ability to send to the DL. Sheesh. I know that we
>> shouldn't give all users the ability to send to it, but I doubt I am going
>> to shift my boss's boss's stance on this one.
>>
>> Any other pointers would be also gratefully received, I am not much of an
>> Exchange bod.
>>
>> TIA,
>>
>>
>> JRR
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>>
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>
>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke such
> a question."
>
> http://raythestray.blogspot.com

RE: Distribution lists

[Carl Houseman]

Or you get keyboard lockdown without DL lockdown and the DL abuse continues 
unchanged.  That's not a win for the OP's problem.

Carl

-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com] 
Sent: Tuesday, July 14, 2009 12:33 PM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

And that's a bad thing?

If you do it from an executive's PC, you get either or both of a
lockdown of the DL and locking screensavers.

If you do it from your least favorite non-executive's machine you get the same.

Seems like a win for you no matter what.

On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
> Think it through.  If you do it from somebody's machine who would have been
> allowed to use the DL, such as an executive, it doesn't help at all.   Not
> to mention, it will probably be found out that it was keyboard-jacking, and
> not employee abuse of the DL, and the result will be mandated
> password-protected screen savers throughout.
>
>
>
> Carl
>
>
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Tuesday, July 14, 2009 3:47 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
>> +1
>>
>>
>>
>> You have given them the recommendation and they have decided. Let it go,
>> move on and ignore the emails in the future. You may be sick of them but
>> management is not. Yet.
>>
>>
>>
>>
>>
>>
>>
>> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> Sent: Monday, July 13, 2009 11:22 AM
>> To: MS-Exchange Admin Issues
>> Subject: RE: Distribution lists
>>
>>
>>
>> In that case my advice is to turn a blind eye and let those execs worry
>> about it.  If it’s un-monitored, it’s just that.  No worries.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:20 AM
>> To: MS-Exchange Admin Issues
>> Subject: Re: Distribution lists
>>
>>
>>
>> I would if I could, but I can't. Not until some idiot sends something that
>> gets on one of the exec team's nerves. Just wondering if there was any
>> other
>> way I could spare myself some pain.
>>
>> I know the old adage about technological solutions to behavioural
>> problems,
>> though, it has never rung truer
>>
>> 2009/7/13 Matt Moore 
>>
>> Limit access to a chosen few and all the spam goes away.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:07 AM
>>
>> To: MS-Exchange Admin Issues
>> Subject: Distribution lists
>>
>>
>>
>> Afternoon Exchange gurus
>>
>> Is it possible to have the "All Staff" distribution list (or any other,
>> really) set up so that when an email is sent to it, it goes to an
>> administrator for approval first? I am sick of getting emails that say
>> "there is a salesman selling cards in reception" and when someone spammed
>> the DL with a hoax that was well-documented on snopes.com, I ended up
>> getting a reprimand from my boss about being harsh to users. I only
>> threatened to remove her ability to send to the DL. Sheesh. I know that we
>> shouldn't give all users the ability to send to it, but I doubt I am going
>> to shift my boss's boss's stance on this one.
>>
>> Any other pointers would be also gratefully received, I am not much of an
>> Exchange bod.
>>
>> TIA,
>>
>>
>> JRR
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>>
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>
>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke such
> a question."
>
> http://raythestray.blogspot.com

RE: Distribution lists

[Matt Moore]

Screen savers for sure; for one case I was involved in a deputy sheriff was
given a months vacation and the locks on all the fire stations were changed
so they automatically lock and were rekeyed.  I don't think I'd advise using
anyone's workstation but your own for email fun.  ;4)
M

-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com] 
Sent: Tuesday, July 14, 2009 9:33 AM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

And that's a bad thing?

If you do it from an executive's PC, you get either or both of a
lockdown of the DL and locking screensavers.

If you do it from your least favorite non-executive's machine you get the
same.

Seems like a win for you no matter what.

On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
> Think it through.  If you do it from somebody's machine who would have
been
> allowed to use the DL, such as an executive, it doesn't help at all.   Not
> to mention, it will probably be found out that it was keyboard-jacking,
and
> not employee abuse of the DL, and the result will be mandated
> password-protected screen savers throughout.
>
>
>
> Carl
>
>
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Tuesday, July 14, 2009 3:47 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
>> +1
>>
>>
>>
>> You have given them the recommendation and they have decided. Let it go,
>> move on and ignore the emails in the future. You may be sick of them but
>> management is not. Yet.
>>
>>
>>
>>
>>
>>
>>
>> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> Sent: Monday, July 13, 2009 11:22 AM
>> To: MS-Exchange Admin Issues
>> Subject: RE: Distribution lists
>>
>>
>>
>> In that case my advice is to turn a blind eye and let those execs worry
>> about it.  If it’s un-monitored, it’s just that.  No worries.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:20 AM
>> To: MS-Exchange Admin Issues
>> Subject: Re: Distribution lists
>>
>>
>>
>> I would if I could, but I can't. Not until some idiot sends something
that
>> gets on one of the exec team's nerves. Just wondering if there was any
>> other
>> way I could spare myself some pain.
>>
>> I know the old adage about technological solutions to behavioural
>> problems,
>> though, it has never rung truer
>>
>> 2009/7/13 Matt Moore 
>>
>> Limit access to a chosen few and all the spam goes away.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:07 AM
>>
>> To: MS-Exchange Admin Issues
>> Subject: Distribution lists
>>
>>
>>
>> Afternoon Exchange gurus
>>
>> Is it possible to have the "All Staff" distribution list (or any other,
>> really) set up so that when an email is sent to it, it goes to an
>> administrator for approval first? I am sick of getting emails that say
>> "there is a salesman selling cards in reception" and when someone spammed
>> the DL with a hoax that was well-documented on snopes.com, I ended up
>> getting a reprimand from my boss about being harsh to users. I only
>> threatened to remove her ability to send to the DL. Sheesh. I know that
we
>> shouldn't give all users the ability to send to it, but I doubt I am
going
>> to shift my boss's boss's stance on this one.
>>
>> Any other pointers would be also gratefully received, I am not much of an
>> Exchange bod.
>>
>> TIA,
>>
>>
>> JRR
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not
able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>>
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not
able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>
>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ide

Re: Distribution lists

[Jonathan Link]

Chances are he'd be violating the org's AUP, since most AUP's have a
stipulation about using assigned accounts.  That is NOT a good thing.  Just
because you don't get caught, or you have a good intention doesn't mean the
action itself is right/good.

-Jonathan

On Tue, Jul 14, 2009 at 12:32 PM, Kurt Buff  wrote:

> And that's a bad thing?
>
> If you do it from an executive's PC, you get either or both of a
> lockdown of the DL and locking screensavers.
>
> If you do it from your least favorite non-executive's machine you get the
> same.
>
> Seems like a win for you no matter what.
>
> On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
> > Think it through.  If you do it from somebody's machine who would have
> been
> > allowed to use the DL, such as an executive, it doesn't help at all.
> Not
> > to mention, it will probably be found out that it was keyboard-jacking,
> and
> > not employee abuse of the DL, and the result will be mandated
> > password-protected screen savers throughout.
> >
> >
> >
> > Carl
> >
> >
> >
> > From: James Rankin [mailto:kz2...@googlemail.com]
> > Sent: Tuesday, July 14, 2009 3:47 AM
> > To: MS-Exchange Admin Issues
> > Subject: Re: Distribution lists
> >
> >
> >
> > That is actually a fine idea
> >
> > 2009/7/13 Kurt Buff 
> >
> > This is an easy fix.
> >
> > Find (or compose) a silly email on someone else's non-attended,
> > non-screensavered machine, and send it to the all users list.
> >
> > One of my favorites is to announce candy or cookies at the victim's desk.
> >
> > Be sure to wipe up for fingerprints afterward, if you happen to do it
> > to an executive, though.
> >
> > Heh.
> >
> > On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim >
> > wrote:
> >> +1
> >>
> >>
> >>
> >> You have given them the recommendation and they have decided. Let it go,
> >> move on and ignore the emails in the future. You may be sick of them but
> >> management is not. Yet.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> From: Matt Moore [mailto:mattmoore...@hotmail.com]
> >> Sent: Monday, July 13, 2009 11:22 AM
> >> To: MS-Exchange Admin Issues
> >> Subject: RE: Distribution lists
> >>
> >>
> >>
> >> In that case my advice is to turn a blind eye and let those execs worry
> >> about it.  If it’s un-monitored, it’s just that.  No worries.
> >>
> >> M
> >>
> >>
> >>
> >> 
> >>
> >> From: James Rankin [mailto:kz2...@googlemail.com]
> >> Sent: Monday, July 13, 2009 7:20 AM
> >> To: MS-Exchange Admin Issues
> >> Subject: Re: Distribution lists
> >>
> >>
> >>
> >> I would if I could, but I can't. Not until some idiot sends something
> that
> >> gets on one of the exec team's nerves. Just wondering if there was any
> >> other
> >> way I could spare myself some pain.
> >>
> >> I know the old adage about technological solutions to behavioural
> >> problems,
> >> though, it has never rung truer
> >>
> >> 2009/7/13 Matt Moore 
> >>
> >> Limit access to a chosen few and all the spam goes away.
> >>
> >> M
> >>
> >>
> >>
> >> 
> >>
> >> From: James Rankin [mailto:kz2...@googlemail.com]
> >> Sent: Monday, July 13, 2009 7:07 AM
> >>
> >> To: MS-Exchange Admin Issues
>  >> Subject: Distribution lists
> >>
> >>
> >>
> >> Afternoon Exchange gurus
> >>
> >> Is it possible to have the "All Staff" distribution list (or any other,
> >> really) set up so that when an email is sent to it, it goes to an
> >> administrator for approval first? I am sick of getting emails that say
> >> "there is a salesman selling cards in reception" and when someone
> spammed
> >> the DL with a hoax that was well-documented on snopes.com, I ended up
> >> getting a reprimand from my boss about being harsh to users. I only
> >> threatened to remove her ability to send to the DL. Sheesh. I know that
> we
> >> shouldn't give all users the ability to send to it, but I doubt I am
> going
> >> to shift my boss's boss's stance on this one.
> >>
> >> Any other pointers would be also gratefully received, I am not much of
> an
> >> Exchange bod.
> >>
> >> TIA,
> >>
> >>
> >> JRR
> >>
> >> --
> >> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
> into
> >> the machine wrong figures, will the right answers come out?' I am not
> able
> >> rightly to apprehend the kind of confusion of ideas that could provoke
> >> such
> >> a question."
> >>
> >> http://raythestray.blogspot.com
> >>
> >> Checked by AVG - www.avg.com
> >> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
> 07/12/09
> >> 17:56:00
> >>
> >>
> >> --
> >> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
> into
> >> the machine wrong figures, will the right answers come out?' I am not
> able
> >> rightly to apprehend the kind of confusion of ideas that could provoke
> >> such
> >> a question."
> >>
> >> http://raythestray.blogspot.com
> >>
> >> Checked by AVG - www.avg.com
> >> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
> 07/12/09
> >> 17:56:00
> >
> >
> >
> >
> >

RE: Distribution lists

[PRamatowski]

Or you get your wrist slapped (or worse) for playing with something that's not 
yours.  

I'd happily retheme a small handful of desktops around here but I wouldn't go 
near the keyboards of 99.% of our users- no matter who they are or what 
their title:)

Delete key is my friend!

-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com] 
Sent: Tuesday, July 14, 2009 12:33 PM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

And that's a bad thing?

If you do it from an executive's PC, you get either or both of a
lockdown of the DL and locking screensavers.

If you do it from your least favorite non-executive's machine you get the same.

Seems like a win for you no matter what.

On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
> Think it through.�� If you do it from somebody's machine who would have been
> allowed to use the DL, such as an executive, it doesn't help at al�� Not
> to mention, it will probably be found out that it was keyboard-jacking, and
> not employee abuse of the DL, and the result will be mandated
> password-protected screen savers throughout.
>
>
>
> Carl
>
>
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Tuesday, July 14, 2009 3:47 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
>> +1
>>
>>
>>
>> You have given them the recommendation and they have decided. Let it go,
>> move on and ignore the emails in the future. You may be sick of them but
>> management is not. Yet.
>>
>>
>>
>>
>>
>>
>>
>> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> Sent: Monday, July 13, 2009 11:22 AM
>> To: MS-Exchange Admin Issues
>> Subject: RE: Distribution lists
>>
>>
>>
>> In that case my advice is to turn a blind eye and let those execs worry
>> about it��� If it���s un-monitored, it���s just that.�� No worries.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:20 AM
>> To: MS-Exchange Admin Issues
>> Subject: Re: Distribution lists
>>
>>
>>
>> I would if I could, but I can't. Not until some idiot sends something that
>> gets on one of the exec team's nerves. Just wondering if there was any
>> other
>> way I could spare myself some pain.
>>
>> I know the old adage about technological solutions to behavioural
>> problems,
>> though, it has never rung truer
>>
>> 2009/7/13 Matt Moore 
>>
>> Limit access to a chosen few and all the spam goes away.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:07 AM
>>
>> To: MS-Exchange Admin Issues
>> Subject: Distribution lists
>>
>>
>>
>> Afternoon Exchange gurus
>>
>> Is it possible to have the "All Staff" distribution list (or any other,
>> really) set up so that when an email is sent to it, it goes to an
>> administrator for approval first? I am sick of getting emails that say
>> "there is a salesman selling cards in reception" and when someone spammed
>> the DL with a hoax that was well-documented on snopes.com, I ended up
>> getting a reprimand from my boss about being harsh to users. I only
>> threatened to remove her ability to send to the DL. Sheesh. I know that we
>> shouldn't give all users the ability to send to it, but I doubt I am going
>> to shift my boss's boss's stance on this one.
>>
>> Any other pointers would be also gratefully received, I am not much of an
>> Exchange bod.
>>
>> TIA,
>>
>>
>> JRR
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>>
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>
>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confu

Restore server

[Jim Dandy]

I have an Exchange 2003 frontend server running on Windows Server 2003
that is having some issues with its hard drive.  I have another
identical hardware server.  I've loaded Windows Server 2003 on the new
hardware but no Exchange.  It's not a domain member, has a different
NetBIOS name and it does not have all the Windows patches installed on
the limper.  My plan was to restore the backup from the limping server
to the other server, unplug the limping server from the network and then
reboot the new server.  My hope is of course that the new server will
come up and begin functioning as the limper did (but without the hard
drive issue).  However, if the new server doesn't come back up I figure
I can just power it down, plug the limper back in and get things up
again quickly.  Does anyone see any issues in doing things this way?
I'm using Backup Exec 12.0.

Thanks for your help.

Curt

RE: Restore server

[Bob Fronk]

http://www.msexchange.org/tutorials/Restoring-Exchange-Server2003-Alternate-Hardware.html


--
Bob Fronk






-Original Message-
From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu] 
Sent: Tuesday, July 14, 2009 2:35 PM
To: MS-Exchange Admin Issues
Subject: Restore server

I have an Exchange 2003 frontend server running on Windows Server 2003
that is having some issues with its hard drive.  I have another
identical hardware server.  I've loaded Windows Server 2003 on the new
hardware but no Exchange.  It's not a domain member, has a different
NetBIOS name and it does not have all the Windows patches installed on
the limper.  My plan was to restore the backup from the limping server
to the other server, unplug the limping server from the network and then
reboot the new server.  My hope is of course that the new server will
come up and begin functioning as the limper did (but without the hard
drive issue).  However, if the new server doesn't come back up I figure
I can just power it down, plug the limper back in and get things up
again quickly.  Does anyone see any issues in doing things this way?
I'm using Backup Exec 12.0.

Thanks for your help.

Curt

Re: Migration and upgrade

[Sherry Abercrombie]

You don't upgrade to E2K7.

On Tue, Jul 14, 2009 at 2:16 PM, James Kerr  wrote:

> Need to migrate exchange 2003 (w/ Win2003) to new server that will be
> running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should
> I install 2003 on the new server, migrate, decomission the old exchange
> sever then upgrade to 2007?
>
> James
>
>


-- 
Sherry Abercrombie

"Any sufficiently advanced technology is indistinguishable from magic."
Arthur C. Clarke

RE: Migration and upgrade

[Steve Hart]

A true "upgrade", where you update the software on an existing server, 
typically isn't possible due to the fact the E2007 needs a 64 bit OS (among 
other reasons). You'll need to set up E2007 on a new server, then migrate all 
of your users and such to the new server.

Exchange is a small part of my job, but I thought I knew it pretty well prior 
to our 2007 deployment. In the end, I was able to handle most of it myself, but 
I was reading for a good month to get there. A consultant would have been a lot 
easier.

Steve

 

-Original Message-
From: James Kerr [mailto:cluster...@gmail.com] 
Sent: Tuesday, July 14, 2009 12:17 PM
To: MS-Exchange Admin Issues
Subject: Migration and upgrade

Need to migrate exchange 2003 (w/ Win2003) to new server that will be running 
exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should I install 
2003 on the new server, migrate, decomission the old exchange sever then 
upgrade to 2007?

James 

RE: Can't Deliver to one Domian

[Lynden A. Philadelphia]

Below is what we get back
 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.  Please 
retry or contact your administrator.



From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian



I have a SBS 2003; for some reason users in that office can's deliver to 
Sympatico.ca domain. we can deliver to any other domain without any issue.  I 
have checked exchange and the sonicwall an can not see anything.
 
I should also mention that Bell is the ISP in question and no black listing is 
in place.
 
Can some one help?
 
 
Lynden 
 
 

Re: Migration and upgrade

[Jonathan Link]

OB slashdot.
E2k7 upgrades you!

On Tue, Jul 14, 2009 at 3:28 PM, Sherry Abercrombie wrote:

> You don't upgrade to E2K7.
>
>
> On Tue, Jul 14, 2009 at 2:16 PM, James Kerr  wrote:
>
>> Need to migrate exchange 2003 (w/ Win2003) to new server that will be
>> running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should
>> I install 2003 on the new server, migrate, decomission the old exchange
>> sever then upgrade to 2007?
>>
>> James
>>
>>
>
>
> --
> Sherry Abercrombie
>
> "Any sufficiently advanced technology is indistinguishable from magic."
> Arthur C. Clarke
>

RE: Can't Deliver to one Domian

[Campbell, Rob]

You're going to need the smtp logs.


From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
Sent: Tuesday, July 14, 2009 2:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

Below is what we get back


Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.  Please 
retry or contact your administrator.


From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian
I have a SBS 2003; for some reason users in that office can's deliver to 
Sympatico.ca domain. we can deliver to any other domain without any issue.  I 
have checked exchange and the sonicwall an can not see anything.

I should also mention that Bell is the ISP in question and no black listing is 
in place.

Can some one help?


Lynden


**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**

Migration and upgrade

[James Kerr]

Need to migrate exchange 2003 (w/ Win2003) to new server that will be 
running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should 
I install 2003 on the new server, migrate, decomission the old exchange 
sever then upgrade to 2007?


James 

RE: Distribution lists

[Don Andrews]

Agreed - all it took here was a few multi-megabyte oops followed by a
huge number of idiots asking "why am I getting this" in a reply to all.
As our Exchange environment is centralized, even locations with good
pipes will experience a few minutes of NO response from anything when a
6-8 meg message is sent to several thousand users and reply to all is
lots of fun as well.

 



From: James Rankin [mailto:kz2...@googlemail.com] 
Sent: Tuesday, July 14, 2009 12:47 AM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

 

That is actually a fine idea

2009/7/13 Kurt Buff 

This is an easy fix.

Find (or compose) a silly email on someone else's non-attended,
non-screensavered machine, and send it to the all users list.

One of my favorites is to announce candy or cookies at the victim's
desk.

Be sure to wipe up for fingerprints afterward, if you happen to do it
to an executive, though.

Heh.


On Mon, Jul 13, 2009 at 08:43, Kennedy,
Jim wrote:
> +1
>
>
>
> You have given them the recommendation and they have decided. Let it
go,
> move on and ignore the emails in the future. You may be sick of them
but
> management is not. Yet.
>
>
>
>
>
>
>
> From: Matt Moore [mailto:mattmoore...@hotmail.com]
> Sent: Monday, July 13, 2009 11:22 AM
> To: MS-Exchange Admin Issues
> Subject: RE: Distribution lists
>
>
>
> In that case my advice is to turn a blind eye and let those execs
worry
> about it.  If it's un-monitored, it's just that.  No worries.
>
> M
>
>
>
> 
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Monday, July 13, 2009 7:20 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> I would if I could, but I can't. Not until some idiot sends something
that
> gets on one of the exec team's nerves. Just wondering if there was any
other
> way I could spare myself some pain.
>
> I know the old adage about technological solutions to behavioural
problems,
> though, it has never rung truer
>
> 2009/7/13 Matt Moore 
>
> Limit access to a chosen few and all the spam goes away.
>
> M
>
>
>
> 
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Monday, July 13, 2009 7:07 AM
>
> To: MS-Exchange Admin Issues
> Subject: Distribution lists
>
>
>
> Afternoon Exchange gurus
>
> Is it possible to have the "All Staff" distribution list (or any
other,
> really) set up so that when an email is sent to it, it goes to an
> administrator for approval first? I am sick of getting emails that say
> "there is a salesman selling cards in reception" and when someone
spammed
> the DL with a hoax that was well-documented on snopes.com, I ended up
> getting a reprimand from my boss about being harsh to users. I only
> threatened to remove her ability to send to the DL. Sheesh. I know
that we
> shouldn't give all users the ability to send to it, but I doubt I am
going
> to shift my boss's boss's stance on this one.
>
> Any other pointers would be also gratefully received, I am not much of
an
> Exchange bod.
>
> TIA,
>
>
> JRR
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
into
> the machine wrong figures, will the right answers come out?' I am not
able
> rightly to apprehend the kind of confusion of ideas that could provoke
such
> a question."
>
> http://raythestray.blogspot.com
>
> Checked by AVG - www.avg.com
> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
07/12/09
> 17:56:00
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
into
> the machine wrong figures, will the right answers come out?' I am not
able
> rightly to apprehend the kind of confusion of ideas that could provoke
such
> a question."
>
> http://raythestray.blogspot.com
>
> Checked by AVG - www.avg.com
> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
07/12/09
> 17:56:00






-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
into the machine wrong figures, will the right answers come out?' I am
not able rightly to apprehend the kind of confusion of ideas that could
provoke such a question."

http://raythestray.blogspot.com

RE: Can't Deliver to one Domian

[Don Guyer]

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

Re: Migration and upgrade

[James Kerr]

Ok, so I can install E2k7 on the new server and migrate everything from the 
old E2k3 server. Anyone have any links detailing how to accomplish this that 
they may have used in the past? I have never done anything with E2k7 before.


James

- Original Message - 
From: "Steve Hart" 

To: "MS-Exchange Admin Issues" 
Sent: Tuesday, July 14, 2009 3:34 PM
Subject: RE: Migration and upgrade


A true "upgrade", where you update the software on an existing server, 
typically isn't possible due to the fact the E2007 needs a 64 bit OS (among 
other reasons). You'll need to set up E2007 on a new server, then migrate 
all of your users and such to the new server.


Exchange is a small part of my job, but I thought I knew it pretty well 
prior to our 2007 deployment. In the end, I was able to handle most of it 
myself, but I was reading for a good month to get there. A consultant would 
have been a lot easier.


Steve



-Original Message-
From: James Kerr [mailto:cluster...@gmail.com]
Sent: Tuesday, July 14, 2009 12:17 PM
To: MS-Exchange Admin Issues
Subject: Migration and upgrade

Need to migrate exchange 2003 (w/ Win2003) to new server that will be 
running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should 
I install 2003 on the new server, migrate, decomission the old exchange 
sever then upgrade to 2007?


James

Re: Can't Deliver to one Domian

[Jonathan Link]

Or 9 times out of 10 when a user shows me this, I ask if they've verified
the email address.  This domain and rr are really bad with these generic
messages when in actuality it's not a valid email address.



On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer wrote:

>  Looks like it tried for 24 hours and gave up. Probably network/DNS
> related. Did this work before?
>
>
>
> Don Guyer
>
> Systems Engineer - Information Services
>
> Prudential, Fox & Roach/Trident Group
>
> 431 W. Lancaster Avenue
>
> Devon, PA 19333
>
> Direct: (610) 993-3299
>
> Fax: (610) 650-5306
>
> don.gu...@prufoxroach.com
>
>
>
> *From:* Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
>
> *Sent:* Tuesday, July 14, 2009 3:36 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Can't Deliver to one Domian
>
>
>
> Below is what we get back
>
>
>
> Your message did not reach some or all of the intended recipients.
>
>   Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am
>
>   Sent: 13/07/2009 2:54 PM
>
> The following recipient(s) cannot be reached:
>
>   n...@sympatico.ca on 14/07/2009 2:57 AM
>
> Could not deliver the message in the time limit specified.
> Please retry or contact your administrator.
>  --
>
> *From:* Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com
> ]
> *Sent:* Fri 10/07/2009 1:46 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Can't Deliver to one Domian
>
> I have a SBS 2003; for some reason users in that office can's deliver to
> Sympatico.ca domain. we can deliver to any other domain without any issue.
> I have checked exchange and the sonicwall an can not see anything.
>
>
>
> I should also mention that Bell is the ISP in question and no black listing
> is in place.
>
>
>
> Can some one help?
>
>
>
>
>
> Lynden
>
>
>
>
>

RE: Migration and upgrade

[Troy Meyer]

Documentation abounds on this subject.

http://msexchangeteam.com/archive/2006/10/27/429522.aspx

http://technet.microsoft.com/en-us/library/bb124008.aspx


along with about a million other blogs on folks' experience.

Plan well and you should be fine.

-troy


-Original Message-
From: James Kerr [mailto:cluster...@gmail.com] 
Sent: Tuesday, July 14, 2009 12:56 PM
To: MS-Exchange Admin Issues
Subject: Re: Migration and upgrade

Ok, so I can install E2k7 on the new server and migrate everything from
the 
old E2k3 server. Anyone have any links detailing how to accomplish this
that 
they may have used in the past? I have never done anything with E2k7
before.

James

- Original Message - 
From: "Steve Hart" 
To: "MS-Exchange Admin Issues" 
Sent: Tuesday, July 14, 2009 3:34 PM
Subject: RE: Migration and upgrade


A true "upgrade", where you update the software on an existing server, 
typically isn't possible due to the fact the E2007 needs a 64 bit OS
(among 
other reasons). You'll need to set up E2007 on a new server, then
migrate 
all of your users and such to the new server.

Exchange is a small part of my job, but I thought I knew it pretty well 
prior to our 2007 deployment. In the end, I was able to handle most of
it 
myself, but I was reading for a good month to get there. A consultant
would 
have been a lot easier.

Steve



-Original Message-
From: James Kerr [mailto:cluster...@gmail.com]
Sent: Tuesday, July 14, 2009 12:17 PM
To: MS-Exchange Admin Issues
Subject: Migration and upgrade

Need to migrate exchange 2003 (w/ Win2003) to new server that will be 
running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or
should 
I install 2003 on the new server, migrate, decomission the old exchange 
sever then upgrade to 2007?

James

RE: Can't Deliver to one Domian

[Don Guyer]

Now that I've read the error again, it looks like it was 12 hours time
difference.

 

If it reached the destination server with an unknown/bad address, it
should've replied immediately. Unless we're talking about a part of the
world that has a 12 hour time difference.

 

Details always help.

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:07 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

 

Or 9 times out of 10 when a user shows me this, I ask if they've
verified the email address.  This domain and rr are really bad with
these generic messages when in actuality it's not a valid email address.



 

On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

 

RE: Can't Deliver to one Domian

[Campbell, Rob]

"Could not deliver the message in the time limit specified.  Please retry or 
contact your administrator."

Usually means it gave up after multiple temporary failures and retries.  Bad 
address is a permanent failure.

I'm betting on a network, dns, or firewall problem.


From: Don Guyer [mailto:don.gu...@prufoxroach.com]
Sent: Tuesday, July 14, 2009 3:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

Now that I've read the error again, it looks like it was 12 hours time 
difference.

If it reached the destination server with an unknown/bad address, it should've 
replied immediately. Unless we're talking about a part of the world that has a 
12 hour time difference.

Details always help.

Don Guyer
Systems Engineer - Information Services
Prudential, Fox & Roach/Trident Group
431 W. Lancaster Avenue
Devon, PA 19333
Direct: (610) 993-3299
Fax: (610) 650-5306
don.gu...@prufoxroach.com

From: Jonathan Link [mailto:jonathan.l...@gmail.com]
Sent: Tuesday, July 14, 2009 4:07 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

Or 9 times out of 10 when a user shows me this, I ask if they've verified the 
email address.  This domain and rr are really bad with these generic messages 
when in actuality it's not a valid email address.



On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
mailto:don.gu...@prufoxroach.com>> wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS related. Did 
this work before?



Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com



From: Lynden A. Philadelphia 
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian



Below is what we get back



Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.  Please 
retry or contact your administrator.



From: Lynden A. Philadelphia 
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to 
Sympatico.ca domain. we can deliver to any other domain without any issue.  I 
have checked exchange and the sonicwall an can not see anything.



I should also mention that Bell is the ISP in question and no black listing is 
in place.



Can some one help?





Lynden





**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**

RE: Can't Deliver to one Domian

[Wulff Jr, Ronald J.]

Sender domain could be blacklisted

Recipient might be expecting TLS

Recipient might be having SMTP server issues.

 

Way too many things to guess really

 

Ronald Wulff Jr 
412.288.3601 
rwu...@reedsmith.com 

Reed Smith LLP 
20 Stanwix St

Suite 1200
Pittsburgh, PA 15222

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: Tuesday, July 14, 2009 4:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

"Could not deliver the message in the time limit specified.  Please
retry or contact your administrator."

 

Usually means it gave up after multiple temporary failures and retries.
Bad address is a permanent failure.

 

I'm betting on a network, dns, or firewall problem.

 



From: Don Guyer [mailto:don.gu...@prufoxroach.com] 
Sent: Tuesday, July 14, 2009 3:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Now that I've read the error again, it looks like it was 12 hours time
difference.

 

If it reached the destination server with an unknown/bad address, it
should've replied immediately. Unless we're talking about a part of the
world that has a 12 hour time difference.

 

Details always help.

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:07 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

 

Or 9 times out of 10 when a user shows me this, I ask if they've
verified the email address.  This domain and rr are really bad with
these generic messages when in actuality it's not a valid email address.



 

On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

 


**
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this
message to  
the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If
you  
have received this communication in error, please notify us immediately
by  
replying to the message and deleting it from your computer. 

** 
 
* * *
 
This E-mail, along with any attachments, is considered confidential and may 
well be legally privileged. If you have received it in error, you are on notice 
of its status. Please notify us immediately by reply e-mail and then delete 
this message from your system. Please do not copy it or use it for any 
purposes, or disclose its contents to any other person. Thank you for your 
cooperation.
* * *
To ensure compliance with Treasury Department regulations, we inform you that, 
unless otherwise indicated in writing, any U.S. Federal tax advice contained in 
this communication  (including any attachments) is not intended or written to 
be used, and cannot be used, for the purpose of (1) avoiding penalties under 
the Internal Revenue Code or applicable state and local provisions or (2) 
promoting, marketing or recommending to ano

RE: Restore server

[Jim Dandy]

The document you referenced is for restoring to different hardware.  My
hardware is the same.  Will the procedure I outlined work - or at least
not cause damage to my existing infrastructure?

Curt

> -Original Message-
> From: Bob Fronk [mailto:b...@btrfronk.com]
> Sent: Tuesday, July 14, 2009 11:44 AM
> To: MS-Exchange Admin Issues
> Subject: RE: Restore server
> 
>
http://www.msexchange.org/tutorials/Restoring-Exchange-Server2003-Altern
ate-
> Hardware.html
> 
> 
> --
> Bob Fronk
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu]
> Sent: Tuesday, July 14, 2009 2:35 PM
> To: MS-Exchange Admin Issues
> Subject: Restore server
> 
> I have an Exchange 2003 frontend server running on Windows Server 2003
> that is having some issues with its hard drive.  I have another
> identical hardware server.  I've loaded Windows Server 2003 on the new
> hardware but no Exchange.  It's not a domain member, has a different
> NetBIOS name and it does not have all the Windows patches installed on
> the limper.  My plan was to restore the backup from the limping server
> to the other server, unplug the limping server from the network and
then
> reboot the new server.  My hope is of course that the new server will
> come up and begin functioning as the limper did (but without the hard
> drive issue).  However, if the new server doesn't come back up I
figure
> I can just power it down, plug the limper back in and get things up
> again quickly.  Does anyone see any issues in doing things this way?
> I'm using Backup Exec 12.0.
> 
> Thanks for your help.
> 
> Curt
> 
> 
> 

Re: Can't Deliver to one Domian

[Jonathan Link]

Oh, I understand what should happen.

On Tue, Jul 14, 2009 at 4:11 PM, Don Guyer wrote:

>  Now that I’ve read the error again, it looks like it was 12 hours time
> difference.
>
>
>
> If it reached the destination server with an unknown/bad address, it
> should’ve replied immediately. Unless we’re talking about a part of the
> world that has a 12 hour time difference.
>
>
>
> Details always help.
>
>
>
> Don Guyer
>
> Systems Engineer - Information Services
>
> Prudential, Fox & Roach/Trident Group
>
> 431 W. Lancaster Avenue
>
> Devon, PA 19333
>
> Direct: (610) 993-3299
>
> Fax: (610) 650-5306
>
> don.gu...@prufoxroach.com
>
>
>
> *From:* Jonathan Link [mailto:jonathan.l...@gmail.com]
> *Sent:* Tuesday, July 14, 2009 4:07 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Can't Deliver to one Domian
>
>
>
> Or 9 times out of 10 when a user shows me this, I ask if they've verified
> the email address.  This domain and rr are really bad with these generic
> messages when in actuality it's not a valid email address.
>
>
>
>
>
> On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
> wrote:
>
> Looks like it tried for 24 hours and gave up. Probably network/DNS related.
> Did this work before?
>
>
>
> Don Guyer
>
> Systems Engineer - Information Services
>
> Prudential, Fox & Roach/Trident Group
>
> 431 W. Lancaster Avenue
>
> Devon, PA 19333
>
> Direct: (610) 993-3299
>
> Fax: (610) 650-5306
>
> don.gu...@prufoxroach.com
>
>
>
> *From:* Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
>
> *Sent:* Tuesday, July 14, 2009 3:36 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Can't Deliver to one Domian
>
>
>
> Below is what we get back
>
>
>
> Your message did not reach some or all of the intended recipients.
>
>   Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am
>
>   Sent: 13/07/2009 2:54 PM
>
> The following recipient(s) cannot be reached:
>
>   n...@sympatico.ca on 14/07/2009 2:57 AM
>
> Could not deliver the message in the time limit specified.
> Please retry or contact your administrator.
>  --
>
> *From:* Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com
> ]
> *Sent:* Fri 10/07/2009 1:46 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Can't Deliver to one Domian
>
> I have a SBS 2003; for some reason users in that office can's deliver to
> Sympatico.ca domain. we can deliver to any other domain without any issue.
> I have checked exchange and the sonicwall an can not see anything.
>
>
>
> I should also mention that Bell is the ISP in question and no black listing
> is in place.
>
>
>
> Can some one help?
>
>
>
>
>
> Lynden
>
>
>
>
>
>
>

Exmerge Question

[Chyka, Robert]

We need to recreate a fresh mailbox for a user and they have a lot of
folders that need to be backed up so that we can create a new mailbox
for them.  Since there are too many folders to export one at a time, I
was going to exmerge them to a .pst.  I never have used Exmerge and was
wondering the syntax I would use for a single user to grab their whole
mailbox for backup while I recreate it.  After the recreating I would
want to restore all of the contents into the new mailbox.

 

Windows 2003 Server running Exchange 2003.

 

Thanks for your help...Just didn't want to screw it up...

 

Bob

RE: Exmerge Question

[Wulff Jr, Ronald J.]

Just launch the exmerge.exe and follow the prompts.  It is easy

 

Ronald Wulff Jr 
412.288.3601 
rwu...@reedsmith.com 

Reed Smith LLP 
20 Stanwix St

Suite 1200
Pittsburgh, PA 15222

 

From: Chyka, Robert [mailto:bch...@medaille.edu] 
Sent: Tuesday, July 14, 2009 4:37 PM
To: MS-Exchange Admin Issues
Subject: Exmerge Question

 

We need to recreate a fresh mailbox for a user and they have a lot of
folders that need to be backed up so that we can create a new mailbox
for them.  Since there are too many folders to export one at a time, I
was going to exmerge them to a .pst.  I never have used Exmerge and was
wondering the syntax I would use for a single user to grab their whole
mailbox for backup while I recreate it.  After the recreating I would
want to restore all of the contents into the new mailbox.

 

Windows 2003 Server running Exchange 2003.

 

Thanks for your help...Just didn't want to screw it up...

 

Bob 
 
* * *
 
This E-mail, along with any attachments, is considered confidential and may 
well be legally privileged. If you have received it in error, you are on notice 
of its status. Please notify us immediately by reply e-mail and then delete 
this message from your system. Please do not copy it or use it for any 
purposes, or disclose its contents to any other person. Thank you for your 
cooperation.
* * *
To ensure compliance with Treasury Department regulations, we inform you that, 
unless otherwise indicated in writing, any U.S. Federal tax advice contained in 
this communication  (including any attachments) is not intended or written to 
be used, and cannot be used, for the purpose of (1) avoiding penalties under 
the Internal Revenue Code or applicable state and local provisions or (2) 
promoting, marketing or recommending to another party any tax-related matters 
addressed herein.
Disclaimer Version RS.US.1.01.03
pdc1

RE: Exmerge Question

[Chyka, Robert]

Will do.

 

Thanks!

 



From: Wulff Jr, Ronald J. [mailto:rwu...@reedsmith.com] 
Sent: Tuesday, July 14, 2009 4:38 PM
To: MS-Exchange Admin Issues
Subject: RE: Exmerge Question

 

Just launch the exmerge.exe and follow the prompts.  It is easy

 

Ronald Wulff Jr 
412.288.3601 
rwu...@reedsmith.com 

Reed Smith LLP 
20 Stanwix St

Suite 1200
Pittsburgh, PA 15222

 

From: Chyka, Robert [mailto:bch...@medaille.edu] 
Sent: Tuesday, July 14, 2009 4:37 PM
To: MS-Exchange Admin Issues
Subject: Exmerge Question

 

We need to recreate a fresh mailbox for a user and they have a lot of
folders that need to be backed up so that we can create a new mailbox
for them.  Since there are too many folders to export one at a time, I
was going to exmerge them to a .pst.  I never have used Exmerge and was
wondering the syntax I would use for a single user to grab their whole
mailbox for backup while I recreate it.  After the recreating I would
want to restore all of the contents into the new mailbox.

 

Windows 2003 Server running Exchange 2003.

 

Thanks for your help...Just didn't want to screw it up...

 

Bob

 

* * * 

 

This E-mail, along with any attachments, is considered confidential and
may well be legally privileged. If you have received it in error, you
are on notice of its status. Please notify us immediately by reply
e-mail and then delete this message from your system. Please do not copy
it or use it for any purposes, or disclose its contents to any other
person. Thank you for your cooperation. 

* * * 

To ensure compliance with Treasury Department regulations, we inform you
that, unless otherwise indicated in writing, any U.S. Federal tax advice
contained in this communication  (including any attachments) is not
intended or written to be used, and cannot be used, for the purpose of
(1) avoiding penalties under the Internal Revenue Code or applicable
state and local provisions or (2) promoting, marketing or recommending
to another party any tax-related matters addressed herein. 

Disclaimer Version RS.US.1.01.03

pdc1

RE: Can't Deliver to one Domian

[Don Guyer]

I didn't mean that towards you, I was just thinking out loud and typing.

 

J

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:32 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

 

Oh, I understand what should happen.

On Tue, Jul 14, 2009 at 4:11 PM, Don Guyer 
wrote:

Now that I've read the error again, it looks like it was 12 hours time
difference.

 

If it reached the destination server with an unknown/bad address, it
should've replied immediately. Unless we're talking about a part of the
world that has a 12 hour time difference.

 

Details always help.

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:07 PM 


To: MS-Exchange Admin Issues

Subject: Re: Can't Deliver to one Domian 

 

Or 9 times out of 10 when a user shows me this, I ask if they've
verified the email address.  This domain and rr are really bad with
these generic messages when in actuality it's not a valid email address.



 

On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

 

 

RE: Restore server

[Steven M. Caesare]

Not using BE myself... it has a bare metal restore option I assume?

-sc

> -Original Message-
> From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu]
> Sent: Tuesday, July 14, 2009 2:35 PM
> To: MS-Exchange Admin Issues
> Subject: Restore server
> 
> I have an Exchange 2003 frontend server running on Windows Server 2003
> that is having some issues with its hard drive.  I have another
> identical hardware server.  I've loaded Windows Server 2003 on the new
> hardware but no Exchange.  It's not a domain member, has a different
> NetBIOS name and it does not have all the Windows patches installed on
> the limper.  My plan was to restore the backup from the limping server
> to the other server, unplug the limping server from the network and
> then
> reboot the new server.  My hope is of course that the new server will
> come up and begin functioning as the limper did (but without the hard
> drive issue).  However, if the new server doesn't come back up I
figure
> I can just power it down, plug the limper back in and get things up
> again quickly.  Does anyone see any issues in doing things this way?
> I'm using Backup Exec 12.0.
> 
> Thanks for your help.
> 
> Curt
> 

RE: Restore server

[Bob Fronk]

It is still "Different Hardware", even if it has same specs.

--
Bob Fronk
���Please print only��as needed.






-Original Message-
From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu] 
Sent: Tuesday, July 14, 2009 4:25 PM
To: MS-Exchange Admin Issues
Subject: RE: Restore server

The document you referenced is for restoring to different hardware.  My
hardware is the same.  Will the procedure I outlined work - or at least
not cause damage to my existing infrastructure?

Curt

> -Original Message-
> From: Bob Fronk [mailto:b...@btrfronk.com]
> Sent: Tuesday, July 14, 2009 11:44 AM
> To: MS-Exchange Admin Issues
> Subject: RE: Restore server
> 
>
http://www.msexchange.org/tutorials/Restoring-Exchange-Server2003-Altern
ate-
> Hardware.html
> 
> 
> --
> Bob Fronk
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu]
> Sent: Tuesday, July 14, 2009 2:35 PM
> To: MS-Exchange Admin Issues
> Subject: Restore server
> 
> I have an Exchange 2003 frontend server running on Windows Server 2003
> that is having some issues with its hard drive.  I have another
> identical hardware server.  I've loaded Windows Server 2003 on the new
> hardware but no Exchange.  It's not a domain member, has a different
> NetBIOS name and it does not have all the Windows patches installed on
> the limper.  My plan was to restore the backup from the limping server
> to the other server, unplug the limping server from the network and
then
> reboot the new server.  My hope is of course that the new server will
> come up and begin functioning as the limper did (but without the hard
> drive issue).  However, if the new server doesn't come back up I
figure
> I can just power it down, plug the limper back in and get things up
> again quickly.  Does anyone see any issues in doing things this way?
> I'm using Backup Exec 12.0.
> 
> Thanks for your help.
> 
> Curt
> 
> 
> 

Re: Changing Subject Line Limits

[Ben Scott]

On Tue, Jul 14, 2009 at 11:32 AM, Micheal Espinola
Jr wrote:
> Readability of such long subject line is difficult if not impossible
> for many mail readers.

  Between BASE64 encoding overhead, UTF-8 encoding overhead, Unicode
codepoints > 255, and combining characters (character modifiers), a
single displayed glyph might well occupy several octets.  In the
pathological case, I think 255 octets could be only 23 displayed
glyphs[1].  The pathological case isn't going to happen in reality,
but it illustrates the point: You're assuming octets == glyphs, and
that's very wrong for the encoded subjects the OP is seeing.

  I would follow MBS's suggestion, use SMTP logging or a packet
sniffer to see if the problem is actually before Exchange or not.

  I would also try a different mail client, accessing Exchange with
IMAP.  This could be an issue in Outlook, or even a MAPI protocol
limitation.

[1] Assume we're dealing with U+1 and up.  That's 4 octets per
Unicode character in UTF-8.  Assume *every* character is modified.
That's 8 octets per displayed glyph.  Assume BASE64 overhead of 1.37.
That's approximately 10.96 octets per glyph.  255 / 10.96 = 23 and
change.

-- Ben

Re: Can't Deliver to one Domian

[Peter van Houten]

Thinking aloud too:
---
OP already said it was not blacklisted.

Unlikely to be a TLS issue as the handshake would cough immediately.

Possibly SMTP recipient problem but it is a large outfit with plenty of
servers.

Time zone unlikely to be a factor as it is going from Boston to Toronto
which, as I remember is only several hundred miles...

Sympatico looks like it is tied to MSN ~ not a blocked keyword in the
Sonicwall?

--
Peter van Houten

On the 14/07/2009 22:23, Wulff Jr, Ronald J. wrote the following:

Sender domain could be blacklisted

Recipient might be expecting TLS

Recipient might be having SMTP server issues.

Way too many things to guess really

*Ronald Wulff Jr*
412.288.3601
rwu...@reedsmith.com 

Reed Smith LLP
20 Stanwix St

Suite 1200
Pittsburgh, PA 15222

*From:* Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
*Sent:* Tuesday, July 14, 2009 4:17 PM
*To:* MS-Exchange Admin Issues
*Subject:* RE: Can't Deliver to one Domian

“Could not deliver the message in the time limit specified. Please retry
or contact your administrator.”

Usually means it gave up after multiple temporary failures and retries.
Bad address is a permanent failure.

I’m betting on a network, dns, or firewall problem.



*From:* Don Guyer [mailto:don.gu...@prufoxroach.com]
*Sent:* Tuesday, July 14, 2009 3:12 PM
*To:* MS-Exchange Admin Issues
*Subject:* RE: Can't Deliver to one Domian

Now that I’ve read the error again, it looks like it was 12 hours time
difference.

If it reached the destination server with an unknown/bad address, it
should’ve replied immediately. Unless we’re talking about a part of the
world that has a 12 hour time difference.

Details always help.

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com 

*From:* Jonathan Link [mailto:jonathan.l...@gmail.com]
*Sent:* Tuesday, July 14, 2009 4:07 PM
*To:* MS-Exchange Admin Issues
*Subject:* Re: Can't Deliver to one Domian

Or 9 times out of 10 when a user shows me this, I ask if they've
verified the email address. This domain and rr are really bad with these
generic messages when in actuality it's not a valid email address.



On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer mailto:don.gu...@prufoxroach.com>> wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com 

*From:* Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com
]
*Sent:* Tuesday, July 14, 2009 3:36 PM
*To:* MS-Exchange Admin Issues
*Subject:* RE: Can't Deliver to one Domian

Below is what we get back

Your message did not reach some or all of the intended recipients.

Subject: FW: Please confirm if you receive -Jul13/09 11:00am

Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

n...@sympatico.ca  on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified. Please retry
or contact your administrator.



*From:* Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com
]
*Sent:* Fri 10/07/2009 1:46 PM
*To:* MS-Exchange Admin Issues
*Subject:* Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue. I have checked exchange and the sonicwall an can not see anything.

I should also mention that Bell is the ISP in question and no black
listing is in place.

Can some one help?

Lynden

**

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**

* * *
This E-mail, along with any attachments, is considered confidential and
may well be legally privileged. If you have received it in error

Re: Changing Subject Line Limits

[Ben Scott]

On Tue, Jul 14, 2009 at 4:44 PM, Ben Scott wrote:
> You're assuming octets == glyphs, and
> that's very wrong for the encoded subjects the OP is seeing.

  Of course, I then thought to actually decode the BASE64 we were
given.  The subject line that made it this far is pure ASCII, and also
ridiculously long.

  If the rest of the subject line is pure ASCII, there's no need for
UTF-8 or BASE64.  Reconfigure the sending system not to do that, and
you'll gain at least BASE64 encoding overhead.

  The decoded subject line was:

PeopleSoft error report: Error: First operand of . is NULL, so cannot
access member Len. (180,236) FUNCLIB_EXT_APP.RESUME.FieldFormula
Name:set_resume_step  PCPC:13552  Statement:

  Per ME2, that should be in the message body, and a summary, e.g.,
"PeopleSoft error report", in the subject.

-- Ben

Re: Distribution lists

[Kurt Buff]

See, there ya go, ruining a perfectly satirical exchange.

Heh.

Of course it's unethical. Don't really do it. But it sure is fun to
think about, isn't it?

Kurt

On Tue, Jul 14, 2009 at 09:58, Jonathan Link wrote:
> Chances are he'd be violating the org's AUP, since most AUP's have a
> stipulation about using assigned accounts.  That is NOT a good thing.  Just
> because you don't get caught, or you have a good intention doesn't mean the
> action itself is right/good.
>
> -Jonathan
>
> On Tue, Jul 14, 2009 at 12:32 PM, Kurt Buff  wrote:
>>
>> And that's a bad thing?
>>
>> If you do it from an executive's PC, you get either or both of a
>> lockdown of the DL and locking screensavers.
>>
>> If you do it from your least favorite non-executive's machine you get the
>> same.
>>
>> Seems like a win for you no matter what.
>>
>> On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
>> > Think it through.  If you do it from somebody's machine who would have
>> > been
>> > allowed to use the DL, such as an executive, it doesn't help at all.
>> > Not
>> > to mention, it will probably be found out that it was keyboard-jacking,
>> > and
>> > not employee abuse of the DL, and the result will be mandated
>> > password-protected screen savers throughout.
>> >
>> >
>> >
>> > Carl
>> >
>> >
>> >
>> > From: James Rankin [mailto:kz2...@googlemail.com]
>> > Sent: Tuesday, July 14, 2009 3:47 AM
>> > To: MS-Exchange Admin Issues
>> > Subject: Re: Distribution lists
>> >
>> >
>> >
>> > That is actually a fine idea
>> >
>> > 2009/7/13 Kurt Buff 
>> >
>> > This is an easy fix.
>> >
>> > Find (or compose) a silly email on someone else's non-attended,
>> > non-screensavered machine, and send it to the all users list.
>> >
>> > One of my favorites is to announce candy or cookies at the victim's
>> > desk.
>> >
>> > Be sure to wipe up for fingerprints afterward, if you happen to do it
>> > to an executive, though.
>> >
>> > Heh.
>> >
>> > On Mon, Jul 13, 2009 at 08:43, Kennedy,
>> > Jim
>> > wrote:
>> >> +1
>> >>
>> >>
>> >>
>> >> You have given them the recommendation and they have decided. Let it
>> >> go,
>> >> move on and ignore the emails in the future. You may be sick of them
>> >> but
>> >> management is not. Yet.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> >> Sent: Monday, July 13, 2009 11:22 AM
>> >> To: MS-Exchange Admin Issues
>> >> Subject: RE: Distribution lists
>> >>
>> >>
>> >>
>> >> In that case my advice is to turn a blind eye and let those execs worry
>> >> about it.  If it’s un-monitored, it’s just that.  No worries.
>> >>
>> >> M
>> >>
>> >>
>> >>
>> >> 
>> >>
>> >> From: James Rankin [mailto:kz2...@googlemail.com]
>> >> Sent: Monday, July 13, 2009 7:20 AM
>> >> To: MS-Exchange Admin Issues
>> >> Subject: Re: Distribution lists
>> >>
>> >>
>> >>
>> >> I would if I could, but I can't. Not until some idiot sends something
>> >> that
>> >> gets on one of the exec team's nerves. Just wondering if there was any
>> >> other
>> >> way I could spare myself some pain.
>> >>
>> >> I know the old adage about technological solutions to behavioural
>> >> problems,
>> >> though, it has never rung truer
>> >>
>> >> 2009/7/13 Matt Moore 
>> >>
>> >> Limit access to a chosen few and all the spam goes away.
>> >>
>> >> M
>> >>
>> >>
>> >>
>> >> 
>> >>
>> >> From: James Rankin [mailto:kz2...@googlemail.com]
>> >> Sent: Monday, July 13, 2009 7:07 AM
>> >>
>> >> To: MS-Exchange Admin Issues
>> >> Subject: Distribution lists
>> >>
>> >>
>> >>
>> >> Afternoon Exchange gurus
>> >>
>> >> Is it possible to have the "All Staff" distribution list (or any other,
>> >> really) set up so that when an email is sent to it, it goes to an
>> >> administrator for approval first? I am sick of getting emails that say
>> >> "there is a salesman selling cards in reception" and when someone
>> >> spammed
>> >> the DL with a hoax that was well-documented on snopes.com, I ended up
>> >> getting a reprimand from my boss about being harsh to users. I only
>> >> threatened to remove her ability to send to the DL. Sheesh. I know that
>> >> we
>> >> shouldn't give all users the ability to send to it, but I doubt I am
>> >> going
>> >> to shift my boss's boss's stance on this one.
>> >>
>> >> Any other pointers would be also gratefully received, I am not much of
>> >> an
>> >> Exchange bod.
>> >>
>> >> TIA,
>> >>
>> >>
>> >> JRR
>> >>
>> >> --
>> >> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
>> >> into
>> >> the machine wrong figures, will the right answers come out?' I am not
>> >> able
>> >> rightly to apprehend the kind of confusion of ideas that could provoke
>> >> such
>> >> a question."
>> >>
>> >> http://raythestray.blogspot.com
>> >>
>> >> Checked by AVG - www.avg.com
>> >> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date:
>> >> 07/12/09
>> >> 17:56:00
>> >>
>> >>
>> >> --
>> >> "On two occasions.

Re: Distribution lists

[Kurt Buff]

ROFL!

I remember a few years ago when just such a reply-all storm hit MSFT.
That was fun to hear about - but, I'm glad I wasn't on the Exchange
admin team.

IIRC, major portions of their Exchange infrastructure were down for a
day or three.

Kurt

On Tue, Jul 14, 2009 at 12:47, Don Andrews wrote:
> Agreed – all it took here was a few multi-megabyte oops followed by a huge
> number of idiots asking “why am I getting this” in a reply to all.  As our
> Exchange environment is centralized, even locations with good pipes will
> experience a few minutes of NO response from anything when a 6-8 meg message
> is sent to several thousand users and reply to all is lots of fun as well.
>
>
>
> 
>
> From: James Rankin [mailto:kz2...@googlemail.com]
> Sent: Tuesday, July 14, 2009 12:47 AM
> To: MS-Exchange Admin Issues
> Subject: Re: Distribution lists
>
>
>
> That is actually a fine idea
>
> 2009/7/13 Kurt Buff 
>
> This is an easy fix.
>
> Find (or compose) a silly email on someone else's non-attended,
> non-screensavered machine, and send it to the all users list.
>
> One of my favorites is to announce candy or cookies at the victim's desk.
>
> Be sure to wipe up for fingerprints afterward, if you happen to do it
> to an executive, though.
>
> Heh.
>
> On Mon, Jul 13, 2009 at 08:43, Kennedy, Jim
> wrote:
>> +1
>>
>>
>>
>> You have given them the recommendation and they have decided. Let it go,
>> move on and ignore the emails in the future. You may be sick of them but
>> management is not. Yet.
>>
>>
>>
>>
>>
>>
>>
>> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> Sent: Monday, July 13, 2009 11:22 AM
>> To: MS-Exchange Admin Issues
>> Subject: RE: Distribution lists
>>
>>
>>
>> In that case my advice is to turn a blind eye and let those execs worry
>> about it.  If it’s un-monitored, it’s just that.  No worries.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:20 AM
>> To: MS-Exchange Admin Issues
>> Subject: Re: Distribution lists
>>
>>
>>
>> I would if I could, but I can't. Not until some idiot sends something that
>> gets on one of the exec team's nerves. Just wondering if there was any
>> other
>> way I could spare myself some pain.
>>
>> I know the old adage about technological solutions to behavioural
>> problems,
>> though, it has never rung truer
>>
>> 2009/7/13 Matt Moore 
>>
>> Limit access to a chosen few and all the spam goes away.
>>
>> M
>>
>>
>>
>> 
>>
>> From: James Rankin [mailto:kz2...@googlemail.com]
>> Sent: Monday, July 13, 2009 7:07 AM
>>
>> To: MS-Exchange Admin Issues
>> Subject: Distribution lists
>>
>>
>>
>> Afternoon Exchange gurus
>>
>> Is it possible to have the "All Staff" distribution list (or any other,
>> really) set up so that when an email is sent to it, it goes to an
>> administrator for approval first? I am sick of getting emails that say
>> "there is a salesman selling cards in reception" and when someone spammed
>> the DL with a hoax that was well-documented on snopes.com, I ended up
>> getting a reprimand from my boss about being harsh to users. I only
>> threatened to remove her ability to send to the DL. Sheesh. I know that we
>> shouldn't give all users the ability to send to it, but I doubt I am going
>> to shift my boss's boss's stance on this one.
>>
>> Any other pointers would be also gratefully received, I am not much of an
>> Exchange bod.
>>
>> TIA,
>>
>>
>> JRR
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>>
>>
>> --
>> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
>> the machine wrong figures, will the right answers come out?' I am not able
>> rightly to apprehend the kind of confusion of ideas that could provoke
>> such
>> a question."
>>
>> http://raythestray.blogspot.com
>>
>> Checked by AVG - www.avg.com
>> Version: 8.5.387 / Virus Database: 270.13.7/ - Release Date: 07/12/09
>> 17:56:00
>
>
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke such
> a question."
>
> http://raythestray.blogspot.com

RE: Distribution lists

[Campbell, Rob]

As long as you're thinking about doing it, you might as well think about 
requesting delivery and read receipts while you're at it.

-Original Message-
From: Kurt Buff [mailto:kurt.b...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:05 PM
To: MS-Exchange Admin Issues
Subject: Re: Distribution lists

See, there ya go, ruining a perfectly satirical exchange.

Heh.

Of course it's unethical. Don't really do it. But it sure is fun to
think about, isn't it?

Kurt

On Tue, Jul 14, 2009 at 09:58, Jonathan Link wrote:
> Chances are he'd be violating the org's AUP, since most AUP's have a
> stipulation about using assigned accounts.  That is NOT a good thing.  Just
> because you don't get caught, or you have a good intention doesn't mean the
> action itself is right/good.
>
> -Jonathan
>
> On Tue, Jul 14, 2009 at 12:32 PM, Kurt Buff  wrote:
>>
>> And that's a bad thing?
>>
>> If you do it from an executive's PC, you get either or both of a
>> lockdown of the DL and locking screensavers.
>>
>> If you do it from your least favorite non-executive's machine you get the
>> same.
>>
>> Seems like a win for you no matter what.
>>
>> On Tue, Jul 14, 2009 at 05:30, Carl Houseman wrote:
>> > Think it through.  If you do it from somebody's machine who would have
>> > been
>> > allowed to use the DL, such as an executive, it doesn't help at all.
>> > Not
>> > to mention, it will probably be found out that it was keyboard-jacking,
>> > and
>> > not employee abuse of the DL, and the result will be mandated
>> > password-protected screen savers throughout.
>> >
>> >
>> >
>> > Carl
>> >
>> >
>> >
>> > From: James Rankin [mailto:kz2...@googlemail.com]
>> > Sent: Tuesday, July 14, 2009 3:47 AM
>> > To: MS-Exchange Admin Issues
>> > Subject: Re: Distribution lists
>> >
>> >
>> >
>> > That is actually a fine idea
>> >
>> > 2009/7/13 Kurt Buff 
>> >
>> > This is an easy fix.
>> >
>> > Find (or compose) a silly email on someone else's non-attended,
>> > non-screensavered machine, and send it to the all users list.
>> >
>> > One of my favorites is to announce candy or cookies at the victim's
>> > desk.
>> >
>> > Be sure to wipe up for fingerprints afterward, if you happen to do it
>> > to an executive, though.
>> >
>> > Heh.
>> >
>> > On Mon, Jul 13, 2009 at 08:43, Kennedy,
>> > Jim
>> > wrote:
>> >> +1
>> >>
>> >>
>> >>
>> >> You have given them the recommendation and they have decided. Let it
>> >> go,
>> >> move on and ignore the emails in the future. You may be sick of them
>> >> but
>> >> management is not. Yet.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> From: Matt Moore [mailto:mattmoore...@hotmail.com]
>> >> Sent: Monday, July 13, 2009 11:22 AM
>> >> To: MS-Exchange Admin Issues
>> >> Subject: RE: Distribution lists
>> >>
>> >>
>> >>
>> >> In that case my advice is to turn a blind eye and let those execs worry
>> >> about it.  If it's un-monitored, it's just that.  No worries.
>> >>
>> >> M
>> >>
>> >>
>> >>
>> >> 
>> >>
>> >> From: James Rankin [mailto:kz2...@googlemail.com]
>> >> Sent: Monday, July 13, 2009 7:20 AM
>> >> To: MS-Exchange Admin Issues
>> >> Subject: Re: Distribution lists
>> >>
>> >>
>> >>
>> >> I would if I could, but I can't. Not until some idiot sends something
>> >> that
>> >> gets on one of the exec team's nerves. Just wondering if there was any
>> >> other
>> >> way I could spare myself some pain.
>> >>
>> >> I know the old adage about technological solutions to behavioural
>> >> problems,
>> >> though, it has never rung truer
>> >>
>> >> 2009/7/13 Matt Moore 
>> >>
>> >> Limit access to a chosen few and all the spam goes away.
>> >>
>> >> M
>> >>
>> >>
>> >>
>> >> 
>> >>
>> >> From: James Rankin [mailto:kz2...@googlemail.com]
>> >> Sent: Monday, July 13, 2009 7:07 AM
>> >>
>> >> To: MS-Exchange Admin Issues
>> >> Subject: Distribution lists
>> >>
>> >>
>> >>
>> >> Afternoon Exchange gurus
>> >>
>> >> Is it possible to have the "All Staff" distribution list (or any other,
>> >> really) set up so that when an email is sent to it, it goes to an
>> >> administrator for approval first? I am sick of getting emails that say
>> >> "there is a salesman selling cards in reception" and when someone
>> >> spammed
>> >> the DL with a hoax that was well-documented on snopes.com, I ended up
>> >> getting a reprimand from my boss about being harsh to users. I only
>> >> threatened to remove her ability to send to the DL. Sheesh. I know that
>> >> we
>> >> shouldn't give all users the ability to send to it, but I doubt I am
>> >> going
>> >> to shift my boss's boss's stance on this one.
>> >>
>> >> Any other pointers would be also gratefully received, I am not much of
>> >> an
>> >> Exchange bod.
>> >>
>> >> TIA,
>> >>
>> >>
>> >> JRR
>> >>
>> >> --
>> >> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put
>> >> into
>> >> the machine wrong figures, will the right answers come out?' I am not
>> >> able
>> >> rightly to apprehend the ki

Re: Exmerge Question

[Eric Woodford]

Why are you creating a new mailbox for a user? The old one moldy or
something?

On Tue, Jul 14, 2009 at 1:37 PM, Chyka, Robert  wrote:

>  We need to recreate a fresh mailbox for a user and they have a lot of
> folders that need to be backed up so that we can create a new mailbox for
> them.  Since there are too many folders to export one at a time, I was going
> to exmerge them to a .pst.  I never have used Exmerge and was wondering the
> syntax I would use for a single user to grab their whole mailbox for backup
> while I recreate it.  After the recreating I would want to restore all of
> the contents into the new mailbox.
>
>
>
> Windows 2003 Server running Exchange 2003.
>
>
>
> Thanks for your help…Just didn’t want to screw it up…
>
>
>
> Bob
>

Re: Exmerge Question

[Ben Scott]

On Tue, Jul 14, 2009 at 5:12 PM, Eric Woodford wrote:
> Why are you creating a new mailbox for a user? The old one moldy or
> something?

  This used to be MS PSS's first response for just about any
malfunction limited to a single mailbox.  I guess they assume the
mailbox is corrupt and EXMERGE won't copy the corruption.  I don't
know if they still do things this way; haven't called them for
Exchange in over a year.  Knock on wood.

-- Ben

RE: Exmerge Question

[Chyka, Robert]

Mailbox is corrupted...these were instructions from Microsoft.

-Original Message-
From: "Eric Woodford" 
To: "MS-Exchange Admin Issues" 
Sent: 7/14/09 5:13 PM
Subject: Re: Exmerge Question

Why are you creating a new mailbox for a user? The old one moldy or
something?

On Tue, Jul 14, 2009 at 1:37 PM, Chyka, Robert  wrote:

>  We need to recreate a fresh mailbox for a user and they have a lot of
> folders that need to be backed up so that we can create a new mailbox for
> them.  Since there are too many folders to export one at a time, I was going
> to exmerge them to a .pst.  I never have used Exmerge and was wondering the
> syntax I would use for a single user to grab their whole mailbox for backup
> while I recreate it.  After the recreating I would want to restore all of
> the contents into the new mailbox.
>
>
>
> Windows 2003 Server running Exchange 2003.
>
>
>
> Thanks for your help…Just didn’t want to screw it up…
>
>
>
> Bob
>

RE: Issue

[Doug Rooney]

Hello all, I am getting MANY of these a day, any suggestions?

 

The MessageLabs Email Security System discovered a possible virus or
unauthorised code (such as a Trojan) in an email sent to you.

The email has now been quarantined and was not delivered.

Please read the whole of this email carefully.  It explains the status
of your email, the nature of the intercepted virus and the next steps
for addressing the problem.

To help identify the quarantined email:

The message sender was 

bounce-8597748-8237...@lyris.sunbelt-software.com

mich...@owa.smithcons.com

exchangelist@lyris.sunbelt-software.com

 

The message originating IP was 64.128.133.151 The message recipients
were 

d...@sonomatilemakers.com

 

The message title was RE: Hub Server

The message date was Tue, 14 Jul 2009 15:49:11 + The virus or
unauthorised code identified in the email is

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in 

>>> '5931055T_1X_PM2_EMQ_MT__message.txt'. Heuristics score: 200 

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in 

>>> '5931055_2X_PM3_EMQ_MH__message.htm'. Heuristics score: 200

 

Some viruses forge the sender address. For more information please visit
the virus FAQ's link at the bottom of this page.

The message was diverted into the virus holding pen on mail server
server-8.tower-190.messagelabs.com (pen id 66693_124758) and will be
held for 30 days before being destroyed Please contact your IT Helpdesk
or Support Department for further assistance.

Answers to virus-related questions can be found on the MessageLabs Virus
FAQ page at

http://www.messagelabs.com/page.asp?id=628

 

Thank You 

~Doug Rooney 
Sonoma Tilemakers 
IT Manager 
7750 Bell Rd. 
Windsor Ca, 95492 
(707) 837-8177 X211
(707) 837-9472 FAX 
i...@sonomatilemakers.com   

 

 

RE: Issue

[John Cook]

Bad Mikey!

John W. Cook
Systems Administrator
Partnership For Strong Families
315 SE 2nd Ave
Gainesville, Fl 32601
Office (352) 393-2741 x320
Cell (352) 215-6944
Fax (352) 393-2746
MCSE, MCTS, MCP+I, A+, N+, VSP

From: Doug Rooney [mailto:d...@sonomatilemakers.com]
Sent: Tuesday, July 14, 2009 5:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Issue
Importance: High


Hello all, I am getting MANY of these a day, any suggestions?



The MessageLabs Email Security System discovered a possible virus or 
unauthorised code (such as a Trojan) in an email sent to you.

The email has now been quarantined and was not delivered.

Please read the whole of this email carefully.  It explains the status of your 
email, the nature of the intercepted virus and the next steps for addressing 
the problem.

To help identify the quarantined email:

The message sender was


bounce-8597748-8237...@lyris.sunbelt-software.com

mich...@owa.smithcons.com


exchangelist@lyris.sunbelt-software.com



The message originating IP was 64.128.133.151 The message recipients were

d...@sonomatilemakers.com



The message title was RE: Hub Server

The message date was Tue, 14 Jul 2009 15:49:11 + The virus or unauthorised 
code identified in the email is

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in

>>> '5931055T_1X_PM2_EMQ_MT__message.txt'. Heuristics score: 200

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in

>>> '5931055_2X_PM3_EMQ_MH__message.htm'. Heuristics score: 200



Some viruses forge the sender address. For more information please visit the 
virus FAQ's link at the bottom of this page.

The message was diverted into the virus holding pen on mail server 
server-8.tower-190.messagelabs.com (pen id 66693_124758) and will be held 
for 30 days before being destroyed Please contact your IT Helpdesk or Support 
Department for further assistance.

Answers to virus-related questions can be found on the MessageLabs Virus FAQ 
page at

http://www.messagelabs.com/page.asp?id=628


Thank You
~Doug Rooney
Sonoma Tilemakers
IT Manager
7750 Bell Rd.
Windsor Ca, 95492
(707) 837-8177 X211
(707) 837-9472 FAX
i...@sonomatilemakers.com





CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you really need 
to.

This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the company. 
Warning: Although precautions have been taken to make sure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage that arise from the use of this email or attachments.

replace Exchange 2003 server

[SMREKAR, JACK]

We upgraded to Exchange 2007 Enterprise Exchange. It was working fairly well 
but we were still having some Outlook 2007 hanging issues where when you first 
stated outlook it would just sit there or every now and then it would also hang.

We then had a consultant come in and help with the configuring of the transport 
roles and he removed the last 2003 Enterprise Exchange server but did not 
remove it cleanly so for some reason we have to redo THE ADPREP as  that is 
what the install of Exchange 2007 told us to do. So after running adprep to see 
where the issue was that the installer of 2007 mentioned and that error is that 
the 2003 Exchange server, that was removed in correctly, cannot be found.

I am guessing that if we try to bring up a new 2003 Exchange server and name it 
the same as the last Exchange that was removed that we will still have issues 
as there were roles on the 2003 server that either did not get transferred 
correctly or did not get transferred at all.

So the question is, can I just put up a 2003 Exchange server to get rid of the 
error or is there a different way to remove any issues that Exchange 2007 is 
having with the phantom server.

Thanks

Jack Smrekar
Appleton Area School District
920-993-7062 Ext. 2123
A+  N+  Server +

[cid:image001.gif@01CA0491.803C1270]
<>

Re: Exmerge Question

[Eric Woodford]

I ask because at a former employer, the Desktop "Apple support" team would
ask us to do this EVERYTIME the Entourage client took a dump.

On my '03 servers, rebuilding the mailbox has fixed the issue once. An issue
that ended up coming back 2 months later and impacting 3 (original+2
friends) people.

On Tue, Jul 14, 2009 at 2:32 PM, Ben Scott  wrote:

> On Tue, Jul 14, 2009 at 5:12 PM, Eric Woodford
> wrote:
> > Why are you creating a new mailbox for a user? The old one moldy or
> > something?
>
>  This used to be MS PSS's first response for just about any
> malfunction limited to a single mailbox.  I guess they assume the
> mailbox is corrupt and EXMERGE won't copy the corruption.  I don't
> know if they still do things this way; haven't called them for
> Exchange in over a year.  Knock on wood.
>
> -- Ben
>
>

Request for Advise with Hub Role and Barracuda

[Schlak, Anthony]

All,

We are looking to migrate all student email to Gmail. What we will need to do 
is route all email, be it internal or external mail, through our Barracuda for 
LDAP lookup. The problem is how to make the Hub Transport role in Exch 2007 
play nicely. Please advise.

Tony Schlak
IT Principal Analyst
Pima Community College
asch...@pima.edu
520-206-4883

RE: Request for Advise with Hub Role and Barracuda

[Campbell, Rob]

Why do you need to route internal mail to the Barracuda for lookup?



From: Schlak, Anthony [mailto:asch...@pima.edu]
Sent: Tuesday, July 14, 2009 5:32 PM
To: MS-Exchange Admin Issues
Subject: Request for Advise with Hub Role and Barracuda

All,

We are looking to migrate all student email to Gmail. What we will need to do 
is route all email, be it internal or external mail, through our Barracuda for 
LDAP lookup. The problem is how to make the Hub Transport role in Exch 2007 
play nicely. Please advise.

Tony Schlak
IT Principal Analyst
Pima Community College
asch...@pima.edu
520-206-4883

**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**

RE: Request for Advise with Hub Role and Barracuda

[Schlak, Anthony]

We can use the Barracuda to do a LDAP lookup and based on the response the 
message will pass to either internal Exchange or onto gmail for the students.


Tony Schlak
IT Principal Analyst
Pima Community College
asch...@pima.edu
520-206-4883

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
Sent: Tuesday, July 14, 2009 3:42 PM
To: MS-Exchange Admin Issues
Subject: RE: Request for Advise with Hub Role and Barracuda

Why do you need to route internal mail to the Barracuda for lookup?



From: Schlak, Anthony [mailto:asch...@pima.edu]
Sent: Tuesday, July 14, 2009 5:32 PM
To: MS-Exchange Admin Issues
Subject: Request for Advise with Hub Role and Barracuda

All,

We are looking to migrate all student email to Gmail. What we will need to do 
is route all email, be it internal or external mail, through our Barracuda for 
LDAP lookup. The problem is how to make the Hub Transport role in Exch 2007 
play nicely. Please advise.

Tony Schlak
IT Principal Analyst
Pima Community College
asch...@pima.edu
520-206-4883


**

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**

RE: Request for Advise with Hub Role and Barracuda

[Campbell, Rob]

I think you're going to want to change your authoritative domain to an internal 
relay domain.

This describes setting up Exchange 2007 for a shared address space, which seems 
to be what you're after.
http://technet.microsoft.com/en-us/library/bb676395.aspx

You don't need to force internal email to go to the Barracuda for lookup, and I 
don't know of any way to do it.  Using an internal relay domain, Exchange will 
first check to see if the email is deliverable internally.  If it isn't 
deliverable internally, it will pass it on to the Barracuda (or whatever you 
have the connector for that domain pointed to) for delivery.




From: Schlak, Anthony [mailto:asch...@pima.edu]
Sent: Tuesday, July 14, 2009 5:46 PM
To: MS-Exchange Admin Issues
Subject: RE: Request for Advise with Hub Role and Barracuda

We can use the Barracuda to do a LDAP lookup and based on the response the 
message will pass to either internal Exchange or onto gmail for the students.


Tony Schlak
IT Principal Analyst
Pima Community College
asch...@pima.edu
520-206-4883

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
Sent: Tuesday, July 14, 2009 3:42 PM
To: MS-Exchange Admin Issues
Subject: RE: Request for Advise with Hub Role and Barracuda

Why do you need to route internal mail to the Barracuda for lookup?



From: Schlak, Anthony [mailto:asch...@pima.edu]
Sent: Tuesday, July 14, 2009 5:32 PM
To: MS-Exchange Admin Issues
Subject: Request for Advise with Hub Role and Barracuda

All,

We are looking to migrate all student email to Gmail. What we will need to do 
is route all email, be it internal or external mail, through our Barracuda for 
LDAP lookup. The problem is how to make the Hub Transport role in Exch 2007 
play nicely. Please advise.

Tony Schlak
IT Principal Analyst
Pima Community College
asch...@pima.edu
520-206-4883


**

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**
**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**

RE: Request for Advise with Hub Role and Barracuda

[Troy Meyer]

What is the first machine to get mail? Lets assume that the barracuda is
your edge mta that receives email from the internet? (this is opposed to
if exchange receives internet email directly in which you should follow
Rob's link)

 

If so, the hub transport roll should play nice with no effort, your
effort is making barracuda work the rules.  Ideally you will query your
LDAP (AD?) servers and if a user has the exchange attribute forward on
to the exchange org (we do this with an internal address but you
shouldn't have to, you could also smarthost), if not send off to Gmail.
I am not familiar with the cuda, but if it uses sendmail for its
software backend, this shouldn't be too difficult.  I might even call
them and ask how others have configured this, I guarantee you aren't the
first.

 

-troy

 

 

From: Schlak, Anthony [mailto:asch...@pima.edu] 
Sent: Tuesday, July 14, 2009 3:32 PM
To: MS-Exchange Admin Issues
Subject: Request for Advise with Hub Role and Barracuda

 

All,

 

We are looking to migrate all student email to Gmail. What we will need
to do is route all email, be it internal or external mail, through our
Barracuda for LDAP lookup. The problem is how to make the Hub Transport
role in Exch 2007 play nicely. Please advise.

 

Tony Schlak

IT Principal Analyst

Pima Community College

asch...@pima.edu  

520-206-4883

 

RE: Restore server

[Jim Dandy]

Bummer

> -Original Message-
> From: Bob Fronk [mailto:b...@btrfronk.com]
> Sent: Tuesday, July 14, 2009 1:44 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Restore server
> 
> It is still "Different Hardware", even if it has same specs.
> 
> --
> Bob Fronk
> Please print onlyas needed.
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu]
> Sent: Tuesday, July 14, 2009 4:25 PM
> To: MS-Exchange Admin Issues
> Subject: RE: Restore server
> 
> The document you referenced is for restoring to different hardware.  My
> hardware is the same.  Will the procedure I outlined work - or at least
> not cause damage to my existing infrastructure?
> 
> Curt
> 
> > -Original Message-
> > From: Bob Fronk [mailto:b...@btrfronk.com]
> > Sent: Tuesday, July 14, 2009 11:44 AM
> > To: MS-Exchange Admin Issues
> > Subject: RE: Restore server
> >
> >
> http://www.msexchange.org/tutorials/Restoring-Exchange-Server2003-Altern
> ate-
> > Hardware.html
> >
> >
> > --
> > Bob Fronk
> >
> >
> >
> >
> >
> >
> > -Original Message-
> > From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu]
> > Sent: Tuesday, July 14, 2009 2:35 PM
> > To: MS-Exchange Admin Issues
> > Subject: Restore server
> >
> > I have an Exchange 2003 frontend server running on Windows Server 2003
> > that is having some issues with its hard drive.  I have another
> > identical hardware server.  I've loaded Windows Server 2003 on the new
> > hardware but no Exchange.  It's not a domain member, has a different
> > NetBIOS name and it does not have all the Windows patches installed on
> > the limper.  My plan was to restore the backup from the limping server
> > to the other server, unplug the limping server from the network and
> then
> > reboot the new server.  My hope is of course that the new server will
> > come up and begin functioning as the limper did (but without the hard
> > drive issue).  However, if the new server doesn't come back up I
> figure
> > I can just power it down, plug the limper back in and get things up
> > again quickly.  Does anyone see any issues in doing things this way?
> > I'm using Backup Exec 12.0.
> >
> > Thanks for your help.
> >
> > Curt
> >
> >
> >
> 
> 

RE: Migration and upgrade

[Adrian Crawford]

I have just moved from SBS 2003 to SBS 2008 along with Exchange.

The best resource I found and used was sbsmigration.com

It had all the steps and processes to move exchange from 2003 to 2008 via a 
swing out to Temporary exchange server, it worked well and the $200US was money 
well spent, at least for my sanity.

Regards

Adrian Crawford

Kirway Constructions P/L
66 Church Street, PO Box 1468, Traralgon VIC 3844, Australia
Ph: +613 5174 0128 Fax: +613 5174 0391 
E-mail: acrawf...@kirway.com.au  
Visit: www.kirway.com.au

PLEASE CONSIDER THE ENVIRONMENT BEFORE YOU PRINT THIS E-MAIL
_

The information contained in this message and or attachments is intended only 
for the person or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon, this information by persons 
or entities other than the intended recipient is prohibited. If you received 
this in error, please contact the sender and delete the material from any 
system and destroy any copies. Thank you.

-Original Message-
From: James Kerr [mailto:cluster...@gmail.com] 
Sent: Wednesday, 15 July 2009 5:17 AM
To: MS-Exchange Admin Issues
Subject: Migration and upgrade

Need to migrate exchange 2003 (w/ Win2003) to new server that will be 
running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should 
I install 2003 on the new server, migrate, decomission the old exchange 
sever then upgrade to 2007?

James 

RE: Migration and upgrade

[Michael B. Smith]

As another poster mentioned, sbsmigration.com is your #1 resource, if you have 
a few bucks to spend.

Otherwise, spend some time at Susan Bradley's blog (the SBS Diva) and I've got 
a few detailed postings on the topic myself:

http://theessentialexchange.com/blogs/michael/archive/2009/01/12/sbs-2003-hardware-upgrade.aspx


From: James Kerr [cluster...@gmail.com]
Sent: Tuesday, July 14, 2009 3:16 PM
To: MS-Exchange Admin Issues
Subject: Migration and upgrade

Need to migrate exchange 2003 (w/ Win2003) to new server that will be
running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or should
I install 2003 on the new server, migrate, decomission the old exchange
sever then upgrade to 2007?

James

RE: replace Exchange 2003 server

[Michael B. Smith]

Yes, no, maybe.

I'd need to look at your environment for a couple of hours to determine the 
answer to your question. There are so many "what ifs"!

To start, google the Microsoft KB articles "How to Remove the Last Exchange 
2003 Server from an Administrative Group" and "How to Remove the Last Exchange 
2003 Server".

Follow those steps.

Most common Outlook 2007 hang issue I've seen with Exchange 2007? You have 
AutoDiscover configured and Outlook Anywhere configured but you don't have BOTH 
"On fast networks" and "On slow networks" checked.


From: SMREKAR, JACK [smre...@aasd.k12.wi.us]
Sent: Tuesday, July 14, 2009 3:51 PM
To: MS-Exchange Admin Issues
Subject: replace Exchange 2003 server

We upgraded to Exchange 2007 Enterprise Exchange. It was working fairly well 
but we were still having some Outlook 2007 hanging issues where when you first 
stated outlook it would just sit there or every now and then it would also hang.

We then had a consultant come in and help with the configuring of the transport 
roles and he removed the last 2003 Enterprise Exchange server but did not 
remove it cleanly so for some reason we have to redo THE ADPREP as  that is 
what the install of Exchange 2007 told us to do. So after running adprep to see 
where the issue was that the installer of 2007 mentioned and that error is that 
the 2003 Exchange server, that was removed in correctly, cannot be found.

I am guessing that if we try to bring up a new 2003 Exchange server and name it 
the same as the last Exchange that was removed that we will still have issues 
as there were roles on the 2003 server that either did not get transferred 
correctly or did not get transferred at all.

So the question is, can I just put up a 2003 Exchange server to get rid of the 
error or is there a different way to remove any issues that Exchange 2007 is 
having with the phantom server.

Thanks

Jack Smrekar
Appleton Area School District
920-993-7062 Ext. 2123
A+  N+  Server +

[MCSA-RGB]
<>

Re: Migration and upgrade

[Jonathan Link]

I paid for it, and it was worth it.  $200 was a small price to pay.

On Tue, Jul 14, 2009 at 8:10 PM, Michael B. Smith  wrote:

> As another poster mentioned, sbsmigration.com is your #1 resource, if you
> have a few bucks to spend.
>
> Otherwise, spend some time at Susan Bradley's blog (the SBS Diva) and I've
> got a few detailed postings on the topic myself:
>
>
> http://theessentialexchange.com/blogs/michael/archive/2009/01/12/sbs-2003-hardware-upgrade.aspx
>
> 
> From: James Kerr [cluster...@gmail.com]
> Sent: Tuesday, July 14, 2009 3:16 PM
>  To: MS-Exchange Admin Issues
> Subject: Migration and upgrade
>
> Need to migrate exchange 2003 (w/ Win2003) to new server that will be
> running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or
> should
> I install 2003 on the new server, migrate, decomission the old exchange
> sever then upgrade to 2007?
>
> James
>
>
>

RE: Issue

[Michael B. Smith]

pppt.

Just because I'm using Win7 and Exchange 2010 does NOT mean it's a virus!


From: John Cook [john.c...@pfsf.org]
Sent: Tuesday, July 14, 2009 5:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Issue

Bad Mikey!

John W. Cook
Systems Administrator
Partnership For Strong Families
315 SE 2nd Ave
Gainesville, Fl 32601
Office (352) 393-2741 x320
Cell (352) 215-6944
Fax (352) 393-2746
MCSE, MCTS, MCP+I, A+, N+, VSP

From: Doug Rooney [mailto:d...@sonomatilemakers.com]
Sent: Tuesday, July 14, 2009 5:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Issue
Importance: High


Hello all, I am getting MANY of these a day, any suggestions?



The MessageLabs Email Security System discovered a possible virus or 
unauthorised code (such as a Trojan) in an email sent to you.

The email has now been quarantined and was not delivered.

Please read the whole of this email carefully.  It explains the status of your 
email, the nature of the intercepted virus and the next steps for addressing 
the problem.

To help identify the quarantined email:

The message sender was


bounce-8597748-8237...@lyris.sunbelt-software.com

mich...@owa.smithcons.com


exchangelist@lyris.sunbelt-software.com



The message originating IP was 64.128.133.151 The message recipients were

d...@sonomatilemakers.com



The message title was RE: Hub Server

The message date was Tue, 14 Jul 2009 15:49:11 + The virus or unauthorised 
code identified in the email is

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in

>>> '5931055T_1X_PM2_EMQ_MT__message.txt'. Heuristics score: 200

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in

>>> '5931055_2X_PM3_EMQ_MH__message.htm'. Heuristics score: 200



Some viruses forge the sender address. For more information please visit the 
virus FAQ's link at the bottom of this page.

The message was diverted into the virus holding pen on mail server 
server-8.tower-190.messagelabs.com (pen id 66693_124758) and will be held 
for 30 days before being destroyed Please contact your IT Helpdesk or Support 
Department for further assistance.

Answers to virus-related questions can be found on the MessageLabs Virus FAQ 
page at

http://www.messagelabs.com/page.asp?id=628


Thank You
~Doug Rooney
Sonoma Tilemakers
IT Manager
7750 Bell Rd.
Windsor Ca, 95492
(707) 837-8177 X211
(707) 837-9472 FAX
i...@sonomatilemakers.com





CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you really need 
to.

This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the company. 
Warning: Although precautions have been taken to make sure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage that arise from the use of this email or attachments.

RE: Changing Subject Line Limits

[Michael B. Smith]

Outlook does (I just tested) limit you to 255 characters for the subject. This 
implies to me that it is storing headers in a _bstr_t variable, instead of a 
CString or wchar_t variable. But that is purely an implementation detail.

Based on my (admittedly limited) testing - Exchange does not reduce the number 
of characters available to you.

While from a user perspective Exchange and Outlook are the same thing, from 
where I sit - they are different! :-P


From: Ben Scott [mailvor...@gmail.com]
Sent: Tuesday, July 14, 2009 4:54 PM
To: MS-Exchange Admin Issues
Subject: Re: Changing Subject Line Limits

On Tue, Jul 14, 2009 at 4:44 PM, Ben Scott wrote:
> You're assuming octets == glyphs, and
> that's very wrong for the encoded subjects the OP is seeing.

  Of course, I then thought to actually decode the BASE64 we were
given.  The subject line that made it this far is pure ASCII, and also
ridiculously long.

  If the rest of the subject line is pure ASCII, there's no need for
UTF-8 or BASE64.  Reconfigure the sending system not to do that, and
you'll gain at least BASE64 encoding overhead.

  The decoded subject line was:

PeopleSoft error report: Error: First operand of . is NULL, so cannot
access member Len. (180,236) FUNCLIB_EXT_APP.RESUME.FieldFormula
Name:set_resume_step  PCPC:13552  Statement:

  Per ME2, that should be in the message body, and a summary, e.g.,
"PeopleSoft error report", in the subject.

-- Ben

RE: Issue

[John Cook]

So why do you suppose that triggered it?
John W. Cook
Systems Administrator
Partnership For Strong Families
315 SE 2nd Ave
Gainesville, Fl 32601
Ph -  352-393-2741 x320
Fax - 352-393-2746
MCSE, MCP+I, MCTS, A+, N+


From: Michael B. Smith [mich...@owa.smithcons.com]
Sent: Tuesday, July 14, 2009 8:19 PM
To: MS-Exchange Admin Issues
Subject: RE: Issue

pppt.

Just because I'm using Win7 and Exchange 2010 does NOT mean it's a virus!


From: John Cook [john.c...@pfsf.org]
Sent: Tuesday, July 14, 2009 5:39 PM
To: MS-Exchange Admin Issues
Subject: RE: Issue

Bad Mikey!

John W. Cook
Systems Administrator
Partnership For Strong Families
315 SE 2nd Ave
Gainesville, Fl 32601
Office (352) 393-2741 x320
Cell (352) 215-6944
Fax (352) 393-2746
MCSE, MCTS, MCP+I, A+, N+, VSP

From: Doug Rooney [mailto:d...@sonomatilemakers.com]
Sent: Tuesday, July 14, 2009 5:40 PM
To: MS-Exchange Admin Issues
Subject: RE: Issue
Importance: High


Hello all, I am getting MANY of these a day, any suggestions?



The MessageLabs Email Security System discovered a possible virus or 
unauthorised code (such as a Trojan) in an email sent to you.

The email has now been quarantined and was not delivered.

Please read the whole of this email carefully.  It explains the status of your 
email, the nature of the intercepted virus and the next steps for addressing 
the problem.

To help identify the quarantined email:

The message sender was


bounce-8597748-8237...@lyris.sunbelt-software.com

mich...@owa.smithcons.com


exchangelist@lyris.sunbelt-software.com



The message originating IP was 64.128.133.151 The message recipients were

d...@sonomatilemakers.com



The message title was RE: Hub Server

The message date was Tue, 14 Jul 2009 15:49:11 + The virus or unauthorised 
code identified in the email is

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in

>>> '5931055T_1X_PM2_EMQ_MT__message.txt'. Heuristics score: 200

>>> Possible MalWare 'W32/Trojan.Horse.gen-6696' found in

>>> '5931055_2X_PM3_EMQ_MH__message.htm'. Heuristics score: 200



Some viruses forge the sender address. For more information please visit the 
virus FAQ's link at the bottom of this page.

The message was diverted into the virus holding pen on mail server 
server-8.tower-190.messagelabs.com (pen id 66693_124758) and will be held 
for 30 days before being destroyed Please contact your IT Helpdesk or Support 
Department for further assistance.

Answers to virus-related questions can be found on the MessageLabs Virus FAQ 
page at

http://www.messagelabs.com/page.asp?id=628


Thank You
~Doug Rooney
Sonoma Tilemakers
IT Manager
7750 Bell Rd.
Windsor Ca, 95492
(707) 837-8177 X211
(707) 837-9472 FAX
i...@sonomatilemakers.com





CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information may 
be protected by the Health Insurance Portability and Accountability Act of 1996 
(HIPAA), and other Federal and Florida laws. Improper or unauthorized use or 
disclosure of this information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you really need 
to.

This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the company. 
Warning: Although precautions have been taken to make sure no viruses are 
present in this email, the company cannot accept responsibility for any loss or 
damage that arise from the use of this email or attachments.


CONFIDENTIALITY STATEMENT: The information transmitted, or contained or 
attached to or with this Notice is intended only for the person or entity to 
which it is addressed and may contain Protected Health Information (PHI), 
confidential and/or privileged material. Any review, transmission, 
dissemination, or other use of, and taking any action in reliance upon this 
information by persons or entities other than the intended recipient without 
the express written consent of the sender are prohibited. This information 

RE: Can't Deliver to one Domian

[Lynden A. Philadelphia]

yes

 

From: Don Guyer [mailto:don.gu...@prufoxroach.com] 
Sent: July-14-09 3:54 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

RE: Can't Deliver to one Domian

[Lynden A. Philadelphia]

All other mail is going out.

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: July-14-09 4:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

"Could not deliver the message in the time limit specified.  Please
retry or contact your administrator."

 

Usually means it gave up after multiple temporary failures and retries.
Bad address is a permanent failure.

 

I'm betting on a network, dns, or firewall problem.

 



From: Don Guyer [mailto:don.gu...@prufoxroach.com] 
Sent: Tuesday, July 14, 2009 3:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Now that I've read the error again, it looks like it was 12 hours time
difference.

 

If it reached the destination server with an unknown/bad address, it
should've replied immediately. Unless we're talking about a part of the
world that has a 12 hour time difference.

 

Details always help.

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:07 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

 

Or 9 times out of 10 when a user shows me this, I ask if they've
verified the email address.  This domain and rr are really bad with
these generic messages when in actuality it's not a valid email address.



 

On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

 


**
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this
message to  
the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If
you  
have received this communication in error, please notify us immediately
by  
replying to the message and deleting it from your computer. 

**

RE: Can't Deliver to one Domain

[Lynden A. Philadelphia]

It's not just that one address it's the entire domain

 

From: Wulff Jr, Ronald J. [mailto:rwu...@reedsmith.com] 
Sent: July-14-09 4:23 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Sender domain could be blacklisted

Recipient might be expecting TLS

Recipient might be having SMTP server issues.

 

Way too many things to guess really

 

Ronald Wulff Jr 
412.288.3601 
rwu...@reedsmith.com 

Reed Smith LLP 
20 Stanwix St

Suite 1200
Pittsburgh, PA 15222

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: Tuesday, July 14, 2009 4:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

"Could not deliver the message in the time limit specified.  Please
retry or contact your administrator."

 

Usually means it gave up after multiple temporary failures and retries.
Bad address is a permanent failure.

 

I'm betting on a network, dns, or firewall problem.

 



From: Don Guyer [mailto:don.gu...@prufoxroach.com] 
Sent: Tuesday, July 14, 2009 3:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Now that I've read the error again, it looks like it was 12 hours time
difference.

 

If it reached the destination server with an unknown/bad address, it
should've replied immediately. Unless we're talking about a part of the
world that has a 12 hour time difference.

 

Details always help.

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:07 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

 

Or 9 times out of 10 when a user shows me this, I ask if they've
verified the email address.  This domain and rr are really bad with
these generic messages when in actuality it's not a valid email address.



 

On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS
related. Did this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.
Please retry or contact your administrator.



From: Lynden A. Philadelphia
[mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to
Sympatico.ca domain. we can deliver to any other domain without any
issue.  I have checked exchange and the sonicwall an can not see
anything.

 

I should also mention that Bell is the ISP in question and no black
listing is in place.

 

Can some one help?

 

 

Lynden 

 

 

 


**
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure.  If the reader of this message is not the
intended  
recipient, or an employee or agent responsible for delivering this
message to  
the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If
you  
have received this communication in error, please notify us immediately
by  
replying to the message and deleting it from your computer. 

**

 

* * * 

 

This E-mail, along with any attachments, is considered confidential and
may well be legally privileged. If you have received it in error, you
are on notice of its status. Please notify us immediately by reply
e-mail and then delete this message from your system. Please do not copy
it or use it for any purposes, or disclose its contents to any other
person. Thank you for your cooperation. 

* * * 

To ensure compliance with Treasury Department regulations, we inform you
that, unless otherwise indicated in writing, any U.S. Federal tax advice
contained in this communication  (including any attachments) is not
inten

Re: Changing Subject Line Limits

[Micheal Espinola Jr]

FWIW, in RFC 2822, its recommend that header fields not exceed 78
characters [for mail reader compatibility, AFAIK] even though up to
998 characters are technically valid.

--
ME2



On Tue, Jul 14, 2009 at 8:34 PM, Michael B.
Smith wrote:
> Outlook does (I just tested) limit you to 255 characters for the subject. 
> This implies to me that it is storing headers in a _bstr_t variable, instead 
> of a CString or wchar_t variable. But that is purely an implementation detail.
>
> Based on my (admittedly limited) testing - Exchange does not reduce the 
> number of characters available to you.
>
> While from a user perspective Exchange and Outlook are the same thing, from 
> where I sit - they are different! :-P
>
> 
> From: Ben Scott [mailvor...@gmail.com]
> Sent: Tuesday, July 14, 2009 4:54 PM
> To: MS-Exchange Admin Issues
> Subject: Re: Changing Subject Line Limits
>
> On Tue, Jul 14, 2009 at 4:44 PM, Ben Scott wrote:
>> You're assuming octets == glyphs, and
>> that's very wrong for the encoded subjects the OP is seeing.
>
>  Of course, I then thought to actually decode the BASE64 we were
> given.  The subject line that made it this far is pure ASCII, and also
> ridiculously long.
>
>  If the rest of the subject line is pure ASCII, there's no need for
> UTF-8 or BASE64.  Reconfigure the sending system not to do that, and
> you'll gain at least BASE64 encoding overhead.
>
>  The decoded subject line was:
>
>        PeopleSoft error report: Error: First operand of . is NULL, so cannot
> access member Len. (180,236) FUNCLIB_EXT_APP.RESUME.FieldFormula
> Name:set_resume_step  PCPC:13552  Statement:
>
>  Per ME2, that should be in the message body, and a summary, e.g.,
> "PeopleSoft error report", in the subject.
>
> -- Ben
>
>
>

Re: Can't Deliver to one Domain

[Sherry Abercrombie]

Have you verified with the ISP/company of that domain that you aren't
somehow blacklisted by their side?

On Tue, Jul 14, 2009 at 7:49 PM, Lynden A. Philadelphia <
lphiladelp...@philadelphiagroup.com> wrote:

>  It’s not just that one address it’s the entire domain
>
>
>
> *From:* Wulff Jr, Ronald J. [mailto:rwu...@reedsmith.com]
> *Sent:* July-14-09 4:23 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Can't Deliver to one Domian
>
>
>
> Sender domain could be blacklisted
>
> Recipient might be expecting TLS
>
> Recipient might be having SMTP server issues.
>
>
>
> Way too many things to guess really
>
>
>
> *Ronald Wulff Jr*
> 412.288.3601
> rwu...@reedsmith.com
>
> Reed Smith LLP
> 20 Stanwix St
>
> Suite 1200
> Pittsburgh, PA 15222
>
>
>
> *From:* Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
> *Sent:* Tuesday, July 14, 2009 4:17 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Can't Deliver to one Domian
>
>
>
> “Could not deliver the message in the time limit specified.  Please retry
> or contact your administrator.”
>
>
>
> Usually means it gave up after multiple temporary failures and retries.
> Bad address is a permanent failure.
>
>
>
> I’m betting on a network, dns, or firewall problem.
>
>
>  --
>
> *From:* Don Guyer [mailto:don.gu...@prufoxroach.com]
> *Sent:* Tuesday, July 14, 2009 3:12 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Can't Deliver to one Domian
>
>
>
> Now that I’ve read the error again, it looks like it was 12 hours time
> difference.
>
>
>
> If it reached the destination server with an unknown/bad address, it
> should’ve replied immediately. Unless we’re talking about a part of the
> world that has a 12 hour time difference.
>
>
>
> Details always help.
>
>
>
> Don Guyer
>
> Systems Engineer - Information Services
>
> Prudential, Fox & Roach/Trident Group
>
> 431 W. Lancaster Avenue
>
> Devon, PA 19333
>
> Direct: (610) 993-3299
>
> Fax: (610) 650-5306
>
> don.gu...@prufoxroach.com
>
>
>
> *From:* Jonathan Link [mailto:jonathan.l...@gmail.com]
> *Sent:* Tuesday, July 14, 2009 4:07 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Can't Deliver to one Domian
>
>
>
> Or 9 times out of 10 when a user shows me this, I ask if they've verified
> the email address.  This domain and rr are really bad with these generic
> messages when in actuality it's not a valid email address.
>
>
>
>
>
> On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer 
> wrote:
>
> Looks like it tried for 24 hours and gave up. Probably network/DNS related.
> Did this work before?
>
>
>
> Don Guyer
>
> Systems Engineer - Information Services
>
> Prudential, Fox & Roach/Trident Group
>
> 431 W. Lancaster Avenue
>
> Devon, PA 19333
>
> Direct: (610) 993-3299
>
> Fax: (610) 650-5306
>
> don.gu...@prufoxroach.com
>
>
>
> *From:* Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
>
> *Sent:* Tuesday, July 14, 2009 3:36 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* RE: Can't Deliver to one Domian
>
>
>
> Below is what we get back
>
>
>
> Your message did not reach some or all of the intended recipients.
>
>   Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am
>
>   Sent: 13/07/2009 2:54 PM
>
> The following recipient(s) cannot be reached:
>
>   n...@sympatico.ca on 14/07/2009 2:57 AM
>
> Could not deliver the message in the time limit specified.
> Please retry or contact your administrator.
>  --
>
> *From:* Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com
> ]
> *Sent:* Fri 10/07/2009 1:46 PM
> *To:* MS-Exchange Admin Issues
> *Subject:* Can't Deliver to one Domian
>
> I have a SBS 2003; for some reason users in that office can's deliver to
> Sympatico.ca domain. we can deliver to any other domain without any issue.
> I have checked exchange and the sonicwall an can not see anything.
>
>
>
> I should also mention that Bell is the ISP in question and no black listing
> is in place.
>
>
>
> Can some one help?
>
>
>
>
>
> Lynden
>
>
>
>
>
>
>
> **
>
> Note:
>
> The information contained in this message may be privileged and confidential 
> and
>
> protected from disclosure.  If the reader of this message is not the intended
>
> recipient, or an employee or agent responsible for delivering this message to
>
> the intended recipient, you are hereby notified that any dissemination,
>
> distribution or copying of this communication is strictly prohibited. If you
>
> have received this communication in error, please notify us immediately by
>
> replying to the message and deleting it from your computer.
>
> **
>
>
>
> * * *
>
>
>
> This E-mail, along with any attachments, is considered confidential and may
> well be legally privileged. If you have received it in error, you are on
> no

RE: Can't Deliver to one Domian

[Campbell, Rob]

Can you telnet to port 25 on their mail server and get it to accept mail?

Sent from my GoodLink synchronized handheld (www.good.com)


 -Original Message-
From:   Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
Sent:   Tuesday, July 14, 2009 08:46 PM Central Standard Time
To: MS-Exchange Admin Issues
Subject:RE: Can't Deliver to one Domian

All other mail is going out.

 

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net] 
Sent: July-14-09 4:17 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Could not deliver the message in the time limit specified.  Please retry or 
contact your administrato�

 

Usually means it gave up after multiple temporary failures and retries.  Bad 
address is a permanent failure.

 

I���m betting on a network, dns, or firewall problem.

 



From: Don Guyer [mailto:don.gu...@prufoxroach.com] 
Sent: Tuesday, July 14, 2009 3:12 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Now that ve read the error again, it looks like it was 12 hours time 
difference.

 

If it reached the destination server with an unknown/bad address, it 
should���ve replied immediately. Unless we���re talking about a part of the 
world that has a 12 hour time difference.

 

Details always help.

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Jonathan Link [mailto:jonathan.l...@gmail.com] 
Sent: Tuesday, July 14, 2009 4:07 PM
To: MS-Exchange Admin Issues
Subject: Re: Can't Deliver to one Domian

 

Or 9 times out of 10 when a user shows me this, I ask if they've verified the 
email address.  This domain and rr are really bad with these generic messages 
when in actuality it's not a valid email address.



 

On Tue, Jul 14, 2009 at 3:53 PM, Don Guyer  wrote:

Looks like it tried for 24 hours and gave up. Probably network/DNS related. Did 
this work before?

 

Don Guyer

Systems Engineer - Information Services

Prudential, Fox & Roach/Trident Group

431 W. Lancaster Avenue

Devon, PA 19333

Direct: (610) 993-3299

Fax: (610) 650-5306

don.gu...@prufoxroach.com  

 

From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com] 
Sent: Tuesday, July 14, 2009 3:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Can't Deliver to one Domian

 

Below is what we get back

 

Your message did not reach some or all of the intended recipients.

  Subject:  FW:  Please confirm if you receive -Jul13/09 11:00am

  Sent: 13/07/2009 2:54 PM

The following recipient(s) cannot be reached:

  n...@sympatico.ca on 14/07/2009 2:57 AM

Could not deliver the message in the time limit specified.  Please 
retry or contact your administrator.



From: Lynden A. Philadelphia [mailto:lphiladelp...@philadelphiagroup.com]
Sent: Fri 10/07/2009 1:46 PM
To: MS-Exchange Admin Issues
Subject: Can't Deliver to one Domian

I have a SBS 2003; for some reason users in that office can's deliver to 
Sympatico.ca domain. we can deliver to any other domain without any issue.  I 
have checked exchange and the sonicwall an can not see anything.

 

I should also mention that Bell is the ISP in question and no black listing is 
in place.

 

Can some one help?

 

 

Lynden 

 

 

 

**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**
**
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 

RE: Migration and upgrade

[Chyka, Robert]

Hi Adrian,

Do they have a method and toolset to buy for server 2003 and exchange
2003 enterprise to server 2008 enterprise and exchange 2007 enterprise?

Thanks..Bob 

-Original Message-
From: Adrian Crawford [mailto:acrawf...@kirway.com.au] 
Sent: Tuesday, July 14, 2009 7:49 PM
To: MS-Exchange Admin Issues
Subject: RE: Migration and upgrade

I have just moved from SBS 2003 to SBS 2008 along with Exchange.

The best resource I found and used was sbsmigration.com

It had all the steps and processes to move exchange from 2003 to 2008
via a swing out to Temporary exchange server, it worked well and the
$200US was money well spent, at least for my sanity.

Regards

Adrian Crawford

Kirway Constructions P/L
66 Church Street, PO Box 1468, Traralgon VIC 3844, Australia
Ph: +613 5174 0128 Fax: +613 5174 0391
E-mail: acrawf...@kirway.com.au
Visit: www.kirway.com.au

PLEASE CONSIDER THE ENVIRONMENT BEFORE YOU PRINT THIS E-MAIL
_

The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended
recipient is prohibited. If you received this in error, please contact
the sender and delete the material from any system and destroy any
copies. Thank you.

-Original Message-
From: James Kerr [mailto:cluster...@gmail.com]
Sent: Wednesday, 15 July 2009 5:17 AM
To: MS-Exchange Admin Issues
Subject: Migration and upgrade

Need to migrate exchange 2003 (w/ Win2003) to new server that will be
running exchange 2007 (w/ Win2008). Can I migrate directly to 2007 or
should I install 2003 on the new server, migrate, decomission the old
exchange sever then upgrade to 2007?

James 

RE: replace Exchange 2003 server

[Doug Gallimore]

It's been my understanding...I've not confirmed this but that once you install 
the first E2K7 server in your ORG there is NO adding more E2K3 servers.  It's 
basically an end to your E2K3 era when you add that first 64bit monster.I'm 
in the middle of my second migration in the last two years and unfortunately, 
there has been too much time in b/w to remember everything I learned from the 
first one, but I distinctly recall that E2K3 is finito once you start on the 
install path of E2K7, now if you didn't do an intraORG upgrade you might be 
able to fake it out, but that's not what I'm sensing is going on here.

Douglas

From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, July 14, 2009 7:16 PM
To: MS-Exchange Admin Issues
Subject: RE: replace Exchange 2003 server

Yes, no, maybe.

I'd need to look at your environment for a couple of hours to determine the 
answer to your question. There are so many "what ifs"!

To start, google the Microsoft KB articles "How to Remove the Last Exchange 
2003 Server from an Administrative Group" and "How to Remove the Last Exchange 
2003 Server".

Follow those steps.

Most common Outlook 2007 hang issue I've seen with Exchange 2007? You have 
AutoDiscover configured and Outlook Anywhere configured but you don't have BOTH 
"On fast networks" and "On slow networks" checked.


From: SMREKAR, JACK [smre...@aasd.k12.wi.us]
Sent: Tuesday, July 14, 2009 3:51 PM
To: MS-Exchange Admin Issues
Subject: replace Exchange 2003 server
We upgraded to Exchange 2007 Enterprise Exchange. It was working fairly well 
but we were still having some Outlook 2007 hanging issues where when you first 
stated outlook it would just sit there or every now and then it would also hang.

We then had a consultant come in and help with the configuring of the transport 
roles and he removed the last 2003 Enterprise Exchange server but did not 
remove it cleanly so for some reason we have to redo THE ADPREP as  that is 
what the install of Exchange 2007 told us to do. So after running adprep to see 
where the issue was that the installer of 2007 mentioned and that error is that 
the 2003 Exchange server, that was removed in correctly, cannot be found.

I am guessing that if we try to bring up a new 2003 Exchange server and name it 
the same as the last Exchange that was removed that we will still have issues 
as there were roles on the 2003 server that either did not get transferred 
correctly or did not get transferred at all.

So the question is, can I just put up a 2003 Exchange server to get rid of the 
error or is there a different way to remove any issues that Exchange 2007 is 
having with the phantom server.

Thanks

Jack Smrekar
Appleton Area School District
920-993-7062 Ext. 2123
A+  N+  Server +

[cid:image001.gif@01CA04D4.0FBF17C0]
<>