Open Bug 156744 Opened 20 years ago Updated 8 years ago

TMDA support missing (automatic reply, wait for confirmation by unknown senders; challenge/response)

Categories

(MailNews Core :: Backend, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

People

(Reporter: 6tsh7a001, Unassigned)

References

(Blocks 1 open bug, )

Details

It would be a great help if mozilla mail supported TMDA.  TMDA cuts down on spam
by making non-whitelisted senders respond to a challenge, which spammers
wouldn't/couldn't (fake from: address) do.  TMDA seems like it's a very
effective anti-spam system, and I'd like to see support for it.
QA Contact: gayatri → laurel
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 11035
*** Bug 215875 has been marked as a duplicate of this bug. ***
My bug was just marked as a dupe (that's OK of course). But I searched for such
a bug before opening a new. However I didn't find this one, because I did not
search for "TMDA", but for "spam"/"junk"/"automatic reply"/"confirmation email".

Is it possible to some of those to the Summary so people can find this bug easier?

Maybe: 
"TMDA support missing (send automatic reply and wait for confirmation, when
email is possible junk)"


Furthermore I think the Bugzilla-Team shuld introduce a new Component of Mail/News
"Junk Defense/Filtering"
as this is becomming a more important part of Mail/News in the future, which
isn't really Backend.
Product: MailNews → Core
I'm not sure implementing TMDA on the client side is really a good idea. After all, spam would still have to be downloaded and kept on the hard disk, so when the sender is verified, the mail could be passed on to the user.

Scott, any ideas on this? Or resolve as WONTFIX?
Summary: TMDA support missing → TMDA support missing (automatic reply, wait for confirmation by unknown senders; challenge/response)
Duplicate of this bug: 238596
See http://www.spamcop.net/fom-serve/cache/329.html about why autoreply is bad, challenge/respose is worse (they both contribute to the spam PROBLEM, not its SOLUTION), and how to replace them by better methods.
Assignee: mscott → nobody
QA Contact: laurel → backend
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.