You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MX record target domainA.de and all mails should go thou haraka and then to an exchange server that has configured the domain domainA.de.
A receive connector has been configured on the Exchange Connector to accept mail from the Haraka IP.
For compliance reasons, we need to redirect one address ([email protected]) to another exchangeserver with the domain domainB.dem and the address [email protected].
Expected behavior
We expect, that all address will proceed separate, but i seems like the plugin uses only the first address to proceed all addresses.
Observed behavior
Mails with multiple recipients are tried to be delivered to the same Exchange server, although the Alias plugin from [email protected] changes to [email protected].
The delivery is rejected by the Exchange of domainB.de, because it is not responsible for domainA.de.
System Info
Haraka
Haraka.js - Version: 3.0.2
Node
v20.3.0
OS
Linux haraka01 5.15.0-75-generic haraka/Haraka#82-Ubuntu SMP Tue Jun 6 23:10:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
openssl
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
When we send an email to [email protected] it will be redirected to the server with the domain domainA.de and the address [email protected]
When we send an email with two or more address in the to/CC/BCC field e.g., [email protected], [email protected] all emails will be redirected to the server with the domain domainB.de. All mails will be rejected.
I forget the specifics but there's something you have to rewrite in the transaction when you modify the destination address using the aliases plugin. It's come up either on the haraka email list or here in GitHub. On my list of things to do is modify the aliases plugin to make that something automatic.
For compliance reasons, we need to redirect one address
Do you need to redirect the address (a mail forward) or do you need to "tap" the address and send a COPY of every message to exchangeB? (my guess: the latter).
One way to do this is with a plugin and just generate a new transaction and insert it into the outbound queue.
Describe the bug
We have two domains domainA.de and domainB.dem
The MX record target domainA.de and all mails should go thou haraka and then to an exchange server that has configured the domain domainA.de.
A receive connector has been configured on the Exchange Connector to accept mail from the Haraka IP.
For compliance reasons, we need to redirect one address ([email protected]) to another exchangeserver with the domain domainB.dem and the address [email protected].
Expected behavior
We expect, that all address will proceed separate, but i seems like the plugin uses only the first address to proceed all addresses.
Observed behavior
Mails with multiple recipients are tried to be delivered to the same Exchange server, although the Alias plugin from [email protected] changes to [email protected].
The delivery is rejected by the Exchange of domainB.de, because it is not responsible for domainA.de.
System Info
Details
We configured the following alias rule:
{ "[email protected]" : { "action" : "alias", "to" : ["[email protected]"] } }
We have the following configuration in smtp_forward.ini:
Plugins:
aliases
rcpt_to.in_host_list
queue/smtp_forward
When we send an email to [email protected] it will be redirected to the server with the domain domainB.de and the address [email protected]
When we send an email to [email protected] it will be redirected to the server with the domain domainA.de and the address [email protected]
When we send an email with two or more address in the to/CC/BCC field e.g., [email protected], [email protected] all emails will be redirected to the server with the domain domainB.de. All mails will be rejected.
The text was updated successfully, but these errors were encountered: