Stefan Nagy

Sorry, this is wrong:

In short, with your stable branch plugin there’s one strange additional element (the empty field), with issue-4 there’s another one (the second “encrypted”-element).

Both of those strange elements are present no matter which of the two branches (stable, issue-4) I install. In fact I don’t really see a difference between those two branches… I can send attachments without any problems, but they are not encrypted (I tried that out with TXT, ODT, PDF and PNG).

Hi Meitar,

sorry it took me some time to reply. I was able to send an attachment with issue-4. It is not encrypted.

But I wanted to tell you something I didn’t mention before because it’s not really a problem… But it’s a bit strange. I’m using Evolution as part of GNOME as e-mail client (on Debian testing) and e-mails sent with your plugin look different than other e-mails…

Please have a look at this screenshot: https://tinyurl.com/z5cvkvo

Beneath the message there’s this green area that says that it is signed and encrypted. With the stable branch of your plugin there’s an additional empty field beneath that green area – just like in the screenshot. I have never received an e-mail with such an additional empty field before (and I’m using Evolution everyday for 10 years now).

Between the green area and this additional empty field there’s an additional element in the screenshot. It says that the message is encrypted… So there’s one element that says the message is signed and encrypted and then there’s an additional element that says it’s encrypted. That’s really strange.

In short, with your stable branch plugin there’s one strange additional element (the empty field), with issue-4 there’s another one (the second “encrypted”-element). Sorry, I’m not trying to sound complicated… English isn’t my native language.

Cheers

Yes, now I get no error message in Contact Form 7 and I receive the sent e-mail without any problems.

However, attached files are still not encrypted (I tried out a JPG and a PNG).

At least in /etc/postfix/main.cf there’s no notify_classes configuration line at all…

I’m a member of hostsharing.net, that’s a webhosting cooperative – so no, I don’t control the server. But at least I should be able to find out whatever you’d like to know.

In /etc/postfix/main.cf the following notice recipients are defined: 2bounce_notice_recipient, bounce_notice_recipient, delay_notice_recipient and error_notice_recipient. The recipient is always the server’s postmaster, not the domain’s (that would be me).

Sorry, nothing really changed… I still get a “Undelivered Mail Returned to Sender”-Mail before I receive the E-Mail sent with Contact Form 7. The Delivery report looks like before.

Sorry, I’m just not experienced enough to answer your question. All I know is that the server is running Debian 7.9 and that Postfix is used as MTA…

Where can I find the relevant config file(s)?

With the patched version I get no error message after submitting the message with Contact Form 7. But I get two e-mails to my admin-address:

Before receiving the E-Mail sent with Contact Form 7 I get a “Undelivered Mail Returned to Sender”-Mail which contains the following in the attached Delivery report:

Final-Recipient: rfc822; [email protected]
Original-Recipient: rfc822;[email protected]
Action: failed
Status: 5.4.4
Diagnostic-Code: X-Postfix; Host or domain name not found. Name service error for name=localhost.invalid type=A: Host not found

With WP PGP Encrypted Emails installed, when I submit a message with Contact Form 7 I get the error message “Sender’s message failed to send” – however I still receive the message.

OK, I wanted to test the experimental branch, but it turned out that the plugin (version 0.4.1) doesn’t work for me anymore.

I can’t use Contact Form 7 to send E-Mails when the plugin is installed – I always get error messages when I click the submit-button. It makes no difference if I install 0.4.1 or the patched code from the experimental branch…

I posted this here because Contact Form 7 is one of the most popular WordPress plugins and I can’t find any sign that someone was affected by this issue before…

Therefore and since the only way I can reproduce this myself is to activate this theme I reckoned it’s caused by it.

Meitar, sorry for my late reply. The website is for a textile printing workshop, so people usually want to attach pictures (usually PNG, JPG, sometimes PDF, EPS or SVG).

I’m really sorry but I have no time for testing right now.

Nice… Thanks for your great work!

Thanks, Meitar. I’ll disable file upload in my contact forms until there is support for encrypted attachments.