Relay access denied 554 5 7 1 in outlook occurs for two main reasons.
Access control relay denied.
In applications tab click on new task and type explorer exe in empty box.
The first reason is that your outgoing mail server smtp doesn t allow to send emails without user authentication and the other reason is that your email address is marked at spam lists as a source of spam.
Apr 13 2010 1 i use my cellphone as a modem when sending email from.
It sounds you need to set up an access control policy that allows your exchange server to use the fortimail as a relay.
As whopper indicated also make sure you update your external mail records as well to avoid being blacklisted.
Some emails get out.
As well as it may get on the firewall blacklist on recipient s side.
Mail servers will not relay mail from just anyone.
If this is the case then view the headers of the bounce email.
In your fortimail console click on policies and expand access control that should get you started.
Start date apr 13 2010.
Press control alt delete key simultaneously to start task manager.
Take ownership of c drive do the following.
Solved relay access denied problem post by free1089 mon may 17 2010 3 12 am quote user uxbod the restriction for reject invalid hostname is what you are hitting i believe.
When access is denied based on the access control list the door remains locked.
It should give your details as to why it was rejected.
Now you will be able to get to desktop.
Right click the c drive and then click properties.
When looking at the log i don t see internal protected email addresses in the from field.
The control panel also ignores a door open signal to prevent an alarm.
Click the security tab.
Relay access denied most likely that your server is not passing the recipient s server anti spam rules and checks.
Fortimail 90 access control outbound hi i have an fml that seems to be working fine for receiving email but when looking at the graph for outbound ermail it shows 80 if emails are blocked by access control relay denied.
Typically it s caused by your server ending up on rbl s realtime blackhole list.