User Support Forum

PCPlus version 11.55 on windows 8 and 10. I am having trouble with the email setup on the church office computer which is running window 8. I get the following error message when I test the settings.

Error within connect
non-success EHLO response
Server reported with
501 syntactically invalid EHLO argument(s)

With the exact same setup on my home computer under windows 10 it works fine. Both systems are using Verizon as the provider.

Not sure why it should work in one place and not the other.

tborgal wrote:PCPlus version 11.55 on windows 8 and 10. I am having trouble with the email setup on the church office computer which is running window 8. I get the following error message when I test the settings.

Error within connect
non-success EHLO response
Server reported with
501 syntactically invalid EHLO argument(s)

With the exact same setup on my home computer under windows 10 it works fine. Both systems are using Verizon as the provider.

Not sure why it should work in one place and not the other.

There should be a file in the PCPLUS115 directory called EmailSession.log, could you cut and paste the contents of that log ??

Neil,

Here it is. I X'd out a few things that I did not want posted here. The one that works is the same (once you get past the greeting error) as the one that does not until you get to the <smtpSocketConnect> area. The main difference I see is that the computer name has an underscore in it. My home computer name has a dash. Could this be the problem and if so is it my host or PowerChurch that does not like it?

<SessionLog>
<Begin>2015-11-11T21:11:08</Begin>
<LogEntry>
<EntryTime>2015-11-11T21:11:08</EntryTime>
<Log><SmtpFailReason>GreetingError</SmtpFailReason>
<ChilkatLog>
<OpenSmtpConnection>
<DllDate>Aug 26 2015</DllDate>
<ChilkatVersion>9.5.0.52</ChilkatVersion>
<UnlockPrefix>POWERC.CBX0717</UnlockPrefix>
<Username>CHURCH_OFFICEHP:XXXXXX</Username>
<Architecture>Little Endian; 32-bit</Architecture>
<Language>ActiveX</Language>
<VerboseLogging>0</VerboseLogging>
<ensureSmtpSession>
<ensureSmtpConnection>
<SmtpHost>smtp.ipower.com</SmtpHost>
<SmtpPort>587</SmtpPort>
<SmtpUsername>XXXXXX@nebible.org</SmtpUsername>
<SmtpSsl>0</SmtpSsl>
<StartTLS>0</StartTLS>
<smtpConnect>
<smtpHostname>smtp.ipower.com</smtpHostname>
<smtpPort>587</smtpPort>
<connectionIsReady>
<info>Need new SMTP connection</info>
</connectionIsReady>
<smtpSocketConnect>
<socketOptions>
<SO_SNDBUF>262144</SO_SNDBUF>
<SO_RCVBUF>4194304</SO_RCVBUF>
<TCP_NODELAY>1</TCP_NODELAY>
<SO_KEEPALIVE>1</SO_KEEPALIVE>
</socketOptions>
</smtpSocketConnect>
<smtpGreeting>
<readSmtpResponse>
<SmtpCmdResp>220 ESMTP Wed, 11 Nov 2015 21:11:09 -0500: UCE strictly prohibited</SmtpCmdResp>
</readSmtpResponse>
</smtpGreeting>
<ehloCommand>
<sendCmdToSmtp>
<SmtpCmdSent><![CDATA[EHLO CHURCH_OFFICEHP<CRLF>]]></SmtpCmdSent>
</sendCmdToSmtp>
<readSmtpResponse>
<SmtpCmdResp>501 Syntactically invalid EHLO argument(s)</SmtpCmdResp>
</readSmtpResponse>
<error>Non-success EHLO response.</error>
</ehloCommand>
<heloCommand>
<sendCmdToSmtp>
<SmtpCmdSent><![CDATA[HELO CHURCH_OFFICEHP<CRLF>]]></SmtpCmdSent>
</sendCmdToSmtp>
<readSmtpResponse>
<SmtpCmdResp>501 Syntactically invalid HELO argument(s)</SmtpCmdResp>
</readSmtpResponse>
<error>Non-success EHLO response.</error>
</heloCommand>
</smtpConnect>
</ensureSmtpConnection>
</ensureSmtpSession>
<error>Failed to connect to SMTP server</error>
<error>Failed.</error>
</OpenSmtpConnection>
</ChilkatLog>
</Log>
</LogEntry>
<LogEntry>
<EntryTime>2015-11-11T21:11:08</EntryTime>
<Log><ChilkatLog>
<CloseSmtpConnection>
<DllDate>Aug 26 2015</DllDate>
<ChilkatVersion>9.5.0.52</ChilkatVersion>
<UnlockPrefix>POWERC.CBX0717</UnlockPrefix>
<Username>CHURCH_OFFICEHP:XXXXXX</Username>
<Architecture>Little Endian; 32-bit</Architecture>
<Language>ActiveX</Language>
<VerboseLogging>0</VerboseLogging>
<sendCmdToSmtp>
<SmtpCmdSent><![CDATA[QUIT<CRLF>]]></SmtpCmdSent>
</sendCmdToSmtp>
<readSmtpResponse>
<SmtpCmdResp>221 bosauthsmtp10.yourhostingaccount.com closing connection</SmtpCmdResp>
</readSmtpResponse>
</CloseSmtpConnection>
</ChilkatLog>
</Log>
</LogEntry>
<End>2015-11-11T21:11:11</End>
</SessionLog>

It looks like the issue is with the computer name, specifically the underscore. Apparently Windows warns about the underscore not being a standard character and potential problems with some applications or network hardware.

In any case, try changing the computer name and replace the _ with a -

Zorak,

So is the problem with the network hardware or PowerChurch?

I will make the change and see if that fixes the problem. Not sure how that will effect other hardware communicating with it though if it works. I may have to make changes elsewhere as well.

Tom B.

tborgal wrote:Zorak,

So is the problem with the network hardware or PowerChurch?

I will make the change and see if that fixes the problem. Not sure how that will effect other hardware communicating with it though if it works. I may have to make changes elsewhere as well.

Tom B.

Tom,

its a problem with the computer name: CHURCH_OFFICEHP. The UNDERSCORE is not allowed, here's the RFC requirement:

To promote interoperability and consistent with long-standing guidance about conservative use of the DNS in naming and applications [...],characters outside the set of alphas, digits, and hyphen MUST NOT appear in domain name labels for SMTP clients or servers. In particular, the underscore character is not permitted.

You'll need to change that to CHURCH-OFFICEHP ..

Unfortunately, you may also have to remap the shared drive on all networked computers, then run NETSETUP115 from the PCPLUS115/Install directory to update the local system's registry.

Thanks Neil. I thought I would have to do that. I will need to fix that the next time I am at the church. Just not sure what else it might break.

Tom B.

tborgal wrote:Thanks Neil. I thought I would have to do that. I will need to fix that the next time I am at the church. Just not sure what else it might break.

Tom B.

Yeah, I can understand that. It all depends on if other areas of that computer are being shared on the network for other reasons.

We need to get the email problem resolved so we will just have to deal with any problems that might arise. I do not foresee anything major though.

Tom B.

Neil and Zorak
Thanks for your help. Changing the underscore to a dash resolved the problem.

Tom B.