Feedbackloop - Revision history

Sebastian at 14:05, 7 October 2024

2024-10-07T14:05:11Z

← Older revision		Revision as of 16:05, 7 October 2024
Line 1:		Line 1:
	[[Category:Deliverability]]		[[Category:Deliverability]]
	[[Category:Reputation]]		[[Category:Reputation]]
			[[Category:Reporting]]
	[[Category:Abuse]]		[[Category:Abuse]]
	'''Complaint Feedback Loops''' are feedback in form of [[ARF]] reports, usually sent by E-Mail to a previously registered address. Feedbackloops are sent by [[ISP]]'s to senders when mail from the sender in question has been marked as [[wikipedia:Email_spam\|SPAM]]. Some feedbackloops are registered by IP, meaning a complaint report is sent when a mail from a certain IP is marked SPAM, and others by domain, meaning a complaint report is sent when a mail from a certain domain is marked SPAM.		'''Complaint Feedback Loops''' are feedback in form of [[ARF]] reports, usually sent by E-Mail to a previously registered address. Feedbackloops are sent by [[ISP]]'s to senders when mail from the sender in question has been marked as [[wikipedia:Email_spam\|SPAM]]. Some feedbackloops are registered by IP, meaning a complaint report is sent when a mail from a certain IP is marked SPAM, and others by domain, meaning a complaint report is sent when a mail from a certain domain is marked SPAM.

Sebastian at 13:31, 10 April 2024

2024-04-10T13:31:16Z

← Older revision		Revision as of 15:31, 10 April 2024
Line 42:		Line 42:
	! Name !! Registration Link !! IP/Domain based !! Note		! Name !! Registration Link !! IP/Domain based !! Note
	\|-		\|-
	\| Abusix \|\| Add a [[#Standardisation\|CFBL header]] to outgoing E-Mail \|\| IP \|\| https://abusix.com/feedback-~~loops~~/ - XARF reports. Will be available soon.		\| Abusix \|\| Add a [[#Standardisation\|CFBL header]] to outgoing E-Mail \|\| IP \|\| [https://docs.abusix.com/global-reporting/ecp6Z7oJuQoCLnUYN4oK1w/getting-started-with-the-abusix-global-feedback-loop-reporting-service/oMzMjR3EPPAHxUoChDtTSK#global-reporting XARF reports]. Will be available soon.
	\|-		\|-
	\| SpamCop \|\| https://www.spamcop.net/anonsignup.shtml \|\| IP \|\| IPs from Mail reported to SpamCop are added to the SpamCop blacklist		\| SpamCop \|\| https://www.spamcop.net/anonsignup.shtml \|\| IP \|\| IPs from Mail reported to SpamCop are added to the SpamCop blacklist

Sebastian at 13:06, 30 September 2023

2023-09-30T13:06:19Z

← Older revision		Revision as of 15:06, 30 September 2023
Line 79:		Line 79:
	=Standardisation=		=Standardisation=

	In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://www.rfc-editor.org/rfc/rfc9477.html Complaint Feedback Loop Address Headers] was started. In September 2023, RFC 9477 was accepted in "experimental" status. ~~Acceptance~~ of this ~~proposed~~ standard would obsolete all paid or otherwise complicated feedbackloops, providing a standardised, open and free subscription mechanism.		In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://www.rfc-editor.org/rfc/rfc9477.html Complaint Feedback Loop Address Headers] was started. In September 2023, RFC 9477 was accepted in "experimental" status. Implementation of this new standard would obsolete all paid or otherwise complicated feedbackloops, providing a standardised, open and free subscription mechanism.

	=Useful links=		=Useful links=

Sebastian at 13:05, 30 September 2023

2023-09-30T13:05:30Z

← Older revision		Revision as of 15:05, 30 September 2023
Line 79:		Line 79:
	=Standardisation=		=Standardisation=

	In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://~~datatracker~~.~~ietf~~.org/~~doc~~/html~~/draft-benecke-cfbl-address-header~~ Complaint Feedback Loop Address Headers] was started. Acceptance of this proposed standard would obsolete all paid or otherwise complicated feedbackloops, providing a standardised, open and free subscription mechanism.		In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://www.rfc-editor.org/rfc/rfc9477.html Complaint Feedback Loop Address Headers] was started. In September 2023, RFC 9477 was accepted in "experimental" status. Acceptance of this proposed standard would obsolete all paid or otherwise complicated feedbackloops, providing a standardised, open and free subscription mechanism.

	=Useful links=		=Useful links=

	* [[wikipedia:Feedback_loop_(email)]]		* [[wikipedia:Feedback_loop_(email)]]
	* https://~~datatracker~~.~~ietf~~.org/~~doc~~/html~~/draft-benecke-cfbl-address-header~~		* [https://www.rfc-editor.org/rfc/rfc9477.html RFC 9477]
	* https://abusix.com/feedback-loops/		* https://abusix.com/feedback-loops/

Sebastian at 19:05, 21 September 2023

2023-09-21T19:05:24Z

← Older revision		Revision as of 21:05, 21 September 2023
Line 85:		Line 85:
	* [[wikipedia:Feedback_loop_(email)]]		* [[wikipedia:Feedback_loop_(email)]]
	* https://datatracker.ietf.org/doc/html/draft-benecke-cfbl-address-header		* https://datatracker.ietf.org/doc/html/draft-benecke-cfbl-address-header
			* https://abusix.com/feedback-loops/

Sebastian at 18:54, 21 September 2023

2023-09-21T18:54:56Z

← Older revision		Revision as of 20:54, 21 September 2023
Line 10:		Line 10:

	=List of free and independent feedbackloops=		=List of free and independent feedbackloops=

			==Directly from the ISP==

			The following list of Feedbackloops is facilitated directly by the ISP receiving the SPAM complaint. If, for example, the earthlink FBL is registered, only Earthlink ARF Reports will be received.

	{\| class="wikitable" style="margin:auto"		{\| class="wikitable" style="margin:auto"
	\|+ Complaint Feedback Loops		\|+ ISP Complaint Feedback Loops
	\|-		\|-
	! Name !! Registration Link !! IP/Domain based !! Note		! Name !! Registration Link !! IP/Domain based !! Note
Line 26:		Line 30:
	\| Microsoft \|\| https://postmaster.live.com/snds/JMRP.aspx \|\| IP \|\| E-Mail reports are not in ARF.		\| Microsoft \|\| https://postmaster.live.com/snds/JMRP.aspx \|\| IP \|\| E-Mail reports are not in ARF.
	\|-		\|-
	\| ~~SpamCop~~ \|\| https://~~www~~.~~spamcop~~.~~net~~/~~anonsignup.shtml~~ \|\| IP \|\| ~~Not directly provided~~ by ~~an ISP~~		\| Yahoo \|\| https://senders.yahooinc.com/contact \|\| Domain \|\|
			\|}

			==Provider independent==

			Provider independent FBLs are facilitated by independent third parties.

			{\| class="wikitable" style="margin:auto"
			\|+ PI Complaint Feedback Loops
			\|-
			! Name !! Registration Link !! IP/Domain based !! Note
	\|-		\|-
	\| ~~Yahoo~~ \|\| https://~~senders~~.~~yahooinc~~.~~com~~/~~contact~~ \|\| ~~Domain~~ \|\|		\| Abusix \|\| Add a [[#Standardisation\|CFBL header]] to outgoing E-Mail \|\| IP \|\| https://abusix.com/feedback-loops/ - XARF reports. Will be available soon.
			\|-
			\| SpamCop \|\| https://www.spamcop.net/anonsignup.shtml \|\| IP \|\| IPs from Mail reported to SpamCop are added to the SpamCop blacklist
	\|}		\|}

Sebastian at 20:12, 11 September 2023

2023-09-11T20:12:27Z

← Older revision		Revision as of 22:12, 11 September 2023
Line 12:		Line 12:

	{\| class="wikitable" style="margin:auto"		{\| class="wikitable" style="margin:auto"
	\|+ ~~Caption text~~		\|+ Complaint Feedback Loops
	\|-		\|-
	! Name !! Registration Link !! IP/Domain based !! Note		! Name !! Registration Link !! IP/Domain based !! Note

Sebastian at 20:06, 11 September 2023

2023-09-11T20:06:50Z

← Older revision		Revision as of 22:06, 11 September 2023
Line 63:		Line 63:
	=Standardisation=		=Standardisation=

	In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://datatracker.ietf.org/doc/html/draft-benecke-cfbl-address-header Complaint Feedback Loop Address Headers] was started. Acceptance of this proposed standard would obsolete all paid feedbackloops, providing a standardised, open and free subscription mechanism.		In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://datatracker.ietf.org/doc/html/draft-benecke-cfbl-address-header Complaint Feedback Loop Address Headers] was started. Acceptance of this proposed standard would obsolete all paid or otherwise complicated feedbackloops, providing a standardised, open and free subscription mechanism.

	=Useful links=		=Useful links=

Sebastian at 20:06, 11 September 2023

2023-09-11T20:06:12Z

← Older revision		Revision as of 22:06, 11 September 2023
Line 63:		Line 63:
	=Standardisation=		=Standardisation=

	In May 2023, work on standardisation of Complaint Feedback ~~Loop~~ via [https://datatracker.ietf.org/doc/html/draft-benecke-cfbl-address-header Complaint Feedback Loop Address Headers] was started. Acceptance of this proposed standard would obsolete all paid feedbackloops, providing a standardised, open and free subscription mechanism.		In May 2023, work on standardisation of registration to Complaint Feedback Loops via [https://datatracker.ietf.org/doc/html/draft-benecke-cfbl-address-header Complaint Feedback Loop Address Headers] was started. Acceptance of this proposed standard would obsolete all paid feedbackloops, providing a standardised, open and free subscription mechanism.

	=Useful links=		=Useful links=

Sebastian at 20:05, 11 September 2023

2023-09-11T20:05:28Z

← Older revision		Revision as of 22:05, 11 September 2023
Line 33:		Line 33:
	=Paid Feedbackloop subscriptions=		=Paid Feedbackloop subscriptions=

	In addition to the above list, it's possible to register for a list of collective Feedbackloops from various small ISPs via Validity's Feedbackloop Service (fbl.validity.com). ~~Since~~ September 2023, receiving ARF reports via E-mail via this service costs $1.500 per year. The service covers the following ~~IPs~~:		In addition to the above list, it's possible to register for a list of collective Feedbackloops from various small ISPs via Validity's Feedbackloop Service (fbl.validity.com). It used to be a free service, but since September 2023, receiving ARF reports via E-mail via this service costs $1.500 per year. The service covers the following ISPs:

	* Bluetie		* Bluetie