ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0022721 | ClearOS | app-smtp - SMTP Server | public | 2019-01-11 13:02 | 2019-02-23 12:29 |
| Reporter | NickH | ||||
| Assigned To | dloper | ||||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | suspended | ||
| Platform | OS | OS Version | |||
| Product Version | 7.6.0 Updates | ||||
| Target Version | 7.6.0 Updates | Fixed in Version | |||
| Summary | 0022721: Start using smtpd_relay_restrictions | ||||
| Description | Round about v2.10 of postfix, a new parameter smtpd_relay_restrictions was introduced. This allowed the separation of open relay control from the smtpd_recipient_restrictions, leaving the smtpd_recipient_restrictions for anti-spam measures only by removing reject_unauth_destination from one of its settings. The line: smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination can take the place of the reject_unauth_destination in the smtpd_recipient_restrictions. This would reduce the chance of a user inadvertently creating an open relay by adding parameters to the smtpd_recipient_restrictions in the wrong order. Note this may be an app-mail bug as I am not sure which does the initial settings. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2019-01-11 13:02 | NickH | New Issue | |||
| 2019-01-11 13:04 | NickH | Description Updated | bug_revision_view_page.php?rev_id=2501#r2501 | ||
| 2019-02-23 12:29 | dloper | Note Added: 0009121 | |||
| 2019-02-23 12:29 | dloper | Status | new => closed | ||
| 2019-02-23 12:29 | dloper | Assigned To | => dloper | ||
| 2019-02-23 12:29 | dloper | Resolution | open => suspended | ||
| Notes | |||||
|
|
|||||
|
|
||||