Bug 35282 - relay handling for specific users
relay handling for specific users
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: Mail
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-07 12:17 CEST by Tim Petersen
Modified: 2020-07-03 20:53 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Petersen univentionstaff 2014-07-07 12:17:27 CEST
Reported at 2014060621008951:

There is no way to use mail/maps/transport/.* for configuring "exceptions":

The customer wanted mails, adressed to an alternative mailadress, to be sent via relay - but only for one specific customer - this does not work with this construct.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2014-07-07 17:38:28 CEST
The current mail stack always rewrites the recipient to univentionMailPrimaryAddress (required for local IMAP mail delivery).
So only the primary mail addresses will be looked up within the transport table.

Workaround for this customer:
swap primary mail address and alternative mail address.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:39:48 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:53:37 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.