SFD

BSN
Inet

Consol
Inet

Berklix will dump all Yahoo mail addresses.

This is: http://berklix.com/~jhs/mail/Yahoo

See Also: Do Not Send From Spammer Domains inc. some Bad Providers

Summary

• Yahoo mail users who send or receive mail to/from any address (personal or list ) @Berklix should mail from / subscribe an address from a new provider other than Yahoo, as all mail from @yahoo will be dumped soon by Berklix .
• Yahoo users subscribed to lists on @Berklix should subscribe themselves with a non Yahoo address.
• Why:
  • All Yahoo addresses will be deleted from all Berklix  lists  ; Yahoo is no longer unacceptable. Mail from Yahoo to Berklix will be dropped by Berklix. To avoid Yahoo users thus being trapped on Berklix  lists , unable to mail change requests to the Berklix subscription robot, they will be removed from Berklix  lists  before the block is implemented.
  • Please unsubscribe your @yahoo address, & subscribe some other address, If you take no action, you will be removed, & no longer able to mail to or from @Berklix people or  lists .

What's The Problem ?

• Yahoo previously blocked abuse@yahoo.com from accepting back spam sent from their site, forwarded back to Yahoo in the same format rogue spammers on Yahoo excreted it.
• Yahoo demanded innocent recipient domain postmasters waste our time=money wrapping up excrement from Yahoo spammer customers in "Abuse Reporting Format", to save Yahoo their time & money, at our expense
• Yahoo then blocked their postmaster@yahoo.com, which per RFC etc is supposed to be a human who can deal with problems.
• Yahoo has now withdrawr their postmaster@, now auto responding, requiring innocent postmasters waste More of their time with Yahoo web pages.

Why Is The Problem Being Responded To Now ?

Administration of this domain :

• Will not work unpaid for Yahoo, Not to increase Yahoo profit, to decrease their loss, to subsidise their lay off programme, or any other reason.
• Will not waste time converting spam from Yahoo to spam report format RFC5965 before returning it to abuse@yahoo.
• Will not waste time unpaid, reading the RFC , & searching for free source based automatic tools that will convert a format from MUA (Mail User Agents) eg EXMH to SRF.
• Are not paid to admin this domain, it runs lots of free lists all with no advertising funding. No money is paid by anyone to fund time to waste working unpaid for Yahoo.
• Will not work harder so Yahoo can earn more money by cutting its staffing costs. Yahoo etc's should deal with their own problem, & implement a robot behind their abuse@yahoo.com to filter forwarded spam into whatever format they might want. Not our responsibility to work unpaid for commercial providers that also emit spam.

• It's fundamentally Wrong for a commercial provider, a source also of spam, to force their work of processing spam from their site, to unpaid administrators of innocent recipient domains of spam.
• Was the RFC commisiioned, or sponsored by people un-representative of or ignoring the wider _Free_ Internet ? Dominated perhaps by representatives of commercial ISPs like Yahoo, making money on advertising, assuming paid administrators were each end of every email server ?
• If a dog excretes on the pavement, it's the owner's responsibility to remove excretia, not a pedestrian's responsibility to box up the excretia stuck on his shoe, carefully documenting the excretia in a format acceptable to the person who houses the dog.
• Yahoo would have innocent recipients bear the burden of formatting into SRF, what some of their users who are spammers excrete.
•   At Dec. 2010 Yahoo is laying off 500 staff, ie 4% How many used to deal with abuse@ mail ? How much of Yahoo work is now dumped on us, unpaid ?

A quick search for SRF tools

• Does not seem to have found free source tools easily to hand ready to integrate into eg, EXMH & Claws, to forward a spam in RFC5965 to an abuse@ISP.
• So Yahoo will be listed as a spammer domain, to dump all mail from Yahoo, to avoid unpaid work Yahoo demands.
• Innocent people with @yahoo addresses will need to be removed from lists. Innocent personal recipients @Berklix will unfortunately not receive personal mail from nnocent senders @yahoo.

• Yahoo gave no warning that was noticed in email response of past reports to abuse@, that they would enforce this RFC in X months time.
• Yahoo were warned, but did not respond. The contagion needs to be excised before it might spread, tempting more responsible mail operators.
• Subscribers of any list on @Berklix are requested to unsubscribe any @yahoo address, & subscribe some other address.

Mail List Threads

• Sat, 18 Dec 2010 13:11:41 +0100 To exmh-users@
• Sat, 18 Dec 2010 16:28:33 +0100 To isp@freebsd
• Not yet looked at.: NMH mail list

Mail List Archive Copies

