Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application

Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices...
Ausführliche Beschreibung

Gespeichert in:

Autor*in:	Lucky Kannan [verfasserIn] Jebakumar R [verfasserIn]

Format:	E-Artikel
Sprache:	Englisch

Erschienen:	2020

Schlagwörter:	email spam detection sender score reputation system blockchain mobile application marketing email

Übergeordnetes Werk:	In: International Journal of Interactive Mobile Technologies - International Association of Online Engineering (IAOE), 2018, 14(2020), 17, Seite 204-213
Übergeordnetes Werk:	volume:14 ; year:2020 ; number:17 ; pages:204-213

Links:	Link aufrufen Link aufrufen Link aufrufen Journal toc

DOI / URN:	10.3991/ijim.v14i17.16609

Katalog-ID:	DOAJ054791383

Internformat


LEADER	01000caa a22002652 4500
001	DOAJ054791383
003	DE-627
005	20230308184220.0
007	cr uuu---uuuuu
008	230227s2020 xx \|\|\|\|\|o 00\| \|\|eng c
024	7		\|a 10.3991/ijim.v14i17.16609 \|2 doi
035			\|a (DE-627)DOAJ054791383
035			\|a (DE-599)DOAJf464710399a749fb9fc7521b175152d4
040			\|a DE-627 \|b ger \|c DE-627 \|e rakwb
041			\|a eng
050		0	\|a TK5101-6720
100	0		\|a Lucky Kannan \|e verfasserin \|4 aut
245	1	0	\|a Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application
264		1	\|c 2020
336			\|a Text \|b txt \|2 rdacontent
337			\|a Computermedien \|b c \|2 rdamedia
338			\|a Online-Ressource \|b cr \|2 rdacarrier
520			\|a Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application.
650		4	\|a email
650		4	\|a spam detection
650		4	\|a sender score
650		4	\|a reputation system
650		4	\|a blockchain
650		4	\|a mobile application
650		4	\|a marketing email
653		0	\|a Telecommunication
700	0		\|a Jebakumar R \|e verfasserin \|4 aut
773	0	8	\|i In \|t International Journal of Interactive Mobile Technologies \|d International Association of Online Engineering (IAOE), 2018 \|g 14(2020), 17, Seite 204-213 \|w (DE-627)558042449 \|w (DE-600)2406982-6 \|x 18657923 \|7 nnns
773	1	8	\|g volume:14 \|g year:2020 \|g number:17 \|g pages:204-213
856	4	0	\|u https://doi.org/10.3991/ijim.v14i17.16609 \|z kostenfrei
856	4	0	\|u https://doaj.org/article/f464710399a749fb9fc7521b175152d4 \|z kostenfrei
856	4	0	\|u https://online-journals.org/index.php/i-jim/article/view/16609 \|z kostenfrei
856	4	2	\|u https://doaj.org/toc/1865-7923 \|y Journal toc \|z kostenfrei
912			\|a GBV_USEFLAG_A
912			\|a SYSFLAG_A
912			\|a GBV_DOAJ
912			\|a GBV_ILN_11
912			\|a GBV_ILN_20
912			\|a GBV_ILN_22
912			\|a GBV_ILN_23
912			\|a GBV_ILN_24
912			\|a GBV_ILN_39
912			\|a GBV_ILN_40
912			\|a GBV_ILN_60
912			\|a GBV_ILN_62
912			\|a GBV_ILN_63
912			\|a GBV_ILN_65
912			\|a GBV_ILN_69
912			\|a GBV_ILN_70
912			\|a GBV_ILN_73
912			\|a GBV_ILN_95
912			\|a GBV_ILN_105
912			\|a GBV_ILN_110
912			\|a GBV_ILN_151
912			\|a GBV_ILN_161
912			\|a GBV_ILN_170
912			\|a GBV_ILN_213
912			\|a GBV_ILN_230
912			\|a GBV_ILN_285
912			\|a GBV_ILN_293
912			\|a GBV_ILN_370
912			\|a GBV_ILN_602
912			\|a GBV_ILN_2014
912			\|a GBV_ILN_2044
912			\|a GBV_ILN_2055
912			\|a GBV_ILN_2086
912			\|a GBV_ILN_2108
912			\|a GBV_ILN_2119
912			\|a GBV_ILN_4012
912			\|a GBV_ILN_4037
912			\|a GBV_ILN_4112
912			\|a GBV_ILN_4125
912			\|a GBV_ILN_4126
912			\|a GBV_ILN_4249
912			\|a GBV_ILN_4305
912			\|a GBV_ILN_4306
912			\|a GBV_ILN_4307
912			\|a GBV_ILN_4313
912			\|a GBV_ILN_4322
912			\|a GBV_ILN_4323
912			\|a GBV_ILN_4324
912			\|a GBV_ILN_4325
912			\|a GBV_ILN_4326
912			\|a GBV_ILN_4338
912			\|a GBV_ILN_4367
912			\|a GBV_ILN_4700
951			\|a AR
952			\|d 14 \|j 2020 \|e 17 \|h 204-213

