20:
239:
103:), and they can analyze the complaint rate and hence how their advertising meets market expectations. By unsubscribing users who complain, marketers reduce their overall complaint rate per IP or domain, ensuring that targeted mail is much more likely to reach subscribers who actually want to receive it.
143:
As sketched above, the process implies that
Spencer, besides being the author (or sender) of the message, is connected to the postmaster responsible for his mail domain. Subscribing to an FBL usually involves the postmaster's authorization. An FBL subscriber may or may not forward abuse reports to
303:
The majority of ESP offering
Feedback Loop do not include in the report the email address of the recipient, who marked the message. This makes it impossible to remove the recipient from the mailing list, where it has subscribed. Such ESPs' practice encourages mailing-lists providers to send
91:. Whether and how to provide an FBL is a choice of the MP. End users should report abuse at their mailbox provider's reporting hub, so as to also help filtering. As an alternative, competent users may send abuse complaints directly, acting as mailbox providers themselves.
299:
Some FBLs provide no option for communicating feedback automatically to multiple parties: the sender, the ESP (if one is involved), or the upstream datacenter/network address provider—as currently construed by the
Federal Trade Commission's (FTC) "Follow the Money"
144:
the relevant authors. If no subscribers exist for a given mail domain, Isaac can omit sending an abuse report at all. In fact, subscriptions have to be done one by one, a laborious task that mail domains not engaged in mass mailing may want to skip.
291:
The feedback loops fail to meet the generic anti-spam criterion of not generating more email messages. Even if the amount of feedback is just a fraction of the number of messages that an ESP sends out, most ESPs are not yet organized for handling
31:
are the two formal endpoints of the feedback loop (blue arrow). Senders need to subscribe, possibly using a web form similar to the one depicted on the upper left corner, in order to become feedback consumers. Recipients typically click a
295:
Using the same button for both abuse reports and list unsubscribe implies guesswork by the (automated) help desk. For example, it does not ease reporting to a list owner that a specific post in the (non moderated) list is actually
304:
individualized message to each recipient (contrary to sending everybody literally the same message), so that mailing list providers can extract from the individualized message coming over the feedback loop the original recipient.
109:, when playing the sender's role, are very sensitive to how sending mail on behalf of their customers may affect their reputation. Monitoring the complaint rate is one of the ways they can control what their users are sending.
452:
187:, whose design is inherited by ARF, an abuse report consists of a human readable part, followed by a machine readable part, and the original message. The report is characterized by a
459:
221:
Google's Gmail is beta testing a non-traditional FBL with select ESPs. Gmail uses their own format—an aggregate report that reveals spam rate per notable sender.
225:
reports that the Gmail FBL, developed and launched by Julian
Tempelsman and Sri Somanchi, is effective at identifying spam that other anti-spam systems miss.
165:
For years, end users have been told not to trust email unsubscribe links, so many users hit the spam button as an alternative to unsubscribing. Consequently,
247:
99:
Marketers striving for their mail to be delivered have a twofold advantage: they can remove subscribers that don't want to receive that kind of advertising (
169:
may act as unsubscribe in some cases. One of the reasons not to hit unsubscribe links is to avoid confirming that the message had been received and opened.
162:
noted that a majority of respondents to a survey on spam reporting marked messages as spam based solely on the subject and sender data.
60:(MP) forwards the complaints originating from their users to the sender's organizations. MPs can receive users' complaints by placing
252:
1096:
1136:
208:
1111:
924:
106:
627:
1302:
152:
addresses the latter shortcoming by proposing auto-subscribe just-in-time FBLs, which can be started by sending an
527:
345:
416:
438:
1091:
973:
825:
792:
759:
726:
696:
606:
523:
Creation and Use of Email
Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)
496:
854:
1131:
556:
Feedback
Providers MUST provide a way for report recipients to request that no further reports be sent.
263:
887:
1106:
1003:
968:
819:
786:
753:
720:
600:
490:
395:
387:
941:
917:
847:
814:
781:
748:
715:
595:
485:
314:
179:
129:
84:, has to come to an agreement with each MP from which they want to collect users' complaints.
569:
1146:
1116:
1083:
631:
541:
359:
8:
1121:
963:
259:
1297:
1287:
1101:
1044:
910:
432:
902:
1242:
1189:
531:
517:
349:
145:
81:
57:
1254:
1224:
958:
897:
682:
544:
521:
362:
339:
149:
139:
part, and sends it to
Spencer if Spencer has signed up to receive that feedback.
121:
Alice complains to Isaac (her ISP or MP) about the message, e.g. by hitting the
1292:
1264:
1234:
1184:
1126:
1049:
1039:
983:
383:
319:
184:
88:
1281:
1199:
1164:
1064:
998:
1247:
1204:
1174:
1024:
635:
77:
69:
657:
417:"What are feedback loops (fbl's) and how can they help my deliverability?"
1209:
1019:
591:
100:
258:
Please help rewrite or integrate negative information to other sections
19:
1179:
1156:
1029:
988:
950:
882:
419:. Email Manual. 2009-07-15. Archived from the original on 6 March 2012
1214:
1194:
1069:
661:
536:
354:
73:
1259:
1169:
1054:
1034:
933:
700:
222:
53:
23:
A sender and a recipient connected by a mailbox provider (MP). The
1141:
1059:
993:
683:"Best Practices for Senders: A Gmail Perspective (slides 47, 48)"
65:
877:
697:"Gmail's Spam Feedback Loop: SendGrid's First-hand Experience"
156:
with further directives (at a minimum, a way to unsubscribe).
1219:
978:
159:
136:
132:
892:
183:(ARF) is the standard format for FBL reports. Much like
932:
846:
Deborah Platt
Majoras; et al. (September 2004).
845:
135:
part, or (less commonly) a standalone message/rfc822
341:
Complaint
Feedback Loop Operational Recommendations
288:
button is said by some to often be used improperly.
883:Messaging Anti-Abuse Working Group - list of FBL´s
453:"Your Reputation Holds the Key to Deliverability"
1279:
516:
16:Process of forwarding user complaints to senders
36:button on a web mail page to start the process.
382:
918:
713:
567:
888:Feedback loop links for some email providers
561:
128:Isaac encapsulates the message as either an
812:
779:
746:
590:
925:
911:
535:
483:
353:
337:
458:. ReturnPath. 2008-08-18. Archived from
18:
191:field whose values may indicate one of
87:Feedback loops are one of the ways for
1280:
893:Abuse Feedback Reporting Format (ARF)
906:
52:, is an inter-organizational form of
848:"A CAN-SPAM Informant Reward System"
248:"criticism" or "controversy" section
232:
172:
112:
13:
1112:Distributed Checksum Clearinghouse
218:(JMR), also use their own format.
14:
1314:
1097:Challenge–response spam filtering
934:Unsolicited digital communication
871:
118:Spencer sends a message to Alice.
338:J.D. Falk, ed. (November 2011).
237:
898:Importance of Customer Feedback
878:Universal Feedback Loop Service
839:
806:
773:
740:
707:
689:
675:
658:"Services for Senders and ISPs"
650:
620:
584:
570:"Getting in the Feedback Loop"
510:
477:
445:
409:
388:"Adding a spam button to MUAs"
376:
331:
207:(more types are registered at
1:
325:
251:may compromise the article's
714:Rich Kulawiec (2008-11-13).
634:. 2007-01-19. Archived from
568:Derek Harding (2006-09-07).
228:
214:Microsoft, who use the name
94:
7:
855:US Federal Trade Commission
628:"Spam Unsubscribe Services"
308:
10:
1319:
1132:Naive Bayes spam filtering
813:Barry Shein (2008-11-13).
780:Barry Shein (2008-11-13).
747:Chris Lewis (2008-11-12).
1233:
1155:
1082:
1012:
949:
940:
437:: CS1 maint: unfit URL (
1303:Complaints organizations
1107:Disposable email address
969:Directory harvest attack
484:J.D. Falk (2008-11-11).
154:unsolicited abuse report
76:. The message sender's
50:complaint feedback loop
315:Abuse Reporting Format
180:Abuse Reporting Format
130:Abuse Reporting Format
82:email service provider
48:), sometimes called a
37:
22:
1117:Email authentication
685:. MAAWG. 2014-02-20.
632:The Spamhaus Project
964:Bulk email software
520:, ed. (June 2012).
386:(9 December 2009).
216:Junk Mail Reporting
68:pages, or in their
260:through discussion
38:
1275:
1274:
1102:Context filtering
1078:
1077:
281:
280:
173:Reporting formats
113:Reporting process
64:buttons on their
29:feedback consumer
25:feedback provider
1310:
1243:Advance-fee scam
1190:Keyword stuffing
947:
946:
927:
920:
913:
904:
903:
866:
865:
863:
861:
852:
843:
837:
836:
834:
832:
824:(Mailing list).
815:"FeedBack loops"
810:
804:
803:
801:
799:
791:(Mailing list).
782:"FeedBack loops"
777:
771:
770:
768:
766:
758:(Mailing list).
749:"FeedBack loops"
744:
738:
737:
735:
733:
725:(Mailing list).
716:"FeedBack loops"
711:
705:
704:
693:
687:
686:
679:
673:
672:
670:
668:
654:
648:
647:
645:
643:
624:
618:
617:
615:
613:
605:(Mailing list).
596:"FeedBack loops"
588:
582:
581:
579:
577:
565:
559:
558:
553:
551:
539:
537:10.17487/RFC6650
518:Murray Kucherawy
514:
508:
507:
505:
503:
495:(Mailing list).
486:"FeedBack loops"
481:
475:
474:
472:
470:
464:
457:
449:
443:
442:
436:
428:
426:
424:
413:
407:
406:
404:
402:
380:
374:
373:
371:
369:
357:
355:10.17487/RFC6449
335:
276:
273:
267:
241:
240:
233:
58:mailbox provider
1318:
1317:
1313:
1312:
1311:
1309:
1308:
1307:
1278:
1277:
1276:
1271:
1255:Make Money Fast
1229:
1225:URL redirection
1151:
1074:
1008:
959:Address munging
936:
931:
874:
869:
859:
857:
850:
844:
840:
830:
828:
811:
807:
797:
795:
778:
774:
764:
762:
745:
741:
731:
729:
712:
708:
695:
694:
690:
681:
680:
676:
666:
664:
656:
655:
651:
641:
639:
626:
625:
621:
611:
609:
589:
585:
575:
573:
566:
562:
549:
547:
515:
511:
501:
499:
482:
478:
468:
466:
462:
455:
451:
450:
446:
430:
429:
422:
420:
415:
414:
410:
400:
398:
381:
377:
367:
365:
336:
332:
328:
311:
277:
271:
268:
257:
246:This article's
242:
238:
231:
185:bounce messages
175:
115:
97:
17:
12:
11:
5:
1316:
1306:
1305:
1300:
1295:
1290:
1273:
1272:
1270:
1269:
1268:
1267:
1257:
1252:
1251:
1250:
1239:
1237:
1235:Internet fraud
1231:
1230:
1228:
1227:
1222:
1217:
1212:
1207:
1202:
1197:
1192:
1187:
1185:Google bombing
1182:
1177:
1172:
1167:
1161:
1159:
1153:
1152:
1150:
1149:
1144:
1139:
1134:
1129:
1127:List poisoning
1124:
1119:
1114:
1109:
1104:
1099:
1094:
1088:
1086:
1080:
1079:
1076:
1075:
1073:
1072:
1067:
1062:
1057:
1052:
1047:
1042:
1037:
1032:
1027:
1022:
1016:
1014:
1010:
1009:
1007:
1006:
1001:
996:
991:
986:
984:Email spoofing
981:
976:
971:
966:
961:
955:
953:
944:
938:
937:
930:
929:
922:
915:
907:
901:
900:
895:
890:
885:
880:
873:
872:External links
870:
868:
867:
838:
805:
772:
739:
706:
688:
674:
649:
619:
594:(2008-11-13).
583:
560:
509:
476:
465:on 11 May 2013
444:
408:
384:John R. Levine
375:
329:
327:
324:
323:
322:
320:Spam reporting
317:
310:
307:
306:
305:
301:
297:
293:
289:
279:
278:
245:
243:
236:
230:
227:
174:
171:
141:
140:
126:
119:
114:
111:
96:
93:
89:reporting spam
15:
9:
6:
4:
3:
2:
1315:
1304:
1301:
1299:
1296:
1294:
1291:
1289:
1286:
1285:
1283:
1266:
1263:
1262:
1261:
1258:
1256:
1253:
1249:
1246:
1245:
1244:
1241:
1240:
1238:
1236:
1232:
1226:
1223:
1221:
1218:
1216:
1213:
1211:
1208:
1206:
1203:
1201:
1200:Referrer spam
1198:
1196:
1193:
1191:
1188:
1186:
1183:
1181:
1178:
1176:
1173:
1171:
1168:
1166:
1163:
1162:
1160:
1158:
1154:
1148:
1145:
1143:
1140:
1138:
1135:
1133:
1130:
1128:
1125:
1123:
1120:
1118:
1115:
1113:
1110:
1108:
1105:
1103:
1100:
1098:
1095:
1093:
1090:
1089:
1087:
1085:
1081:
1071:
1068:
1066:
1065:Telemarketing
1063:
1061:
1058:
1056:
1053:
1051:
1048:
1046:
1043:
1041:
1038:
1036:
1033:
1031:
1028:
1026:
1023:
1021:
1018:
1017:
1015:
1011:
1005:
1002:
1000:
999:Pink contract
997:
995:
992:
990:
987:
985:
982:
980:
977:
975:
972:
970:
967:
965:
962:
960:
957:
956:
954:
952:
948:
945:
943:
939:
935:
928:
923:
921:
916:
914:
909:
908:
905:
899:
896:
894:
891:
889:
886:
884:
881:
879:
876:
875:
856:
849:
842:
827:
823:
821:
816:
809:
794:
790:
788:
783:
776:
761:
757:
755:
750:
743:
728:
724:
722:
717:
710:
703:. 2014-03-28.
702:
698:
692:
684:
678:
663:
659:
653:
638:on 2009-03-09
637:
633:
629:
623:
608:
604:
602:
597:
593:
587:
571:
564:
557:
546:
543:
538:
533:
529:
525:
524:
519:
513:
498:
494:
492:
487:
480:
461:
454:
448:
440:
434:
418:
412:
397:
393:
389:
385:
379:
364:
361:
356:
351:
347:
343:
342:
334:
330:
321:
318:
316:
313:
312:
302:
298:
294:
290:
287:
283:
282:
275:
265:
261:
255:
254:
249:
244:
235:
234:
226:
224:
219:
217:
212:
210:
206:
202:
198:
194:
190:
189:Feedback-Type
186:
182:
181:
170:
168:
163:
161:
157:
155:
151:
147:
138:
134:
131:
127:
124:
120:
117:
116:
110:
108:
104:
102:
92:
90:
85:
83:
79:
75:
71:
67:
63:
59:
55:
51:
47:
43:
42:feedback loop
35:
30:
26:
21:
1248:Lottery scam
1205:Scraper site
1175:Doorway page
1045:Mobile phone
1025:Cold calling
858:. Retrieved
841:
829:. Retrieved
822:mailing list
818:
808:
796:. Retrieved
789:mailing list
785:
775:
763:. Retrieved
756:mailing list
752:
742:
730:. Retrieved
723:mailing list
719:
709:
691:
677:
665:. Retrieved
652:
640:. Retrieved
636:the original
622:
610:. Retrieved
603:mailing list
599:
586:
574:. Retrieved
563:
555:
548:. Retrieved
522:
512:
500:. Retrieved
493:mailing list
489:
479:
467:. Retrieved
460:the original
447:
421:. Retrieved
411:
399:. Retrieved
391:
378:
366:. Retrieved
340:
333:
285:
269:
250:
220:
215:
213:
204:
200:
196:
192:
188:
178:
176:
166:
164:
158:
153:
142:
122:
105:
98:
86:
78:organization
70:email client
61:
49:
45:
41:
39:
33:
28:
24:
1210:Social spam
1122:Greylisting
1092:Client-side
1020:Auto dialer
831:18 November
798:18 November
765:18 November
732:16 November
667:11 November
642:16 November
612:18 November
592:John Levine
576:16 November
502:18 November
469:16 November
368:30 November
286:report spam
167:report spam
123:report spam
101:listwashing
80:, often an
62:report spam
56:by which a
1282:Categories
1215:Spam blogs
1180:Forum spam
1157:Spamdexing
1030:Flyposting
989:Image spam
951:Email spam
860:8 November
326:References
253:neutrality
74:help desks
1298:Anti-spam
1195:Link farm
1165:Blog spam
1084:Anti-spam
1050:Newsgroup
1040:Messaging
942:Protocols
662:Microsoft
300:strategy.
264:talk page
229:Criticism
95:Rationale
72:, or via
1288:Spamming
1260:Phishing
1170:Cloaking
1147:Spamhaus
1055:Robocall
1035:Junk fax
701:SendGrid
433:cite web
401:22 April
309:See also
272:May 2014
223:SendGrid
54:feedback
27:and the
1142:SpamCop
1060:Spambot
1004:Spambot
994:Joe job
572:. ClikZ
550:28 June
423:15 July
262:on the
125:button.
66:webmail
148:
1293:Email
1265:Voice
1220:Sping
1137:SORBS
1013:Other
979:DNSWL
974:DNSBL
851:(PDF)
463:(PDF)
456:(PDF)
296:spam.
205:other
203:, or
201:virus
197:fraud
193:abuse
160:Ipsos
1070:VoIP
862:2011
833:2008
826:IRTF
820:ASRG
800:2008
793:IRTF
787:ASRG
767:2008
760:IRTF
754:ASRG
734:2008
727:IRTF
721:ASRG
669:2011
644:2008
614:2008
607:IRTF
601:ASRG
578:2008
552:2012
545:6650
528:IETF
504:2008
497:IRTF
491:ASRG
471:2008
439:link
425:2009
403:2011
396:ASRG
392:mail
370:2011
363:6449
346:IETF
284:The
209:IANA
177:The
150:6650
137:MIME
133:MIME
107:ESPs
34:spam
542:RFC
532:doi
360:RFC
350:doi
292:it.
211:).
146:RFC
46:FBL
1284::
853:.
817:.
784:.
751:.
718:.
699:.
660:.
630:.
598:.
554:.
540:.
530:.
526:.
488:.
435:}}
431:{{
394:.
390:.
358:.
348:.
344:.
199:,
195:,
40:A
926:e
919:t
912:v
864:.
835:.
802:.
769:.
736:.
671:.
646:.
616:.
580:.
534::
506:.
473:.
441:)
427:.
405:.
372:.
352::
274:)
270:(
266:.
256:.
44:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
.png)