Still no luck with an increased fuzz (you can get the current file
directly from the svn browser):
Code:
v2:/usr/local/src/ispcp# patch -F4 -p0 < ../mxpatch.txt
patching file engine/ispcp-dmn-mngr
Hunk #1 FAILED at 2079.
Hunk #2 succeeded at 2088 with fuzz 3 (offset -21 lines).
Hunk #3 FAILED at 2111.
Hunk #4 succeeded at 2181 with fuzz 3 (offset -21 lines).
Hunk #5 succeeded at 2218 with fuzz 3 (offset -21 lines).
Hunk #6 succeeded at 3637 with fuzz 2 (offset -24 lines).
2 out of 6 hunks FAILED -- saving rejects to file engine/ispcp-dmn-mngr.rej
patching file gui/include/database-update-functions.php
patching file gui/include/ispcp-functions.php
patching file gui/reseller/edit_domain.php
patching file gui/themes/omega_original/reseller/edit_domain.tpl
I've (a pair of) customers that use backup inet providers so when their main connection goes down mail should be served through another IP. Using an MX relay this is easy as cake
ispcomm Wrote:I prefer to add reject_unverified_recipients by hand. It would be nice to be able to do it on a per-domain basis (is this possible in postfix)?
This is untested so it may not work, but you'll get the idea:
main.cf:
Code:
...
smtpd_recipient_restrictions = reject_non_fqdn_recipient,
reject_unknown_recipient_domain,
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
+ check_recipient_access hash:/etc/postfix/ispcp/relayed_domains
reject_unlisted_recipient,
check_policy_service inet:127.0.0.1:12525,
check_policy_service inet:127.0.0.1:60000,
permit
+ smtpd_restriction_classes = verify_relayed
+ verify_relayed = reject_unverified_recipients,
+ check_policy_service inet:127.0.0.1:12525,
+ check_policy_service inet:127.0.0.1:60000,
+ permit
...
/etc/postfix/ispcp/relayed_domains:
Code:
relayed-domain1.tld verify_relayed
relayed-domain2.tld verify_relayed
....
Hope this helps, keep up the good work ispcomm! Thanks again!