Email Alias - Can users send "from" an alias?

Greetings.

Using SBS 2003 with Exchange 2003 SP2. Mail is delivered straight to
exchange server. No pop connector.

User has several email aliases (for example, ,
, , etc.)

User wants to reply to an email message that comes in to one of the alias
email addresses () to "come from" the alias email
address, instead of the default email address.

Is this possible?

Thanks in advance!

 

You can expose the "From" field for outbound email addresses in Outlook and
once it is exposed it stays exposed until you choose to hide it. Once it
is exposed you can type in a from address which could be an address other
than the default smtp address for the user. The way that you expose that
field varies with the version of Outlook etc. In general, create a new
email message then go to view, or options (Outlook 2007), etc. on the menu
bar and chekc the from field.

I hope this helps.

Jim Martin - (MSFT)

Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

 

I have tried that, but, I receive the following error message:

"Yopu do not have the permission to send the message on behalf of the
specified user"

Any ideas?

 

Grant the user "Send As" permissions for the second alias.

 

Hello all,

Jim and kj, your suggestions are wrong. Exchange doesn't allow you to send
as non-default SMTP address natively.

GNSM100, have a look at this third-party add-in:

http://www.ivasoft.com/choosefrom.shtml

Regards,
Victor Ivanidze

 

The suggestions are "not applicable" to a non default recipient address.

The suggestions work fine for sending to the SMTP default address of a
different user/alias/contact/dl.

Perhaps the question wasn't correctly understood and that's why the
suggestions didn't match.

 

How about creating a new email account in Outlook with the alias' info, using
the exchange server as the smtp address and anything for the pop3 address,
but tell outlook to not check for new messages on that account.

 

Thanks Victor - that seems to do the trick.

For whatever it's worth (to those Microsoft peeps looking around here), this
is an issue that comes up frequently with my clients, and, it'd be nice if
this were supported in Exchange.

In the meantime, 3rd party apps to the rescue!

Thanks again!