Fix lỗi can t connect to the printer 0057 năm 2024
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Show
Fix issues with printers, scanners, and LOB apps that send email using Microsoft 365
In this articleEmail clients provide actionable error messages when something goes wrong. Sending email from devices and applications is less easy to fix, and you might not get clear information to help you. This article can help you troubleshoot, and it uses printer configurations as examples. As a first step to fixing any problems, check your configuration. See How to set up a multifunction device or application to send email using Microsoft 365 or Office 365 for detailed information about the configuration options. My printer is already configured for email, but I don't know which configuration option it usesThe following list describes the available configuration options:
Fix issues with SMTP AUTH client submissionI set up my printer for SMTP AUTH client submission, but it still can't send email
To learn more, see New opt-in endpoint available for SMTP AUTH clients still needing legacy TLS For more information about TLS, see How Exchange Online uses TLS to secure email connections. I receive an authentication error when my device tries to send emailThis error can be caused by a number of issues:
Error: Authentication unsuccessfulIf you receive one of the following errors:
There are a few things you should check:
Error: 5.7.60 SMTP; Client does not have permissions to send as this senderThis error indicates that the device is trying to send an email from an address that doesn't match the logon credentials. An example would be if your entered login credentials for [email protected] in your application settings but the application tries to send emails from [email protected]. If your application or printer behaves this way, use Microsoft 365 or Office 365 SMTP relay because SMTP client submission does not support this scenario. Error: Client was not authenticated to send anonymous mail during MAIL FROMThis error indicates that your printer connects to the SMTP client submission endpoint (smtp.office365.com). However, your printer must also logon to a mailbox to send a message. This error occurs when you have not entered mailbox logon credentials in the printer's settings. If there is no option to enter credentials, this printer does not support SMTP client submission; use either direct send or Microsoft 365 or Office 365 SMTP relay instead. See How to set up a multifunction device or application to send email using Microsoft 365 or Office 365. Error: 550 5.1.8 Bad outbound senderThis error indicates that the device is trying to send an email from a Microsoft 365 or Office 365 mailbox that is on a spam block list. For help, see Remove blocked users from the Restricted Users portal. Error: 535 5.7.139 Authentication unsuccessful, federated STS service was unreachable.This error related to federation gateway servers hosted on-premises by customers. We were unable to reach the configured server location and therefore could not authenticate the federated user. Error: 535 5.7.139 Authentication unsuccessful, the federated STS URL does not support HTTPS.This error related to federation gateway servers hosted on-premises by customers. We were unable to establish the required secure connection with the server and therefore could not authenticate the federated user. Note: This may be due to the deprecation of TLS1.0 and TLS1.1 which is occurring in 2022. You need to make sure your servers are able to use TLS1.2. You can find more information here: Preparing for TLS 1.2 in Office 365 and Office 365 GCC. Fix issues with direct sendI set up my printer for direct send and it's not sending email - or - My device was sending email using direct send, but it stopped workingThis can be caused by a number of issues.
Client was not authenticated to send anonymous mail during MAIL FROM errorThis indicates that you are connecting to the SMTP client submission endpoint (smtp.office365.com), which can't be used for direct send. For direct send, use the MX endpoint for your Microsoft 365 or Office 365 organization, which ends with "mail.protection.outlook.com." You can find your MX endpoint by following the steps in . My emails are not sent to recipients who are not in my organizationThis is by design. Direct send allows email to be sent only to recipients in your organization that are hosted in Microsoft 365 or Office 365. If you need to send to external recipients, use SMTP client submission or Microsoft 365 or Office 365 SMTP relay. The MX endpoint is too long for the printer setting box. Can I use an IP address instead?It's not possible to use an IP address in place of an MX endpoint. This could result in your not being able to send messages in the future. If the MX endpoint is too long, consider using SMTP client submission, which has a shorter endpoint (smtp.office365.com). Emails from my device are marked as junk by Microsoft 365 or Office 365For direct send, we recommend using a device that sends from a static IP address. This allows you to set up a Sender Policy Framework (SPF) record to help prevent emails being marked as spam. Check that your SPF record is set up with your static IP address. A network or ISP change could change your static IP address. Update your SPF record to reflect this change. If you aren't sending from your own static IP address, consider SMTP client submission instead. Fix issues with Microsoft 365 or Office 365 SMTP relayI set up my printer for Microsoft 365 or Office 365 SMTP relay but it's not sending email -or- My device was sending email using SMTP relay, but it stopped workingThis can be caused by a number of issues.
Emails are no longer being sent to external recipientsNetwork or ISP changes might change your static IP address. This results in your connector not identifying and relaying your messages to external recipients. Update your connector and your SPF record with the new IP address. Follow the steps in to edit your existing connector settings. 5.7.64 TenantAttribution; Relay Access Denied or 4.4.62 Mail sent to the wrong Office 365 regionThis error indicates that email sent from your application or device is not correctly attributed to your tenant. A common cause of this issue is a change in your dedicated and static IP address or a change in the certificate used by your application or device. Update the inbound connector with the new IP address or new certificate information. Email from my device is marked as junk by Microsoft 365 or Office 365Microsoft 365 or Office 365 SMTP relay requires your device to send email from a static IP address. Check that your SPF record is set up with your static IP address. A network or ISP change could change your static IP address. Update your SPF record to reflect this change. If you aren't sending from your own static IP address, consider SMTP client submission instead. Run diagnostic to setup applications or devices sending email using Microsoft 365Note This feature requires a Microsoft 365 administrator account. If you still need help to fix issues with applications or devices sending email using Microsoft 365, you can run an automated diagnostic. To run the diagnostic check, select the following button: A flyout page opens in the Microsoft 365 admin center. Select the appropriate option that you are looking for, eg. new setup or troubleshooting existing setup. |