Gil Hardwick

Just to update and close this thread, I finally decided that this stupid problem simply isn’t worth the effort being spent on it, for so little gain either immediately or in terms of overall client contact efficiency.

All my sites are smart phone savvy anyway, even my hand-coded pages, and with so very many people browsing on the move these days, or over a morning coffee or a beer later, rather than bother with the site itself being able to send email via some variety of contact form I merely returned to my older style of embedding <tel:> and <mailto:> links in the relevant pages.

The prospective client only has to tap one of the little page icons now, and either call directly or email with preset subject: and body: content.

I don’t see this technique as any sort of work-around for bad or broken code, it simply renders the entire question redundant.

Thanks anyway.

OK, new problem. I propagated a yum update on the system and noticed it updated the kernel and some PHP-related files.

I had Configure SMTP running OK, and receiving emails, but I get an error message:

SMTP -> ERROR: Failed to connect to server: php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution (0)

I’m getting this same message on all my sites.

What do I need to do to fix this?

Thanks, and kind regards,

Gil

GREAT!! Thanks enormously.

Home and hosed ??

Hello Michael, this works OK except that it appears in Flamingo as an inbound message (as yet retaining skip_email=false including all-fields) not as a blog post, which is what I want to achieve.

It seems to me there still needs to be an explicit post_content field to enable the post, into which all-fields are aggregated.

Thanks again for your help to this point. Getting there . . .

Hello Michael, this is on posting to WordPress from a CF7 form, with skip_mail = true.

My question to you is concerned with how to post all the form fields from a custom, say, resume or job vacancy form rather than only your two post_title and post_content fields, with an optional post_category_name?