Showing papers on "MX record published in 2019"
Patent•
19 Aug 2019
TL;DR: In this paper, a system for reducing email spam without wasting network bandwidth is proposed, which consists of two groups of boxes, Domboxes and Mailboxes, each of which has a disposable email address associated with a primary domain.
Abstract: Systems and methods are provided for reducing email spam without wasting network bandwidth. The system contains two groups of boxes. Domboxes and Mailboxes. (a) Domboxes should be used only for non-conversational mails. E.g. website/app mails. Each Dombox has a disposable email address and associated with a primary domain. The primary domain can authorize additional domains in the DNS. We primarily rely on the SPF record for validating Dombox mails. (b) Mailboxes are designed to accept only conversational mails. Conversational Mails can be termed as Human-to-Human, Mailbox-to-Mailbox or MX-to-MX mails. We pull the MX record from the Envelope Domain and verify whether it's really originating from one of the MX servers. Spammer is a Human. Since we accept only MX record verified mails, spammers need registered domains to send spam. Additional checks can be performed with the help of Domain registration date, Spam Filters, Challenge/Response etc.
4 citations
Patent•
2 Jul 2019
TL;DR: In this paper, a junk mail processing method, device and system and a computer readable storage medium, is described, which relates to the technical field of network information security, and relates to a method for intercepting a mail exchange MX record query request sent by a sending end server.
Abstract: The invention relates to a junk mail processing method, device and system and a computer readable storage medium, and relates to the technical field of network information security. The method comprises the following steps: intercepting a mail exchange MX record query request sent by a sending end server; analyzing the MX record query request, and obtaining the IP address of the sending end server; comparing the IP address of the sending end server with the IP address in the blacklist database; and responding to the IP address of the sending end server in the blacklist database, and returningthe IP address of the honeypot server as a response of the MX record query request to the sending end server. According to the technical scheme, the spam mail processing cost can be reduced, and the processing efficiency is improved.
24 Jan 2019
TL;DR: This memo defines a Sieve extension that fills this gap: it adds a test for checking whether a special-use attribute is assigned for a particular mailbox or any mailbox, and it adds the ability to file messages into an anonymous mailbox that has a particular special- use attribute assigned.
Abstract: The SPECIAL-USE capability of the IMAP protocol (RFC 6154) allows
clients to identify special-use mailboxes; e.g., where draft or sent
messages should be put. This simplifies client configuration. In
contrast, the Sieve mail filtering language (RFC 5228) currently has
no such capability. This memo defines a Sieve extension that fills
this gap: it adds a test for checking whether a special-use attribute
is assigned for a particular mailbox or any mailbox, and it adds the
ability to file messages into a mailbox identified solely by a
special-use attribute.