I have an Exchange 2013 server.
Faced with a strange issue of email delivery what I can not solve.
Exchange is rejecting email
if one of the recipients is not exist in a domain
Email will be rejected totally and sender will receive NDR for not existing user.
scenario:
Exchange mailboxes user#domain.com // valid user
user1#domain.com //**user mailbox is not exist**
Sending email from external domain to my exchange server:
TO: user#domain.com,user1#domain.com
Reciving NDR Remote Server returned '550 5.1.1 RESOLVER.ADR.RecipNotFound;
valid user didn't receive email also.
email is rejected
.
I start to google and found that How do I reject incoming email for unknown users in MS Exchange 2013?
exchange has a user validation feature that is enabled by default
I disable it on a console restart transport role.
Set-RecipientFilterConfig -RecipientValidationEnabled $false
run the same scenario again
user#domain.com, user1.domain.com
I receive NDR for not existing user.
but email was delivered to valid user.
Is it a normal behavior for exchange?
What is right by RFC deliver for valid users or reject email?
how it will affect our server hit the public spam list?
Does this not reduce our spam filter resistance?
Please advice.
Thank you.
It's normal for Exchange to send an NDR for non existing users. As you already said, this might also trigger some spam lists because you are sending out mails (NDR) to possible spam honey pots.
A better way to do this would be to have your external MTA (the server which accepts the mail from the internet) check the recipients and refuse to accept mail for non existent email addresses. This way you would never have to send out NDR reports, as the server trying to deliver mail would be informed that it cannot deliver and notifies the sender itself.
Related
So I thought I have this setup correctly, but it is not working. Maybe someone can help?
I setup a mailbox called formsmbx (for FORMS MailBoX)
I setup a distribution list (DL) in Exchange 2013 named forms
In this DL, I added one member (formsmbx).
In Exchange, I setup a mail flow rule with these parameters:
If sender is 'outside the organization' AND the To or CC box contains forms#,
Then bcc the message to formsmbx#.
I logged into a Windows computer running Outlook 2019 as formsmbx. I went to File/Manage Ruls & Alerts. I setup a Rule that says:
after message arrives
have server reply using 'auto reply'
So finally, I sent an email from test#gmail.com to forms#domain.com. What I found was the formsmbx# inbox receives the email, but there is never an auto-reply sent out.
If I send an email directly to formsmbx#, I do not get any reply.
Is it possible to change the From Name of an email (not the sending address) when sending an email from Outlook Exchange?
Is there any add-in that can help us achieve this?
I can see with Exchange only admin can change the sending from name. Is there an alternative?
In general, you can't do that out of the box. The latest version of hosted (M365) Exchange allows to configure a mailbox to send as one of its proxy SMTP addresses, but the sender display name will still be the same.
You can try to use an addin like Proxy Manager (I am its author) - besides allowing to send through any of the mailbox proxy addresses, it also allows an end-user to change the sender display name.
I have noticed something very odd about certain emails sent on outlook via an exchange server -- it appears if certain URLs and embedded in the message, message send will fail silently. The message will show up in the "sent items" folder, but it is never actually received by the recipient.
I checked in with GoDaddy who supports my Office365 subscription and they confirmed the behavior (they couldn't send successfully send it either, other me or others in their organization) but had no explanation for the behavior.
I have confirmed that the message sends normally if I use one of my gmail accounts through outlook or or an icloud email account. But my two exchange accounts (on different domains) neither send nor receive any email with this particular embedded url:
(Makes no different if sent in plaintext or not). And other emails, with either no urls or even other urls, send normally. Does Microsoft have a problem with foundation? Or with NFTs or something?
https://foundation.app/#NyanCat/foundation/219
This happens to be the NyanCat NFT that sold for ~$700K a while ago, but no idea what it is about simply the presence of the URL in the body of the message to cause it to fail silently when sent or received on an Exchange server. Not sure if impacts other Exchange servers besides GoDaddy's, but does can anybody explain how this even happening or why?
I have the mail exchange server for pratice. And in this exchange server, I create a bulk recipients but still not logon anytime.
When I run Get-MailboxStatics it return an warning that:
WARNING: The user hasn't logged on to mailbox 'abc'
('76768175-4db5-4cbb-a36b-fdbde574ccbc'), so there is no data to
return. After the user logs on, this warning will no longer appear.
So with the large number recipients over 100, how can I use powershell code to stimulate that I already logon successful for all recipient in this server?
I would suggest you look at using LoadGen https://www.microsoft.com/en-au/download/details.aspx?id=40726 and that will generate load on the server which will populate all the log files for you to look at and test. (the 2013 version will run fine on Exchange 2016).
We've been using Mandrill for years to deploy our app's signup confirmation and password reset emails. This has worked perfectly as we've had SPF and DKIM records added to the DNS configuration according to Mandrill's documentation for verifying sending domains.
However, after merging the Mandrill account with a new Mailchimp account--which is mandated by April 27th--it's requiring me to send a verification email to an address at that domain. The problem is that we don't have a mail server set up to receive emails. The domain is only used to send the "noreply#domain.com" emails.
Any ideas on how I might resolve this? Mailchimp is not giving an option to undo the merge, so effectively I have an app that users are not able to sign up for at the moment, which is problematic to say the least.
You'll want to configure at least one mailbox on that domain somehow to receive mail. That's the only way to confirm ownership of the domain.