I have multi mailboxs connecting into one domain.
My machine have Redemption version 5.22 with Outlook 2013.
The mailboxs from serveur Exchange 2013 can login and send the mails. But the mailbox Exchange 2016 can just login and can't send mail because of the code :
-2147467259,Could not resolve the message recipients
This is the code to login. Both of them are logged on.
RDOSession.LogonExchangeMailbox O365#abc.fr, rapport.groupe.abc.fr
RDOSession.LogonExchangeMailbox Exchange2013#abc.fr, rapport.groupe.abc.fr
RDOSession.LogonExchangeMailbox EXCH_2016#abc.fr, rapport.groupe.abc.fr
The mail has same destination.
Do I miss some installation on the machine ?
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.
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.
I built an Outlook Add-in and it uses a token to download email attachments from the Exchange server.
On my O365 developer account, it successfully retrieves the token.
The Add-in has been deployed to the client's Outlook but when they try to retrieve the token, this is the response message:
MessageText:"The token for this extension could not be retrieved.
"ResponseClass:"Error"
ResponseCode:"ErrorInvalidClientAccessTokenRequest"
Token:null
__type:"GetClientAccessTokenResponseMessage:#Exchange"
The code is exactly the same and so is the request. Is there any clues I could look into to figure out what about their environment would cause this to fail?
The ErrorInvalidClientAccessTokenRequest field is applicable for clients that target Exchange Online and versions of Exchange starting with Exchange Server 2013.
I am developing an email client using EWS. I know there is a XML tag MarkAsJunk to mark an email as Junk. But this tag is only available for Exchange version 2013 or later. What is the way to mark an email as Junk/Spam in Exchange version less than 2013 ??. Does move an email to Junk Email folder will ban future emails coming from that sender ??
In Outlook 2016 (Outlook 2016 MSO 16.0.4266.1001 64 bit) , when S/Mime user accepts a calendar invitation sent by a non s-mime user, following error is displayed.
"Microsoft Outlook cannot sign or encrypt this message because there are no certificates which can be used to send from the email address . Either get a new digital ID to use with this account, or use the accounts button to send the message using an account that you have certificates for."
This error is not seen with Outlook 2013.
These 3 security properties are checked on opening the event (which are unchecked in Outlook 2013)
Encrypt message contents and attachments.
Add digital signature to outgoing messages.
Request S/Mime receipt for this message.
What mapi properties are used to check/uncheck these security properties?