Community

OUTBOUND email is down?

#1

On ALL outbound emails, regardless of recipient, I am getting 1 of 2 error messages.

1.) a popup saying “the email could not be sent”
2.) After sending, an immediate mailer daemon email from the Axigen server saying “permanent failure” with a description in the body of “failed to authenticate”

I’m using the Axigen webmail client. How could it be failing to authenticate?
I’ve logged out & back in. I’ve updated my password int eh webadmin portal and then logged out & back in. I’ve verified the email addresses. (Half of them are my other accounts).

What gives?

Rebooting server next…

#2

Here is the daemon message:

I am deeply sorry, but I was not able to deliver your mail to the following addresses:
[EMAIL ADDRESS] : authentication required, 3 retry(ies) remaining.
[EMAIL ADDRESS] : authentication required, 3 retry(ies) remaining.
This is a permanent delivery failure. The delivery has been tried 0 times and will not be rescheduled again.

#3

the problem persists after reboot

#4

image
image.png1010×135 4.09 KB

#5

2019-06-20 09:29:50 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Relay mail 2F8FE1: connecting to 52.124.3.12:25
2019-06-20 09:29:50 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Relay mail 2F8FE1: connected to 52.124.3.12:25
2019-06-20 09:29:50 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Start sending mail 2F8FE1
2019-06-20 09:29:51 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Negative reply to MAIL command: authentication required, 3 retry(ies) remaining.
2019-06-20 09:29:51 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Set recipient supportnamorgycom@namorgy.freshdesk.com state to RELAY ERROR
2019-06-20 09:29:51 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Delivery attempt completed for mail 2F8FE1; schedule for cleanup
2019-06-20 09:29:51 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Set mail state to SENT
2019-06-20 09:29:51 -0500 08 AXIGENSVR SMTP-OUT:0000001C: Disconnected from 52.124.3.12

#6

Continuing the discussion from OUTBOUND email is down?:

Changing from using SMTP relay to direct resolved the issue. However, the entire Class C IP subnet for my pub IP is on RBL and cant be lifted. So I need to go back to using a SMTP relay…

My current SMTP relay is not blacklisted. I confirmed my account and settings with my SMTP relay. Not sure why this is happening. AGRH

#7

Hello Pete,

Please increase the log level for SMTP Sending service to Protocol Communication and retest using your SMTP relay configuration checking the SMTP-OUT log lines for any hints of why the message was rejected.

Maybe that relay is asking for authentication, in which case all you have is to ask for your credentials and configure them accordingly (in WebAdmin > Security & Filtering > Acceptance & Routing > Routing Basic Settings > Outgoing delivery settings set Username and Password under Enable authentication).

HTH,
Ioan

1 Like