Hi!

I am a novice but as I saw that someone even has 2 active antivirus ... maybe you have a Malwarebytes Antimalware as.
I say this because sometimes I feel my problems. Especially your web module.

Cheers and have a nice day!!![:D]

Not a new issue - maybe a few months worth. Not bad if I don't send any attachments, but then a big problem.

Using Pegasus 4.63 and Win XP SP3.  Firewall is Comodo 5.10+.  Anti-Virus is Avast 6.0137+/-.  I use four different identities in Pegasus, and do POP3  email via gmail. Have done so for "years."

Problem started some months back and is intermittent but serious. Frequently when sending with attachments, especially large ones, Pegasus starts to send, but then stops. Usually within 5 seconds or less, never more than 15 seconds.  I've reset my timeout lengths to 60 or 120 seconds - way longer than it takes prior to the error showing. Both on Internet General tab and SMTP General tab.

Error description is Connection timeout (no response from host). The Trace "always" ends:

<< 0006 DATA
>> 0033 354 Go ahead xxxxxxxx.x  (string of numbers)

(I'm not posting the full Trace.  When I tried asking for help here a month or two back I was told that the trace exposes email and password in hex format.  I had to change passwords.)

I've reset my SMTP stuff MULTIPLE times!!!! TLS and SSL and back again many times with variations of the authentication options.

Sometimes it works, but at times I can't send - every time it fails.  I have to delete the queued email, close,  Pegasus and then retry. Sometimes time after time, sometimes it then works right away.

I just did a test. A simple email sent OK AFTER I emptied the queue.

Then I sent with an attachment (a pdf file).  After three seconds of sending, the error came up.  I've now spent over an hour trying to send off three emails with attachments just under 3 Meg in size - way under gmail's 25 Meg limit. (Should have taken a minute or two.)  One sent.  The other two have had the repeated error after error.  VERY FRUSTRATING.  I'll send this, then reboot the computer and see if that helps.

Thanks.

Rich

> Error description is Connection timeout (no response from host). The Trace "always" ends:
> << 0006 DATA
> >> 0033 354 Go ahead xxxxxxxx.x  (string of numbers)
>
> (I'm not posting the full Trace.  When I tried asking for help here a
> month or two back I was told that the trace exposes email and password
> in hex format.  I had to change passwords.)
>
> I've reset my SMTP stuff MULTIPLE times!!!! TLS and SSL and back again
> many times with variations of the authentication options.

We really need to see more of that session log, just munge the hex strings so that you username and password are not sent in Base64 in response to the AUTH command.


FWIW, this does not look like any sort of username and password problem but make sure you set the TCP/IP timeout in the SMTP setup to around 180 seconds to give the host plenty of time to respond.

 

OK- here is the censored Trace with x's - did I do it OK, for you and for me?

>> 0014 250 STARTTLS
<< 0010 STARTTLS
>> 0030 220 2.0.0 Ready to start TLS
<< 0022 EHLO [192.168.1.100]
>> 0050 250-mx.google.com at your service, [24.8.231.71]
>> 0019 250-SIZE 35882577
>> 0014 250-8BITMIME
>> 0029 250-AUTH LOGIN PLAIN XOAUTH
>> 0025 250 ENHANCEDSTATUSCODES
<< 0012 AUTH LOGIN
>> 0018 334 xxxxxxxxxxxx
<< 0018 c3Bsxxxxxxxxxxxx
>> 0018 334 xxxxxxxxxxx
<< 0014 bW9uxxxxxxxx
>> 0020 235 2.7.0 Accepted
<< 0047 MAIL FROM:<myemailaddress@gmail.com> SIZE=3256461
>> 0031 250 2.1.0 OK xxxxxxxxxxxxxx.x
<< 0026 RCPT TO:<email address of target>
>> 0031 250 2.1.5 OK xxxxxxxxxxxxxx.x same as two lines up
<< 0006 DATA
>> 0032 354 Go ahead xxxxxxxxxxxxxx.x same as two lines up

Thomas, when I do get this "hang" in queue, do I have to delete the email in "Final Form?" Does that Final Form include the Security aspects?  Or can I leave it in queue while I try other settings or reboots or whatever?

I changed the the SMTP Timeout setting from 120 to 180 seconds.  But I get the error from Pegasus in maybe 3 or 5 or 10 seconds, usually.

Rich

I just changed Security (again!) to SSL, per Google's settings page at:

http://support.google.com/mail/bin/answer.py?hl=en&answer=13287

My send of an attachment failed again.  Here is the SSL trace:

This is with Security ar SSL

[*] Connection established to 173.194.77.109
>> 0042 220 mx.google.com ESMTP d9sm4540076obq.0
<< 0022 EHLO [192.168.1.100]
>> 0050 250-mx.google.com at your service, [24.8.231.71]
>> 0019 250-SIZE 35882577
>> 0014 250-8BITMIME
>> 0029 250-AUTH LOGIN PLAIN XOAUTH
>> 0025 250 ENHANCEDSTATUSCODES
<< 0012 AUTH LOGIN
>> 0018 334 VXNlcm5hbWU6
<< 0018 XXXXX
>> 0018 334 UGFzc3dvcmQ6
<< 0014 XXXXX
>> 0020 235 2.7.0 Accepted
<< 0047 MAIL FROM:<my email address> SIZE=3256462
>> 0031 250 2.1.0 OK d9sm4540076obq.0
<< 0026 RCPT TO:<target address>
>> 0031 250 2.1.5 OK d9sm4540076obq.0
<< 0006 DATA
>> 0032 354 Go ahead d9sm4540076obq.0

I sure hope somebody there can help - this is really stopping me.  Is it Google or Pegasus or me or another program?  I used to send even large attachments without a care, and they always went just fine. Other than repeatedly checking/changing my Security settings AFTER I had problems, I don't know of any changes that would have caused the issues.

Thanks.

Rich

> I just changed Security (again!) to SSL, per Google's settings page at:
> http://support.google.com/mail/bin/answer.py?hl=en&answer=13287
>
> My send of an attachment failed again.  Here is the SSL trace:
> This is with Security ar SSL
>
>
> Connection established to 173.194.77.109
> >> 0042 220 mx.google.com ESMTP d9sm4540076obq.0
> << 0022 EHLO  [192.168.1.100]
> >> 0050 250-mx.google.com at your service, [24.8.231.71]
> >> 0019 250-SIZE 35882577
> >> 0014 250-8BITMIME
> >> 0029 250-AUTH LOGIN PLAIN XOAUTH
> >> 0025 250 ENHANCEDSTATUSCODES
> << 0012 AUTH LOGIN
> >> 0018 334 VXNlcm5hbWU6
> << 0018 XXXXX
> >> 0018 334 UGFzc3dvcmQ6
> << 0014 XXXXX
> >> 0020 235 2.7.0 Accepted
> << 0047 MAIL FROM:<my email address> SIZE=3256462
> >> 0031 250 2.1.0 OK d9sm4540076obq.0
> << 0026 RCPT TO:<target address>
> >> 0031 250 2.1.5 OK d9sm4540076obq.0
> << 0006 DATA
> >> 0032 354 Go ahead d9sm4540076obq.0

Is this the entire session log?  There is nothing at all going on and no error messages at all.  The server is saying go ahead and send and then nothing at all.  If the TCP/Ip connection failed to respond then Pegasus Mail would show some sort of timeout.  

>
> I sure hope somebody there can help - this is really stopping me.  Is
> it Google or Pegasus or me or another program?  

I doubt if it is GMail since from the part we can see it is accepting your connection.  

It's probably not Pegasus Mail itself either since I have no problems at all with Pegasus Mail and GMail servers.

This looks like some sort of TCP/IP problem, especially if you have anything between Pegasus Mail and the GMail SMTP host.

> I used to send even large attachments without a care, and they always
> went just fine. Other than repeatedly checking/changing my Security
> settings AFTER I had problems, I don't know of any changes that would
> have caused the issues.

Probably something outside of Pegasus Mail and GMail, but I would really like to see a session log up to the point of failure showing an error message of some sort.. 

> Thomas, when I do get this "hang" in queue, do I have to delete the

email in "Final Form?"
> Does that Final Form include the Security

aspects?  Or can I leave it in queue while I try
> other settings or

reboots or whatever?

The final form is just the RFC 2822 message body, it does not have any of the transactions between Pegasus Mail and the SMTP host that you see before the DATA statement that the server sends when it is ready to receive the actual message.

BTW, have you tried using another SMTP host?  If you would send me a message to the e-mail address in my signature  I could provide you with a SMTP host for doing a test.

This could be an Avast Mail Shield configuration problem.  Mail Shield can't handle encryption so Avast must create its own secure connection and then relay the traffic.  If you have the Mail Shield feature of Avast enabled check to make sure the clients that require a secure connection are configured in the "SSL Accounts" section of the Mail Shield configuration.  There is an article on the Avast knowledgebase that might help:

 https://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=842&nav=0,64

This article refers to emails not being scanned but provides details on configuring SSL accounts in Mail Shield.

Those ARE the full Traces.    Sorry.  They struck me the same way - no clue as to a problem.  But I am just a simple user, so I have no way of knowing what it should be like. I have sent an email to Thomas about the other SMTP test aspect.

And the failures happen fast - often 3 or 4 seconds after I click Send.  I start to see percentages of mail sent, and then the error pops up.  Usually 3 to 5 seconds after Send.  Nowhere near any timeout setting that I can see.

I'll investigate the Avast aspect.  A very preliminary trial of just saying "don't scan outgoing messages" didn't seem to help, but I need to experiment further.  Maybe shut it off completely as a test.  It may be the SSL issues. I need to read that and try it.  Then I'll post results. Thanks to Brian for the link.  Could it also be the Comodo Firewall in some way, or is Avast more likely, and so first priority?

Rich

> Could it also be the Comodo Firewall in some way, or is Avast more likely, and so first priority?

Yes it could be either and for testing I would bypass both initially.  If it works then try turning on one and then the other to see wich one is doing the blocking.   I do use Avast! but my Avast! does not check any of my Pegasus Mail or Mercury directories nor my mail connections to/from the outside world.  

FWIW, It's never a good idea to be checking the outbound mail anyway, if it catches a virus outbound then your system is already infected.

using 2 AntiVirus at the same time especially turning on the protection could create what I called "positive problem" :). So it would be better to switch off one of the AV