Email Broken

[RichardU]

Is the first one that they aren't using 25 for SMTP?

No. 25 is correct.

Any way you can get me a capture of the traffic going back and forth?

Sure. How?

[Dean Roddey]

Well, I can't say for sure it's the stuff sent upon connection. But at some point along the line, it's getting a reply that's less than the minimum legal length, and based on the logged error it's just an empty line.

[Dean Roddey]

BTW, it may be worth just upgrading to the latest beta. It's solid and basically what 4.3 is going to be, and I wouldn't be particularly suprised if the issue doesn't just go away. So many improvements were made in all of the SMTP, HTTP, URL, etc... stuff that it's almost not worth even trying to figure it out until you upgrade and see if the issue even still exists. If you are under maintenance coverage you can upgrade any time. It may be that something changed but that we just are more forgiving of it these days.

[Dean Roddey]

No. 25 is correct.

Something's got to be wrong. Surely things aren't so messed up in CQC that it can't even make a connection to the server.

Sure. How?

It would require using something like Wireshark, or other TCP/IP spying type program to watch the traffic. Wireshark isn't a light weight program to learn necessarily, but it's not a bad tool to have in your arsenal from time to time.

[Dean Roddey]

BTW, do you have any other CQC based server side functionality that is going off network? Do you have the Weather CHannel driver or anything like that loaded and it's working correctly? Just making sure you are able to get out at all from the CQC backend. If not, and you aren't running the CQC service under an administrative account, you might want to do that to see if the update somehow is now preventing the service from getting out when running under the standard service account.

[bbrendon]

Hmm. I've heard of ISPs changing port 25 rules randomly. Many ISPs don't even allow outbound on port 25.

[Dean Roddey]

I use Comcast, and at least here they don't use 25.

[DaveB]

Google for me will not work; As for Comcast, these are my settings;

Type: SMTP
Name: Comcast
Server: SMTP.COMCAST.NET
User: xxxxxxxxx
Password: *******
From Addr: {must be a valid address}
IP Port: 587

Works great.

[RichardU]

Here, Comcast used port 25 until about three days ago. I can now get them on port 587. Thanks for the heads-up.

Google still does not work. I have tried both a gmail account and a google apps account. Their server must be looking for something CQC is not providing.

Thanks everyone for all the support.

[Dean Roddey]

I think that Google requires a secure connection, right? Aren't other folks here using Stunnel or something to do Google mail?