Slash Boxes

SoylentNews is people

posted by cmn32480 on Sunday April 24 2016, @11:38PM   Printer-friendly
from the spammers-should-be-{insert-punishment-here} dept.

Peter N. M. Hansteen asks the question, "Does Your Email Provider Know What A "Joejob" Is?" in his blog and provides some data and discussion. He provides anecdotal evidence which seems to indicate that Google and possibly other mail service providers are either quite ignorant of history when it comes to email and spam, or are applying unsavory tactics to capture market dominance.

[Ed Note: I had to look up "joe job" to find out what it is. According to wikipedia:

A joe job is a spamming technique that sends out unsolicited e-mails using spoofed sender data. Early joe jobs aimed at tarnishing the reputation of the apparent sender or inducing the recipients to take action against them (see also e-mail spoofing), but they are now typically used by commercial spammers to conceal the true origin of their messages.


Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Monday April 25 2016, @07:15PM

    by Anonymous Coward on Monday April 25 2016, @07:15PM (#337046)

    Well thx for all the reply.
    it is assumed that the person wanting to use emails has his/her own internet connection on which the server would sit (st0p complaing about 3rd party snooping already).

    REAL! that internet connection connects you to each and every other internet connection!

    the two things that are absolutely required (and then some) is a internet connection (dynamic or static, whatever) and a "identity" or "name".

    thus one sends a text and the receiver only gets a notification.
    the content is still on the senders server and HDD.
    it is then up to intended recipient to go fetch (pull) the email .. or not.

    of course one could add some form of identity verification (of sender server) to disallow sender-spoofing -ala- self-signed certs with https.

    there's obviously not much knowledge about email "in the wild" as compared to say ... uhm ... setting up a lamp stack.

    also the hops-and-loops needed to jump through to get a simple system to send text from one ip to another is comparable to the obstacle course in boot camp.
    one must assume that a whole business system thrives around email which feeds quiet a few families through winters and life in general thus leading to the assumption that it is kept artificially difficult to setup ...