Page 1 of 1

Issue with PC v11.1

Posted: Wed Nov 04, 2020 8:07 am
by NoahGreat
We're running PC+ v11.1 with Win 7. Our Prayer Line has worked for years without any problems or errors. Now we've got one person who uses his work email and doesn't get our daily messages sent out. He's checked with his IT people, and their spam list (they check it every week) doesn't show anything obvious.
The message we get from our end when sending out the prayer line is as follows:

Message Blocked ...
Your message to xxxx@ ... com has been blocked. Please see the technical details below:
The remote server's response was as follows:
550 Envelope blocked - User Entry - https://www.worktime.com/employee-monitoring docs/DOC-1369#550 [ZSEsuUJ-PuWDuPo_OmdysQ.us148]

Does anyone else have this problem?
Thank you. Noah

Re: Issue with PC v11.1

Posted: Wed Nov 04, 2020 9:15 am
by Zorak
From the looks of that message, the receiving email account or domain has blocked incoming emails from you.

It could be related to the email setup in PowerChurch. Are you sending email from the same account/domain that is listed in the Outgoing Mail Server (SMTP) and Authentication sections of the email settings in PowerChurch? For example, using smtp.gmail.com with a gmail user and password to send email from a yourchurchwebsite.org email address.

It is difficult to say what the receiving mail server doesn't like about your incoming email. If the IT staff at the company where the email is intended to go are stumped, it's hard to say who would be the next best source of assistance.

Re: Issue with PC v11.1

Posted: Wed Nov 04, 2020 9:40 am
by NeilZ
I've seen this before ... that error 550 - envelope blocked is defined as
The sender's email address or domain has triggered a Blocked Senders Policy, or there's a SPF hard rejection. The Block Sender Policy on the recipient mail server needs to be deleted or modified to exclude the sender address
If you don't have a SPF record in your domain'S DNS records, it could trigger this since that record is used to prove that the email indeed came from your domain. Even if you do, if you have a domain that shares an SMTP server, that server may be triggering the block.

If that's not the case, the only alternatives are for their IT dept to whitelist that server, or the person in question to use an alternative email address.