Resolved SeaMonkey Send Mail With Attachment Fails

My Verizon mail account allows 8MB attachments. When I try to send a message with a large attachment, the transfer stops at about 2.5MB. My old Netscape did the same, but resumed after a delay. SeaMonkey displays a message blaming the connection to the SMTP server. The connection works fine for small or no attachments. Any ideas?

 

I did a thorough search, and found a lot of complaints about the Verizon issue . Read the question, and you will see that Verizon does not have a "real" answer. Most likely, it will work with Microsoft-based software, but even that guess is uncertain. I, personally, do not send mail with attachments of any size, whether using a mail program, nor webmail. One reason is because the person receiving the mail may have problems.

 

I just spent an hour with Verizon India and was able to upload a 5mb attachment with IE into Verizon Webmail. It is very slow at about 1MB a minute. Netscape and Seamonkey are faster, but get stuck at 2.5MB. Netscape recovers after a couple minutes, but Seamonkey gives up.

 

Ken,

Keep complaining to Verizon, as Westside pointed out, because there are a lot of SeaMonkey users who share the problem.

 

I just did a large attachment from Seamonkey directly into Verizon Webmail with out any problem other than it is slow. The problem appears to be confined to the Seamonkey mail software and it's inability to cope with Verizon interrupting the transfer. My old Netscape 7.2 could deal with it. Perhaps the root cause is a buffer on Verizon's input that can only handle 2.5MB.

 

It is no inability on the part of Seamonkey, but, rather, the inability of the ISP to accept anything which it does not care to accept. It is a common problem. For instance one could not get AOL music using Seamonkey, but one could use Firefox.
If you pay for a service, you have a right to be served. It, just, takes some minimal open mindedness on part of the ISP!

 

I did some analysis and I am posting for the benefit of the viewers that may not understand this issue. I used Outlook Express that allows the time out to be extended 60 sec. at a time and to view the transfer progress. Verizon DSL will accept the first 2.5MB at a 135kbps rate and then stops the transfer for about 4 minutes. When transfer resumes and through the remainder of the transfer, the rate is 10kbps which is far short of the advertised upload rate.

 

So, 8 MB are allowed, but how long it takes is a different story. I wonder what would happen if a 7.5 MB attachment would be broken up in three equal pieces, and how long it would take to send the entire thing. Also, would it matter to .zip the attachment?

 

Two 2.5MB attachments makes no difference. The Verizon input must just count bits, so a zipped file shouldn't help unless it is under 2.5MB. Verizon acts like it has a 2.5MB input register that accepts at the advertised rate until it is full.It then shuts down while it unloads at 10kbps. When there is sufficient space available, it accepts more input at the 10kbps output rate. I can input directly into their webmail, but only at the 10kbps rate. Netscape7.2 would wait forever, Outlook express times out after 1 min. but allows one to extend the time 1 min. at a time for as long as it takes. Seamonkey times out and claims the connection was lost with no options.

 

Ken,
your question interested me, quite a bit, not per se, because I, rarely, if ever, send attachments, but because my wireless company, Alltel, has been purchased by Verizon, which is beginning a push, in the area, to get into the Internet business. Here, high speed internet is handled by Cox Cable, and Qwest DSL. I have all my telecommunication services with Cox, which I prefer, since it is not Microsoft-centric.
To satisfy myself that Cox is fine, and that I can use, successfully, alternate programs, I decided to try to send a message with a single 9MB attachment (the limit is 20MB with Cox). I, immediately, found out that sending .exe or .exe.paf (of portable programs) was not permitted, for security reasons, as told by the Cox techs. But, I was advised to .zip the files if I had only such files. It was good to know, because .zip files could be sent, using Thunderbird or Seamonkey. So, Verizon is a bummer. You can tell them that Cox can send files larger than the upper limit of Verizon. I am using medium speed cable, with Win98SE, so it does not do it like a ball of fire, but, at 20-40 kbps I can't complain.

 

I am sure that you will find that when interacting with Verizon-India, they have no idea that their mail port acts as I described.

 

For what it's worth, I just sent all 4 of my e-mail addresses a 13.5MB attachment using SeaMonkey. It took appx. 7½ minutes (I played solitaire so I wouldn't waste my time testing this) using AT&T. And, it took appx. 3¾ minutes to download the message in SeaMonkey. I don't have the Super Speed, but the middle-of-the-road 1.5\384.

So, I'm guessing it has to be a Verizon thing. Curiously, only one of my mail accounts rejected it as being too large.

 

Your ISP appears to accept a long slow transfer or small enough gulps that SeaMonkey doesn't time out. Verizon accepts a large fast gulp and then stops the transfer while digesting, so SeaMonkey times out. It is a Verizon problem that I get around by using Outlet Express only when I need to send a large attachment. Not often.

 

SeaMonkey Mail and Verizon

I started a thread on this issue some weeks ago and now have new information.
The problem is Verizon interupts the transfer of large files and then SeaMonkey times out with no way to complete the transfer.
Using Outlook Express, I changed the outgoing Verizon port from 25 to 587 and I now can transfer large files without intervention.
How can I likewise change the SeaMonkey properties?

I found the edit function for the SMTP settings and now SeaMonkey is well.