Getting tired of the John and Jane doe testing account names?
Here some funny and creative ones — let me know if you got some to add 🙂
Owa Tegyu Siam
Chuck U Farley
Solomon I. Lands
Loo King Good
Sum Dum Chum
So Soo Mee
Kisme U. Fool
Phil D Basket
Funny thing happend……
For some reason new email accounts (older then 24 hours) and email aliases was not working properly within Office365.
External contacts was reporting:
tried to deliver your message, but it was rejected by the server for the recipient domain mydomain by mydomain.mail.protection.outlook.com
550 5.4.1 [<username>@<mydomain>]: Recipient address rejected: Access denied
- Accounts was is getting propagated in an accepted time frame (24 hours)
- The affected accounts is unable to receive email from external contacts – emails are not getting delivered.
- We changed the accepted domain to Internal relay to resolve the issue.
- As a precaution we enabled Conditional Sender ID and NDR backscatter to avoid spam attacks.
Articles on Mail Flow for reference:
Exchange Online Protection Limits
How Office 365 does SPF checks for customer-to-customer mail
Manage Transport Rules
Configure your spam filter policies
Submitting spam and non-spam messages to Microsoft for analysis
Advanced spam filtering options
Spam email and Office 365 environment
There seems to be some doubt about Office 2016 when to install 64-bit version of office vs 32-bit
Limitations of the 64-bit version of Office
The 64-bit version of Office may perform better in some cases, but there are limitations:
- Solutions using ActiveX controls library, ComCtl controls won’t work.
- Third-party ActiveX controls and add-ins won’t work.
- Visual Basic for Applications (VBA) that contain Declare statements won’t work in the 64-bit version of Office without being updated.
- Compiled Access databases, like .MDE and .ACCDE files, won’t work unless they’re specifically written for the 64-bit version of Office.
- In SharePoint, the list view won’t be available.
If you have specific add-ins that you use in the 32-bit version of Office, they may not work in 64-bit Office, and vice versa. If you’re concerned, check your current version of Office before installing the new one. Considering testing the add-in with 64-bit Office, or finding out if a 64-bit version of the add-in is available from the developer.
The 64-bit version of Office has some limitations, but is the right choice when:
- You work with extremely large data sets, like enterprise-scale Excel workbooks with complex calculations, many PivotTables, connections to external databases, PowerPivot, PowerMap, or PowerView. The 64-bit version of Office may perform better for you.
- You work with extremely large pictures, videos, or animations in PowerPoint. The 64-bit version of Office may be better suited to handle these complex slide decks.
- You work with extremely large Word documents. The 64-bit version of Office may be better suited to handle Word documents with large tables, graphics, or other objects.
- You’re working with files over 2GB in Project, especially if the project has many subprojects.
- You want to keep the 64-bit version of Office that you’re already using. The 32-bit and 64-bit versions of Office programs aren’t compatible, so you can’t install both on the same computer.
- You’re developing in-house Office solutions, like add-ins or document-level customizations.
- Your organization requires Hardware Data Execution Prevention (DEP) be enforced for Office applications. DEP is a set of hardware and software technologies that some organizations use to enhance security.