Error - Couldn't get mail server response codes

[ApplianceJunk]

Using SMF 2.0.11

Have not changed anything on our site for probably months.
Started seeing these errors show up a few weeks ago.

http://appliancejunk.com/forums/index.php?board=35;action=post2
Couldn't get mail server response codes

I have not changed any forum email settings since 2013 when I started using gmail as I posted about here.
http://www.simplemachines.org/community/index.php?topic=525116.0

Here are my port settings.

SMTP server
ssl://smtp.gmail.com

SMTP port
465

Not sure when or why the errors show up. Our forum seems to be running fine. At least I have not noticed anything wrong other then the errors in the log and no members have been reporting any problems.

Thoughts?

Thanks,

Mods list.

1.   SMF 2.0.11 Update   1.0   [ Uninstall ]
2.   SMF 1.1.21 / 2.0.10 Update   1.0   [ Uninstall ]
3.   SMF 1.1.20 / 2.0.9 Update   1.0   [ Uninstall ]
4.   SMF 2.0.8 Update   1.0   [ Uninstall ]
5.   URL Popup   1.0.2   [ Uninstall ]
6.   Add IP2Location to Track IP   1.31   [ Uninstall ]
7.   Custom Copyright   1.0.4   [ Uninstall ]
8.   SMF 2.0.7 Update   1.0   [ Uninstall ]
9.   SMF 1.1.19 / 2.0.6 Update   1.0   [ Uninstall ]
10.   Simple Audio Video Embedder   2.1.1   [ Uninstall ]
11.   SMF 2.0.5 Update   1.0   [ Uninstall ]
12.   Social Login   2.3   [ Uninstall ]
13.   Add Facebook Like, Tweet, and Google +1   1.0.3a   [ Uninstall ]
14.   Add Social Media Icons To Profiles   1.0.8   [ Uninstall ]
15.   Enhanced About Page   0.02   [ Uninstall ]
16.   Register At Post View v.1.1   1.1   [ Uninstall ]
17.   Change All Subjects   1.1.2   [ Uninstall ]
18.   SMF 2.0.4 Update   1.0   [ Uninstall ]
19.   Country Flags   2.1   [ Uninstall ]
20.   Similar Topics   0.4   [ Uninstall ]
21.   Google Translate for SMF 2.0   1.3   [ Uninstall ]
22.   SMF Store   2.0.1   [ Uninstall ]
23.   SMF 2.0.3 Update   1.0   [ Uninstall ]
24.   Add Join Date to Post   1.0   [ Uninstall ]
25.   Repair Form   1.0   [ Uninstall ]
26.   Invitation Message In Your Face (IMIYF)   0.3.1   [ Uninstall ]
27.   Google Analytics Code   1.4   [ Uninstall ]
28.   SMF Links   2.5.3   [ Uninstall ]
29.   APP Tag for ApplianceJunk.com   1.0.0   [ Uninstall ]
30.   SMF Articles   2.0   [ Uninstall ]
31.   Google Member Map   2.6   [ Uninstall ]
32.   Additional Instant Messengers   1.0.1   [ Uninstall ]
33.   More Spiders   1.2   [ Uninstall ]
34.   GoogAd Mod v.1.4   1.3   [ Uninstall ]
35.   New Topic Button   1.0   [ Uninstall ]
36.   Guest Registration Notification   1.4.2   [ Uninstall ]
37.   SMF 2.0.2 Update   1.0   [ Uninstall ]
38.   Sitemap   2.2.0   [ Uninstall ]
39.   View Only Boards   1.2b   [ Uninstall ]
40.   reCAPTCHA for SMF   0.9.8a   [ Uninstall ]
41.   SMF 2.0.1 Update   1.0   [ Uninstall ]
42.   Online Users Area   1.2   [ Uninstall ]
43.   Show your social networks   3.0   [ Uninstall ]
44.   Contact Page   3.0   [ Uninstall ]
45.   PM to New Members   1.2   [ Uninstall ]
46.   Treasury   2.10   [ Uninstall ]
47.   Search Focus Dropdown   1.6.1   [ Uninstall ]
48.   Buy me a beer   1.0   [ Uninstall ]
49.   Internal Links Use Same Window   1.2   [ Uninstall ]
50.   Enable or Disable "« Last Edit: by »" for Administrators   1.3a   [ Uninstall ]
51.   SMF Gallery Lite   3.1.1   [ Uninstall ]
52.   Downloads System Pro   2.0.4a   [ Uninstall ]
53.   Ad Seller Pro   1.0.9   [ Uninstall ]

[Kindred]

See the other thread about gmail.they changed something

[Shambles]

...they changed something

They tightened up their enforcement of rfc2821 - the extended HELLO (EHLO) command.

The other gmail thread Kindred mentioned provides a solution.

[ApplianceJunk]

I have edited the Sources/Subs-Post.php as shown in the other post.
It's only been a few hours since I made the edit, but I have yet to see the error show up since.

I never could figure out exactly what it took to trigger the error.
Could someone tell me?

Thanks,

[Shambles]

I never could figure out exactly what it took to trigger the error.

Sending a mail via google's smtp server 

[ApplianceJunk]

I never could figure out exactly what it took to trigger the error.

Of course ha, thanks.