Undelivered Mail Returned to Sender

giampablo · 2018-04-19 10:14:13

Using com_connect plugin the mail message is not delivered to recipient, because SPAM is detected.
The Mail delivery System sends back this notice: host [...IP address...] said: 552 5.2.0 c9BJ1x00C3uqbu1019BJEL spam content detected (in reply to end of DATA command).

Is it possible that the textpack translation in Italian leads the mail system to interprete the message as SPAM?
Or should I just ask the postmaster at host to be less restrictive?

colak · 2018-04-19 12:34:37

Hi giampablo

In gmail most mails from such forms end up in the spam as the “from” address is not real. I had to create a filter to allow them to the inbox.

giampablo · 2018-04-19 14:24:28

Hi Yiannis,

no gmail is involved, either sender or recipient. Maybe the problem is the host (too strict) that confuses legitimate email and spam email.

phiw13 · 2018-04-19 22:26:01

Do you have the SMTP field in Preferences > Admin filled in? And do you use the same email address for the contact form?

In the contact form, this is what I use:

<txp:com_connect to="me@example.com" from="me@example.com" …

And the address is the same email address used in the SMPT field mentioned.

giampablo · 2018-04-30 08:04:24

It was a Server problem.

Seems that header’s X-PHP-Originating-Script: field has
"19316157:txplib_misc.php(1803) : eval()'d code"

The culprit is eval()'d code that could be used to inject malicious code.

Aruba (hosting), by the way, solved my problem and now all messages go through as expected.

Thanks everybody

phiw13 · 2018-04-30 08:07:25

giampablo wrote #311516:

It was a Server problem.

Seems that header’s X-PHP-Originating-Script: field has
"19316157:txplib_misc.php(1803) : eval()'d code"

The culprit is eval()'d code that could be used to inject malicious code.

oh indeed that is asking for problems…

Edit: I opened issue 64 on the GitHub repo

Last edited by phiw13 (2018-04-30 08:12:32)

Bloke · 2018-04-30 11:15:00

The deep irony here is that X-PHP-Originating-Script itself appears to be an anti-spam measure employed to (somehow) help recipients track down scripts that are bothering them.

I’ve tried a few hacky methdos to trick the server into using something else, but so far to no avail. Looks like we’re stuck with it, since that line of txplib_misc.php is indeed the “originating script” where Txp hands off control to the plugin.

Perhaps if we one day find a better way to load plugins without the use of eval() then at least the message may become less verbose. Until then, not sure what we can do. If anyone has any ideas, please let us know.

colak · 2018-04-30 11:31:05

Would it be good to hear how Aruba solved the problem then?

Bloke · 2018-04-30 11:56:13

Probably either turned off that directive in php.ini or tweaked their spam filters to permit this specific case through.

Gallex · 2018-05-21 12:00:53

phiw13 wrote #311235:

Do you have the SMTP field in Preferences > Admin filled in? And do you use the same email address for the contact form?

In the contact form, this is what I use:

<txp:com_connect to="meexample.com” from=“me@example.com” ……@

And the address is the same email address used in the SMPT field mentioned.

i put my gmail address into both fields, also into SMPT.

the email arrives, but with a warning from google:

Be careful with this message
This may be a spoofed message. The message claims to have been sent from your account, but Gmail couldn’t verify the actual source. Avoid clicking links or replying with sensitive information, unless you are sure that you actually sent this message. (No need to reset your password, the real sender does not actually have access to your account!)

secondly, if from field is filled, my address is always on a header of arrived messages ,not senders

phiw13 · 2018-05-21 12:08:13

Gallex wrote #311936:

i put my gmail address into both fields, also into SMPT.

the email arrives, but with a warning from google:

Be careful with this message…

Yes other people have mentioned similar warnings with Gmail in the plugin’s thread.

secondly, if from field is filled, my address is always on a header of arrived messages, not senders

But the senders address is in the reply-to field, no?

Gallex · 2018-05-23 08:30:39

phiw13 wrote #311937:

But the senders address is in the reply-to field, no?

yes

Textpattern CMS

Textpattern CMS support forum

#1 2018-04-19 10:14:13