Mailing List CGatePro@mail.stalker.com Message #105217
From: Tom Rymes <trymes@rymes.com>
Subject: Re: Yahoo, unreachable for too long ?
Date: Fri, 10 Oct 2014 07:47:37 -0700
To: <CGatePro>
Jonn,

Maybe you're right, but the rest of us are using CGP and not having this
problem, so blaming it on CGP sure does seem premature. More likely is
that your configuration (CGP, firewall, something) is somehow causing
this behavior.

I would suggest that you continue to pursue this here, as it sounds like
you can resolve this issue. After you resolve it, if you still think
that another product is the right choice for you, then that's fine, but
don't make that decision based on this Yahoo issue, which none of us
have run into at this time.

Tom

On 10/08/2014 9:04 AM, Taylor, Jonn wrote:
> This is actually a problem with CGP even though support says not. I can
> send test messages with the same attachments to 4 different mail servers
> that we are demoing right now and NONE of them have this problem. In
> fact when I was talking to other companies that make mail server
> software they thought that CommuniGate Pro was dead.
>
> In light of the things that I have seen on this list and the responses
> that I got from support. I thing it is time to move away from
> CommuniGate. I like what they have, they are just not fixing things list
> ActiveSync, Calendaring other issues like this one. Always saying the
> problem is someone else is not a good sign.
>
> Taylor Telephone Systems, Inc <http://www.taylortelephone.com/>
>
> Jonn Taylor
> 651-683-4002 Direct / 651-245-4836 Cell / jonnt@taylortelephone.com
> <mailto:jonnt@taylortelephone.com>
>
> Taylor Telephone Systems, Inc Office: 651-454-5866 / Fax: 651-683-4019
> 8334 Argenta Trail, Inver Grove Heights, MN 55077
> http://www.taylortelephone.com/
>
> On 10/07/2014 07:40 AM, James Roman wrote:
>> On Oct 7, 2014, at 7:00 AM, CommuniGate Pro Discussions
>> <CGatePro@mail.stalker.com <mailto:CGatePro@mail.stalker.com>> wrote:
>>
>>> *From: *"Taylor, Jonn" <jonnt@taylortelephone.com
>>> <mailto:jonnt@taylortelephone.com>>
>>> *Subject: **Re: Yahoo, unreachable for too long ?*
>>> *Date: *October 6, 2014 at 9:43:38 AM EDT
>>>
>>>
>>> Search yor logs for this.
>>>
>>> 19:54:40.348 3 SMTPI-020151(nm23-vm4.bullet.mail.gq1.yahoo.com
>>> <http://yahoo.com/>) failed
>>> to receive message body (11850 bytes). Error Code=message line is too
>>> long
>>> 20:22:37.813 3 SMTPI-020199(nm14-vm8.bullet.mail.gq1.yahoo.com
>>> <http://yahoo.com/>) failed
>>> to receive message body (3741 bytes). Error Code=message line is too long
>>> 21:00:33.034 3 SMTPI-020251(nm3-vm6.bullet.mail.gq1.yahoo.com
>>> <http://yahoo.com/>) failed to
>>> receive message body (12964 bytes). Error Code=message line is too long
>>> 21:04:07.560 3 SMTPI-020260(nm29-vm1.bullet.mail.gq1.yahoo.com
>>> <http://yahoo.com/>) failed
>>> to receive message body (14835 bytes). Error Code=message line is too
>>> long
>>> 21:05:23.167 3 SMTPI-020262(nm3-vm7.bullet.mail.gq1.yahoo.com
>>> <http://yahoo.com/>) failed to
>>> receive message body (3742 bytes). Error Code=message line is too long
>>> 21:08:18.474 3 SMTPI-020268(nm9-vm2.bullet.mail.gq1.yahoo.com
>>> <http://yahoo.com/>) failed to
>>> receive message body (4159 bytes). Error Code=message line is too long
>>>
>>> What OS are you using? I am on CentOS 5.11 x86_64
>>>
>>> Taylor Telephone Systems, Inc <http://www.taylortelephone.com/>
>>
>> This doesn’t look like your connection with Yahoo is actually using
>> TLS (or at least your mail server doesn’t think it is). Are you using
>> a firewall that is configured to inspect your mail traffic (Cisco ASA,
>> etc.)?  If you telnet to port  25 on your mail gateway from an
>> external host what response do you get? It should look something like:
>>
>> prompt$ *telnet /mx.maildomain.com <http://mx.maildomain.com>/ 25*
>> Trying 111.111.1.11…
>> Connected to mx.maildomain.com <http://mx.maildomain.com>.
>> Escape character is '^]'.
>> 220 maildomain.com <http://maildomain.com> ESMTP is glad to see you!
>> *EHLO /myhostname.mydomain.com <http://myhostname.mydomain.com>/*
>> 250-maildomain.com <http://250-maildomain.com> we trust you
>> myhostname.mydomain.com <http://myhostname.mydomain.com>
>> 250-DSN
>> 250-SIZE 31457280
>> 250-STARTTLS
>> 250-AUTH LOGIN PLAIN
>> 250-ETRN
>> 250-TURN
>> 250-ATRN
>> 250-NO-SOLICITING
>> 250-HELP
>> 250-PIPELINING
>> 250 EHLO
>> *QUIT*
>> 221 maildomain.com <http://maildomain.com> maildomain.com
>> <http://maildomain.com> Mail Server SMTP closing connection
>> Connection closed by foreign host.
>>
>> Replace the server name and host name with the appropriate values.
>>
>> If you don’t see the STARTTLS command returned or it is returned with
>> something like “2-XXXXXXXXX” then your firewall is screwing with your
>> mail stream and preventing TLS communication so that it can inspect
>> the contents of the message. This inspection is on by default on most
>> Cisco firewalls. This is normally appropriate for SMTP connections to
>> or from clients behind a firewall, where they are trying to bypass
>> your mail gateway, but not for the mail gateway itself. You would need
>> to configure a separate (non-default) inspection rule for your mail
>> server.
>>
>
>
> #############################################################
> This message is sent to you because you are subscribed to
>   the mailing list <CGatePro@mail.stalker.com>.
> To unsubscribe, E-mail to: <CGatePro-off@mail.stalker.com>
> To switch to the DIGEST mode, E-mail to <CGatePro-digest@mail.stalker.com>
> To switch to the INDEX mode, E-mail to <CGatePro-index@mail.stalker.com>
> Send administrative queries to  <CGatePro-request@mail.stalker.com>
>

Subscribe (FEED) Subscribe (DIGEST) Subscribe (INDEX) Unsubscribe Mail to Listmaster