Re: SMTP email problem
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Thu, 13 Apr 2006 16:14:25 -0500
I found the security group thing doesn't work. There are several other
methods of filtering the recipient policy - I tested one and posted it to
your other thread.
Another method is by using the 'department' field in the user properties.
IMHO, unless you have a *very* small number of users affected, you never
want to uncheck the automatic box - that disables recipient policy updates.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"HMOOC" <HMOOC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:07495665-1CFE-4968-9854-9D71F67849A2@xxxxxxxxxxxxxxxx
Hi Les,
Thank you for your help. I have tried to apply DomainB policy but what it
does it it makes ALL the mailboxes the DomainB as it's primary set email
address. I did try the methology you have suggested which is to create a
DomainB security group and apply the DomainB policy but that still caused
all
the mailboxes to set it's primary address to domainB.
If I have to apply the DomainB policy, I can do that again but would it be
OK to manually uncheck the box where it said, "automatically update domain
policy" within the property box of the user? Also it's OK to manually set
the primary email address for the DomainA right?
Hope this make sense.
Thanks,
Helen
"Les Connor [SBS Community Member - SBS M" wrote:
DomainB is going to have to be in your recipient policy, or exchange
doesn't
know about it.
About a week ago, I replied with information that would enable you to use
recipient policies to selectively generate primary addresses for
different
domains.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"HMOOC" <HMOOC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:925CFAD0-0E27-4C37-AAFA-F509743B9E1C@xxxxxxxxxxxxxxxx
Hi all,
I just slaved all night to put the Small Business Server last night.
This
is something I did not expect to happen since I was using one of the
address I have set up on the server to email myself and assume all
different
smtp added I have added to mailboxes work.
Currently the server is working properly for users with the default
Domain
email address. There are some one users who have a second email
address
and
the way I have orginally configure it was to create another mailbox and
simply set the second email address as the Primary Set email. Some of
the
users can not receive emails with those email address.
The default email address for all users start with first initiate and
then
their last name. For example JBrown@xxxxxxxxxxx for John Brown,
The second email address for some of the users start with their first
name
and then their last name. For example John.Brown@xxxxxxxxxxx for John
Brown. When I try to send a test email to myself with the second email
address, this is the message I getting using a pop mail account:
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<helen.mooc@xxxxxxxxxxxxxxxxxx>:
216.183.94.11 does not like recipient.
Remote host said: 550 5.7.1 Unable to relay for
helen.mooc@xxxxxxxxxxxxxxxxxx
Giving up on 216.183.94.11.
--- Below this line is a copy of the message.
Return-Path: <hmooc@xxxxxxxxxx>
Received: (qmail 22050 invoked by uid 60001); 13 Apr 2006 17:19:48
-0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=rogers.com;
h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content
-Transfer-Encoding;
b=JfdUEeBeZAQ69IFEc1gl7tBvntC1n+PxQF0v0luBRu319G+uDyQNhMdCKzJYmPiRGcJa4b50pM
zvm8MRiDGuXDRgyorrH1a8k7ck5JIVsjJh6upEbU4Ap1C68cvdMjA0EfmT77Y6n3McULxnX9phNA
WuHmy5ElGGrtoakUaiGko=
;
Message-ID: <20060413171948.22048.qmail@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Received: from [216.183.94.12] by web88210.mail.re2.yahoo.com via HTTP;
Thu, 13 Apr 2006 13:19:48 EDT
Date: Thu, 13 Apr 2006 13:19:48 -0400 (EDT)
From: Helen Mooc <hmooc@xxxxxxxxxx>
Subject: test
To: helen.mooc@xxxxxxxxxxxxxxxxxx
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="0-124658836-1144948788=:21991"
Content-Transfer-Encoding: 8bit
--0-124658836-1144948788=:21991
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
--0-124658836-1144948788=:21991
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
--0-124658836-1144948788=:21991--
Anyone had encounter this issue? Would you have any suggestions?
thanks,Helen
.
- Follow-Ups:
- Re: SMTP email problem
- From: HMOOC
- Re: SMTP email problem
- References:
- SMTP email problem
- From: HMOOC
- Re: SMTP email problem
- From: Les Connor [SBS Community Member - SBS MVP]
- Re: SMTP email problem
- From: HMOOC
- SMTP email problem
- Prev by Date: Etrust antivirus locking up SBS2003
- Next by Date: Re: Backup SBS 2003 to DVD instead of tape backup?
- Previous by thread: Re: SMTP email problem
- Next by thread: Re: SMTP email problem
- Index(es):
Relevant Pages
|
