• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 351
  • Last Modified:

Not allowed to send as from different domain / recipient policy

Hi experts,

As of recently we added a new domain to our exchange configuration using an additional recipient policy. Naturally we contacted our providers to set up the public DNS and required MX records. Internally receiving the mail from @other_company.com is working fine.

The problem occurs when someone is trying to send as the new domain. Say my user account is filtered by both policies and as a result i get the following mail aliasses assigned.

----------Policy one --------------
SMTP : chris.gralike@company.com
smtp : c.gralike@company.com
---------Policy two ---------------
smtp : chris.gralike@other_company.com
Now i try to send from: (using the from header in the new mail) chris.gralike@other_company.com

I receive an NDR stating the following error,
You dont have the right permissions to e-mail to the following addresses. Contact your system engineer (me :/) for more information...

anyone with any clues?
Chris Gralike
Chris Gralike
  • 3
  • 2
2 Solutions
You need to look at your IMAP service. Check your RDNS settings too
Also refer: http://www.petri.co.il/forums/showthread.php?t=6409
Chris GralikeSpecialistAuthor Commented:
Hi gupnit,
Does this actually mean that by using the microsoft MAPI (rpc) connection method there is no way for me to send mail from the additionaly added email aliasses?

Because it does look like a Outlook misconfiguration, and not an exchange misconfiguration. i.e.

When using telnet (after removing the sender filters)
the following is returned. (see sniplet)

And is received as expected in the expected mailbox....

220 amisnt30.AMIS.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at  Tue, 21 Apr 2009 15:38:33 +0200
250 ****nt30.***.local Hello []
mail from:chris.gralike@*****professioinals.nl
250 2.1.0 chris.gralike@*****professioinals.nl....Sender OK
rcpt to:servicedesk@****.nl
250 2.1.5 servicedesk@****.nl
354 Start mail input; end with <CRLF>.<CRLF>
Testing test
testing Test
250 2.6.0 <****NT30jbDt3HvoFOA000000f4@****nt30.****.local> Queued mail for delivery
451 Timeout waiting for client input
Connection to host lost.

Open in new window

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

As far as Exchange/Outlook is concerned, all users only have one email address - the default one. All email the user sends goes out as that address. There is no functionality in Exchange to allow the user to select which address they can send email "as".

You can do so with SMTP/telnet tests because you can put anything you like as the From field. As long as the recipient is valid on the server, Exchange will accept it.

There are various ways to work with this issue
- multiple accounts
- dummy POP3 configurations
- third party tools.

I have outlined the main options here:

Chris GralikeSpecialistAuthor Commented:
Thanks for clearing that up.

This means that this issues has become a functional question instead of a technical one. Reading the suggested solutions using the IMAP4 virtual server just isnt going to work for us, and i think will suggest the multiple accounts sollution with the send as, send on behave permissions set.

Thanks again for the prompt replies :-)
Chris GralikeSpecialistAuthor Commented:
Thanks all, mstha received more points because its a 'cleaner' solution using mulitple accounts (wich was our idea too) just needed to know if it was a technical (conf) problem or functional one. It seems to be the functional one...

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now