Salesforce.org System Administrators

@Eric Pohlabel @Ankur Jain

 Hello from the future. Did you figure this out? I was running into a similar situation and discovered that somehow the seasonal address fields had been set to use an old address for month 1 to month 12, and all days. When I updated those fields to be empty the addresses updated everywhere else as expected.   

Not sure if this is the same situation, but I felt the need to share after spending some time searching through trailhead for similar issues.  

Hi Russell,

That long string of random characters (something like user=company.com__xyz...@salesforce.com or via bnc.salesforce.com) appears because Salesforce sends emails on your users' behalf using Sender ID compliance and bounce management, which modifies the envelope From / Return-Path header.

Here is how to remove that string and send clean, reputable emails showing only your rep’s name and corporate email address:

Solution 1: Turn Off Sender ID Compliance & Bounce Management (Quickest)

If you send emails directly through Salesforce servers without an external email integration, Salesforce rewrites the sender envelope by default.

1. Go to Setup > enter Deliverability in the Quick Find box > select Deliverability.
2. Scroll to the Email Security Compliance section.
3. Uncheck the following boxes:
   • Enable Sender ID compliance
   • Enable bounce management
4. Click Save.

Solution 2: Use "Send through External Email Service" (Recommended Best Practice)

The cleanest, most reliable approach is to route user emails through your company's actual mail server (Google Workspace or Microsoft 365). This eliminates the Salesforce relay address completely and places sent emails directly in the user’s corporate "Sent Items" folder.

1. Go to Setup > enter Send through External Email Services in the Quick Find box.
2. Toggle on Send through external email services.
3. Enable either:
   • Send through Gmail (if using Google Workspace)
   • Send through Office 365 (if using Microsoft 365)
4. The next time a user clicks the Send Email button in Salesforce, they will be prompted once to authenticate with their corporate email credentials.

After connecting, all emails sent by that user will come directly from their native mail server—no Salesforce routing strings, no header spoofing flags, and maximum inbox deliverability.

I know this is a very old question, but just in case it helps someone. The External Data Source should first be granted to the individual user via permset/profile. That is all it meant by the bolded line. 

User should now see a banner they can follow to authenticate with that data source, or otherwise follow. 

If you get to the point where you are seeing an error like this

• AllSites.FullControl
• EnterpriseResource.Write
• MyFiles.Write
• Sites.Search.All

if you add all those, then resync the external source metadata and try again it should work

Dynamic related lists are supported for key objects (Contact, Account, Opportunity, Lead, Case), custom objects, and hundreds of other standard objects in Salesforce. However, some objects are not yet supported. Salesforce will continue to make additional objects available to use with dynamic related lists over time.

https://admin.salesforce.com/blog/2023/view-all-for-dynamic-related-lists-learn-moar-spring-23

I couldn't find a specific list anywhere, but I guess this is just not a supported standard object at this time.

Hi Manjula Rajaram, 

Recently I worked on the Data Migration- Attachements Of Contacts (Export:10,000 and Import:7,000 Attachments) by using Data loader  and also I used third party tool both were working fine. 

Please fallow the below steps for Export:   

1.Prepare the Soql and apply the export operation.

Select  FieldsALL()  FROM Attachment where Parent.Type = 'Contact' order by createddate limit 1000