Gray Cloud

hello i am new to exchange setup so my question may be dumb...

i have a sbs 2003 with exchange in witch i have already set pop3 conector
to receive my emails from my websites to users accounts.

what i need to now is if it is possible to set up in some way the smtp to
send mail using my website smtp user and pass (and if possible different web
mail accounts)

thanks.

i think i didnt make myself clear

send mail using:

smtp server - website smtp
smtp user - website user
smtp pass - website pass

JulioMGM wrote:
> hello i am new to exchange setup so my question may be dumb...

Nah. I've heard a lot worse. ;-)
>
> i have a sbs 2003 with exchange

I'm setting up my reply to crosspost to the SBS group - you should post all
SBS questions in there even if you *also* crosspost to the regular groups.

> in witch i have already set pop3
> conector to receive my emails from my websites to users accounts.

Ah. Don't do that. The POP connector is not the way to handle your mail. Use
direct SMTP delivery of mail to all your domains - it's the way Exchange is
meant to work, and will not cause you so many problems.

http://www.msexchange.org/tutorials/MF002.html will help, but since you're
using SBS you will run the CEICW again.

>
> what i need to now is if it is possible to set up in some way the
> smtp to send mail using my website smtp user and pass (and if
> possible different web mail accounts)

If you set up Exchange to handle all your mail, you'll send from your domain
address(es).

One mailbox user can't (easily) send from different addresses in exchange -
you can *receive* to as many as you like.
>
> thanks.

I tottaly agree you should deliver your email directly to the server
and avoid the use of the POP3 connector.

There is however a way to allow users to send from different
domains/accounts.

First enable IMAP on your Exchange server. Then on the client side in
Outlook add an IMAP connection to the server with the email address you
want to send from. When the user composes a new message, a new button
will show up near the Send button, this button will be called "Account"
and it will let you specify which account the user is sending from.

Hope that helps,

Mark D. MacLachlan

Mark D. MacLachlan wrote:
> I tottaly agree you should deliver your email directly to the server
> and avoid the use of the POP3 connector.
>
> There is however a way to allow users to send from different
> domains/accounts.
>
> First enable IMAP on your Exchange server. Then on the client side in
> Outlook add an IMAP connection to the server with the email address
> you want to send from. When the user composes a new message, a new
> button will show up near the Send button, this button will be called
> "Account" and it will let you specify which account the user is
> sending from.
>
> Hope that helps,
>
> Mark D. MacLachlan

Yes, that works (as does a dummy POP account set up to send only, not
receive...if the addresses are all aliases in the mailbox) . However, it's
awkward and does not scale well, so I tend to avoid it.

On Thu, 02 Jul 2009 09:35:58 -0700, "Mark D. MacLachlan"
wrote:

>I tottaly agree you should deliver your email directly to the server
>and avoid the use of the POP3 connector.
>
>There is however a way to allow users to send from different
>domains/accounts.
>
>First enable IMAP on your Exchange server. Then on the client side in
>Outlook add an IMAP connection to the server with the email address you
>want to send from. When the user composes a new message, a new button
>will show up near the Send button, this button will be called "Account"
>and it will let you specify which account the user is sending from.
>
>Hope that helps,
>
>Mark D. MacLachlan


Managing two accounts like that in Outlook is buggy at times and not
really recommended.

Lanwench [MVP - Exchange] wrote:

> Mark D. MacLachlan wrote:[color=green]
> > I tottaly agree you should deliver your email directly to the server
> > and avoid the use of the POP3 connector.
> >
> > There is however a way to allow users to send from different
> > domains/accounts.
> >
> > First enable IMAP on your Exchange server. Then on the client side
> > in Outlook add an IMAP connection to the server with the email
> > address you want to send from. When the user composes a new
> > message, a new button will show up near the Send button, this
> > button will be called "Account" and it will let you specify which
> > account the user is sending from.
> >
> > Hope that helps,
> >
> > Mark D. MacLachlan
>
> Yes, that works (as does a dummy POP account set up to send only, not
> receive...if the addresses are all aliases in the mailbox) . However,
> it's awkward and does not scale well, so I tend to avoid it.[/color]

Using IMAP you are accessing the same messages on the server as you
would from your regular mailbox account. With POP the client would try
to download those messages locally and then round robin then back into
the information store so I don't like that approach.

--

Mark D. MacLachlan wrote:
> Lanwench [MVP - Exchange] wrote:
>[color=green]
>> Mark D. MacLachlan wrote:[color=darkred]
>>> I tottaly agree you should deliver your email directly to the server
>>> and avoid the use of the POP3 connector.
>>>
>>> There is however a way to allow users to send from different
>>> domains/accounts.
>>>
>>> First enable IMAP on your Exchange server. Then on the client side
>>> in Outlook add an IMAP connection to the server with the email
>>> address you want to send from. When the user composes a new
>>> message, a new button will show up near the Send button, this
>>> button will be called "Account" and it will let you specify which
>>> account the user is sending from.
>>>
>>> Hope that helps,
>>>
>>> Mark D. MacLachlan
>>
>> Yes, that works (as does a dummy POP account set up to send only, not
>> receive...if the addresses are all aliases in the mailbox) . However,
>> it's awkward and does not scale well, so I tend to avoid it.[/color]
>
> Using IMAP you are accessing the same messages on the server as you
> would from your regular mailbox account. With POP the client would
> try to download those messages locally and then round robin then back
> into the information store so I don't like that approach.[/color]

Yes, which is why I said a "dummy" account, which is set up in Outlook not
to retrieve but only to send. All the inbound mail is in the user's mailbox
anyway because the alias addresses are there.

Lanwench [MVP - Exchange] wrote:

> Yes, which is why I said a "dummy" account, which is set up in
> Outlook not to retrieve but only to send. All the inbound mail is in
> the user's mailbox anyway because the alias addresses are there.

Lanwrench, how would you setup a POP account to not retrieve email? The
only way I can think of would be to give it a bad POP server address
which would then produce errors.

--

Mark D. MacLachlan wrote:
> Lanwench [MVP - Exchange] wrote:
>[color=green]
>> Yes, which is why I said a "dummy" account, which is set up in
>> Outlook not to retrieve but only to send. All the inbound mail is in
>> the user's mailbox anyway because the alias addresses are there.
>
> Lanwrench, how would you setup a POP account to not retrieve email?
> The only way I can think of would be to give it a bad POP server
> address which would then produce errors.[/color]

You tell Outlook (in the send/receive settings) not to check for mail on
that account.
And it's Lanwench, btw.