That fixed it.  I had this problem once before with my old q mail rocks
install.  That time it was my fault messing around with the queue while
it was running.  Not sure what caused it this time.

You're showing your age now!

Cheers all thanks for all your efforts.

CJ

Eric Shubert wrote:
> Ok CJ. I really like Max Smart though, from the old TV series. Used to
> watch it all the time.
>
> Anywise, try this:
> # qmailctl stop
> # queue_repair.py -r
> # qmailctl start
>
> I think you'll like it.
>
> Please report the output of the queue_repair.py command. I think
> you'll see some errors fixed there.
>
> Maxwell Smart wrote:
>> Sounds good.
>> FWIW I just did a telnet to my IMAP and it worked as expected with no
>> delays.
>>
>> It's actually CJ Eric, Maxwell Smart is an alias that just stuck from
>> Win95 days. :)
>>
>> Eric Shubert wrote:
>>> Hey Max,
>>>
>>> I'm working this with someone else who appears to have the same
>>> symptoms. It's still a mystery, but we're testing some things out.
>>> We'll let you know when we find something, hopefully soon.
>>>
>>> Maxwell Smart wrote:
>>>> I am not quite sure what I am looking for so here goes.  The first is
>>>> qmlog -f imap  The second is qmlog -f smtp.  You can see the login to
>>>> send the email and the times are identical.  I then switched folders
>>>> causing it to login again and no mail.  I have checked a couple of
>>>> times
>>>> and no go.   I am flying blind here so if what I am posting is totally
>>>> irrelevant, point me in the right direction.
>>>>
>>>> 09-25 10:59:07 tcpserver: status: 2/40
>>>> 09-25 10:59:07 tcpserver: pid 27244 from 192.168.0.2
>>>> 09-25 10:59:07 tcpserver: ok 27244
>>>> laetitia.area510.net:192.168.0.80:143
>>>> :192.168.0.2::46756
>>>> 09-25 10:59:07 DEBUG: Connection, ip=[192.168.0.2]
>>>> 09-25 10:59:07 INFO: LOGIN, user...@yother.com, ip=[192.168.0.2],
>>>> protocol=IMAP
>>>> 09-25 11:00:08 tcpserver: status: 3/40
>>>> 09-25 11:00:08 tcpserver: pid 27356 from 192.168.0.2
>>>> 09-25 11:00:08 tcpserver: ok 27356
>>>> laetitia.area510.net:192.168.0.80:143
>>>> :192.168.0.2::46757
>>>> 09-25 11:00:08 DEBUG: Connection, ip=[192.168.0.2]
>>>> 09-25 11:00:08 INFO: LOGIN, user...@yother.com, ip=[192.168.0.2],
>>>> protocol=IMAP
>>>>
>>>> 09-25 10:59:07 tcpserver: pid 27234 from
>>>> 192.168.0.2                                                                
>>>>                                                         
>>>>
>>>> 09-25 10:59:07 tcpserver: ok 27234
>>>> laetitia.area510.net:192.168.0.80:25
>>>> :192.168.0.2::53340                                                        
>>>>                          
>>>>
>>>> 09-25 10:59:07 CHKUSER accepted sender: from
>>>> <c...@yother.com:c...@yother.com:> remote
>>>> <[192.168.0.86]:unknown:192.168.0.2> rcpt <> : sender
>>>> accepted                             09-25 10:59:07 CHKUSER accepted
>>>> rcpt: from
>>>> <c...@yother.com:c...@yother.com:> remote
>>>> <[192.168.0.86]:unknown:192.168.0.2> rcpt <c...@yother.com> : found
>>>> existing recipient         09-25 10:59:07 policy_check: local
>>>> c...@yother.com -> local c...@yother.com
>>>> (AUTHENTICATED
>>>> SENDER)                                                                    
>>>>           
>>>>
>>>> 09-25 10:59:07 policy_check: policy allows
>>>> transmission                                                               
>>>>                                                       
>>>>
>>>> 09-25 10:59:07
>>>> simscan:[27234]:RELAYCLIENT:0.0197s:-:192.168.0.2:c...@yother.com:c...@yother.com
>>>>                                                                            
>>>>      
>>>>
>>>> 09-25 10:59:07 tcpserver: end 27234 status 0
>>>>
>>>> Jake Vickers wrote:
>>>>> Eric Shubert wrote:
>>>>>> Maxwell Smart wrote:
>>>>>>> This would be monitoring the /var/log/qmail/imap/current file or
>>>>>>> looking at the contents in /var/log/qmail/imap correct?
>>>>>> # qmlog -f imap4
>>>>>> # qmlog -f imap4-ssl
>>>>>> (depending on which you use)
>>>>>>
>>>>>>> OK,  I'll follow up on both suggestions later.  I have some
>>>>>>> fabrication work that needs to get delivered.  For the moment it
>>>>>>> appears to be working albeit slower than I'd like.
>>>>>>>
>>>>>>> 2 quick questions.
>>>>>>> What file tells the update history?
>>>>>>> Is there an archive of older toaster rpms?
>>>>>> Providing you use qtp-newmodel to update, you'll find these
>>>>>> things in
>>>>>> /usr/src/qtp-upgrade/* directories. They should be pretty self
>>>>>> explanatory.
>>>>>>
>>>>> I have copies of older packages available here. If you let me know
>>>>> what version, I can check to see if I have it and make it
>>>>> available to
>>>>> you.
>>>>>
>>>>> (What does everyone think of an "archive" page of older versions of
>>>>> the packages? )
>>>>>
>>>>> ---------------------------------------------------------------------------------
>>>>>
>
>

---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
    Vickers Consulting Group offers Qmailtoaster support and installations.
      If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
     Please visit qmailtoaster.com for the latest news, updates, and packages.
     
      To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
     For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


Reply via email to