Hello Thomas et al

Attachment problem fixed. There must have been some relevent file corruption. What and where I cannot say. No virus' found but reloading the operating system (overwriting the OS) fixed the problem. Of course you then need to reload everything else but I can once again send emails with attachments with the email program of choice PEGASUS. Thank you for your time and help. This fix may be one you can add to the tool box.

Regards

Jonathan Berry

Hello All

For no reason I can ascertain PMAIL has has stopped and wont send attachments.

I get the following message-

Connection Timeout (no response from host)

[*] Connection established to 211.29.132.250
>> 0094 220 mail04.syd.optusnet.com.au ESMTP Sendmail 8.13.1/8.13.1; Thu, 31 Jul 2008 16:25:49 +1000
<< 0020 EHLO [192.168.0.1]
>> 0119 250-mail04.syd.optusnet.com.au Hello c122-108-196-53.rochd4.qld.optusnet.com.au [122.108.196.53], pleased to meet you
>> 0025 250-ENHANCEDSTATUSCODES
>> 0016 250-PIPELINING
>> 0014 250-8BITMIME
>> 0019 250-SIZE 10485760
>> 0009 250-DSN
>> 0010 250-ETRN
>> 0022 250-AUTH PLAIN LOGIN
>> 0014 250-STARTTLS
>> 0015 250-DELIVERBY
>> 0010 250 HELP
<< 0052 MAIL FROM:<savewater@greywater.com.au> SIZE=288920
>> 0053 250 2.1.0 <savewater@greywater.com.au>... Sender ok
<< 0037 RCPT TO:<jonathan@greywater.com.au>
>> 0055 250 2.1.5 <jonathan@greywater.com.au>... Recipient ok
<< 0006 DATA
>> 0050 354 Enter mail, end with "." on a line by itself

I have been reading threads on similar issues but am getting nowhere.

I can send the attachments using outlook but I prefer pegasus.

Does anyone have a simple solution for this???

Thank you in advance.

Regards

Jonathan

Connection Timeout (no response from host)

First increase the timeout in File | Network configuration | (Sending) SMTP to something like 90-120 seconds.  If this does not work you may have a packet fragmentation problem.  The POP3/SMTP transmissions may fail if the MTU packet size is so large that a packet is fragmented.  In many cases the receiving system router blocks the receiving servers "packets fragmented" response to the sending system using "MTU Discovery".  These oversize packets are not accepted and so are resent.  This results in a timeout, generally at the end of the message transmission but it can be anywhere in the process.  You need to reduce the MTU size. Windows defaults to a 1500 MTU and many routers and DSL connections need 1492.  You might simply want to turn off the MTU Discovery operation.

You might want to get a copy of SG TCP Optimizer that I find quite handy.  http://www.speedguide.net/downloads.php  This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers.  If will also make it easy to adjust the MTU. 

And finally, does this computer, by chance, happen to have an NVidia NForce 4 chipset on the motherboard?  If so, many other have had this exact problem, and it turned out to be an optimization setting for the built in NIC which caused the problems with packet fragmentation. Disabling the advanced optimization capability called "checksum offload" made all the problems of sending SMTP mail via WinPMail disappear.

Hello Thomas

I have read your previous responses to similar problems such as mine and changed the timeout to 120 and more seconds.

I have used the SG TCP Optimizer and changes the MTU to a lower value. I have disabled the checksum offload on th TCP-IP.

All to no avail. The wierd thing is I haven't changed anything and Pegasus has been running on this computer with no problem for years.

Sending large attachments happily. Otyher email programs will do it. but Pegasus has stopped. I'm still getting the same error message as shown previously.

I have reloaded the program on a different drive but the problem persists.

If you have any other ideas please let me know. Thank you.

Reagrds

Jonathan

Turn off the MTU discovery completely and try again. 

Hello Thomas

MTU Discovery is turned off but I still can't send attachments.

Regards

Jonathan

The yuo have some low level TCP error I have never seen before.  There are generally only two things that cause this sort of problem; a low timeout and/or a packet fragmentation.  This could also be the mail server itself I guess but I doubt it.  The only thing I can tell you to do is setup a GMail account and then send via the GMail account.  If you still have the problem then it's on your end.  If yuo do not then it's on their end.

Here's the basic setup for using Pegasus Mail with GMail when yuo have turned on the POP3 and/or IMAP4.

(a) -POP3-

  Server host name: pop.gmail.com
  User name: <your_user_name>@gmail.com
  Password: <your_password>
  Server TCP/IP port: 995
  SSL/TLS: via direct SSL connect
  Enable server certificate fingerprint tracking: checked

(b) -SMTP STARTTLS -

  Server host name: smtp.gmail.com
  Server TCP/IP port: 587
  SSL/TLS: via STARTTLS
  Enable server certificate fingerprint tracking: checked
  SMTP Authentication: Login to the SMTP server using POP3
  username/password (the GMAIL-POP3-definition has been chosen)

(c) - SMTP via SSL -

  Server host name: smtp.gmail.com
  Server TCP/IP port: 465
  SSL/TLS: via direct ssl connection
  Enable server certificate fingerprint tracking: unchecked
  SMTP Authentication: Login to the SMTP server using POP3
  username/password (the GMAIL-POP3-definition has been chosen)

(d) - IMAP4 via SSL -

  Server host name: imap.gmail.com
  User name: <your_user_name>@gmail.com
  Password: <your_password>
  Server TCP/IP port: 993
  SSL/TLS: via direct SSL connect