Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 1,524
    • Issues 1,524
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #2388

Closed
Open
Opened Feb 07, 2013 by Gabriel K.@typoworx
  • Report abuse
  • New issue
Report abuse New issue

ispConfig Mail-Transport/Routes do not work by giving the Domain-Name!

I noticed that there seems to be something wrong with the ispConfig configuration for Mail-Transport/-Routes.

I'm hosting a customers Web (WWW-Only!) whereas the Mail hosting is done by their own Exchange-Server. The DNS-Record correctly points to their own MX. But my Server (PHP based Web) tries to deliver them to the origin of the Customers-Domain A-Record (=My Machine responsible for WWW-Hosting only!).

Then I tried to enter the Domain as SMTP-Mail Route and then entered the Customers-Domain in Mail -> Global-Filters -> Relay Recipients.

But I noticed that "Relay Recipients" doesn't seem to accept a Domain-name by testing this route. My Smtp rejects the E-Mail send by my own E-Mail Account hosted on the same machine.

I would expect it right if the Domain-Name matching the "Relay-Transport" in MySQL would match the Domain-TLD of the outgoing E-Mail. Testing the same Route-Setup with a full E-Mail Address under the "Relay Recipients" in ispConfig works fine and confirms the wrong behaviour.

I think this can be fixed by altering the MySQL-Query in the Postfix's "mysql-virtual-transport" Query.

Assignee
Assign to
Planned features
Milestone
Planned features
Assign milestone
Time tracking
None
Due date
No due date
2
Labels
3.0.4.6 Feature Request
Assign labels
  • View project labels
Reference: ispconfig/ispconfig3#2388