• From owner-freebsd-hackers@@@freebsd.org Tue Dec 21 11:07:23 2010
  Message-Id: <201012210101.oBL117OZ005993@@@fire.js.berklix.net>
  To: hackers@@@freebsd.org
  From: "Julian H. Stacey" <jhs@@@berklix.com>
  Date: Tue, 21 Dec 2010 02:01:07 +0100
  Subject: Forward to abuse@@@ button for http://tools.ietf.org/html/rfc5965
  
  Hi hackers@@@,
  No reply to this on <isp@@@freebsd.org> , so asking on this bigger list
  
  --------------
  
  I just posted a question [see below] to exmh-users@@@redhat.com,
  
  A similar question extends for nmh & claws-mail etc:
      Any tools to auto forward spam into RFC5965 format for abuse@@@ ?
  
  ] To: exmh-users@@@redhat.com
  ] Subject: Forward to abuse@@@ button for http://tools.ietf.org/html/rfc5965 ?
  ] Date: Sat, 18 Dec 2010 13:11:41 +0100
  ]
  ] Anyone working on an extension to EXMH 2.7.2 01/07/2005 to support
  ]   http://tools.ietf.org/html/rfc5965
  ] (spam report format) ?
  ]
  ] I just got this bounced back to me:
  ] --------
  ] Date: Fri, 17 Dec 2010 13:44:15 -0800
  ] To: "Julian H. Stacey" <jhs@@@berklix.com>
  ] Subject: RE: File for your claim! (fwd)  (KMM120695297V22240L0KM)
  ] From: Yahoo! Mail <abuse@@@yahoo.com>
  ] Reply-To: Yahoo! Mail <abuse@@@yahoo.com>
  ] MIME-Version: 1.0
  ] Content-Type: text/plain; charset = "us-ascii"
  ] Content-Transfer-Encoding: 7bit
  ] X-Mailer: KANA Response 7.0.1.142.15
  ]
  ] Thank you for your email, but this address now only accepts messages in
  ] Abuse Reporting Format (http://tools.ietf.org/html/rfc5965)
  ]
  ] To report abuse manually (or to get help with security or abuse related
  ] issues), please go to Yahoo! Abuse:
  ] http://abuse.yahoo.com
  ]
  ] For questions about using Yahoo! services, please visit Yahoo Help:
  ] http://help.yahoo.com
  ]
  ] Thank you,
  ]  - Yahoo! Customer Care
  ]
  ] Note: Please do not reply to this email as replies will not be answered.
  ] --------
  
  PS Spot the connection ?
  Yahoo dumps anti spam work on unpaid suckers.  Yahoo lays off 4% of staff,
      http://berklix.com/~jhs/mail/no_rfc5965.html
  

• Date: Tue, 21 Dec 2010 07:56:10 -1000
  From: Clifton Royston <cliftonr@@@lava.net>
  To: "Julian H. Stacey" <jhs@@@berklix.com>
  Cc: hackers@@@
  freebsd.org
  Subject: Re: Forward to abuse@@@ button for http://tools.ietf.org/html/rfc5965
  Message-ID: <20101221175610.GC28185@@@lava.net>
  
  > Date: Tue, 21 Dec 2010 02:01:07 +0100
  > From: "Julian H. Stacey" <jhs@@@berklix.com>
  > Subject: Forward to abuse@@@ button for
  >    http://tools.ietf.org/html/rfc5965
  > To: hackers@@@
  freebsd.org
  > Message-ID: <201012210101.oBL117OZ005993@@@fire.js.berklix.net>
  >
  > Hi hackers@@@,
  ..
  > I just posted a question [see below] to exmh-users@@@redhat.com,
  >
  > A similar question extends for nmh & claws-mail etc:
  >    Any tools to auto forward spam into rfc5965 format for abuse@@@ ?
  >
  > ] To: exmh-users@@@redhat.com
  ..
  > ] From: Yahoo! Mail <abuse@@@yahoo.com>
  > ] Reply-To: Yahoo! Mail <abuse@@@yahoo.com>
  > ] MIME-Version: 1.0
  > ] Content-Type: text/plain; charset = "us-ascii"
  > ] Content-Transfer-Encoding: 7bit
  > ] X-Mailer: KANA Response 7.0.1.142.15
  > ]
  > ] Thank you for your email, but this address now only accepts messages in
  > ] Abuse Reporting Format (http://tools.ietf.org/html/rfc5965)
  > ]
  > ] To report abuse manually (or to get help with security or abuse related
  > ] issues), please go to Yahoo! Abuse:
  > ] http://abuse.yahoo.com
  > ]
  > ] For questions about using Yahoo! services, please visit Yahoo Help:
  > ] http://help.yahoo.com
  > ]
  > ] Thank you,
  > ]  - Yahoo! Customer Care
  > ]
  > ] Note: Please do not reply to this email as replies will not be answered.
  > ] --------
  >
  > PS Spot the connection ?
  > Yahoo dumps anti spam work on unpaid suckers.  Yahoo lays off 4% of staff,
  >    http://berklix.com/~jhs/mail/no_rfc5965.html
  >
  > Cheers,
  > Julian
  
  Julian,
    The only reference I've seen to date on a public tool for ARF
  formatting are Perl modules - Mail::ARF, Email::ARF, and MIME::ARF; but
  you should be able to craft something with those.  ARF is a variation
  on the previously existing MIME Multipart/Report format, so you can
  also look at any MIME generation tools which play well with exmh.
  Email::ARF is on CPAN and a link to MIME::ARF can be found here:
    http://wordtothewise.com/resources/arfdeveloper.html
  
    John Levine, a long-time FreeBSD user and Internet mail guru, was one
  of the developers who helped work it through the IETF, so I did some
  searches on his site (Google search on: "arf site:jl.ly" but don't find
  anything specifically about tools.
  
    However, I can also inform you that that even if you submit a
  properly formatted ARF report, a good fraction of the time Yahoo! may
  still bounce it indicating that you must submit an ARF report.  I have
  seen a number of reports of that.  Outsourcing, I'm sure.  (They also
  have been known to firmly claim that a number of Yahoo's mail outbounds
  are not their servers.)  AOL will actually process ARF messages and so
  will some other major providers, so it's still worth doing.
  
    -- Clifton
  
  --
      Clifton Royston  --  cliftonr@@@iandicomputing.com / cliftonr@@@lava.net
  

postmaster@yahoo.com also crippled by January 2012

Do Not Mail From or Subscribe from @yahoo.com To Berklix