-
Topics
-
Blogs
-
News
-
Community
-
Industry
Australia has cracked down on junk mail with an industry code for tackling spam.
Under the new code, internet service providers (ISPs) will bear some of the responsibility for helping fight spam. Service providers must offer spam-filtering options to their subscribers and advise them on how to best deal with and report the nuisance mail. ISPs will also be compelled to impose "reasonable" limits on subscribers' sending email.
Read full story: The Register
To post comments, please login or create an account.
IP AddressingSponsored by Avenue4 LLC |
|
DNS SecuritySponsored by Afilias |
|
CybersecuritySponsored by Verisign |
|
Mobile InternetSponsored by Afilias Mobile & Web Services |
|
ACCELR/8 is a transformative IPv4 market solution developed by industry veterans Marc Lindsey and Janine Goodman that enables organizations buying or selling blocks as small as /20s to keep pace with the evolving demands of the market by applying processes that have delivered value for many of the largest market participants. more»
A world-renowned source for Internet Developments. Serving since 2002.
Primary source information on this matter can be found at the Australian Communications and Media Authority's website: ACMA registers internet industry code on spam.
From a technical perspective, this code of practice is noteworthy in that it considers publication of SPF records a "best practice" to be followed. It also prohibits open proxies and open relays, whether on the ISP's hosts or customer hosts, and reserves the right for ISPs to scan for such services as a part of enforcing their AUP. Outgoing mail must use SMTP "AUTH" or similar, and outgoing port 25 blockage is required of dynamically addressed hosts "where technically and commercially viable".
The "best practice" SPF requirement is a little dubious, given that development in this area (MARID — Mail Authentication Records In DNS) is still very much a work in progress. Still, that particular requirement has very little impact in actual practice, since it's quite possible to publish an explicitly noncommittal SPF record.