Jump to content
EduGeek EdSec 2026 is on Tuesday in Derby! Join us for a day of EdTech security focused talks, networking, and an evening social ×

Recommended Posts

Posted

I've just added a new alias to a user......a process that has worked fine in the past with out any issue, but this time it's not playing ball and i can't work out why.

 

I'm using the same domain name, nothings changed there. All i'm adding is a new SMTP alias of [email protected] for example. I can send to it internally fine, but when i sent to it from an external source i get a bounceback with the error "Recipient address rejected: Access denied" anyone have any ideas?

 

Google is failing me on this one, everything points towards the domain name, but i know that's fine and is in the accepted domains list (I'd have a few problems if it wasn't!)

Posted
Do you have a policy that restricts emails from external recipients?

 

Nope, I've even created a "bypass spam filtering" rule for any emails sent to that alias as a test, still no joy.

 

The server returned status code 550 - Mailbox unavailable. The server response was: 5.4.1 [[email protected]]: Recipient address rejected: Access denied
Exception details:
Message: Mailbox unavailable. The server response was: 5.4.1 [[email protected]]: Recipient address rejected: Access denied
Type: System.Net.Mail.SmtpFailedRecipientException
Stack trace:
at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, Boolean allowUnicode, SmtpFailedRecipientException& exception)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()
Elapsed Time: 5699 ms

 

That's the response i get on an inbound email test on the microsoft connectivity tester. (obviously real email address removed)

Posted
Nevermind! I was just being impatient, i didn't give azure ad sync time to process the next run. It works now :p The joys of a hybrid solution...
Posted
Nevermind! I was just being impatient, i didn't give azure ad sync time to process the next run. It works now :p The joys of a hybrid solution...

 

Sync issue, nothing's ever quick enough lol

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...