3 ms·

> Botnets appeared as a way to get around RBLs, and in response spam fighters mapped out the internet to create a "policy block list" - ranges of IPs that were

> Botnets appeared as a way to get around RBLs, and in response spam fighters mapped out the internet to create a "policy block list" - ranges of IPs that were assigned to residential connections and thus should not be sending any email at all. While I understand that _some_ residential ISPs don't let you run services on your connection, policies like this make me sad because it means the web is becoming more-and-more something you need other people to do for you.

pmlnr 10y ago
smtpd_helo_restrictions = permit_mynetworks, reject_invalid_helo_hostname, permit smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_non_fqdn_recipient, reject_unknown_recipient_domain, reject_unauth_pipelining, reject_unauth_destination, check_policy_service unix:private/policy-spf, check_client_access pcre:${config_directory}/dspam_filter_access, permit This is in my postfix config. The invalid hostname and non_fqdn tests are working quite well against residential hosts: they don't have valid reverse DNS or an fqdn, and so they get eliminated fast.
- jimktrains2 10y ago
  How's this address my point that we're moving forward to a web that needs to be done for most people, not by?
hlandau 10y ago
As far as I am concerned the PBL is a tool to facilitate net neutrality violations, not by ISPs, but by e. mail service providers.* Another effort by anti-spam people to encourage network neutrality violations is the SUBMISSION port, port 587 as opposed to port 25, for the authenticated submission of mail by MUAs. As far as I can tell, the only possible utility of this split is to make it more politically feasible for ISPs to block port 25 out, i.e. to facilitate network neutrality violations. As such I do not view the SUBMISSION port RFC well. (*Some people argue that PBL networks have no business sending mail because they have dynamic IPs. This is false; there are PBL-listed networks which assign static IPs, and it is at any rate a moot point. No specification requires that MTAs for domain outgoing mail and MXs (that is, MTAs for incoming mail) be one and the same, and there is only a technical need for the latter to have fixed IPs.) See also my site https://violations.devever.net/w/Violation_Type:Rejects_Valid_E._mail https://violations.devever.net/w/Violation_Type:Rejects_Vali...

pmlnr 10y ago

smtpd_helo_restrictions = permit_mynetworks, reject_invalid_helo_hostname, permit smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_hostname, reject_non_fqdn_recipient, reject_unknown_recipient_domain, reject_unauth_pipelining, reject_unauth_destination, check_policy_service unix:private/policy-spf, check_client_access pcre:${config_directory}/dspam_filter_access, permit This is in my postfix config. The invalid hostname and non_fqdn tests are working quite well against residential hosts: they don't have valid reverse DNS or an fqdn, and so they get eliminated fast.

jimktrains2 10y ago
How's this address my point that we're moving forward to a web that needs to be done for most people, not by?

hlandau 10y ago

As far as I am concerned the PBL is a tool to facilitate net neutrality violations, not by ISPs, but by e. mail service providers.* Another effort by anti-spam people to encourage network neutrality violations is the SUBMISSION port, port 587 as opposed to port 25, for the authenticated submission of mail by MUAs. As far as I can tell, the only possible utility of this split is to make it more politically feasible for ISPs to block port 25 out, i.e. to facilitate network neutrality violations. As such I do not view the SUBMISSION port RFC well. (*Some people argue that PBL networks have no business sending mail because they have dynamic IPs. This is false; there are PBL-listed networks which assign static IPs, and it is at any rate a moot point. No specification requires that MTAs for domain outgoing mail and MXs (that is, MTAs for incoming mail) be one and the same, and there is only a technical need for the latter to have fixed IPs.) See also my site https://violations.devever.net/w/Violation_Type:Rejects_Valid_E._mail https://violations.devever.net/w/Violation_Type:Rejects_Vali...