Indexfelder

author_variant	l k lk j r jr
matchkey_str	article:18657923:2020----::ulcedrcrssesbepfrmisamtgtowtsoeaa
hierarchy_sort_str	2020
callnumber-subject-code	TK
publishDate	2020
allfields	10.3991/ijim.v14i17.16609 doi (DE-627)DOAJ054791383 (DE-599)DOAJf464710399a749fb9fc7521b175152d4 DE-627 ger DE-627 rakwb eng TK5101-6720 Lucky Kannan verfasserin aut Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application 2020 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application. email spam detection sender score reputation system blockchain mobile application marketing email Telecommunication Jebakumar R verfasserin aut In International Journal of Interactive Mobile Technologies International Association of Online Engineering (IAOE), 2018 14(2020), 17, Seite 204-213 (DE-627)558042449 (DE-600)2406982-6 18657923 nnns volume:14 year:2020 number:17 pages:204-213 https://doi.org/10.3991/ijim.v14i17.16609 kostenfrei https://doaj.org/article/f464710399a749fb9fc7521b175152d4 kostenfrei https://online-journals.org/index.php/i-jim/article/view/16609 kostenfrei https://doaj.org/toc/1865-7923 Journal toc kostenfrei GBV_USEFLAG_A SYSFLAG_A GBV_DOAJ GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_2014 GBV_ILN_2044 GBV_ILN_2055 GBV_ILN_2086 GBV_ILN_2108 GBV_ILN_2119 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 AR 14 2020 17 204-213
spelling	10.3991/ijim.v14i17.16609 doi (DE-627)DOAJ054791383 (DE-599)DOAJf464710399a749fb9fc7521b175152d4 DE-627 ger DE-627 rakwb eng TK5101-6720 Lucky Kannan verfasserin aut Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application 2020 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application. email spam detection sender score reputation system blockchain mobile application marketing email Telecommunication Jebakumar R verfasserin aut In International Journal of Interactive Mobile Technologies International Association of Online Engineering (IAOE), 2018 14(2020), 17, Seite 204-213 (DE-627)558042449 (DE-600)2406982-6 18657923 nnns volume:14 year:2020 number:17 pages:204-213 https://doi.org/10.3991/ijim.v14i17.16609 kostenfrei https://doaj.org/article/f464710399a749fb9fc7521b175152d4 kostenfrei https://online-journals.org/index.php/i-jim/article/view/16609 kostenfrei https://doaj.org/toc/1865-7923 Journal toc kostenfrei GBV_USEFLAG_A SYSFLAG_A GBV_DOAJ GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_2014 GBV_ILN_2044 GBV_ILN_2055 GBV_ILN_2086 GBV_ILN_2108 GBV_ILN_2119 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 AR 14 2020 17 204-213
allfields_unstemmed	10.3991/ijim.v14i17.16609 doi (DE-627)DOAJ054791383 (DE-599)DOAJf464710399a749fb9fc7521b175152d4 DE-627 ger DE-627 rakwb eng TK5101-6720 Lucky Kannan verfasserin aut Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application 2020 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application. email spam detection sender score reputation system blockchain mobile application marketing email Telecommunication Jebakumar R verfasserin aut In International Journal of Interactive Mobile Technologies International Association of Online Engineering (IAOE), 2018 14(2020), 17, Seite 204-213 (DE-627)558042449 (DE-600)2406982-6 18657923 nnns volume:14 year:2020 number:17 pages:204-213 https://doi.org/10.3991/ijim.v14i17.16609 kostenfrei https://doaj.org/article/f464710399a749fb9fc7521b175152d4 kostenfrei https://online-journals.org/index.php/i-jim/article/view/16609 kostenfrei https://doaj.org/toc/1865-7923 Journal toc kostenfrei GBV_USEFLAG_A SYSFLAG_A GBV_DOAJ GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_2014 GBV_ILN_2044 GBV_ILN_2055 GBV_ILN_2086 GBV_ILN_2108 GBV_ILN_2119 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 AR 14 2020 17 204-213
allfieldsGer	10.3991/ijim.v14i17.16609 doi (DE-627)DOAJ054791383 (DE-599)DOAJf464710399a749fb9fc7521b175152d4 DE-627 ger DE-627 rakwb eng TK5101-6720 Lucky Kannan verfasserin aut Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application 2020 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application. email spam detection sender score reputation system blockchain mobile application marketing email Telecommunication Jebakumar R verfasserin aut In International Journal of Interactive Mobile Technologies International Association of Online Engineering (IAOE), 2018 14(2020), 17, Seite 204-213 (DE-627)558042449 (DE-600)2406982-6 18657923 nnns volume:14 year:2020 number:17 pages:204-213 https://doi.org/10.3991/ijim.v14i17.16609 kostenfrei https://doaj.org/article/f464710399a749fb9fc7521b175152d4 kostenfrei https://online-journals.org/index.php/i-jim/article/view/16609 kostenfrei https://doaj.org/toc/1865-7923 Journal toc kostenfrei GBV_USEFLAG_A SYSFLAG_A GBV_DOAJ GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_2014 GBV_ILN_2044 GBV_ILN_2055 GBV_ILN_2086 GBV_ILN_2108 GBV_ILN_2119 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 AR 14 2020 17 204-213
allfieldsSound	10.3991/ijim.v14i17.16609 doi (DE-627)DOAJ054791383 (DE-599)DOAJf464710399a749fb9fc7521b175152d4 DE-627 ger DE-627 rakwb eng TK5101-6720 Lucky Kannan verfasserin aut Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application 2020 Text txt rdacontent Computermedien c rdamedia Online-Ressource cr rdacarrier Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application. email spam detection sender score reputation system blockchain mobile application marketing email Telecommunication Jebakumar R verfasserin aut In International Journal of Interactive Mobile Technologies International Association of Online Engineering (IAOE), 2018 14(2020), 17, Seite 204-213 (DE-627)558042449 (DE-600)2406982-6 18657923 nnns volume:14 year:2020 number:17 pages:204-213 https://doi.org/10.3991/ijim.v14i17.16609 kostenfrei https://doaj.org/article/f464710399a749fb9fc7521b175152d4 kostenfrei https://online-journals.org/index.php/i-jim/article/view/16609 kostenfrei https://doaj.org/toc/1865-7923 Journal toc kostenfrei GBV_USEFLAG_A SYSFLAG_A GBV_DOAJ GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_2014 GBV_ILN_2044 GBV_ILN_2055 GBV_ILN_2086 GBV_ILN_2108 GBV_ILN_2119 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700 AR 14 2020 17 204-213
language	English
source	In International Journal of Interactive Mobile Technologies 14(2020), 17, Seite 204-213 volume:14 year:2020 number:17 pages:204-213
sourceStr	In International Journal of Interactive Mobile Technologies 14(2020), 17, Seite 204-213 volume:14 year:2020 number:17 pages:204-213
format_phy_str_mv	Article
institution	findex.gbv.de
topic_facet	email spam detection sender score reputation system blockchain mobile application marketing email Telecommunication
isfreeaccess_bool	true
container_title	International Journal of Interactive Mobile Technologies
authorswithroles_txt_mv	Lucky Kannan @@aut@@ Jebakumar R @@aut@@
publishDateDaySort_date	2020-01-01T00:00:00Z
hierarchy_top_id	558042449
id	DOAJ054791383
language_de	englisch
fullrecord	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">DOAJ054791383</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20230308184220.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">230227s2020 xx \|\|\|\|\|o 00\| \|\|eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.3991/ijim.v14i17.16609</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)DOAJ054791383</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)DOAJf464710399a749fb9fc7521b175152d4</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">TK5101-6720</subfield></datafield><datafield tag="100" ind1="0" ind2=" "><subfield code="a">Lucky Kannan</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2020</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">email</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">spam detection</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">sender score</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">reputation system</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">blockchain</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">mobile application</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">marketing email</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Telecommunication</subfield></datafield><datafield tag="700" ind1="0" ind2=" "><subfield code="a">Jebakumar R</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">In</subfield><subfield code="t">International Journal of Interactive Mobile Technologies</subfield><subfield code="d">International Association of Online Engineering (IAOE), 2018</subfield><subfield code="g">14(2020), 17, Seite 204-213</subfield><subfield code="w">(DE-627)558042449</subfield><subfield code="w">(DE-600)2406982-6</subfield><subfield code="x">18657923</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:14</subfield><subfield code="g">year:2020</subfield><subfield code="g">number:17</subfield><subfield code="g">pages:204-213</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://doi.org/10.3991/ijim.v14i17.16609</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://doaj.org/article/f464710399a749fb9fc7521b175152d4</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://online-journals.org/index.php/i-jim/article/view/16609</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="u">https://doaj.org/toc/1865-7923</subfield><subfield code="y">Journal toc</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_DOAJ</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_11</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_20</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_22</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_23</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_24</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_39</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_40</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_60</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_62</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_63</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_65</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_69</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_73</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_95</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_105</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_110</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_151</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_161</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_170</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_213</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_230</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_285</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_293</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_370</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_602</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2014</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2044</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2055</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2086</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2108</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2119</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4012</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4037</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4112</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4125</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4126</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4249</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4305</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4306</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4307</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4313</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4322</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4323</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4324</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4325</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4326</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4338</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4367</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4700</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">14</subfield><subfield code="j">2020</subfield><subfield code="e">17</subfield><subfield code="h">204-213</subfield></datafield></record></collection>
callnumber-first	T - Technology
author	Lucky Kannan
spellingShingle	Lucky Kannan misc TK5101-6720 misc email misc spam detection misc sender score misc reputation system misc blockchain misc mobile application misc marketing email misc Telecommunication Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application
authorStr	Lucky Kannan
ppnlink_with_tag_str_mv	@@773@@(DE-627)558042449
format	electronic Article
delete_txt_mv	keep
author_role	aut aut
collection	DOAJ
remote_str	true
callnumber-label	TK5101-6720
illustrated	Not Illustrated
issn	18657923
topic_title	TK5101-6720 Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application email spam detection sender score reputation system blockchain mobile application marketing email
topic	misc TK5101-6720 misc email misc spam detection misc sender score misc reputation system misc blockchain misc mobile application misc marketing email misc Telecommunication
topic_unstemmed	misc TK5101-6720 misc email misc spam detection misc sender score misc reputation system misc blockchain misc mobile application misc marketing email misc Telecommunication
topic_browse	misc TK5101-6720 misc email misc spam detection misc sender score misc reputation system misc blockchain misc mobile application misc marketing email misc Telecommunication
format_facet	Elektronische Aufsätze Aufsätze Elektronische Ressource
format_main_str_mv	Text Zeitschrift/Artikel
carriertype_str_mv	cr
hierarchy_parent_title	International Journal of Interactive Mobile Technologies
hierarchy_parent_id	558042449
hierarchy_top_title	International Journal of Interactive Mobile Technologies
isfreeaccess_txt	true
familylinks_str_mv	(DE-627)558042449 (DE-600)2406982-6
title	Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application
ctrlnum	(DE-627)DOAJ054791383 (DE-599)DOAJf464710399a749fb9fc7521b175152d4
title_full	Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application
author_sort	Lucky Kannan
journal	International Journal of Interactive Mobile Technologies
journalStr	International Journal of Interactive Mobile Technologies
callnumber-first-code	T
lang_code	eng
isOA_bool	true
recordtype	marc
publishDateSort	2020
contenttype_str_mv	txt
container_start_page	204
author_browse	Lucky Kannan Jebakumar R
container_volume	14
class	TK5101-6720
format_se	Elektronische Aufsätze
author-letter	Lucky Kannan
doi_str_mv	10.3991/ijim.v14i17.16609
author2-role	verfasserin
title_sort	public sender score system (s3) by esps for email spam mitigation with score management in mobile application
callnumber	TK5101-6720
title_auth	Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application
abstract	Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application.
abstractGer	Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application.
abstract_unstemmed	Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application.
collection_details	GBV_USEFLAG_A SYSFLAG_A GBV_DOAJ GBV_ILN_11 GBV_ILN_20 GBV_ILN_22 GBV_ILN_23 GBV_ILN_24 GBV_ILN_39 GBV_ILN_40 GBV_ILN_60 GBV_ILN_62 GBV_ILN_63 GBV_ILN_65 GBV_ILN_69 GBV_ILN_70 GBV_ILN_73 GBV_ILN_95 GBV_ILN_105 GBV_ILN_110 GBV_ILN_151 GBV_ILN_161 GBV_ILN_170 GBV_ILN_213 GBV_ILN_230 GBV_ILN_285 GBV_ILN_293 GBV_ILN_370 GBV_ILN_602 GBV_ILN_2014 GBV_ILN_2044 GBV_ILN_2055 GBV_ILN_2086 GBV_ILN_2108 GBV_ILN_2119 GBV_ILN_4012 GBV_ILN_4037 GBV_ILN_4112 GBV_ILN_4125 GBV_ILN_4126 GBV_ILN_4249 GBV_ILN_4305 GBV_ILN_4306 GBV_ILN_4307 GBV_ILN_4313 GBV_ILN_4322 GBV_ILN_4323 GBV_ILN_4324 GBV_ILN_4325 GBV_ILN_4326 GBV_ILN_4338 GBV_ILN_4367 GBV_ILN_4700
container_issue	17
title_short	Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application
url	https://doi.org/10.3991/ijim.v14i17.16609 https://doaj.org/article/f464710399a749fb9fc7521b175152d4 https://online-journals.org/index.php/i-jim/article/view/16609 https://doaj.org/toc/1865-7923
remote_bool	true
author2	Jebakumar R
author2Str	Jebakumar R
ppnlink	558042449
callnumber-subject	TK - Electrical and Nuclear Engineering
mediatype_str_mv	c
isOA_txt	true
hochschulschrift_bool	false
doi_str	10.3991/ijim.v14i17.16609
callnumber-a	TK5101-6720
up_date	2024-07-04T00:37:15.804Z
_version_	1803606751510003712
fullrecord_marcxml	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">DOAJ054791383</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20230308184220.0</controlfield><controlfield tag="007">cr uuu---uuuuu</controlfield><controlfield tag="008">230227s2020 xx \|\|\|\|\|o 00\| \|\|eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.3991/ijim.v14i17.16609</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)DOAJ054791383</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)DOAJf464710399a749fb9fc7521b175152d4</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">TK5101-6720</subfield></datafield><datafield tag="100" ind1="0" ind2=" "><subfield code="a">Lucky Kannan</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2020</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">Computermedien</subfield><subfield code="b">c</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Online-Ressource</subfield><subfield code="b">cr</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Many businesses use email as a medium for advertising and they use emails to communicate with their customers. In the email world, the most common issue that remains unresolved even now is spamming or in other terms unsolicited bulk email. Currently, there is no common way to regulate the practices of an email sender. This proposed system is to formulate a protocol common for all the ESPs or inbox providers and a centralized system that will easily find the spammers and block them. By this method, the Email Service Providers (ESPs) or Inbox Providers need not wait for the sender behaviour and then take actions on the sender or sender domain or sender IP address. Instead, they can get the sender history of reputation from blockchain where the ESPs or Inbox Provider provides a score based on the emails they have received from the sender. The ESPs can get the Public Sender Score(S3) from the mobile application or web application which provides the score management user interface and APIs. The email marketers can also monitor their score through the application.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">email</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">spam detection</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">sender score</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">reputation system</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">blockchain</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">mobile application</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">marketing email</subfield></datafield><datafield tag="653" ind1=" " ind2="0"><subfield code="a">Telecommunication</subfield></datafield><datafield tag="700" ind1="0" ind2=" "><subfield code="a">Jebakumar R</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">In</subfield><subfield code="t">International Journal of Interactive Mobile Technologies</subfield><subfield code="d">International Association of Online Engineering (IAOE), 2018</subfield><subfield code="g">14(2020), 17, Seite 204-213</subfield><subfield code="w">(DE-627)558042449</subfield><subfield code="w">(DE-600)2406982-6</subfield><subfield code="x">18657923</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:14</subfield><subfield code="g">year:2020</subfield><subfield code="g">number:17</subfield><subfield code="g">pages:204-213</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://doi.org/10.3991/ijim.v14i17.16609</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://doaj.org/article/f464710399a749fb9fc7521b175152d4</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="856" ind1="4" ind2="0"><subfield code="u">https://online-journals.org/index.php/i-jim/article/view/16609</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="u">https://doaj.org/toc/1865-7923</subfield><subfield code="y">Journal toc</subfield><subfield code="z">kostenfrei</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_DOAJ</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_11</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_20</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_22</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_23</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_24</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_39</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_40</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_60</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_62</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_63</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_65</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_69</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_73</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_95</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_105</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_110</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_151</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_161</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_170</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_213</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_230</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_285</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_293</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_370</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_602</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2014</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2044</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2055</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2086</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2108</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2119</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4012</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4037</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4112</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4125</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4126</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4249</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4305</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4306</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4307</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4313</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4322</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4323</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4324</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4325</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4326</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4338</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4367</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4700</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">14</subfield><subfield code="j">2020</subfield><subfield code="e">17</subfield><subfield code="h">204-213</subfield></datafield></record></collection>
score	7.401143

Nicht das Richtige dabei?

Schreiben Sie uns!

Public Sender Score System (S3) by ESPs for Email Spam Mitigation with Score Management in Mobile Application

Nicht das Richtige dabei?

Zugang & Verfügbarkeit

Vorhandene Bände

Nicht das Richtige dabei?