Anonymous users are not allowed to send themselves a copy because it can be abused to spam people. In the submit handler, the option is checked directly and a notice is produced.

I have set the patch RTBC beacuse it only adds a simple isset before using the value.

CommentFileSizeAuthor
#2 contact-copy-check-210260-2.patch648 bytesdropcube
contact-copy-check.patch734 bytesdropcube

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Reviewed & tested by the community » Needs work

What about adding a #value field with FALSE for the copy field, if the user is not allowed to ask for a copy. That would make it simpler to handle this situation in other modules as well (so that isset()s can be avoided).

dropcube’s picture

dropcube commented
Status: Needs work » Reviewed & tested by the community
StatusFileSize
new contact-copy-check-210260-2.patch648 bytes

Ok, the patch adds a value field set to FALSE if the user is anonymous, this way the isset() is not required as Gábor suggested.
Again, I have set the status RTBC beacuse the patch is really simple.

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Reviewed & tested by the community » Fixed

Thanks, committed.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

Monzer Emam’s picture

Monzer Emam commented
Version: 6.x-dev » 6.15
Assigned: dropcube » Unassigned
Status: Closed (fixed) » Active

if the Category aut-reply is set the contact form still email the anonymous user a copy

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Version: 6.15 » 6.x-dev
Status: Active » Closed (fixed)

Yes, that's by design. It's an auto-reply. Please don't open closed-for-two-years issues either.