I can't send emails outside the domain, "Relay Access Denied" error

OK, that looks fine.

And, actually I now see authentication failures in the log…I missed it earlier, as there’s so many.

This one seems simple: Wrong username or password.

Check your username in the Edit Users page (depending on configuration, the username may be prueba and not prueba@consulproy.com). And, try logging in via Usermin or ssh (assuming ssh allows password authentication) to see if you’ve got the right password.

It’s possible your saslauthd configuration is broken (we alter the config to allow user@domain.tld users, if you’ve uninstalled saslauthd at some point it may have reverted to the default that doesn’t work for those users).

Hi, I can log in normally with my username and password from usermin, but I still can’t send emails to external domains from Thunderbird or another email manager for PC!

Jan  8 01:26:19 vmi2077506 dovecot[655617]: imap-login: Login: user=<prueba2@consulproy.com>, method=PLAIN, rip=181.199.61.156, lip=77.237.236.188, mpid=3055099, TLS, session=<ks8W6SYrFt21xz2c>
Jan  8 01:29:52 vmi2077506 postfix/smtpd[3055442]: NOQUEUE: reject: RCPT from unknown[181.199.61.156]: 454 4.7.1 <sochmal@gmail.com>: Relay access denied; from=<prueba@consulproy.com> to=<sochmal@gmail.com> proto=ESMTP helo=<[192.168.1.6]>

I am sending an email to sochmal@gmail.com from prueba2@consulproy.com

No. Had you either set up autodiscover OR the smtp server correctly as mentioned above this wouldn’t be happening.
You log in as prueba2@consulproy.com

Jan  8 01:26:19 vmi2077506 dovecot[655617]: imap-login: Login: user=<prueba2@consulproy.com>, method=PLAIN, rip=181.199.61.156, lip=77.237.236.188, mpid=3055099, TLS, session=<ks8W6SYrFt21xz2c>

You send as

from=<prueba@consulproy.com> 

See post 11. SMTP is set up separately.

Is it because you are using LOGIN authentication and not PLAIN?

Hi, I already did that test of everything you indicated, I still have the same problem.

Have you seen our troubleshooting email guide? We need to narrow this down to a specific problem, there’s a million ways email servers and clients can be misconfigured.

If you get prove or disprove SASL authentication is working, we can then move on to the client side, probably.

As mentioned above, the client does need to use PLAIN authentication (because there are no other auth types that line up between system users and IMAP/POP, and as long as you’re using encrypted protocols, it’s safe).

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.