Replies: 0
hi,
I think it’s better to substitute
//$result->invalidate( $tag, __( ‘Email address seems invalid.’, ‘contact-form-7’ ) );
$result->invalidate( $tag, wpcf7_get_message( ‘invalid_email’ ) );
so that it makes use of the form-specific localized custom text for that case
Also, note it’s recommended to chmod no more than 0774 for logdir, and I’d add chmod 0640 for the logfile too (not really needed with 0774 dir though)
Last, I’ve excluded ‘outlook.com’ from exclusion list (so it’s void basically so far) since it seems that the try ‘rcpt to:’ yields ok or no error, e.g.
– – [2016-12-03 10:44:07] CLIENT -> SERVER: VRFY ***
– – [2016-12-03 10:44:07] SERVER -> CLIENT: 252 Cannot VRFY user, but will take message for <***@hotmail.com>
which seems true also for ‘protected’ domains. YMMV so better put a note/howto in the docs/faq.
Also I think a docs/faq note for timeout – which I raised to 8s – is worth, and on antispam/greylisting: MTAs may engage in antispam challanges that make this simple smtp check fail, so a +feature could be soft-fail on timeout, passing on green light to CF7 to send the form anyway, but throwing a warning on the UI like “Warning: Your message was sent successfully, but could not verify email you entered: ‘[your-email]’. Please redo if you mistyped it. Thanks”
thx