1 Topic by d.payet

  • d.payet
  • Member
  • Offline
  • Registered: 2020-11-24
  • Posts: 15

Topic: SMTP AUTH for a forward

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.2 MARIADB edition
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version:  Debian 10
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

<support@domain1.com>: host my_iredmail_server said: 554 5.7.1
    <support@domain1.com>: Recipient address rejected: SMTP AUTH is required
    for users under this sender domain (in reply to RCPT TO command)


Hello,

here's my problem :
- i have a domain 'domain1.com' and my customer have a 'domain2.com' hosted on another ISP. He has configured his mailserver to forward hostmaster@domain2.com to support@domain1.com (my iRedMail server).
- if anyone send to hostmaster@domain2.com, it comes to support@domain1.com, no problem.
- if I send (with an account on domain1.com) to hostmaster@domain2.com, I receive the previous error message. I see the problem but I can't figure how to solve this.

Thanks smile

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: SMTP AUTH for a forward

d.payet wrote:

- if I send (with an account on domain1.com) to hostmaster@domain2.com, I receive the previous error message. I see the problem but I can't figure how to solve this.

This error is expected since the sender address is still your email address but sender server is NOT your server. That's why it says "SMTP AUTH is required for users under this sender domain". And the forwarding mail server is expected to rewrite address to something like "srs0...@domain2.com" (or other address).

No perfect solution for this loop without address rewrite. A working solution but not "perfect" is: add parameter "ALLOWED_FORGED_SENDERS" in /opt/iredapd/settings.py to tell iRedAPD to allow "forged" sender address like this:

ALLOWED_FORGED_SENDERS = ["sender@domain1.com"]

Restarting "iredapd" service is required after the change.