atom feed3 messages in com.googlegroups.gmail-help-pop-and-imap-enSOLUTION: Server Error 421, Error Num...
FromSent OnAttachments
BitBucketSep 6, 2006 9:03 pm 
wár17 §Sep 7, 2006 8:47 am 
BitBucketSep 8, 2006 5:50 pm 
Subject:SOLUTION: Server Error 421, Error Number: 0x800CCC67
From:BitBucket ()
Date:Sep 6, 2006 9:03:11 pm
List:com.googlegroups.gmail-help-pop-and-imap-en

PROBLEM

Using Gmail SMTP to send email from a client system using Outlook Express email client, the email client fails to send email from the Outbox queue, timing out with the error message: .................................................................................................... An unknown error has occurred. Subject 'Fw: Death wish', Account: 'BitBucket (gmail)', Server: 'smtp.gmail.com', Protocol: SMTP, Server Response: '421 4.7.0 Temporary System Problem. Try again later. q13sm6319122qbq', Port: 465, Secure(SSL): Yes, Server Error: 421, Error Number: 0x800CCC67 ....................................................................................................

Extending the timeout value from 1 minute to the maximum 5 minutes does not solve the problem. (Tools | Accounts | Account | Properties | Advanced | Server timeouts 1 minute --> 5 minutes) A search of the Gmail-POP-and-Forwarding forum yields no solutions. All SMTP settings are correct, and have been working up until this problem.

SOLUTION

Move the first message in the Outbox to the Drafts folder. The rest of the messages in the Outbox are then released, and SMTP works normally to send the client email.

DISCUSSION

It turned out that the first message in the queue, addressed to eight recipients, had a .wmv attachment of 7.05 MB. Even though this is under the nominal 10 MB Gmail limit, and would be under the limit even with some communication overhead, its transmission apparently timed out.

The upload speed of the internet connection on this client system is at least 35 KB/s steady state, and no other transmissions were in progress through the router or on the LAN. The upload should take no longer than 3.4 minutes. The actual timeout was measured with a stopwatch at 6:30, so it extended beyond the nominal 5 minutes allowed by Outlook Express. Perhaps a 10-minute limit in Outlook would have allowed the transmission.

There ia a way to increase the max server timeout value by modifying a registry key, ............................................................ http://www.x-setup.net/forum/showthread.php?p=4247#post4247

You'll have to set the following Registry values to the values you wish (in seconds):

HKCU\Identities\{Identity GUID}\Software\Microsoft\Internet Account Manager\Accounts\Account ID\ POP3 Timeout (DWORD) SMTP Timeout (DWORD ..........................................................

I didn't find the key under that branch. But I did find the SMTP Timeout registry value under the key:

HKEY_CURRENT_USER\Software\Microsoft\Internet Account Manager\Accounts\00000001

Current value 0x12C (300) --> 0x258 (600)

Also under:

HKEY_USERS\S-1-5-21-1343024091-1454471165-725345543-1003\Software\Microsoft\Internet Account Manager\Accounts\00000001

Setting either the SMTP Timeout value to 600 and the POP3 Timeout to 600 as well, and rebooting the client, still was not able to get past about 6:15 before the connection timed out. So perhaps Google itself has a hard shutoff timeout working here (although the client still indicated 5 minute timeout even after set to 10 minutes in registry).

There is no evidence of this being the problem in the error message, which lasted for at least 24 hours of attempts. It was only as an afterthought that I even moved the lead email, unlocking the Outbox queue.

-- Roy Zider

Windows XP Professional SP2 with current updates Outlook Express 6 6.00.2900.2180