Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
I
ISPConfig 3
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 494
    • Issues 494
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 30
    • Merge Requests 30
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #3769

Closed
Open
Opened Feb 19, 2016 by Eric@epek

Configuration improvement suggestion for postfix 2.10+

In http://www.postfix.org/SMTPD_ACCESS_README.html#danger Vietse advises to specify relay policy under smtpd_relay_restrictions and spam blocking policy under smtpd_recipient_restrictions. Cause: "Then, a permissive spam blocking policy will not result in a permissive mail relay policy."

Current configuration looks like this: smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf

which seems to be ok, but invites for errors in case of manual reconfiguration.

Edited Aug 27, 2020 by Thom
Assignee
Assign to
3.2
Milestone
3.2
Assign milestone
Time tracking
None
Due date
None
Reference: ispconfig/ispconfig3#3769