Search the Archives

RFC 1939: spoofing is a problem which, at this point, seems to be in...

<< Back to: RFC 1939

Reader comments:

Comment by loungelizard
Submitted on 1/17/2007
Related RFC: RFC 1939
Rating: Not yet rated	Rate this comment:
spoofing is a problem which, at this point, seems to be in the too hard basket to solve. I am sure that out there in virtual space there are clever minds capable of developing a system which can validate the sender.This is just a thought and am not sure that it is possible but, lets assume that the POP3 standards are change to include the processor ID/Serial # of the email account owner operating system and a private encryption key to be used for the processor ID/Serial # is provided to the POP3 service provider by the account holder. When mail is sent from the email account owner and validated, the messages are sent of to the addressee or dumped.Mail software would have to include provisions to identify the processor ID/Serial # and encrypt using the same private key, the resulting encrypted id is included in the FROM header.Obviously the private key is only provided to the POP3 service provider and should be able to be changed by the user at any time.There should also be provision for sending mail away from the account owners systems, this could possibly be achieved by providing a process to register additional processor ID/Serial # which can be revoked by the user at any time.The POP3 and SMTP standards would have to change to incorporate this to work.As I said, this is just a thought! Is there any one out there that could make something like this work?

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 1939