Okay this is my last email for today on this.. ;-)

I was able to do this other emails, so I don't think it has anything to
do with the header I included here.. In fact I was able to do it with an
email I sent from Powermail to myself, so it would have most of the
"Powermail-only generated headers"....

I also tried it with a variety of email sizes and was able to reproduce
it on anything from a .2k email to a 175k email so I don't think size has
anything to do with it either..

I also tried aborting it at the "connect to mail.xxxx.xxx" message and
the "sending N message to mail.xxx.xxx" message and it made no
difference... Though, oddly, ocassionally an email would manage to get
through, when I tried it a few more times it would eventually hang like
all the others... So I do NOT think this problem is email specific...

- Greg

>Sorry for so many emails on this subject....  I can definitely recreate
>part of this by doing the following:
>
>When "Connecting to mail.xxxx.xxx" status is up, disconnect from the
>internet...  Then close Powermail.. It will complain (rightfully so)
>about being connected...
>
>The next time powermail starts up, it will attempt to connect and send
>this emails...  
>
>All of this behaves correctly... But, what I think is going on is
>_something_ inside of Powermail is not correctly toggling whatever bits
>are used to keep track of if an email is being sent or not.. 
>
>I notice that if the email is properly aborted the icon changes to an
>"alarm clock" type of icon... If it is trying to send it, it looks like a
>lightning bolt...  When I experience this problem the suspect messages
>all have lightning bolts for their icons, indicating to me that something
>has toggle the bit saying "hey, we're sending this message now", even
>though the actual steps necessary to send it are not getting kicked off -
>or somehow did not get "reset" back to a different status based on some
>error which occurred during the transfer (SMTP server timeout for
example?)...
>
>.....  you know what... I think I just figured out the "bug"......
>
>It seems to croak on certain types of emails, with the following headers
>(the total message size is usually about 20k):
>
>------------------ RFC822 Header Follows ------------------
>Return-Path: <[EMAIL PROTECTED]>
>Delivered-To: [EMAIL PROTECTED]
>Received: (qmail 37528 invoked from network); 20 May 2003 19:49:20 -0000
>Received: from unknown (HELO www.runrev.com) (64.23.0.192)
>  by net-virtual.com with SMTP; 20 May 2003 19:49:20 -0000
>Received: from www.runrev.com (IDENT:[EMAIL PROTECTED]
>[127.0.0.1])
>       by www.runrev.com (8.9.3/8.9.3) with ESMTP id OAA03159;
>       Tue, 20 May 2003 14:29:28 -0400
>Date: Tue, 20 May 2003 14:29:28 -0400
>Message-Id: <[EMAIL PROTECTED]>
>From: [EMAIL PROTECTED]
>Subject: use-revolution digest, Vol 1 #1373 - 17 msgs
>X-Mailer: Mailman v2.0.8
>MIME-version: 1.0
>Content-type: text/plain
>To: [email protected]
>Sender: [EMAIL PROTECTED]
>Errors-To: [EMAIL PROTECTED]
>X-BeenThere: [email protected]
>X-Mailman-Version: 2.0.8
>Precedence: bulk
>Reply-To: [email protected]
>X-Reply-To: [email protected]
>List-Help: <mailto:[EMAIL PROTECTED]>
>List-Post: <mailto:[email protected]>
>List-Subscribe: <http://lists.runrev.com/mailman/listinfo/use-revolution>,
>       <mailto:[EMAIL PROTECTED]>
>List-Id: How to use Revolution <use-revolution.lists.runrev.com>
>List-Unsubscribe: <http://lists.runrev.com/mailman/listinfo/use-revolution>,
>       <mailto:[EMAIL PROTECTED]>
>List-Archive: <http://lists.runrev.com/pipermail/use-revolution/>
>-----------------------------------------------------------
>
>To reproduce this problem 100% of the time:
>
>Step #1: Reply to/redirect an email which was received with headers
>similar to the above.  During the send "cancel" it.
>Step #2: Now send another email.  Notice now no emails are sending out of
>the system..
>
>
>It is notable that sending/replying to/redirecting other emails and
>performing the above 2 steps does NOT cause this lock situation... So
>either it is something in this email header or the email itself (unlikely
>because the email is basically pure text)...
>
>I hope this helps, I just stumbled across it....
>
>I can't debug this further because I can't figure out how to manually add
>headers to an outgoing email -- is it possible?...
>
>- Greg
>
>>I stand corrected on one point:
>>
>>Apparently this is NOT reproducable in the manner I specified below... 
>>It must have been a fluke that it failed so many times.. I just tried it
>>again and everything worked fine...
>>
>>- Greg
>>
>>>Marlyse,
>>>
>>>I really appreciate your help.. I will do the best I can to answer your
>>>questions...
>>>
>>>>I think it changed it's location. Was talking about the Immediately when
>>>>queued option. 
>>>>
>>>>So you have that ENabled? With other words, you compose a message and hit
>>>>send and it will close the message and automatically begin sending that
>>>>message? 
>>>
>>>Yes, I have that enabled.. If no messages are in my "Out Tray", it
>>>becomes bold and the message goes into a "Waiting" status...
>>>
>>>>
>>>>How come so many messages add up then in the Outbox? Still trying to get
>>>>a picture of your setup.
>>>
>>>Because when they enter the "Out Tray", they are stuck in this "waiting"
>>>status...  I was actually playing around trying to recreate this and I
>>>think I figured out a reliable way to recreate this problem: send an
>>>email and cancel the send before it is finished...  The message will be
>>>in a "Waiting" status and when you exit Powermail it will complain about
>>>"being connected"...  If you continue to send email, it will eventually
>>>get corrupted enough that you need to disable the outgoing queue in order
>>>to get things cleaned up...
>>>
>>>NOTE: I do NOT cancel my emails when they send...  But, it does try to
>>>send emails when I am downloading from other accounts, so perhaps it is
>>>unable to connect to the SMTP server because of POP3 traffic - but I am
>>>just speculating here...
>>>
>>>>
>>>>You have some settings where you could play around with and see if that
>>>>changes anything, namely: 
>>>>
>>>>"Retrieve/Send from/to multiple accounts" set it to NOT simultaneously
>>>>(under sheduling these options are). Sometimes sending simultaneously can
>>>>hang up an account and get stuff into an endless loop.
>>>
>>>Yeah, I have this set already....
>>>
>>>>
>>>>Are you continously on a connection, or dialing up each time when sending?
>>>
>>>I have a FreeBSD system which connects to the internet.. All of my
>>>computers connect through this central gateway... 
>>>
>>>NOTE: I am sure this is NOT the problem.. I do not experience problems
>>>with any other application on any of the systems which use this gateway/
>>>router to connect to the internet...  Though, the connection does go up
>>>and down - it is always up when I am checking/responding to email..
>>>
>>>>
>>>>The problem doesn't make sense to me - and the last time we had one of
>>>>these, it turned out to be something quite simple. Thus my questions for
>>>>details on the problem and your specific setup and which specific
>>>>situation creates the problem.
>>>
>>>It seems like a bug/poor design to me, but that's just my gut feeling....
>>>
>>>>
>>>>---marlyse
>


Reply via email to