tag:blogger.com,1999:blog-4262690568972857623.post2256836460822371662..comments2024-03-11T18:00:51.306+00:00Comments on Lets Exchange: 550 5.7.1 Submission has been disabled for this accountNuno Motahttp://www.blogger.com/profile/02579565400597081970noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-4262690568972857623.post-7838384821770617462016-04-30T05:50:40.844+01:002016-04-30T05:50:40.844+01:00Thanks for sharing James, that's good to know!...Thanks for sharing James, that's good to know!Nuno Motahttps://www.blogger.com/profile/02579565400597081970noreply@blogger.comtag:blogger.com,1999:blog-4262690568972857623.post-15648556065934954042016-04-29T16:02:33.602+01:002016-04-29T16:02:33.602+01:00I experienced the same issue in the Hybrid environ...I experienced the same issue in the Hybrid environment I work in. Basically messages from and o365 mailbox sent to external addresses and on premise mailboxes. The mailbox user on premise reported initially that they were not receiving the messages. After digging into AD I found that these senders in o365 were all at one time, terminated or disabled accounts that were re-enabled but the tick mark in ADUC along with the customer attributes still showed disabled or termed. Once those values and tick were changed the mail flowed without issue. So that's something to look at. Anonymoushttps://www.blogger.com/profile/07471832258642290251noreply@blogger.comtag:blogger.com,1999:blog-4262690568972857623.post-84162707915311592422013-10-15T14:22:08.294+01:002013-10-15T14:22:08.294+01:00Thanks for sharing!Thanks for sharing!Nuno Motahttps://www.blogger.com/profile/02579565400597081970noreply@blogger.comtag:blogger.com,1999:blog-4262690568972857623.post-74078430043865166142013-09-24T20:13:21.330+01:002013-09-24T20:13:21.330+01:00Very useful...another thing I figured out is even ...Very useful...another thing I figured out is even the mailbox is set to use the datastore quota if it has set as grayed out the settings to configure locally the quotas and it is set as 0KB the issue occurs.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4262690568972857623.post-48935385850441320812013-01-29T23:26:17.354+00:002013-01-29T23:26:17.354+00:00Hi Alexei,
Thank you! Glad you find it useful :)...Hi Alexei,<br /><br />Thank you! Glad you find it useful :)<br />Have you seen this happening even when the quotas are not set to 0KB?<br /><br />Regards, NunoNuno Motahttps://www.blogger.com/profile/02579565400597081970noreply@blogger.comtag:blogger.com,1999:blog-4262690568972857623.post-18366788564742558782013-01-29T23:17:59.520+00:002013-01-29T23:17:59.520+00:00Very useful information thank you. To add a bit mo...Very useful information thank you. To add a bit more info, the issue seems to occur when an Exchange 2007 Hub Transport server handles a message destined for an Exchange 2010 Hub Transport Server. This can occur in Orgs that have only Exchange 2010 mailboxes, but legacy 2007 HT servers that handle inter-site traffic.Anonymoushttps://www.blogger.com/profile/03042063843253715912noreply@blogger.com