You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Ajay Navgale <an...@gmail.com> on 2013/02/12 12:45:21 UTC
James Server SMTP Spooling Issue
Hi,
We are using james 3.0 beta4.
We have an issue while sending an email. There is always one outgoing mail
left in spool and is delivered when any new outgoing mail is to be sent.
Now previous mail gets delivered and this recent once sits in the spool.
This is happening for Remote delivery.
Can anyone throw some light on this.
Thanks & Regards,
Ajay
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Can you also inspect the MBeans located under org.apache.activemq.
The information you will find there may be more accurate as you will
directly go to ActiveMQ (this will allow to see if James has a bug).
Also, do you see any messsage in the log that could indicate an error
(can be related to MX record, rejection of the remote SMTP...) when
James tries to send out mails?
Thx, Eric
On 18/02/2013 14:09, Farooq Ahmed wrote:
> Hi Eric,
>
> More information on this...
> I run flush operation of mbean
> :org.apache.james:name=queue,queue=outgoing,type=component:
> after that size was 4 later i send one mail and now size reported was 5.
> but when i run operation browse it shows me details of only three mails.
>
> state of all is error
>
> Regards,
> Farooq
>
> On Mon, Feb 18, 2013 at 6:09 PM, Farooq Ahmed
> <fa...@centralogic.net>wrote:
>
>> Hi Eric,
>>
>> Here is the output which i get when i use Bean
>> org.apache.james:name=queue,queue=outgoing,type=component
>>
>> $>bean org.apache.james:name=queue,queue=outgoing,type=component
>> #bean is set to org.apache.james:name=queue,queue=outgoing,type=component
>> $>info
>> #mbean = org.apache.james:name=queue,queue=outgoing,type=component
>> #class name = org.apache.james.queue.library.MailQueueManagement
>> # attributes
>> %0 - Size (long, r)
>> # operations
>> %0 - java.util.List browse()
>> %1 - long clear()
>> %2 - long flush()
>> %3 - long removeWithName(java.lang.String p1)
>> %4 - long removeWithRecipient(java.lang.String p1)
>> %5 - long removeWithSender(java.lang.String p1)
>> #there's no notifications
>> $>get Size
>> #mbean = org.apache.james:name=queue,queue=outgoing,type=component:
>> Size = 7;
>>
>> Let me know if you need any further details.
>> can you educate me as to Size= 7 is the no of mails still in outgoing
>> spool or is some default size of outgoing queue.
>>
>> Also note that do deal with this spooling problem, the workaround that we
>> did temporarily is that we created an application that sends an email to
>> some email address every 30 sec.
>>
>> Regards,
>> Farooq
>>
>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>>
>>> Hi,
>>>
>>> Maybe the cloud's firewall blocks your requests.
>>>
>>> For JMX command line, type 'jmx cli' in google and experiment (tried one
>>> of these long time ago).
>>>
>>> Thx, Eric
>>>
>>>
>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>>> connection
>>>> method specified on http://james.apache.org/**
>>>> server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>> But i could not get connected to jmx on my email server.
>>>>
>>>> Note that the server where i have deployed james is on azure cloud PAS
>>>> network and is Ubunto system.
>>>> Is there any mechanism where i can observe the message queue contents on
>>>> local ubunto system using ssh only.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>>> ajay.navgale@centralogic.net
>>>>
>>>>> wrote:
>>>>>
>>>>
>>>>
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Eric Charles <er...@apache.org>
>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>> Subject: Re: James Server SMTP Spooling Issue
>>>>> To: James Users List <se...@james.apache.org>
>>>>>
>>>>>
>>>>> Hi,
>>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>>> After that, the latest one remains stucked in the queu?
>>>>>
>>>>> If such, that's very strange and we never saw that before.
>>>>> Do you use JMX to inspect the queue content/size?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> We are using james 3.0 beta4.
>>>>>> We have an issue while sending an email. There is always one outgoing
>>>>>> mail
>>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>>> sent.
>>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>>> spool.
>>>>>> This is happening for Remote delivery.
>>>>>>
>>>>>> Can anyone throw some light on this.
>>>>>>
>>>>>> Thanks & Regards,
>>>>>> Ajay
>>>>>>
>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>>
>>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
More information on this...
I run flush operation of mbean
:org.apache.james:name=queue,queue=outgoing,type=component:
after that size was 4 later i send one mail and now size reported was 5.
but when i run operation browse it shows me details of only three mails.
state of all is error
Regards,
Farooq
On Mon, Feb 18, 2013 at 6:09 PM, Farooq Ahmed
<fa...@centralogic.net>wrote:
> Hi Eric,
>
> Here is the output which i get when i use Bean
> org.apache.james:name=queue,queue=outgoing,type=component
>
> $>bean org.apache.james:name=queue,queue=outgoing,type=component
> #bean is set to org.apache.james:name=queue,queue=outgoing,type=component
> $>info
> #mbean = org.apache.james:name=queue,queue=outgoing,type=component
> #class name = org.apache.james.queue.library.MailQueueManagement
> # attributes
> %0 - Size (long, r)
> # operations
> %0 - java.util.List browse()
> %1 - long clear()
> %2 - long flush()
> %3 - long removeWithName(java.lang.String p1)
> %4 - long removeWithRecipient(java.lang.String p1)
> %5 - long removeWithSender(java.lang.String p1)
> #there's no notifications
> $>get Size
> #mbean = org.apache.james:name=queue,queue=outgoing,type=component:
> Size = 7;
>
> Let me know if you need any further details.
> can you educate me as to Size= 7 is the no of mails still in outgoing
> spool or is some default size of outgoing queue.
>
> Also note that do deal with this spooling problem, the workaround that we
> did temporarily is that we created an application that sends an email to
> some email address every 30 sec.
>
> Regards,
> Farooq
>
> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>
>> Hi,
>>
>> Maybe the cloud's firewall blocks your requests.
>>
>> For JMX command line, type 'jmx cli' in google and experiment (tried one
>> of these long time ago).
>>
>> Thx, Eric
>>
>>
>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>> connection
>>> method specified on http://james.apache.org/**
>>> server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>> But i could not get connected to jmx on my email server.
>>>
>>> Note that the server where i have deployed james is on azure cloud PAS
>>> network and is Ubunto system.
>>> Is there any mechanism where i can observe the message queue contents on
>>> local ubunto system using ssh only.
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>> ajay.navgale@centralogic.net
>>>
>>>> wrote:
>>>>
>>>
>>>
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: Eric Charles <er...@apache.org>
>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>> Subject: Re: James Server SMTP Spooling Issue
>>>> To: James Users List <se...@james.apache.org>
>>>>
>>>>
>>>> Hi,
>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>> After that, the latest one remains stucked in the queu?
>>>>
>>>> If such, that's very strange and we never saw that before.
>>>> Do you use JMX to inspect the queue content/size?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> We are using james 3.0 beta4.
>>>>> We have an issue while sending an email. There is always one outgoing
>>>>> mail
>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>> sent.
>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>> spool.
>>>>> This is happening for Remote delivery.
>>>>>
>>>>> Can anyone throw some light on this.
>>>>>
>>>>> Thanks & Regards,
>>>>> Ajay
>>>>>
>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>> >
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>> >
>>>>
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi Farooq,
It can be a bug in James or a specific to your settings/env.
I can't do much regarding your specifics.
I am now working to have a better stress test coverage of James (with
MPT, Postage...)
Thx, Eric
On 11/03/2013 07:05, Farooq Ahmed wrote:
> Hi Eric,
>
> were you able to get hold of the issue. Can i be of any help to share any
> further details..
>
> Regards,
> Farooq
>
> On Thu, Mar 7, 2013 at 4:37 PM, Farooq Ahmed
> <fa...@centralogic.net>wrote:
>
>> Hi Eric,
>>
>> There are error emails(with invalid email id but valid smtp server).
>> My observation is when i send emails to gmail with non existing ids gmail
>> replies with error saying.
>>
>> "INFO | jvm 1 | 2013/03/07 10:33:24 | INFO 10:33:24,410 |
>> james.mailetcontext | Permanent exception delivering mail
>> (Mail1362652364324-f93c8d53-d32e-4310-8f9f-5788b46b87b7-to-gmail.com.
>> RemoteHost said: ( abc123abc123abc1231111@gmail.com - [550-5.1.1 The
>> email account that you tried to reach does not exist.
>>
>> But there are other email providers which does not respond like gmail when
>> mail is sent to non existing ids on there server.Instead only spooling
>> message is logged as i said earlier.
>>
>> Also outgoing queue contains messages which are deliverable and still
>> getting stuck and gets delivered with a large delay...following is the
>> header of such an email.
>>
>> Delivered-To: farooq.ahmed.sse@gmail.com
>> Received: by 10.112.147.138 with SMTP id tk10csp25276lbb;
>> Wed, 6 Mar 2013 10:40:34 -0800 (PST)
>> X-Received: by 10.182.177.101 with SMTP id cp5mr18241284obc.69.1362595224373;
>> Wed, 06 Mar 2013 10:40:24 -0800 (PST)
>> Return-Path: <fa...@zoduka.com>
>> Received: from localhost ([168.63.166.176])
>> by mx.google.com with ESMTP id w6si32635824obc.207.2013.03.06.10.40.22;
>> Wed, 06 Mar 2013 10:40:23 -0800 (PST)
>> Received-SPF: neutral (google.com: 168.63.166.176 is neither permitted nor denied by best guess record for domain of farooq@zoduka.com) client-ip=168.63.166.176;
>> Authentication-Results: mx.google.com;
>> spf=neutral (google.com: 168.63.166.176 is neither permitted nor denied by best guess record for domain of farooq@zoduka.com) smtp.mail=farooq@zoduka.com
>> Return-Path: <fa...@zoduka.com>
>> MIME-Version: 1.0
>> X-UserIsAuth: true
>> Received: from 122.169.117.98 (EHLO [192.168.1.8]) ([122.169.117.98])
>> by huhokadevmail (JAMES SMTP Server ) with ESMTPA ID 185995668
>> for <fa...@gmail.com>;
>> Wed, 06 Mar 2013 01:54:46 +0000 (UTC)
>> Message-ID: <51...@zoduka.com>
>> Date: Wed, 06 Mar 2013 19:24:48 +0530
>> From: farooq_zoduka <fa...@zoduka.com>
>> User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
>> To: Farooq Ahmed <fa...@gmail.com>
>> Subject: test 7:25
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>> Content-Transfer-Encoding: 7bit
>>
>>
>> Conclusion:
>> ------------------
>> Condition Result outgoing queue status invalid email server no mail
>> delivered no messages in outgoing queue. invalid email id exception with
>> gmail ids,
>> with others we tested mails gets spooled outgoing queue size increases
>> and even valid mail
>> gets stuck and delivered with large delay
>>
>> Regards,
>> Farooq
>>
>>
>> On Thu, Mar 7, 2013 at 3:06 PM, Eric Charles <er...@apache.org> wrote:
>>
>>> Are you sure the mails in the outgoing queue are 'deliverable' mails
>>> (there is a remote SMTP ready to receive them)?
>>>
>>> Thx, Eric
>>>
>>> On 07/03/2013 08:13, Farooq Ahmed wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> "Could it be that the mail you send to the non-existing id bounce back
>>>> from
>>>> the remote smtp, and that your mailet config send them again to the
>>>> remote
>>>> SMTP, and so on... "
>>>> I get following INFO message only in "smtpserver.log" when ever we send
>>>> mails to invalid emaild ids.No error no bounce information is logged by
>>>> James.
>>>>
>>>> INFO 14:07:21,331 | james.smtpserver | Id='632328207' User='
>>>> test4@zoduka.com' Successfully spooled mail
>>>> Mail1362492441321-ccbd5501-**6777-42c5-9164-c143c9487c3f from
>>>> test4@zoduka.comon xxx.xxx.xxx.xx/xxx.xxx.xxx.xx for [
>>>> b3bd918c-a03a-453d-901b-**bdce5fd0969a@rediffmail.com<b3...@rediffmail.com>
>>>> ]
>>>>
>>>> Also
>>>> "bouncing so many times that your outgoing queue is overloaded?"
>>>> We initially sent few 100 emails to incorrect ids and then we stopped
>>>> after
>>>> stopping what ever was the count of outgoing queue its same after that it
>>>> only increases when we send a new email to valid id. So there seems no
>>>> matter of outgoing queue getting overloaded. But yes there is some thing
>>>> which is waiting to get complete to send emails.
>>>>
>>>> and we have no custom mailets to handle bounced mails nor we have
>>>> customized smtpserver.conf to handle bounce emails.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Thu, Mar 7, 2013 at 1:15 PM, Eric Charles <er...@apache.org> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> Could it be that the mail you send to the non-existing id bounce back
>>>>> from
>>>>> the remote smtp, and that your mailet config send them again to the
>>>>> remote
>>>>> SMTP, and so on... bouncing so many times that your outgoing queue is
>>>>> overloaded?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>>
>>>>> On 06/03/2013 12:27, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>>
>>>>>> Here is the test scenario.
>>>>>> I have created a new instance of James and the only difference between
>>>>>> the
>>>>>> earlier instance and this one is that earlier instance uses java 1.7
>>>>>> and
>>>>>> this one uses java 1.6 , else every thing is same.
>>>>>>
>>>>>> With this difference also i am able to reproduce the issue.
>>>>>>
>>>>>> Initially i sent emails to valid email ids and emails were getting
>>>>>> delivered as expected.
>>>>>> Later i sent email to multiple ids which does not exist, though there
>>>>>> mail
>>>>>> providers were valid.
>>>>>>
>>>>>> e.g SomeUniqueID@vsnl.net,
>>>>>> SomeUniqueID@rediffmail.com etc
>>>>>>
>>>>>> After next day i checked bean
>>>>>> org.apache.james:name=queue,****queue=outgoing,type=component
>>>>>>
>>>>>> and there were many mails all having "state = error;".
>>>>>> Now today mail are getting spooled and not delivered, though i can
>>>>>> instantly receiving emails but outgoing emails are getting stucked in
>>>>>> queue.
>>>>>>
>>>>>> I am using james3beta4.
>>>>>> Let me know if you can reproduce using same version.
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> Hi Farooq,
>>>>>>
>>>>>>>
>>>>>>> Unfortunately, I can not reproduce it.
>>>>>>> Any chance for you to write a Java unit test that shows this?
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 25/02/2013 05:25, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>>>
>>>>>>>> Any further info on this, this issue is still unresolved..
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>>>>>>>> <fa...@centralogic.net>******wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>> We do use to restart the system after that the spooled mails are
>>>>>>>>
>>>>>>>> delivered
>>>>>>>>> and after restart first mail is sent out with out getting stuck in
>>>>>>>>> outgoing
>>>>>>>>> queue but from second mail onwards one mail always keeps stuck in
>>>>>>>>> outgoing
>>>>>>>>> queue.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Did you already tried a stop/start of James to see if those
>>>>>>>>> numbers
>>>>>>>>>
>>>>>>>>> change?
>>>>>>>>>>
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>>>>>>>> Queue(ActiveMQ)
>>>>>>>>>>> and
>>>>>>>>>>> Size is also 2 in name=queue,queue=outgoing,******
>>>>>>>>>>> **type=component
>>>>>>>>>>> (james)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The only logical relation that i can see between ActiveMQ and
>>>>>>>>>>> James
>>>>>>>>>>> is
>>>>>>>>>>> the
>>>>>>>>>>> outgoing queue size in both is 2. Where as there are no messages
>>>>>>>>>>> in
>>>>>>>>>>> List
>>>>>>>>>>> returned by james bean and ActiveMQ bean shows one message in
>>>>>>>>>>> queue.
>>>>>>>>>>>
>>>>>>>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>>>>>>>> configuration
>>>>>>>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we
>>>>>>>>>>> dont
>>>>>>>>>>> store copy of sent mails.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Farooq
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Farooq,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Looking at Destination=outgoing,Type=**********Queue, the
>>>>>>>>>>>> EnqueueCount/DequeueCount/**********QueueSize seem odd (14976 -
>>>>>>>>>>>> 14975 <>
>>>>>>>>>>>>
>>>>>>>>>>>> 2).
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Can you link/find some logic between those ActiveMQ numbers and
>>>>>>>>>>>> the
>>>>>>>>>>>> numbers shown in the James MBeans?
>>>>>>>>>>>>
>>>>>>>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any
>>>>>>>>>>>> changes
>>>>>>>>>>>> in
>>>>>>>>>>>> the configuration?
>>>>>>>>>>>>
>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Here you go..
>>>>>>>>>>>>> Attributes Value
>>>>>>>>>>>>> BeanName ConsumerCount
>>>>>>>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>>>>>>>> EnqueueCount
>>>>>>>>>>>>> browse
>>>>>>>>>>>>> Destination=ActiveMQ.DLQ,Type=**********Queue 0 0
>>>>>>>>>>>>> 1
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 Shows 1 message in
>>>>>>>>>>>>> outgoing queue,
>>>>>>>>>>>>> invalid recepient
>>>>>>>>>>>>> Destination=outgoing,Type=**********Queue 10 5
>>>>>>>>>>>>> 2
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 14976
>>>>>>>>>>>>>
>>>>>>>>>>>>> 14975 shows 1 message
>>>>>>>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>>>>>>>> Destination=spool,Type=Queue 2 3 0 15146
>>>>>>>>>>>>> 15146
>>>>>>>>>>>>> no emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********TempQueue,Type=Topic
>>>>>>>>>>>>> 1
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 0 146 no
>>>>>>>>>>>>> emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Queue,Type=Topic 0
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0
>>>>>>>>>>>>> 0 6 no emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Producer.Queue.spool,**
>>>>>>>>>>>>> **
>>>>>>>>>>>>> Type=**
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****Topic
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 0 0 3 no emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Producer.Queue.**
>>>>>>>>>>>>> outgoing,****
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Type=**Topic
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 0 0 0 5 no emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Consumer.Queue.spool,**
>>>>>>>>>>>>> **
>>>>>>>>>>>>> Type=**
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****Topic
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 0 0 253212 no emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Consumer.Queue.**
>>>>>>>>>>>>> outgoing,****
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Type=**Topic
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Connection,Type=Topic
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 0 0 1 no
>>>>>>>>>>>>> emails
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we
>>>>>>>>>>>>> send
>>>>>>>>>>>>> every 30 sec..
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Farooq
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>> All, except the first and the last ones.
>>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Which mbean of activemq would you like me to check
>>>>>>>>>>>>> from
>>>>>>>>>>>>> the
>>>>>>>>>>>>> following ...
>>>>>>>>>>>>> org.apache.activemq:__**********
>>>>>>>>>>>>> BrokerName=james,__**
>>>>>>>>>>>>> ConnectorName=tcp_//localhost_**********__0,Type=Connector
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.Connection,**********__Type=Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__**********Queue.outgoing,Type=***
>>>>>>>>>>>>> *Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__**********Queue.spool,Type=Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.Producer.__**********Queue.outgoing,Type=***
>>>>>>>>>>>>> *Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.Producer.__**********Queue.spool,Type=Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.Queue,Type=**********__Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.Advisory.TempQueue,_**********_Type=Topic
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _outgoing,Type=Queue
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> _spool,Type=Queue
>>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>>> BrokerName=james,Type=Broker
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Farooq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>>>>>>>> eric@apache.org
>>>>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any chance to compare those numbers with the
>>>>>>>>>>>>> ones
>>>>>>>>>>>>> given by
>>>>>>>>>>>>> the activemq
>>>>>>>>>>>>> mbeans?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>
>>>>>>>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx
>>>>>>>>>>>>> cli,
>>>>>>>>>>>>>
>>>>>>>>>>>>> "You mean to 'push out' the queue.
>>>>>>>>>>>>> The mail you send triggers the pending
>>>>>>>>>>>>> mails to
>>>>>>>>>>>>> go
>>>>>>>>>>>>> out?"
>>>>>>>>>>>>>
>>>>>>>>>>>>> Yes this new mail push the earlier mail out
>>>>>>>>>>>>> but
>>>>>>>>>>>>> itself
>>>>>>>>>>>>> gets stuck in
>>>>>>>>>>>>> spool,to which a new mail after 30 sec
>>>>>>>>>>>>> pushes
>>>>>>>>>>>>> out
>>>>>>>>>>>>> and
>>>>>>>>>>>>> that mail gets
>>>>>>>>>>>>> struck
>>>>>>>>>>>>> and soon...
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can you guide me how to figure out the
>>>>>>>>>>>>> reason
>>>>>>>>>>>>> as to
>>>>>>>>>>>>> why
>>>>>>>>>>>>> the size attribute
>>>>>>>>>>>>> value is 5 and the browse List only
>>>>>>>>>>>>> contains 3
>>>>>>>>>>>>> mails
>>>>>>>>>>>>> details.
>>>>>>>>>>>>> Also Why The mail which gets stuck in spool
>>>>>>>>>>>>> its
>>>>>>>>>>>>> count
>>>>>>>>>>>>> is
>>>>>>>>>>>>> incremented in
>>>>>>>>>>>>> attribure Size but its details are not
>>>>>>>>>>>>> present
>>>>>>>>>>>>> in
>>>>>>>>>>>>> browse
>>>>>>>>>>>>> List..?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Farooq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric
>>>>>>>>>>>>> Charles
>>>>>>>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Farooq,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here is the output which i get when
>>>>>>>>>>>>> i
>>>>>>>>>>>>> use
>>>>>>>>>>>>> Bean
>>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>>> ********
>>>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>>>
>>>>>>>>>>>>> $>bean
>>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>>> ********
>>>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> #bean is set to
>>>>>>>>>>>>> org.apache.james:name=queue,**
>>>>>>>>>>>>> queue=outgoing,type=component
>>>>>>>>>>>>> $>info
>>>>>>>>>>>>> #mbean =
>>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>>> ********
>>>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>>> #class name =
>>>>>>>>>>>>> org.apache.james.queue.****__***
>>>>>>>>>>>>> *******
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> library.MailQueueManagement
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> # attributes
>>>>>>>>>>>>> %0 - Size (long, r)
>>>>>>>>>>>>> # operations
>>>>>>>>>>>>> %0 - java.util.List browse()
>>>>>>>>>>>>> %1 - long clear()
>>>>>>>>>>>>> %2 - long flush()
>>>>>>>>>>>>> %3 - long
>>>>>>>>>>>>> removeWithName(java.lang.****_****
>>>>>>>>>>>>> ******_String
>>>>>>>>>>>>> p1)
>>>>>>>>>>>>> %4 - long
>>>>>>>>>>>>> removeWithRecipient(java.lang.**
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> ****__****String
>>>>>>>>>>>>> p1)
>>>>>>>>>>>>> %5 - long
>>>>>>>>>>>>> removeWithSender(java.lang.*****
>>>>>>>>>>>>> ****
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****__*String
>>>>>>>>>>>>>
>>>>>>>>>>>>> p1)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> #there's no notifications
>>>>>>>>>>>>> $>get Size
>>>>>>>>>>>>> #mbean =
>>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>>> ********
>>>>>>>>>>>>> __**queue=outgoing,type=__**********component:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Size = 7;
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Cool, it seems like you have found a
>>>>>>>>>>>>> JXM CLI
>>>>>>>>>>>>> which
>>>>>>>>>>>>> works fine.
>>>>>>>>>>>>> Which one is it?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Let me know if you need any further
>>>>>>>>>>>>> details.
>>>>>>>>>>>>>
>>>>>>>>>>>>> can you educate me as to Size= 7 is
>>>>>>>>>>>>> the
>>>>>>>>>>>>> no
>>>>>>>>>>>>> of
>>>>>>>>>>>>> mails still in outgoing
>>>>>>>>>>>>> spool
>>>>>>>>>>>>> or is some default size of outgoing
>>>>>>>>>>>>> queue.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is the number of pending
>>>>>>>>>>>>> mails in
>>>>>>>>>>>>> the
>>>>>>>>>>>>> queue.
>>>>>>>>>>>>>
>>>>>>>>>>>>> So you have 7 mails waiting to be sent
>>>>>>>>>>>>> to
>>>>>>>>>>>>> the
>>>>>>>>>>>>> outside world/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Also note that do deal with this
>>>>>>>>>>>>> spooling
>>>>>>>>>>>>> problem, the workaround that
>>>>>>>>>>>>> we
>>>>>>>>>>>>>
>>>>>>>>>>>>> did temporarily is that we created
>>>>>>>>>>>>> an
>>>>>>>>>>>>> application that sends an email to
>>>>>>>>>>>>> some email address every 30 sec.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> You mean to 'push out' the queue.
>>>>>>>>>>>>> The mail you send triggers the pending
>>>>>>>>>>>>> mails
>>>>>>>>>>>>> to go
>>>>>>>>>>>>> out?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Farooq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM,
>>>>>>>>>>>>> Eric
>>>>>>>>>>>>> Charles
>>>>>>>>>>>>> <eric@apache.org <mailto:
>>>>>>>>>>>>> eric@apache.org>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Maybe the cloud's firewall
>>>>>>>>>>>>> blocks
>>>>>>>>>>>>> your
>>>>>>>>>>>>> requests.
>>>>>>>>>>>>>
>>>>>>>>>>>>> For JMX command line, type 'jmx
>>>>>>>>>>>>> cli' in
>>>>>>>>>>>>> google and experiment (tried
>>>>>>>>>>>>> one
>>>>>>>>>>>>> of these long time ago).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 18/02/2013 10:11, Farooq
>>>>>>>>>>>>> Ahmed
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> I tried remotely connecting
>>>>>>>>>>>>> to
>>>>>>>>>>>>> JMX
>>>>>>>>>>>>> using
>>>>>>>>>>>>> Jconsole and remote jmx
>>>>>>>>>>>>> connection
>>>>>>>>>>>>> method specified on
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<__***
>>>>>>>>>>>>> *****
>>>>>>>>>>>>> **ht**tp://
>>>>>>>>>>>>> james.apache.org/****
>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org/****>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<*****
>>>>>>>>>>>>> *****
>>>>>>>>>>>>> ht__tp://
>>>>>>>>>>>>> james.apache.org/**__**server/********3/config-system.html<http://james.apache.org/**__**server/******3/config-system.html>
>>>>>>>>>>>>> <htt**p://james.apache.org/**__****server/****3/config-system.*
>>>>>>>>>>>>> *html<http://james.apache.org/**__**server/****3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <http:**//james.apache.org/**_**_****server/**3/config-system.*
>>>>>>>>>>>>> *html<http://james.apache.org/**__****server/**3/config-system.html>
>>>>>>>>>>>>> <http://james.apache.org/****__**server/**3/config-system.**
>>>>>>>>>>>>> html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://**james.apache.org/**_**
>>>>>>>>>>>>> **_**server/**3/config-system.****html<http://james.apache.org/**_**_**server/**3/config-system.**html>
>>>>>>>>>>>>> <http://james.apache.**org/**__**server/**3/config-**
>>>>>>>>>>>>> system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.org/****_**_**server/3/config-system.****
>>>>>>>>>>>>> html<http://james.apache.org/****__**server/3/config-system.**html>
>>>>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://**james.apache.org/**_**
>>>>>>>>>>>>>> ****_server/3/**config-system.****<http://james.apache.org/**_****_server/3/**config-system.**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> html <http://james.apache.org/**_****
>>>>>>>>>>>>> _server/3/**config-system.html<http://james.apache.org/**_**_server/3/**config-system.html>
>>>>>>>>>>>>> **>
>>>>>>>>>>>>> <http://james.apache.org/****_**_server/3/**config-system.****
>>>>>>>>>>>>> html<http://james.apache.org/****__server/3/**config-system.**html>
>>>>>>>>>>>>> <http://james.apache.org/****__server/3/**config-system.**html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **<http://james.apache.org/**_****_**server/3/config-system.*
>>>>>>>>>>>>> *html<http://james.apache.org/**_**_**server/3/config-system.html>
>>>>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> **<http://james.apache.org/**_**_**server/3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <
>>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> server/3/config-system.html<******ht**tp://
>>>>>>>>>>>>> james.apache.org/****** <http://james.apache.org/****>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <ht**tp://
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> james.apache.org/**_**** <http://james.apache.org/**_****>
>>>>>>>>>>>>> **** <http://james.apache.org/**_********<http://james.apache.org/**_******>
>>>>>>>>>>>>> <http://james.apache.org/****_****<http://james.apache.org/**_****>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> *_** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> _server/**3/config-system.********html<http://james.apache.**
>>>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>>> **** <http://james.apache.org/*******><
>>>>>>>>>>>>> http://james.apache.org/******* <http://james.apache.org/*****>
>>>>>>>>>>>>> <http://james.apache.org/***>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *__server/**3/config-system.********html<http://james.apache.
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *__server/**3/config-system.******html<http://james.apache.**
>>>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/**
>>>>>>>>>>>>> **__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <
>>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> server/**3/config-system.html<********
>>>>>>>>>>>>> http://james.apache.org/********<http://james.apache.org/******>
>>>>>>>>>>>>> <http://james.apache.**org/**** <http://james.apache.org/****>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/***
>>>>>>>>>>>>> *** <http://james.apache.org/****>
>>>>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> **<__http://james.apache.org/_**
>>>>>>>>>>>>>> ******_**server/**3/config-**<http://james.apache.org/_******_**server/**3/config-**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> system.**<http://james.apache.**org/_****_**server/**3/config-*
>>>>>>>>>>>>> *system.**<http://james.apache.org/_****_**server/**3/config-system.**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> **html<http://james.apache.****org/_**_**server/**3/config-**
>>>>>>>>>>>>>> system.**html<http://james.**apache.org/_**_**server/**3/**
>>>>>>>>>>>>>> config-system.**html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <http://james.apache.**org/__***
>>>>>>>>>>>>>> ***server/**3/config-**system.****
>>>>>>>>>>>>>> html<http://james.apache.org/_****_**server/**3/config-system.
>>>>>>>>>>>>>> ****<http://james.apache.org/_**_**server/**3/config-system.**>
>>>>>>>>>>>>>> html <http://james.apache.org/__****
>>>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>>>>> **>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <http://james.apache.org/_**_***
>>>>>>>>>>>>>>> ***server/**3/config-system.**html<http://james.apache.org/_**_****server/**3/config-system.html>
>>>>>>>>>>>>>>> <http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **<http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>>>>> <http://james.apache.org/_****_server/**3/config-system.**html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <**http://james.apache.org/__******server/**3/config-system.
>>>>>>>>>>>>>> **html<http://james.apache.org/__****server/**3/config-system.html>
>>>>>>>>>>>>>> <http://james.apache.org/_**_**server/**3/config-system.**html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **<http://james.apache.org/__****server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>>>> **<http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> **>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <
>>>>>>>>>>>>>> http://james.apache.org/**
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> server/**3/config-system.html<********
>>>>>>>>>>>>> http://james.apache.org/**** <http://james.apache.org/**>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/**
>>>>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> **>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**
>>>>>>>>>>>>>> http://james.apache.org/**_******<http://james.apache.org/**_****><
>>>>>>>>>>>>>> http://james.apache.org/**_****>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **** <http://james.apache.org/**_********<http://james.apache.org/**_******>
>>>>>>>>>>>>> <http://james.apache.org/****_****<http://james.apache.org/**_****>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> *_** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> _server/3/config-system.html<******h**ttp://james.apache.org/**
>>>>>>>>>>>>> **_** <http://james.apache.org/**_**>
>>>>>>>>>>>>> _**** <http://james.apache.org/**__******<http://james.apache.org/**__****>
>>>>>>>>>>>>>> <http://james.apache.org/*
>>>>>>>>>>>>> ***__** <http://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/**__*
>>>>>>>>>>>>> ***** <http://james.apache.org/**__****><
>>>>>>>>>>>>> http://james.apache.org/****__**<http://james.apache.org/**__**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**__**
>>>>>>>>>>>>> ** <http://james.apache.org/**__**>
>>>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <
>>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/***
>>>>>>>>>>>>> *** <http://james.apache.org/****>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**ht__tp://james.apache.org/**********server/__3/config-*
>>>>>>>>>>>>>> *system<http://james.apache.org/********server/__3/config-system>
>>>>>>>>>>>>>> .
>>>>>>>>>>>>>>
>>>>>>>>>>>>> ****html<http://james.apache.**org/******server/__3/config-**
>>>>>>>>>>>>> system.**html<http://james.apache.org/******server/__3/config-system.**html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.**org/******server/__3/config-**system.**
>>>>>>>>>>>>> html<http://james.apache.org/******server/__3/config-system.**
>>>>>>>>>>>>> html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.org/********server/__3/config-system.html<http://james.apache.org/******server/__3/config-system.html>
>>>>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> **>
>>>>>>>>>>>>>> **<http://james.apache.org/********server/__3/config-system.**
>>>>>>>>>>>>>> html<http://james.apache.org/******server/__3/config-system.html>
>>>>>>>>>>>>>> <http://james.apache.org/******server/__3/config-system.**html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <**http://james.apache.org/*****
>>>>>>>>>>>>>> *server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <
>>>>>>>>>>>>>> http://james.apache.org/**
>>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/***
>>>>>>>>>>>>> *** <http://james.apache.org/****>
>>>>>>>>>>>>> server/** <http://james.apache.org/****server/**<http://james.apache.org/**server/**>
>>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.**org/**server/**<http://james.apache.**
>>>>>>>>>>>>> org/server/** <http://james.apache.org/server/**>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> 3/config-system.html<http://******james.apache.org/server/3/***
>>>>>>>>>>>>> *<http://james.apache.org/**server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> config-system.html<http://**ja**mes.apache.org/server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>>>> config-system.html<http://**james.apache.org/server/3/**
>>>>>>>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> But i could not get
>>>>>>>>>>>>> connected to
>>>>>>>>>>>>> jmx
>>>>>>>>>>>>> on
>>>>>>>>>>>>> my email server.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Note that the server where i
>>>>>>>>>>>>> have
>>>>>>>>>>>>> deployed james is on azure
>>>>>>>>>>>>> cloud
>>>>>>>>>>>>> PAS
>>>>>>>>>>>>> network and is Ubunto
>>>>>>>>>>>>> system.
>>>>>>>>>>>>> Is there any mechanism
>>>>>>>>>>>>> where i
>>>>>>>>>>>>> can
>>>>>>>>>>>>> observe the message queue
>>>>>>>>>>>>> contents
>>>>>>>>>>>>> on
>>>>>>>>>>>>> local ubunto system using
>>>>>>>>>>>>> ssh
>>>>>>>>>>>>> only.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>> Farooq
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Feb 12, 2013 at
>>>>>>>>>>>>> 11:02
>>>>>>>>>>>>> PM,
>>>>>>>>>>>>> Ajay
>>>>>>>>>>>>> Navgale <
>>>>>>>>>>>>>
>>>>>>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>>>>>>> <mailto:ajay.navgale@******
>>>>>>>>>>>>> central**
>>>>>>>>>>>>> ogic.net <http://centralogic.net><ajay.******navgale@**
>>>>>>>>>>>>> centralogic.net<
>>>>>>>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>**
>>>>>>>>>>>>> **>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ---------- Forwarded
>>>>>>>>>>>>> message
>>>>>>>>>>>>> ----------
>>>>>>>>>>>>>
>>>>>>>>>>>>> From: Eric Charles <
>>>>>>>>>>>>> eric@apache.org
>>>>>>>>>>>>> <mailto:eric@apache.org
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Date: Tue, Feb 12, 2013
>>>>>>>>>>>>> at
>>>>>>>>>>>>> 7:52 PM
>>>>>>>>>>>>> Subject: Re: James
>>>>>>>>>>>>> Server
>>>>>>>>>>>>> SMTP
>>>>>>>>>>>>> Spooling Issue
>>>>>>>>>>>>> To: James Users List
>>>>>>>>>>>>> <
>>>>>>>>>>>>> server-user@james.apache.org
>>>>>>>>>>>>> <mailto:
>>>>>>>>>>>>> server-user@james.
>>>>>>>>>>>>> **
>>>>>>>>>>>>> apache.org <se...@james.apache.org>********>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>> You mean you the newly
>>>>>>>>>>>>> spooled
>>>>>>>>>>>>> mails
>>>>>>>>>>>>> 'push-out' the remaining
>>>>>>>>>>>>> ones.
>>>>>>>>>>>>> After that, the latest
>>>>>>>>>>>>> one
>>>>>>>>>>>>> remains
>>>>>>>>>>>>> stucked in the queu?
>>>>>>>>>>>>>
>>>>>>>>>>>>> If such, that's very
>>>>>>>>>>>>> strange
>>>>>>>>>>>>> and
>>>>>>>>>>>>> we
>>>>>>>>>>>>> never saw that before.
>>>>>>>>>>>>> Do you use JMX to
>>>>>>>>>>>>> inspect
>>>>>>>>>>>>> the
>>>>>>>>>>>>> queue
>>>>>>>>>>>>> content/size?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 12/02/2013 11:45,
>>>>>>>>>>>>> Ajay
>>>>>>>>>>>>> Navgale
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> We are using james
>>>>>>>>>>>>> 3.0
>>>>>>>>>>>>> beta4.
>>>>>>>>>>>>> We have an issue
>>>>>>>>>>>>> while
>>>>>>>>>>>>> sending
>>>>>>>>>>>>> an email. There is
>>>>>>>>>>>>> always
>>>>>>>>>>>>> one
>>>>>>>>>>>>> outgoing
>>>>>>>>>>>>> mail
>>>>>>>>>>>>> left in spool and is
>>>>>>>>>>>>> delivered
>>>>>>>>>>>>> when any new
>>>>>>>>>>>>> outgoing
>>>>>>>>>>>>> mail
>>>>>>>>>>>>> is
>>>>>>>>>>>>> to
>>>>>>>>>>>>> be
>>>>>>>>>>>>> sent.
>>>>>>>>>>>>> Now previous mail
>>>>>>>>>>>>> gets
>>>>>>>>>>>>> delivered
>>>>>>>>>>>>> and this recent once
>>>>>>>>>>>>> sits
>>>>>>>>>>>>> in
>>>>>>>>>>>>> the
>>>>>>>>>>>>> spool.
>>>>>>>>>>>>> This is happening
>>>>>>>>>>>>> for
>>>>>>>>>>>>> Remote
>>>>>>>>>>>>> delivery.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Can anyone throw
>>>>>>>>>>>>> some
>>>>>>>>>>>>> light on
>>>>>>>>>>>>> this.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>>> Ajay
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> __********--------------------**********--__--**
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --**
>>>>>>>>>>>>> --**
>>>>>>>>>>>>>
>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>>
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-unsubscribe@james.
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> **
>>>>>>>>>>>>> __********
>>>>>>>>>>>>> apache.org <
>>>>>>>>>>>>> http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-**unsubscribe@
>>>>>>>>>>>>> **__
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> **ja**
>>>>>>>>>>>>> mes.apache.org
>>>>>>>>>>>>> <http://mes.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http:/
>>>>>>>>>>>>>>
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> **/__
>>>>>>>>>>>>> james.apache.org
>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org>>
>>>>>>>>>>>>> <unsubscribe@
>>>>>>>>>>>>> **james.apache.__
>>>>>>>>>>>>> ****
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> **org
>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> unsubscribe@james.apache.org
>>>>>>>>>>>>> <mailto:
>>>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>>>> **
>>>>>>>>>>>>> apache.org <un...@james.apache.org>********>>__>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>>>> ***
>>>>>>>>>>>>>
>>>>>>>>>>>>> ***
>>>>>>>>>>>>>
>>>>>>>>>>>>> j**
>>>>>>>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**
>>>>>>>>>>>>>>
>>>>>>>>>>>>> unsubscribe@__james.apache.org
>>>>>>>>>>>>> <mailto:
>>>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>>>> **
>>>>>>>>>>>>> apache.org <un...@james.apache.org>********>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>>>> __*
>>>>>>>>>>>>>
>>>>>>>>>>>>> ***
>>>>>>>>>>>>>
>>>>>>>>>>>>> j**
>>>>>>>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>>>>>>>> <mailto:
>>>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>>>> **
>>>>>>>>>>>>> apache.org <un...@james.apache.org>**
>>>>>>>>>>>>> ******><server-user-__**
>>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>>>>> james.apache.org <server-user-__unsubscribe@****j**
>>>>>>>>>>>>> ames.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <mailto:server-user-
>>>>>>>>>>>>>>> **
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>>>>
>>>>>>>>>>>>> james.apache.org <server-user-unsubscribe@****jam**
>>>>>>>>>>>>> es.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> For additional
>>>>>>>>>>>>> commands,
>>>>>>>>>>>>> e-mail:
>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> __**
>>>>>>>>>>>>> **
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****org<
>>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>>> ****__*
>>>>>>>>>>>>> *****
>>>>>>>>>>>>>
>>>>>>>>>>>>> apach**e.org
>>>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>>>> http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>>> **__***
>>>>>>>>>>>>> ***
>>>>>>>>>>>>>
>>>>>>>>>>>>> apach**
>>>>>>>>>>>>> e.org
>>>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>>>> http://apache.org
>>>>>>>>>>>>>
>>>>>>>>>>>>> <
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>>>>
>>>>>>>>>>>>> ****
>>>>>>>>>>>>>
>>>>>>>>>>>>> apach**
>>>>>>>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>>>>>>>> user-help@james.__apache.org
>>>>>>>>>>>>> <mailto:
>>>>>>>>>>>>> server-user-help@**
>>>>>>>>>>>>> james.apache.org <server-user-help@james.******apac**he.org<
>>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>>> <server-user-help@james.****apac**he.org <http://apache.org><
>>>>>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> **
>>>>>>>>>>>>> __******----------------------**********--__--**
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --**
>>>>>>>>>>>>>
>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> server-user-unsubscribe@james.*
>>>>>>>>>>>>> ***
>>>>>>>>>>>>> ****
>>>>>>>>>>>>> **__******
>>>>>>>>>>>>> apache.org
>>>>>>>>>>>>> <http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> server-user-**unsubscribe@*****
>>>>>>>>>>>>> ***
>>>>>>>>>>>>> **ja**
>>>>>>>>>>>>>
>>>>>>>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>>>>>>>> <http://james.apache.org><****
>>>>>>>>>>>>> unsubscribe@__
>>>>>>>>>>>>> james.apache.org
>>>>>>>>>>>>> <mailto:unsubscribe@james.*****
>>>>>>>>>>>>> ***
>>>>>>>>>>>>> ap**
>>>>>>>>>>>>> ache.org<http://apache.org**>
>>>>>>>>>>>>> <unsubscribe@james.**apache.******org <http://apache.org> <
>>>>>>>>>>>>> unsubscribe@james.apache.org>******>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>>>> __*****
>>>>>>>>>>>>>
>>>>>>>>>>>>>> **
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *j**
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> unsubscribe@james.**
>>>>>>>>>>>>> apache.org <un...@james.apache.org>**
>>>>>>>>>>>>> ******><server-user-__**
>>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>>>>> james.apache.org <server-user-__unsubscribe@****j**
>>>>>>>>>>>>> ames.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>>>>
>>>>>>>>>>>>> james.apache.org <server-user-unsubscribe@****jam**
>>>>>>>>>>>>> es.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> For additional commands,
>>>>>>>>>>>>> e-mail:
>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.apache.***
>>>>>>>>>>>>> *****
>>>>>>>>>>>>> **__**
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****org<
>>>>>>>>>>>>> server-user-help@james.**__****
>>>>>>>>>>>>> *****
>>>>>>>>>>>>> *apach**
>>>>>>>>>>>>>
>>>>>>>>>>>>> e.org
>>>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>>>> http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> server-user-help@james.********
>>>>>>>>>>>>> **
>>>>>>>>>>>>> apach**__
>>>>>>>>>>>>>
>>>>>>>>>>>>> e.org
>>>>>>>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>>>>> <http://apache.org><server-****
>>>>>>>>>>>>> ******
>>>>>>>>>>>>> user-help@james.
>>>>>>>>>>>>> __apache.org
>>>>>>>>>>>>> <mailto:server-user-help@******
>>>>>>>>>>>>> **
>>>>>>>>>>>>> jam**
>>>>>>>>>>>>> es.apache.org <http://james.apache.org><******server-user-**
>>>>>>>>>>>>> help@james.apache.org <server-user-help@james.****apac**he.org<
>>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>>> <server-user-help@james.**apac**he.org <http://apache.org><
>>>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------**
>>>>>>>>>>>>> ********
>>>>>>>>>>>>> __****------------------------**********--__--**
>>>>>>>>>>>>>
>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> server-user-unsubscribe@james.****
>>>>>>>>>>>>> ******__****
>>>>>>>>>>>>> apache.org
>>>>>>>>>>>>> <http://apache.org><
>>>>>>>>>>>>> server-user-**unsubscribe@__****
>>>>>>>>>>>>> ****ja**
>>>>>>>>>>>>>
>>>>>>>>>>>>> mes.apache.org<
>>>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>>>> <mailto:unsubscribe@james.********ap**
>>>>>>>>>>>>> ache.org<
>>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>>> <unsubscribe@james.**apache.******org <http://apache.org> <
>>>>>>>>>>>>> unsubscribe@james.apache.org>******>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <server-user-__**unsubscribe@********james.apache.org<**
>>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>>>
>>>>>>>>>>>>> james.apache.org <un...@james.apache.org>****>
>>>>>>>>>>>>>> <server-user-_**_unsubscribe@******james.apache.org<**
>>>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>>>> james.apache.org <un...@james.apache.org>**>
>>>>>>>>>>>>>> <server-user-_**_unsubscribe@****james.apache.org<unsubscribe@
>>>>>>>>>>>>>> **james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <mailto:server-user-********
>>>>>>>>>>>>>>> unsubscr**
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ibe@james.apache.org <un...@james.apache.org>**
>>>>>>>>>>>>> ****<server-**
>>>>>>>>>>>>> user-unsubscribe@james.apache.********org<server-user-****
>>>>>>>>>>>>> unsubscribe@
>>>>>>>>>>>>> **
>>>>>>>>>>>>>
>>>>>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> server-user-help@james.apache.****
>>>>>>>>>>>>> ******__****org<
>>>>>>>>>>>>> server-user-help@james.*********
>>>>>>>>>>>>> *apach**__
>>>>>>>>>>>>> e.org<
>>>>>>>>>>>>>
>>>>>>>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>>>>> <http://apache.org>
>>>>>>>>>>>>> <server-user-help@james.__******
>>>>>>>>>>>>> **apac**
>>>>>>>>>>>>> he.org<
>>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>>> <mailto:server-user-help@********jam**
>>>>>>>>>>>>> es.apache.org<http://**james.****apache.org<http://james.**
>>>>>>>>>>>>> apache.org <http://james.apache.org>><
>>>>>>>>>>>>> http://james.apache.org>>
>>>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------**********
>>>>>>>>>>>>> __**--------------------------**********--__--**---------
>>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>> server-user-unsubscribe@james.**********__**
>>>>>>>>>>>>> apache.org
>>>>>>>>>>>>> <http://apache.org><server-*********
>>>>>>>>>>>>> *user-__unsubscribe@james.
>>>>>>>>>>>>> **
>>>>>>>>>>>>> apache.org <server-user-__unsubscribe@******j**ames.apache.org<
>>>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>>>> <server-user-__**unsubscribe@****james.apache.org<unsubscribe@*
>>>>>>>>>>>>> *james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> <mailto:server-user-********unsubscr**
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ibe@james.apache.org**<**unsubsc**ribe@james.apache.org**<
>>>>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <server-**user-unsubscribe@******james.apache.**org<server-**
>>>>>>>>>>>>>
>>>>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**
>>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> server-user-help@james.apache.********
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **__**org<server-user-help@**
>>>>>>>>>>>>> james.__apache.org
>>>>>>>>>>>>> <mailto:server-user-help@********jam**
>>>>>>>>>>>>> es.apache.org<
>>>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------****
>>>>>>>>>>>>> ******__----------------------****--
>>>>>>>>>>>>> **--**
>>>>>>>>>>>>> --**
>>>>>>>>>>>>> --__---------
>>>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.*
>>>>>>>>>>>>> ***
>>>>>>>>>>>>> ******__
>>>>>>>>>>>>> apache.org
>>>>>>>>>>>>> <mailto:server-user-********unsubscr**
>>>>>>>>>>>>> ibe@james.apache.org****
>>>>>>>>>>>>> **<
>>>>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>>>>> <server-**user-unsubscribe@******james.apache.**org<server-**
>>>>>>>>>>>>>
>>>>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**
>>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ****
>>>>>>>>>>>>>>
>>>>>>>>>>>>> __org
>>>>>>>>>>>>> <mailto:server-user-help@********jam**es.apache.org
>>>>>>>>>>>>> <http://**
>>>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------**********----------------------*
>>>>>>>>>>>>> *--**
>>>>>>>>>>>>> --**--**
>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**
>>>>>>>>>>>>> ********
>>>>>>>>>>>>> apache.org<
>>>>>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>>>> ****
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **
>>>>>>>>>>>>> **org<server-user-help@james.********apache.org<server-user-***
>>>>>>>>>>>>> *help@
>>>>>>>>>>>>> **
>>>>>>>>>>>>> james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ------------------------------**
>>>>>>>>>>>>> ********----------------------**--*
>>>>>>>>>>>>> *--**
>>>>>>>>>>>>> --**
>>>>>>>>>>>>>
>>>>>>>>>>>>> --**---------
>>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**********
>>>>>>>>>>>> apache.org<
>>>>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> server-user-help@james.apache.***
>>>>>>>>>>>>> ***
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****org<
>>>>>>>>>>>> server-user-help@james.******apach**e.org <http://apache.org> <
>>>>>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org><
>>>>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------**
>>>>>>>>>>>> ******------------------------**--**
>>>>>>>>>>>>
>>>>>>>>>>> --**
>>>>>>>>>>>
>>>>>>>>>>> --**---------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>>>> apache.org<
>>>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
were you able to get hold of the issue. Can i be of any help to share any
further details..
Regards,
Farooq
On Thu, Mar 7, 2013 at 4:37 PM, Farooq Ahmed
<fa...@centralogic.net>wrote:
> Hi Eric,
>
> There are error emails(with invalid email id but valid smtp server).
> My observation is when i send emails to gmail with non existing ids gmail
> replies with error saying.
>
> "INFO | jvm 1 | 2013/03/07 10:33:24 | INFO 10:33:24,410 |
> james.mailetcontext | Permanent exception delivering mail
> (Mail1362652364324-f93c8d53-d32e-4310-8f9f-5788b46b87b7-to-gmail.com.
> RemoteHost said: ( abc123abc123abc1231111@gmail.com - [550-5.1.1 The
> email account that you tried to reach does not exist.
>
> But there are other email providers which does not respond like gmail when
> mail is sent to non existing ids on there server.Instead only spooling
> message is logged as i said earlier.
>
> Also outgoing queue contains messages which are deliverable and still
> getting stuck and gets delivered with a large delay...following is the
> header of such an email.
>
> Delivered-To: farooq.ahmed.sse@gmail.com
> Received: by 10.112.147.138 with SMTP id tk10csp25276lbb;
> Wed, 6 Mar 2013 10:40:34 -0800 (PST)
> X-Received: by 10.182.177.101 with SMTP id cp5mr18241284obc.69.1362595224373;
> Wed, 06 Mar 2013 10:40:24 -0800 (PST)
> Return-Path: <fa...@zoduka.com>
> Received: from localhost ([168.63.166.176])
> by mx.google.com with ESMTP id w6si32635824obc.207.2013.03.06.10.40.22;
> Wed, 06 Mar 2013 10:40:23 -0800 (PST)
> Received-SPF: neutral (google.com: 168.63.166.176 is neither permitted nor denied by best guess record for domain of farooq@zoduka.com) client-ip=168.63.166.176;
> Authentication-Results: mx.google.com;
> spf=neutral (google.com: 168.63.166.176 is neither permitted nor denied by best guess record for domain of farooq@zoduka.com) smtp.mail=farooq@zoduka.com
> Return-Path: <fa...@zoduka.com>
> MIME-Version: 1.0
> X-UserIsAuth: true
> Received: from 122.169.117.98 (EHLO [192.168.1.8]) ([122.169.117.98])
> by huhokadevmail (JAMES SMTP Server ) with ESMTPA ID 185995668
> for <fa...@gmail.com>;
> Wed, 06 Mar 2013 01:54:46 +0000 (UTC)
> Message-ID: <51...@zoduka.com>
> Date: Wed, 06 Mar 2013 19:24:48 +0530
> From: farooq_zoduka <fa...@zoduka.com>
> User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
> To: Farooq Ahmed <fa...@gmail.com>
> Subject: test 7:25
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
>
>
> Conclusion:
> ------------------
> Condition Result outgoing queue status invalid email server no mail
> delivered no messages in outgoing queue. invalid email id exception with
> gmail ids,
> with others we tested mails gets spooled outgoing queue size increases
> and even valid mail
> gets stuck and delivered with large delay
>
> Regards,
> Farooq
>
>
> On Thu, Mar 7, 2013 at 3:06 PM, Eric Charles <er...@apache.org> wrote:
>
>> Are you sure the mails in the outgoing queue are 'deliverable' mails
>> (there is a remote SMTP ready to receive them)?
>>
>> Thx, Eric
>>
>> On 07/03/2013 08:13, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> "Could it be that the mail you send to the non-existing id bounce back
>>> from
>>> the remote smtp, and that your mailet config send them again to the
>>> remote
>>> SMTP, and so on... "
>>> I get following INFO message only in "smtpserver.log" when ever we send
>>> mails to invalid emaild ids.No error no bounce information is logged by
>>> James.
>>>
>>> INFO 14:07:21,331 | james.smtpserver | Id='632328207' User='
>>> test4@zoduka.com' Successfully spooled mail
>>> Mail1362492441321-ccbd5501-**6777-42c5-9164-c143c9487c3f from
>>> test4@zoduka.comon xxx.xxx.xxx.xx/xxx.xxx.xxx.xx for [
>>> b3bd918c-a03a-453d-901b-**bdce5fd0969a@rediffmail.com<b3...@rediffmail.com>
>>> ]
>>>
>>> Also
>>> "bouncing so many times that your outgoing queue is overloaded?"
>>> We initially sent few 100 emails to incorrect ids and then we stopped
>>> after
>>> stopping what ever was the count of outgoing queue its same after that it
>>> only increases when we send a new email to valid id. So there seems no
>>> matter of outgoing queue getting overloaded. But yes there is some thing
>>> which is waiting to get complete to send emails.
>>>
>>> and we have no custom mailets to handle bounced mails nor we have
>>> customized smtpserver.conf to handle bounce emails.
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Thu, Mar 7, 2013 at 1:15 PM, Eric Charles <er...@apache.org> wrote:
>>>
>>> Hi,
>>>>
>>>> Could it be that the mail you send to the non-existing id bounce back
>>>> from
>>>> the remote smtp, and that your mailet config send them again to the
>>>> remote
>>>> SMTP, and so on... bouncing so many times that your outgoing queue is
>>>> overloaded?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>>
>>>> On 06/03/2013 12:27, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>>
>>>>> Here is the test scenario.
>>>>> I have created a new instance of James and the only difference between
>>>>> the
>>>>> earlier instance and this one is that earlier instance uses java 1.7
>>>>> and
>>>>> this one uses java 1.6 , else every thing is same.
>>>>>
>>>>> With this difference also i am able to reproduce the issue.
>>>>>
>>>>> Initially i sent emails to valid email ids and emails were getting
>>>>> delivered as expected.
>>>>> Later i sent email to multiple ids which does not exist, though there
>>>>> mail
>>>>> providers were valid.
>>>>>
>>>>> e.g SomeUniqueID@vsnl.net,
>>>>> SomeUniqueID@rediffmail.com etc
>>>>>
>>>>> After next day i checked bean
>>>>> org.apache.james:name=queue,****queue=outgoing,type=component
>>>>>
>>>>> and there were many mails all having "state = error;".
>>>>> Now today mail are getting spooled and not delivered, though i can
>>>>> instantly receiving emails but outgoing emails are getting stucked in
>>>>> queue.
>>>>>
>>>>> I am using james3beta4.
>>>>> Let me know if you can reproduce using same version.
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org>
>>>>> wrote:
>>>>>
>>>>> Hi Farooq,
>>>>>
>>>>>>
>>>>>> Unfortunately, I can not reproduce it.
>>>>>> Any chance for you to write a Java unit test that shows this?
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 25/02/2013 05:25, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>>
>>>>>>> Any further info on this, this issue is still unresolved..
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>>>>>>> <fa...@centralogic.net>******wrote:
>>>>>>>
>>>>>>>
>>>>>>> We do use to restart the system after that the spooled mails are
>>>>>>>
>>>>>>> delivered
>>>>>>>> and after restart first mail is sent out with out getting stuck in
>>>>>>>> outgoing
>>>>>>>> queue but from second mail onwards one mail always keeps stuck in
>>>>>>>> outgoing
>>>>>>>> queue.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Did you already tried a stop/start of James to see if those
>>>>>>>> numbers
>>>>>>>>
>>>>>>>> change?
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>>>>>>> Queue(ActiveMQ)
>>>>>>>>>> and
>>>>>>>>>> Size is also 2 in name=queue,queue=outgoing,******
>>>>>>>>>> **type=component
>>>>>>>>>> (james)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The only logical relation that i can see between ActiveMQ and
>>>>>>>>>> James
>>>>>>>>>> is
>>>>>>>>>> the
>>>>>>>>>> outgoing queue size in both is 2. Where as there are no messages
>>>>>>>>>> in
>>>>>>>>>> List
>>>>>>>>>> returned by james bean and ActiveMQ bean shows one message in
>>>>>>>>>> queue.
>>>>>>>>>>
>>>>>>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>>>>>>> configuration
>>>>>>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we
>>>>>>>>>> dont
>>>>>>>>>> store copy of sent mails.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Farooq
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Farooq,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Looking at Destination=outgoing,Type=**********Queue, the
>>>>>>>>>>> EnqueueCount/DequeueCount/**********QueueSize seem odd (14976 -
>>>>>>>>>>> 14975 <>
>>>>>>>>>>>
>>>>>>>>>>> 2).
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Can you link/find some logic between those ActiveMQ numbers and
>>>>>>>>>>> the
>>>>>>>>>>> numbers shown in the James MBeans?
>>>>>>>>>>>
>>>>>>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any
>>>>>>>>>>> changes
>>>>>>>>>>> in
>>>>>>>>>>> the configuration?
>>>>>>>>>>>
>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Here you go..
>>>>>>>>>>>> Attributes Value
>>>>>>>>>>>> BeanName ConsumerCount
>>>>>>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>>>>>>> EnqueueCount
>>>>>>>>>>>> browse
>>>>>>>>>>>> Destination=ActiveMQ.DLQ,Type=**********Queue 0 0
>>>>>>>>>>>> 1
>>>>>>>>>>>>
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 0 Shows 1 message in
>>>>>>>>>>>> outgoing queue,
>>>>>>>>>>>> invalid recepient
>>>>>>>>>>>> Destination=outgoing,Type=**********Queue 10 5
>>>>>>>>>>>> 2
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 14976
>>>>>>>>>>>>
>>>>>>>>>>>> 14975 shows 1 message
>>>>>>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>>>>>>> Destination=spool,Type=Queue 2 3 0 15146
>>>>>>>>>>>> 15146
>>>>>>>>>>>> no emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********TempQueue,Type=Topic
>>>>>>>>>>>> 1
>>>>>>>>>>>>
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 0 0 146 no
>>>>>>>>>>>> emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Queue,Type=Topic 0
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>> 0
>>>>>>>>>>>> 0 6 no emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Producer.Queue.spool,**
>>>>>>>>>>>> **
>>>>>>>>>>>> Type=**
>>>>>>>>>>>>
>>>>>>>>>>>> ****Topic
>>>>>>>>>>>>
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>> 0 0 0 3 no emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Producer.Queue.**
>>>>>>>>>>>> outgoing,****
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Type=**Topic
>>>>>>>>>>>>
>>>>>>>>>>>> 0 0 0 0 5 no emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Consumer.Queue.spool,**
>>>>>>>>>>>> **
>>>>>>>>>>>> Type=**
>>>>>>>>>>>>
>>>>>>>>>>>> ****Topic
>>>>>>>>>>>>
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>> 0 0 0 253212 no emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Consumer.Queue.**
>>>>>>>>>>>> outgoing,****
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Type=**Topic
>>>>>>>>>>>>
>>>>>>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Connection,Type=Topic
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>> 0
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 0 0 1 no
>>>>>>>>>>>> emails
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we
>>>>>>>>>>>> send
>>>>>>>>>>>> every 30 sec..
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Farooq
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>> All, except the first and the last ones.
>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>
>>>>>>>>>>>> Which mbean of activemq would you like me to check
>>>>>>>>>>>> from
>>>>>>>>>>>> the
>>>>>>>>>>>> following ...
>>>>>>>>>>>> org.apache.activemq:__**********
>>>>>>>>>>>> BrokerName=james,__**
>>>>>>>>>>>> ConnectorName=tcp_//localhost_**********__0,Type=Connector
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.Connection,**********__Type=Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__**********Queue.outgoing,Type=***
>>>>>>>>>>>> *Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__**********Queue.spool,Type=Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.Producer.__**********Queue.outgoing,Type=***
>>>>>>>>>>>> *Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.Producer.__**********Queue.spool,Type=Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.Queue,Type=**********__Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.Advisory.TempQueue,_**********_Type=Topic
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _outgoing,Type=Queue
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>>> ******
>>>>>>>>>>>> _spool,Type=Queue
>>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>>> BrokerName=james,Type=Broker
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Farooq
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>>>>>>> eric@apache.org
>>>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Any chance to compare those numbers with the
>>>>>>>>>>>> ones
>>>>>>>>>>>> given by
>>>>>>>>>>>> the activemq
>>>>>>>>>>>> mbeans?
>>>>>>>>>>>>
>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>
>>>>>>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx
>>>>>>>>>>>> cli,
>>>>>>>>>>>>
>>>>>>>>>>>> "You mean to 'push out' the queue.
>>>>>>>>>>>> The mail you send triggers the pending
>>>>>>>>>>>> mails to
>>>>>>>>>>>> go
>>>>>>>>>>>> out?"
>>>>>>>>>>>>
>>>>>>>>>>>> Yes this new mail push the earlier mail out
>>>>>>>>>>>> but
>>>>>>>>>>>> itself
>>>>>>>>>>>> gets stuck in
>>>>>>>>>>>> spool,to which a new mail after 30 sec
>>>>>>>>>>>> pushes
>>>>>>>>>>>> out
>>>>>>>>>>>> and
>>>>>>>>>>>> that mail gets
>>>>>>>>>>>> struck
>>>>>>>>>>>> and soon...
>>>>>>>>>>>>
>>>>>>>>>>>> Can you guide me how to figure out the
>>>>>>>>>>>> reason
>>>>>>>>>>>> as to
>>>>>>>>>>>> why
>>>>>>>>>>>> the size attribute
>>>>>>>>>>>> value is 5 and the browse List only
>>>>>>>>>>>> contains 3
>>>>>>>>>>>> mails
>>>>>>>>>>>> details.
>>>>>>>>>>>> Also Why The mail which gets stuck in spool
>>>>>>>>>>>> its
>>>>>>>>>>>> count
>>>>>>>>>>>> is
>>>>>>>>>>>> incremented in
>>>>>>>>>>>> attribure Size but its details are not
>>>>>>>>>>>> present
>>>>>>>>>>>> in
>>>>>>>>>>>> browse
>>>>>>>>>>>> List..?
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Farooq
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric
>>>>>>>>>>>> Charles
>>>>>>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Farooq,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Here is the output which i get when
>>>>>>>>>>>> i
>>>>>>>>>>>> use
>>>>>>>>>>>> Bean
>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>> ********
>>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>>
>>>>>>>>>>>> $>bean
>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>> ********
>>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> #bean is set to
>>>>>>>>>>>> org.apache.james:name=queue,**
>>>>>>>>>>>> queue=outgoing,type=component
>>>>>>>>>>>> $>info
>>>>>>>>>>>> #mbean =
>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>> ********
>>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>> #class name =
>>>>>>>>>>>> org.apache.james.queue.****__***
>>>>>>>>>>>> *******
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> library.MailQueueManagement
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> # attributes
>>>>>>>>>>>> %0 - Size (long, r)
>>>>>>>>>>>> # operations
>>>>>>>>>>>> %0 - java.util.List browse()
>>>>>>>>>>>> %1 - long clear()
>>>>>>>>>>>> %2 - long flush()
>>>>>>>>>>>> %3 - long
>>>>>>>>>>>> removeWithName(java.lang.****_****
>>>>>>>>>>>> ******_String
>>>>>>>>>>>> p1)
>>>>>>>>>>>> %4 - long
>>>>>>>>>>>> removeWithRecipient(java.lang.**
>>>>>>>>>>>> ****
>>>>>>>>>>>> ****__****String
>>>>>>>>>>>> p1)
>>>>>>>>>>>> %5 - long
>>>>>>>>>>>> removeWithSender(java.lang.*****
>>>>>>>>>>>> ****
>>>>>>>>>>>>
>>>>>>>>>>>> ****__*String
>>>>>>>>>>>>
>>>>>>>>>>>> p1)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> #there's no notifications
>>>>>>>>>>>> $>get Size
>>>>>>>>>>>> #mbean =
>>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>>> ********
>>>>>>>>>>>> __**queue=outgoing,type=__**********component:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Size = 7;
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Cool, it seems like you have found a
>>>>>>>>>>>> JXM CLI
>>>>>>>>>>>> which
>>>>>>>>>>>> works fine.
>>>>>>>>>>>> Which one is it?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Let me know if you need any further
>>>>>>>>>>>> details.
>>>>>>>>>>>>
>>>>>>>>>>>> can you educate me as to Size= 7 is
>>>>>>>>>>>> the
>>>>>>>>>>>> no
>>>>>>>>>>>> of
>>>>>>>>>>>> mails still in outgoing
>>>>>>>>>>>> spool
>>>>>>>>>>>> or is some default size of outgoing
>>>>>>>>>>>> queue.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> It is the number of pending
>>>>>>>>>>>> mails in
>>>>>>>>>>>> the
>>>>>>>>>>>> queue.
>>>>>>>>>>>>
>>>>>>>>>>>> So you have 7 mails waiting to be sent
>>>>>>>>>>>> to
>>>>>>>>>>>> the
>>>>>>>>>>>> outside world/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Also note that do deal with this
>>>>>>>>>>>> spooling
>>>>>>>>>>>> problem, the workaround that
>>>>>>>>>>>> we
>>>>>>>>>>>>
>>>>>>>>>>>> did temporarily is that we created
>>>>>>>>>>>> an
>>>>>>>>>>>> application that sends an email to
>>>>>>>>>>>> some email address every 30 sec.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> You mean to 'push out' the queue.
>>>>>>>>>>>> The mail you send triggers the pending
>>>>>>>>>>>> mails
>>>>>>>>>>>> to go
>>>>>>>>>>>> out?
>>>>>>>>>>>>
>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Farooq
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM,
>>>>>>>>>>>> Eric
>>>>>>>>>>>> Charles
>>>>>>>>>>>> <eric@apache.org <mailto:
>>>>>>>>>>>> eric@apache.org>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Maybe the cloud's firewall
>>>>>>>>>>>> blocks
>>>>>>>>>>>> your
>>>>>>>>>>>> requests.
>>>>>>>>>>>>
>>>>>>>>>>>> For JMX command line, type 'jmx
>>>>>>>>>>>> cli' in
>>>>>>>>>>>> google and experiment (tried
>>>>>>>>>>>> one
>>>>>>>>>>>> of these long time ago).
>>>>>>>>>>>>
>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 18/02/2013 10:11, Farooq
>>>>>>>>>>>> Ahmed
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> I tried remotely connecting
>>>>>>>>>>>> to
>>>>>>>>>>>> JMX
>>>>>>>>>>>> using
>>>>>>>>>>>> Jconsole and remote jmx
>>>>>>>>>>>> connection
>>>>>>>>>>>> method specified on
>>>>>>>>>>>>
>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<__***
>>>>>>>>>>>> *****
>>>>>>>>>>>> **ht**tp://
>>>>>>>>>>>> james.apache.org/****
>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org/****>
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<*****
>>>>>>>>>>>> *****
>>>>>>>>>>>> ht__tp://
>>>>>>>>>>>> james.apache.org/**__**server/********3/config-system.html<http://james.apache.org/**__**server/******3/config-system.html>
>>>>>>>>>>>> <htt**p://james.apache.org/**__****server/****3/config-system.*
>>>>>>>>>>>> *html<http://james.apache.org/**__**server/****3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> <http:**//james.apache.org/**_**_****server/**3/config-system.*
>>>>>>>>>>>> *html<http://james.apache.org/**__****server/**3/config-system.html>
>>>>>>>>>>>> <http://james.apache.org/****__**server/**3/config-system.**
>>>>>>>>>>>> html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <http://**james.apache.org/**_**
>>>>>>>>>>>> **_**server/**3/config-system.****html<http://james.apache.org/**_**_**server/**3/config-system.**html>
>>>>>>>>>>>> <http://james.apache.**org/**__**server/**3/config-**
>>>>>>>>>>>> system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> <http://james.apache.org/****_**_**server/3/config-system.****
>>>>>>>>>>>> html<http://james.apache.org/****__**server/3/config-system.**html>
>>>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <http://**james.apache.org/**_**
>>>>>>>>>>>>> ****_server/3/**config-system.****<http://james.apache.org/**_****_server/3/**config-system.**>
>>>>>>>>>>>>>
>>>>>>>>>>>> html <http://james.apache.org/**_****
>>>>>>>>>>>> _server/3/**config-system.html<http://james.apache.org/**_**_server/3/**config-system.html>
>>>>>>>>>>>> **>
>>>>>>>>>>>> <http://james.apache.org/****_**_server/3/**config-system.****
>>>>>>>>>>>> html<http://james.apache.org/****__server/3/**config-system.**html>
>>>>>>>>>>>> <http://james.apache.org/****__server/3/**config-system.**html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> **<http://james.apache.org/**_****_**server/3/config-system.*
>>>>>>>>>>>> *html<http://james.apache.org/**_**_**server/3/config-system.html>
>>>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> **<http://james.apache.org/**_**_**server/3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/3/config-system.html<******ht**tp://
>>>>>>>>>>>> james.apache.org/****** <http://james.apache.org/****>
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <ht**tp://
>>>>>>>>>>>>>>
>>>>>>>>>>>>> james.apache.org/**_**** <http://james.apache.org/**_****>
>>>>>>>>>>>> **** <http://james.apache.org/**_********<http://james.apache.org/**_******>
>>>>>>>>>>>> <http://james.apache.org/****_****<http://james.apache.org/**_****>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>>>>>
>>>>>>>>>>>> *_** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>>> >>
>>>>>>>>>>>> _server/**3/config-system.********html<http://james.apache.**
>>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>> **** <http://james.apache.org/*******><
>>>>>>>>>>>> http://james.apache.org/******* <http://james.apache.org/*****>
>>>>>>>>>>>> <http://james.apache.org/***>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *__server/**3/config-system.********html<http://james.apache.
>>>>>>>>>>>> ****
>>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>>
>>>>>>>>>>>> *__server/**3/config-system.******html<http://james.apache.**
>>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/**
>>>>>>>>>>>> **__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/**3/config-system.html<********
>>>>>>>>>>>> http://james.apache.org/********<http://james.apache.org/******>
>>>>>>>>>>>> <http://james.apache.**org/**** <http://james.apache.org/****>>
>>>>>>>>>>>>
>>>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/***
>>>>>>>>>>>> *** <http://james.apache.org/****>
>>>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> **<__http://james.apache.org/_**
>>>>>>>>>>>>> ******_**server/**3/config-**<http://james.apache.org/_******_**server/**3/config-**>
>>>>>>>>>>>>>
>>>>>>>>>>>> system.**<http://james.apache.**org/_****_**server/**3/config-*
>>>>>>>>>>>> *system.**<http://james.apache.org/_****_**server/**3/config-system.**>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>> **html<http://james.apache.****org/_**_**server/**3/config-**
>>>>>>>>>>>>> system.**html<http://james.**apache.org/_**_**server/**3/**
>>>>>>>>>>>>> config-system.**html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://james.apache.**org/__***
>>>>>>>>>>>>> ***server/**3/config-**system.****
>>>>>>>>>>>>> html<http://james.apache.org/_****_**server/**3/config-system.
>>>>>>>>>>>>> ****<http://james.apache.org/_**_**server/**3/config-system.**>
>>>>>>>>>>>>> html <http://james.apache.org/__****
>>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>>> >**>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://james.apache.org/_**_***
>>>>>>>>>>>>>> ***server/**3/config-system.**html<http://james.apache.org/_**_****server/**3/config-system.html>
>>>>>>>>>>>>>> <http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>>>>> >
>>>>>>>>>>>>>>
>>>>>>>>>>>>> **<http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>>>> <http://james.apache.org/_****_server/**3/config-system.**html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**http://james.apache.org/__******server/**3/config-system.
>>>>>>>>>>>>> **html<http://james.apache.org/__****server/**3/config-system.html>
>>>>>>>>>>>>> <http://james.apache.org/_**_**server/**3/config-system.**html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>> **<http://james.apache.org/__****server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>>> **<http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> **>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org/**
>>>>>>>>>>>>>
>>>>>>>>>>>>> server/**3/config-system.html<********
>>>>>>>>>>>> http://james.apache.org/**** <http://james.apache.org/**>
>>>>>>>>>>>>
>>>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/**
>>>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> **>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <**
>>>>>>>>>>>>> http://james.apache.org/**_******<http://james.apache.org/**_****><
>>>>>>>>>>>>> http://james.apache.org/**_****>
>>>>>>>>>>>>>
>>>>>>>>>>>>> **** <http://james.apache.org/**_********<http://james.apache.org/**_******>
>>>>>>>>>>>> <http://james.apache.org/****_****<http://james.apache.org/**_****>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>>>>>
>>>>>>>>>>>> *_** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>>> >>
>>>>>>>>>>>> _server/3/config-system.html<******h**ttp://james.apache.org/**
>>>>>>>>>>>> **_** <http://james.apache.org/**_**>
>>>>>>>>>>>> _**** <http://james.apache.org/**__******<http://james.apache.org/**__****>
>>>>>>>>>>>> ><http://james.apache.org/*
>>>>>>>>>>>> ***__** <http://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>>>>> >>
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/**__*
>>>>>>>>>>>> ***** <http://james.apache.org/**__****><
>>>>>>>>>>>> http://james.apache.org/****__**<http://james.apache.org/**__**>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**__**
>>>>>>>>>>>> ** <http://james.apache.org/**__**>
>>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/***
>>>>>>>>>>>> *** <http://james.apache.org/****>
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <**ht__tp://james.apache.org/**********server/__3/config-*
>>>>>>>>>>>>> *system<http://james.apache.org/********server/__3/config-system>
>>>>>>>>>>>>> .
>>>>>>>>>>>>>
>>>>>>>>>>>> ****html<http://james.apache.**org/******server/__3/config-**
>>>>>>>>>>>> system.**html<http://james.apache.org/******server/__3/config-system.**html>
>>>>>>>>>>>> >
>>>>>>>>>>>> <http://james.apache.**org/******server/__3/config-**system.**
>>>>>>>>>>>> html<http://james.apache.org/******server/__3/config-system.**
>>>>>>>>>>>> html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> <http://james.apache.org/********server/__3/config-system.html<http://james.apache.org/******server/__3/config-system.html>
>>>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>> <**http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> **>
>>>>>>>>>>>>> **<http://james.apache.org/********server/__3/config-system.**
>>>>>>>>>>>>> html<http://james.apache.org/******server/__3/config-system.html>
>>>>>>>>>>>>> <http://james.apache.org/******server/__3/config-system.**html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <**http://james.apache.org/*****
>>>>>>>>>>>>> *server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <
>>>>>>>>>>>>> http://james.apache.org/**
>>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/***
>>>>>>>>>>>> *** <http://james.apache.org/****>
>>>>>>>>>>>> server/** <http://james.apache.org/****server/**<http://james.apache.org/**server/**>
>>>>>>>>>>>> ><
>>>>>>>>>>>> http://james.apache.**org/**server/**<http://james.apache.**
>>>>>>>>>>>> org/server/** <http://james.apache.org/server/**>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> 3/config-system.html<http://******james.apache.org/server/3/***
>>>>>>>>>>>> *<http://james.apache.org/**server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>> config-system.html<http://**ja**mes.apache.org/server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>>> config-system.html<http://**james.apache.org/server/3/**
>>>>>>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> But i could not get
>>>>>>>>>>>> connected to
>>>>>>>>>>>> jmx
>>>>>>>>>>>> on
>>>>>>>>>>>> my email server.
>>>>>>>>>>>>
>>>>>>>>>>>> Note that the server where i
>>>>>>>>>>>> have
>>>>>>>>>>>> deployed james is on azure
>>>>>>>>>>>> cloud
>>>>>>>>>>>> PAS
>>>>>>>>>>>> network and is Ubunto
>>>>>>>>>>>> system.
>>>>>>>>>>>> Is there any mechanism
>>>>>>>>>>>> where i
>>>>>>>>>>>> can
>>>>>>>>>>>> observe the message queue
>>>>>>>>>>>> contents
>>>>>>>>>>>> on
>>>>>>>>>>>> local ubunto system using
>>>>>>>>>>>> ssh
>>>>>>>>>>>> only.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>> Farooq
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Feb 12, 2013 at
>>>>>>>>>>>> 11:02
>>>>>>>>>>>> PM,
>>>>>>>>>>>> Ajay
>>>>>>>>>>>> Navgale <
>>>>>>>>>>>>
>>>>>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>>>>>> <mailto:ajay.navgale@******
>>>>>>>>>>>> central**
>>>>>>>>>>>> ogic.net <http://centralogic.net><ajay.******navgale@**
>>>>>>>>>>>> centralogic.net<
>>>>>>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>**
>>>>>>>>>>>> **>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ---------- Forwarded
>>>>>>>>>>>> message
>>>>>>>>>>>> ----------
>>>>>>>>>>>>
>>>>>>>>>>>> From: Eric Charles <
>>>>>>>>>>>> eric@apache.org
>>>>>>>>>>>> <mailto:eric@apache.org
>>>>>>>>>>>> >>
>>>>>>>>>>>>
>>>>>>>>>>>> Date: Tue, Feb 12, 2013
>>>>>>>>>>>> at
>>>>>>>>>>>> 7:52 PM
>>>>>>>>>>>> Subject: Re: James
>>>>>>>>>>>> Server
>>>>>>>>>>>> SMTP
>>>>>>>>>>>> Spooling Issue
>>>>>>>>>>>> To: James Users List
>>>>>>>>>>>> <
>>>>>>>>>>>> server-user@james.apache.org
>>>>>>>>>>>> <mailto:
>>>>>>>>>>>> server-user@james.
>>>>>>>>>>>> **
>>>>>>>>>>>> apache.org <se...@james.apache.org>********>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>> You mean you the newly
>>>>>>>>>>>> spooled
>>>>>>>>>>>> mails
>>>>>>>>>>>> 'push-out' the remaining
>>>>>>>>>>>> ones.
>>>>>>>>>>>> After that, the latest
>>>>>>>>>>>> one
>>>>>>>>>>>> remains
>>>>>>>>>>>> stucked in the queu?
>>>>>>>>>>>>
>>>>>>>>>>>> If such, that's very
>>>>>>>>>>>> strange
>>>>>>>>>>>> and
>>>>>>>>>>>> we
>>>>>>>>>>>> never saw that before.
>>>>>>>>>>>> Do you use JMX to
>>>>>>>>>>>> inspect
>>>>>>>>>>>> the
>>>>>>>>>>>> queue
>>>>>>>>>>>> content/size?
>>>>>>>>>>>>
>>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On 12/02/2013 11:45,
>>>>>>>>>>>> Ajay
>>>>>>>>>>>> Navgale
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> We are using james
>>>>>>>>>>>> 3.0
>>>>>>>>>>>> beta4.
>>>>>>>>>>>> We have an issue
>>>>>>>>>>>> while
>>>>>>>>>>>> sending
>>>>>>>>>>>> an email. There is
>>>>>>>>>>>> always
>>>>>>>>>>>> one
>>>>>>>>>>>> outgoing
>>>>>>>>>>>> mail
>>>>>>>>>>>> left in spool and is
>>>>>>>>>>>> delivered
>>>>>>>>>>>> when any new
>>>>>>>>>>>> outgoing
>>>>>>>>>>>> mail
>>>>>>>>>>>> is
>>>>>>>>>>>> to
>>>>>>>>>>>> be
>>>>>>>>>>>> sent.
>>>>>>>>>>>> Now previous mail
>>>>>>>>>>>> gets
>>>>>>>>>>>> delivered
>>>>>>>>>>>> and this recent once
>>>>>>>>>>>> sits
>>>>>>>>>>>> in
>>>>>>>>>>>> the
>>>>>>>>>>>> spool.
>>>>>>>>>>>> This is happening
>>>>>>>>>>>> for
>>>>>>>>>>>> Remote
>>>>>>>>>>>> delivery.
>>>>>>>>>>>>
>>>>>>>>>>>> Can anyone throw
>>>>>>>>>>>> some
>>>>>>>>>>>> light on
>>>>>>>>>>>> this.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>>> Ajay
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>> ****
>>>>>>>>>>>> __********--------------------**********--__--**
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --**
>>>>>>>>>>>> --**
>>>>>>>>>>>>
>>>>>>>>>>>> --**---------
>>>>>>>>>>>>
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-unsubscribe@james.
>>>>>>>>>>>> ****
>>>>>>>>>>>> **
>>>>>>>>>>>> __********
>>>>>>>>>>>> apache.org <
>>>>>>>>>>>> http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-**unsubscribe@
>>>>>>>>>>>> **__
>>>>>>>>>>>> ****
>>>>>>>>>>>> **ja**
>>>>>>>>>>>> mes.apache.org
>>>>>>>>>>>> <http://mes.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>> <http:/
>>>>>>>>>>>>>
>>>>>>>>>>>> ****
>>>>>>>>>>>> **/__
>>>>>>>>>>>> james.apache.org
>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org>>
>>>>>>>>>>>> <unsubscribe@
>>>>>>>>>>>> **james.apache.__
>>>>>>>>>>>> ****
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> **org
>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> unsubscribe@james.apache.org
>>>>>>>>>>>> <mailto:
>>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>>> **
>>>>>>>>>>>> apache.org <un...@james.apache.org>********>>__>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>>> ***
>>>>>>>>>>>>
>>>>>>>>>>>> ***
>>>>>>>>>>>>
>>>>>>>>>>>> j**
>>>>>>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>> <**
>>>>>>>>>>>>>
>>>>>>>>>>>> unsubscribe@__james.apache.org
>>>>>>>>>>>> <mailto:
>>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>>> **
>>>>>>>>>>>> apache.org <un...@james.apache.org>********>>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>>> __*
>>>>>>>>>>>>
>>>>>>>>>>>> ***
>>>>>>>>>>>>
>>>>>>>>>>>> j**
>>>>>>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>>>>>>> <mailto:
>>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>>> **
>>>>>>>>>>>> apache.org <un...@james.apache.org>**
>>>>>>>>>>>> ******><server-user-__**
>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>>>> james.apache.org <server-user-__unsubscribe@****j**
>>>>>>>>>>>> ames.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <mailto:server-user-
>>>>>>>>>>>>>> **
>>>>>>>>>>>>>>
>>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>>>
>>>>>>>>>>>> james.apache.org <server-user-unsubscribe@****jam**
>>>>>>>>>>>> es.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> For additional
>>>>>>>>>>>> commands,
>>>>>>>>>>>> e-mail:
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>> ****
>>>>>>>>>>>> __**
>>>>>>>>>>>> **
>>>>>>>>>>>>
>>>>>>>>>>>> ****org<
>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>> ****__*
>>>>>>>>>>>> *****
>>>>>>>>>>>>
>>>>>>>>>>>> apach**e.org
>>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>>> http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>> **__***
>>>>>>>>>>>> ***
>>>>>>>>>>>>
>>>>>>>>>>>> apach**
>>>>>>>>>>>> e.org
>>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>>> http://apache.org
>>>>>>>>>>>>
>>>>>>>>>>>> <
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>>>
>>>>>>>>>>>> ****
>>>>>>>>>>>>
>>>>>>>>>>>> apach**
>>>>>>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>>>>>>> user-help@james.__apache.org
>>>>>>>>>>>> <mailto:
>>>>>>>>>>>> server-user-help@**
>>>>>>>>>>>> james.apache.org <server-user-help@james.******apac**he.org<
>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>> <server-user-help@james.****apac**he.org <http://apache.org><
>>>>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------
>>>>>>>>>>>> ****
>>>>>>>>>>>> **
>>>>>>>>>>>> __******----------------------**********--__--**
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --**
>>>>>>>>>>>>
>>>>>>>>>>>> --**---------
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> server-user-unsubscribe@james.*
>>>>>>>>>>>> ***
>>>>>>>>>>>> ****
>>>>>>>>>>>> **__******
>>>>>>>>>>>> apache.org
>>>>>>>>>>>> <http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> server-user-**unsubscribe@*****
>>>>>>>>>>>> ***
>>>>>>>>>>>> **ja**
>>>>>>>>>>>>
>>>>>>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>>>>>>> <http://james.apache.org><****
>>>>>>>>>>>> unsubscribe@__
>>>>>>>>>>>> james.apache.org
>>>>>>>>>>>> <mailto:unsubscribe@james.*****
>>>>>>>>>>>> ***
>>>>>>>>>>>> ap**
>>>>>>>>>>>> ache.org<http://apache.org**>
>>>>>>>>>>>> <unsubscribe@james.**apache.******org <http://apache.org> <
>>>>>>>>>>>> unsubscribe@james.apache.org>******>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>>> __*****
>>>>>>>>>>>>
>>>>>>>>>>>>> **
>>>>>>>>>>>>>
>>>>>>>>>>>>> *j**
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> unsubscribe@james.**
>>>>>>>>>>>> apache.org <un...@james.apache.org>**
>>>>>>>>>>>> ******><server-user-__**
>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>>>> james.apache.org <server-user-__unsubscribe@****j**
>>>>>>>>>>>> ames.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>>>>>>>
>>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>>>
>>>>>>>>>>>> james.apache.org <server-user-unsubscribe@****jam**
>>>>>>>>>>>> es.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> For additional commands,
>>>>>>>>>>>> e-mail:
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.apache.***
>>>>>>>>>>>> *****
>>>>>>>>>>>> **__**
>>>>>>>>>>>>
>>>>>>>>>>>> ****org<
>>>>>>>>>>>> server-user-help@james.**__****
>>>>>>>>>>>> *****
>>>>>>>>>>>> *apach**
>>>>>>>>>>>>
>>>>>>>>>>>> e.org
>>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>>> http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> server-user-help@james.********
>>>>>>>>>>>> **
>>>>>>>>>>>> apach**__
>>>>>>>>>>>>
>>>>>>>>>>>> e.org
>>>>>>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>>>> <http://apache.org><server-****
>>>>>>>>>>>> ******
>>>>>>>>>>>> user-help@james.
>>>>>>>>>>>> __apache.org
>>>>>>>>>>>> <mailto:server-user-help@******
>>>>>>>>>>>> **
>>>>>>>>>>>> jam**
>>>>>>>>>>>> es.apache.org <http://james.apache.org><******server-user-**
>>>>>>>>>>>> help@james.apache.org <server-user-help@james.****apac**he.org<
>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>> <server-user-help@james.**apac**he.org <http://apache.org><
>>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------**
>>>>>>>>>>>> ********
>>>>>>>>>>>> __****------------------------**********--__--**
>>>>>>>>>>>>
>>>>>>>>>>>> --**---------
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> server-user-unsubscribe@james.****
>>>>>>>>>>>> ******__****
>>>>>>>>>>>> apache.org
>>>>>>>>>>>> <http://apache.org><
>>>>>>>>>>>> server-user-**unsubscribe@__****
>>>>>>>>>>>> ****ja**
>>>>>>>>>>>>
>>>>>>>>>>>> mes.apache.org<
>>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>>> <mailto:unsubscribe@james.********ap**
>>>>>>>>>>>> ache.org<
>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>> <unsubscribe@james.**apache.******org <http://apache.org> <
>>>>>>>>>>>> unsubscribe@james.apache.org>******>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-user-__**unsubscribe@********james.apache.org<**
>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>>
>>>>>>>>>>>> james.apache.org <un...@james.apache.org>****>
>>>>>>>>>>>>> <server-user-_**_unsubscribe@******james.apache.org<**
>>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>>> james.apache.org <un...@james.apache.org>**>
>>>>>>>>>>>>> <server-user-_**_unsubscribe@****james.apache.org<unsubscribe@
>>>>>>>>>>>>> **james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <mailto:server-user-********
>>>>>>>>>>>>>> unsubscr**
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ibe@james.apache.org <un...@james.apache.org>**
>>>>>>>>>>>> ****<server-**
>>>>>>>>>>>> user-unsubscribe@james.apache.********org<server-user-****
>>>>>>>>>>>> unsubscribe@
>>>>>>>>>>>> **
>>>>>>>>>>>>
>>>>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.apache.****
>>>>>>>>>>>> ******__****org<
>>>>>>>>>>>> server-user-help@james.*********
>>>>>>>>>>>> *apach**__
>>>>>>>>>>>> e.org<
>>>>>>>>>>>>
>>>>>>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>>>> <http://apache.org>
>>>>>>>>>>>> <server-user-help@james.__******
>>>>>>>>>>>> **apac**
>>>>>>>>>>>> he.org<
>>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>>> <mailto:server-user-help@********jam**
>>>>>>>>>>>> es.apache.org<http://**james.****apache.org<http://james.**
>>>>>>>>>>>> apache.org <http://james.apache.org>><
>>>>>>>>>>>> http://james.apache.org>>
>>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------**********
>>>>>>>>>>>> __**--------------------------**********--__--**---------
>>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>> server-user-unsubscribe@james.**********__**
>>>>>>>>>>>> apache.org
>>>>>>>>>>>> <http://apache.org><server-*********
>>>>>>>>>>>> *user-__unsubscribe@james.
>>>>>>>>>>>> **
>>>>>>>>>>>> apache.org <server-user-__unsubscribe@******j**ames.apache.org<
>>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>>> <server-user-__**unsubscribe@****james.apache.org<unsubscribe@*
>>>>>>>>>>>> *james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> <mailto:server-user-********unsubscr**
>>>>>>>>>>>>>
>>>>>>>>>>>>> ibe@james.apache.org**<**unsubsc**ribe@james.apache.org**<
>>>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <server-**user-unsubscribe@******james.apache.**org<server-**
>>>>>>>>>>>>
>>>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**
>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>> >>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> server-user-help@james.apache.********
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> **__**org<server-user-help@**
>>>>>>>>>>>> james.__apache.org
>>>>>>>>>>>> <mailto:server-user-help@********jam**
>>>>>>>>>>>> es.apache.org<
>>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------****
>>>>>>>>>>>> ******__----------------------****--
>>>>>>>>>>>> **--**
>>>>>>>>>>>> --**
>>>>>>>>>>>> --__---------
>>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.*
>>>>>>>>>>>> ***
>>>>>>>>>>>> ******__
>>>>>>>>>>>> apache.org
>>>>>>>>>>>> <mailto:server-user-********unsubscr**
>>>>>>>>>>>> ibe@james.apache.org****
>>>>>>>>>>>> **<
>>>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>>>> <server-**user-unsubscribe@******james.apache.**org<server-**
>>>>>>>>>>>>
>>>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**
>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>> >>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>>>
>>>>>>>>>>>>> ****
>>>>>>>>>>>>>
>>>>>>>>>>>> __org
>>>>>>>>>>>> <mailto:server-user-help@********jam**es.apache.org
>>>>>>>>>>>> <http://**
>>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org>
>>>>>>>>>>>> <
>>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------**********----------------------*
>>>>>>>>>>>> *--**
>>>>>>>>>>>> --**--**
>>>>>>>>>>>> --**---------
>>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**
>>>>>>>>>>>> ********
>>>>>>>>>>>> apache.org<
>>>>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>>> ****
>>>>>>>>>>>>>
>>>>>>>>>>>>> **
>>>>>>>>>>>> **org<server-user-help@james.********apache.org<server-user-***
>>>>>>>>>>>> *help@
>>>>>>>>>>>> **
>>>>>>>>>>>> james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ------------------------------**
>>>>>>>>>>>> ********----------------------**--*
>>>>>>>>>>>> *--**
>>>>>>>>>>>> --**
>>>>>>>>>>>>
>>>>>>>>>>>> --**---------
>>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**********
>>>>>>>>>>> apache.org<
>>>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>>>
>>>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> server-user-help@james.apache.***
>>>>>>>>>>>> ***
>>>>>>>>>>>>
>>>>>>>>>>>> ****org<
>>>>>>>>>>> server-user-help@james.******apach**e.org <http://apache.org> <
>>>>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org><
>>>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------**
>>>>>>>>>>> ******------------------------**--**
>>>>>>>>>>>
>>>>>>>>>> --**
>>>>>>>>>>
>>>>>>>>>> --**---------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>>> apache.org<
>>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
There are error emails(with invalid email id but valid smtp server).
My observation is when i send emails to gmail with non existing ids gmail
replies with error saying.
"INFO | jvm 1 | 2013/03/07 10:33:24 | INFO 10:33:24,410 |
james.mailetcontext | Permanent exception delivering mail
(Mail1362652364324-f93c8d53-d32e-4310-8f9f-5788b46b87b7-to-gmail.com.
RemoteHost said: ( abc123abc123abc1231111@gmail.com - [550-5.1.1 The email
account that you tried to reach does not exist.
But there are other email providers which does not respond like gmail when
mail is sent to non existing ids on there server.Instead only spooling
message is logged as i said earlier.
Also outgoing queue contains messages which are deliverable and still
getting stuck and gets delivered with a large delay...following is the
header of such an email.
Delivered-To: farooq.ahmed.sse@gmail.com
Received: by 10.112.147.138 with SMTP id tk10csp25276lbb;
Wed, 6 Mar 2013 10:40:34 -0800 (PST)
X-Received: by 10.182.177.101 with SMTP id cp5mr18241284obc.69.1362595224373;
Wed, 06 Mar 2013 10:40:24 -0800 (PST)
Return-Path: <fa...@zoduka.com>
Received: from localhost ([168.63.166.176])
by mx.google.com with ESMTP id w6si32635824obc.207.2013.03.06.10.40.22;
Wed, 06 Mar 2013 10:40:23 -0800 (PST)
Received-SPF: neutral (google.com: 168.63.166.176 is neither permitted
nor denied by best guess record for domain of farooq@zoduka.com)
client-ip=168.63.166.176;
Authentication-Results: mx.google.com;
spf=neutral (google.com: 168.63.166.176 is neither permitted
nor denied by best guess record for domain of farooq@zoduka.com)
smtp.mail=farooq@zoduka.com
Return-Path: <fa...@zoduka.com>
MIME-Version: 1.0
X-UserIsAuth: true
Received: from 122.169.117.98 (EHLO [192.168.1.8]) ([122.169.117.98])
by huhokadevmail (JAMES SMTP Server ) with ESMTPA ID 185995668
for <fa...@gmail.com>;
Wed, 06 Mar 2013 01:54:46 +0000 (UTC)
Message-ID: <51...@zoduka.com>
Date: Wed, 06 Mar 2013 19:24:48 +0530
From: farooq_zoduka <fa...@zoduka.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130215
Thunderbird/17.0.3
To: Farooq Ahmed <fa...@gmail.com>
Subject: test 7:25
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Conclusion:
------------------
Condition Result outgoing queue status invalid email server no mail
delivered no messages in outgoing queue. invalid email id exception with
gmail ids,
with others we tested mails gets spooled outgoing queue size increases and
even valid mail
gets stuck and delivered with large delay
Regards,
Farooq
On Thu, Mar 7, 2013 at 3:06 PM, Eric Charles <er...@apache.org> wrote:
> Are you sure the mails in the outgoing queue are 'deliverable' mails
> (there is a remote SMTP ready to receive them)?
>
> Thx, Eric
>
> On 07/03/2013 08:13, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> "Could it be that the mail you send to the non-existing id bounce back
>> from
>> the remote smtp, and that your mailet config send them again to the remote
>> SMTP, and so on... "
>> I get following INFO message only in "smtpserver.log" when ever we send
>> mails to invalid emaild ids.No error no bounce information is logged by
>> James.
>>
>> INFO 14:07:21,331 | james.smtpserver | Id='632328207' User='
>> test4@zoduka.com' Successfully spooled mail
>> Mail1362492441321-ccbd5501-**6777-42c5-9164-c143c9487c3f from
>> test4@zoduka.comon xxx.xxx.xxx.xx/xxx.xxx.xxx.xx for [
>> b3bd918c-a03a-453d-901b-**bdce5fd0969a@rediffmail.com<b3...@rediffmail.com>
>> ]
>>
>> Also
>> "bouncing so many times that your outgoing queue is overloaded?"
>> We initially sent few 100 emails to incorrect ids and then we stopped
>> after
>> stopping what ever was the count of outgoing queue its same after that it
>> only increases when we send a new email to valid id. So there seems no
>> matter of outgoing queue getting overloaded. But yes there is some thing
>> which is waiting to get complete to send emails.
>>
>> and we have no custom mailets to handle bounced mails nor we have
>> customized smtpserver.conf to handle bounce emails.
>>
>> Regards,
>> Farooq
>>
>> On Thu, Mar 7, 2013 at 1:15 PM, Eric Charles <er...@apache.org> wrote:
>>
>> Hi,
>>>
>>> Could it be that the mail you send to the non-existing id bounce back
>>> from
>>> the remote smtp, and that your mailet config send them again to the
>>> remote
>>> SMTP, and so on... bouncing so many times that your outgoing queue is
>>> overloaded?
>>>
>>> Thx, Eric
>>>
>>>
>>>
>>> On 06/03/2013 12:27, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>>
>>>> Here is the test scenario.
>>>> I have created a new instance of James and the only difference between
>>>> the
>>>> earlier instance and this one is that earlier instance uses java 1.7 and
>>>> this one uses java 1.6 , else every thing is same.
>>>>
>>>> With this difference also i am able to reproduce the issue.
>>>>
>>>> Initially i sent emails to valid email ids and emails were getting
>>>> delivered as expected.
>>>> Later i sent email to multiple ids which does not exist, though there
>>>> mail
>>>> providers were valid.
>>>>
>>>> e.g SomeUniqueID@vsnl.net,
>>>> SomeUniqueID@rediffmail.com etc
>>>>
>>>> After next day i checked bean
>>>> org.apache.james:name=queue,****queue=outgoing,type=component
>>>>
>>>> and there were many mails all having "state = error;".
>>>> Now today mail are getting spooled and not delivered, though i can
>>>> instantly receiving emails but outgoing emails are getting stucked in
>>>> queue.
>>>>
>>>> I am using james3beta4.
>>>> Let me know if you can reproduce using same version.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org> wrote:
>>>>
>>>> Hi Farooq,
>>>>
>>>>>
>>>>> Unfortunately, I can not reproduce it.
>>>>> Any chance for you to write a Java unit test that shows this?
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 25/02/2013 05:25, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>>>
>>>>>> Any further info on this, this issue is still unresolved..
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>>>>>> <fa...@centralogic.net>******wrote:
>>>>>>
>>>>>>
>>>>>> We do use to restart the system after that the spooled mails are
>>>>>>
>>>>>> delivered
>>>>>>> and after restart first mail is sent out with out getting stuck in
>>>>>>> outgoing
>>>>>>> queue but from second mail onwards one mail always keeps stuck in
>>>>>>> outgoing
>>>>>>> queue.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Did you already tried a stop/start of James to see if those
>>>>>>> numbers
>>>>>>>
>>>>>>> change?
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>>
>>>>>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>>>>>> Queue(ActiveMQ)
>>>>>>>>> and
>>>>>>>>> Size is also 2 in name=queue,queue=outgoing,********type=component
>>>>>>>>> (james)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> The only logical relation that i can see between ActiveMQ and James
>>>>>>>>> is
>>>>>>>>> the
>>>>>>>>> outgoing queue size in both is 2. Where as there are no messages in
>>>>>>>>> List
>>>>>>>>> returned by james bean and ActiveMQ bean shows one message in
>>>>>>>>> queue.
>>>>>>>>>
>>>>>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>>>>>> configuration
>>>>>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we
>>>>>>>>> dont
>>>>>>>>> store copy of sent mails.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi Farooq,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Looking at Destination=outgoing,Type=**********Queue, the
>>>>>>>>>> EnqueueCount/DequeueCount/**********QueueSize seem odd (14976 -
>>>>>>>>>> 14975 <>
>>>>>>>>>>
>>>>>>>>>> 2).
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Can you link/find some logic between those ActiveMQ numbers and
>>>>>>>>>> the
>>>>>>>>>> numbers shown in the James MBeans?
>>>>>>>>>>
>>>>>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any
>>>>>>>>>> changes
>>>>>>>>>> in
>>>>>>>>>> the configuration?
>>>>>>>>>>
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Here you go..
>>>>>>>>>>> Attributes Value
>>>>>>>>>>> BeanName ConsumerCount
>>>>>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>>>>>> EnqueueCount
>>>>>>>>>>> browse
>>>>>>>>>>> Destination=ActiveMQ.DLQ,Type=**********Queue 0 0
>>>>>>>>>>> 1
>>>>>>>>>>>
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 0 Shows 1 message in
>>>>>>>>>>> outgoing queue,
>>>>>>>>>>> invalid recepient
>>>>>>>>>>> Destination=outgoing,Type=**********Queue 10 5
>>>>>>>>>>> 2
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 14976
>>>>>>>>>>>
>>>>>>>>>>> 14975 shows 1 message
>>>>>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>>>>>> Destination=spool,Type=Queue 2 3 0 15146
>>>>>>>>>>> 15146
>>>>>>>>>>> no emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********TempQueue,Type=Topic
>>>>>>>>>>> 1
>>>>>>>>>>>
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 0 0 146 no
>>>>>>>>>>> emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Queue,Type=Topic 0
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>> 0
>>>>>>>>>>> 0 6 no emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Producer.Queue.spool,***
>>>>>>>>>>> *
>>>>>>>>>>> Type=**
>>>>>>>>>>>
>>>>>>>>>>> ****Topic
>>>>>>>>>>>
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>> 0 0 0 3 no emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Producer.Queue.**
>>>>>>>>>>> outgoing,****
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Type=**Topic
>>>>>>>>>>>
>>>>>>>>>>> 0 0 0 0 5 no emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Consumer.Queue.spool,***
>>>>>>>>>>> *
>>>>>>>>>>> Type=**
>>>>>>>>>>>
>>>>>>>>>>> ****Topic
>>>>>>>>>>>
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>> 0 0 0 253212 no emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Consumer.Queue.**
>>>>>>>>>>> outgoing,****
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Type=**Topic
>>>>>>>>>>>
>>>>>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>>>>>> Destination=ActiveMQ.Advisory.**********Connection,Type=Topic
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>> 0
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 0 0 1 no
>>>>>>>>>>> emails
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we
>>>>>>>>>>> send
>>>>>>>>>>> every 30 sec..
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Farooq
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>> All, except the first and the last ones.
>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>> Which mbean of activemq would you like me to check
>>>>>>>>>>> from
>>>>>>>>>>> the
>>>>>>>>>>> following ...
>>>>>>>>>>> org.apache.activemq:__**********
>>>>>>>>>>> BrokerName=james,__**
>>>>>>>>>>> ConnectorName=tcp_//localhost_**********__0,Type=Connector
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.Connection,**********__Type=Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__**********Queue.outgoing,Type=****
>>>>>>>>>>> Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__**********Queue.spool,Type=Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.Producer.__**********Queue.outgoing,Type=****
>>>>>>>>>>> Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.Producer.__**********Queue.spool,Type=Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.Queue,Type=**********__Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.Advisory.TempQueue,_**********_Type=Topic
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _outgoing,Type=Queue
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>>> ******
>>>>>>>>>>> _spool,Type=Queue
>>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>>> BrokerName=james,Type=Broker
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Farooq
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>>>>>> eric@apache.org
>>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Any chance to compare those numbers with the ones
>>>>>>>>>>> given by
>>>>>>>>>>> the activemq
>>>>>>>>>>> mbeans?
>>>>>>>>>>>
>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>>>>>>>
>>>>>>>>>>> "You mean to 'push out' the queue.
>>>>>>>>>>> The mail you send triggers the pending mails
>>>>>>>>>>> to
>>>>>>>>>>> go
>>>>>>>>>>> out?"
>>>>>>>>>>>
>>>>>>>>>>> Yes this new mail push the earlier mail out
>>>>>>>>>>> but
>>>>>>>>>>> itself
>>>>>>>>>>> gets stuck in
>>>>>>>>>>> spool,to which a new mail after 30 sec pushes
>>>>>>>>>>> out
>>>>>>>>>>> and
>>>>>>>>>>> that mail gets
>>>>>>>>>>> struck
>>>>>>>>>>> and soon...
>>>>>>>>>>>
>>>>>>>>>>> Can you guide me how to figure out the reason
>>>>>>>>>>> as to
>>>>>>>>>>> why
>>>>>>>>>>> the size attribute
>>>>>>>>>>> value is 5 and the browse List only contains
>>>>>>>>>>> 3
>>>>>>>>>>> mails
>>>>>>>>>>> details.
>>>>>>>>>>> Also Why The mail which gets stuck in spool
>>>>>>>>>>> its
>>>>>>>>>>> count
>>>>>>>>>>> is
>>>>>>>>>>> incremented in
>>>>>>>>>>> attribure Size but its details are not
>>>>>>>>>>> present
>>>>>>>>>>> in
>>>>>>>>>>> browse
>>>>>>>>>>> List..?
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Farooq
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Farooq,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Here is the output which i get when i
>>>>>>>>>>> use
>>>>>>>>>>> Bean
>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>> ********
>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>
>>>>>>>>>>> $>bean
>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>> ********
>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> #bean is set to
>>>>>>>>>>> org.apache.james:name=queue,**
>>>>>>>>>>> queue=outgoing,type=component
>>>>>>>>>>> $>info
>>>>>>>>>>> #mbean =
>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>> ********
>>>>>>>>>>> __**queue=outgoing,type=__**********component
>>>>>>>>>>> #class name =
>>>>>>>>>>> org.apache.james.queue.****__***
>>>>>>>>>>> *******
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> library.MailQueueManagement
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> # attributes
>>>>>>>>>>> %0 - Size (long, r)
>>>>>>>>>>> # operations
>>>>>>>>>>> %0 - java.util.List browse()
>>>>>>>>>>> %1 - long clear()
>>>>>>>>>>> %2 - long flush()
>>>>>>>>>>> %3 - long
>>>>>>>>>>> removeWithName(java.lang.****_****
>>>>>>>>>>> ******_String
>>>>>>>>>>> p1)
>>>>>>>>>>> %4 - long
>>>>>>>>>>> removeWithRecipient(java.lang.******
>>>>>>>>>>> ****__****String
>>>>>>>>>>> p1)
>>>>>>>>>>> %5 - long
>>>>>>>>>>> removeWithSender(java.lang.*********
>>>>>>>>>>>
>>>>>>>>>>> ****__*String
>>>>>>>>>>>
>>>>>>>>>>> p1)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> #there's no notifications
>>>>>>>>>>> $>get Size
>>>>>>>>>>> #mbean =
>>>>>>>>>>> org.apache.james:name=queue,****
>>>>>>>>>>> ********
>>>>>>>>>>> __**queue=outgoing,type=__**********component:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Size = 7;
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Cool, it seems like you have found a JXM
>>>>>>>>>>> CLI
>>>>>>>>>>> which
>>>>>>>>>>> works fine.
>>>>>>>>>>> Which one is it?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Let me know if you need any further
>>>>>>>>>>> details.
>>>>>>>>>>>
>>>>>>>>>>> can you educate me as to Size= 7 is
>>>>>>>>>>> the
>>>>>>>>>>> no
>>>>>>>>>>> of
>>>>>>>>>>> mails still in outgoing
>>>>>>>>>>> spool
>>>>>>>>>>> or is some default size of outgoing
>>>>>>>>>>> queue.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> It is the number of pending mails
>>>>>>>>>>> in
>>>>>>>>>>> the
>>>>>>>>>>> queue.
>>>>>>>>>>>
>>>>>>>>>>> So you have 7 mails waiting to be sent to
>>>>>>>>>>> the
>>>>>>>>>>> outside world/
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Also note that do deal with this
>>>>>>>>>>> spooling
>>>>>>>>>>> problem, the workaround that
>>>>>>>>>>> we
>>>>>>>>>>>
>>>>>>>>>>> did temporarily is that we created an
>>>>>>>>>>> application that sends an email to
>>>>>>>>>>> some email address every 30 sec.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> You mean to 'push out' the queue.
>>>>>>>>>>> The mail you send triggers the pending
>>>>>>>>>>> mails
>>>>>>>>>>> to go
>>>>>>>>>>> out?
>>>>>>>>>>>
>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Farooq
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric
>>>>>>>>>>> Charles
>>>>>>>>>>> <eric@apache.org <mailto:
>>>>>>>>>>> eric@apache.org>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Maybe the cloud's firewall blocks
>>>>>>>>>>> your
>>>>>>>>>>> requests.
>>>>>>>>>>>
>>>>>>>>>>> For JMX command line, type 'jmx
>>>>>>>>>>> cli' in
>>>>>>>>>>> google and experiment (tried
>>>>>>>>>>> one
>>>>>>>>>>> of these long time ago).
>>>>>>>>>>>
>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 18/02/2013 10:11, Farooq Ahmed
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi Eric,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> I tried remotely connecting
>>>>>>>>>>> to
>>>>>>>>>>> JMX
>>>>>>>>>>> using
>>>>>>>>>>> Jconsole and remote jmx
>>>>>>>>>>> connection
>>>>>>>>>>> method specified on
>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<__***
>>>>>>>>>>> *****
>>>>>>>>>>> **ht**tp://
>>>>>>>>>>> james.apache.org/****
>>>>>>>>>>> <
>>>>>>>>>>> http://james.apache.org/****>
>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<*****
>>>>>>>>>>> *****
>>>>>>>>>>> ht__tp://
>>>>>>>>>>> james.apache.org/**__**server/********3/config-system.html<http://james.apache.org/**__**server/******3/config-system.html>
>>>>>>>>>>> <htt**p://james.apache.org/**__****server/****3/config-system.**
>>>>>>>>>>> html<http://james.apache.org/**__**server/****3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>> <http:**//james.apache.org/**_**_****server/**3/config-system.**
>>>>>>>>>>> html<http://james.apache.org/**__****server/**3/config-system.html>
>>>>>>>>>>> <http://james.apache.org/****__**server/**3/config-system.**html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <http://**james.apache.org/**_****_**server/**3/config-system.
>>>>>>>>>>> ****html<http://james.apache.org/**_**_**server/**3/config-system.**html>
>>>>>>>>>>> <http://james.apache.**org/**__**server/**3/config-**system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>> <http://james.apache.org/****_**_**server/3/config-system.****
>>>>>>>>>>> html<http://james.apache.org/****__**server/3/config-system.**html>
>>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <http://**james.apache.org/**_**
>>>>>>>>>>>> ****_server/3/**config-system.****<http://james.apache.org/**_****_server/3/**config-system.**>
>>>>>>>>>>>>
>>>>>>>>>>> html <http://james.apache.org/**_****
>>>>>>>>>>> _server/3/**config-system.html<http://james.apache.org/**_**_server/3/**config-system.html>
>>>>>>>>>>> **>
>>>>>>>>>>> <http://james.apache.org/****_**_server/3/**config-system.****
>>>>>>>>>>> html<http://james.apache.org/****__server/3/**config-system.**html>
>>>>>>>>>>> <http://james.apache.org/****__server/3/**config-system.**html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> **<http://james.apache.org/**_****_**server/3/config-system.**
>>>>>>>>>>> html<http://james.apache.org/**_**_**server/3/config-system.html>
>>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>> **<http://james.apache.org/**_**_**server/3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>
>>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/**
>>>>>>>>>>> **** <http://james.apache.org/****>
>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <ht**tp://
>>>>>>>>>>>>>
>>>>>>>>>>>> james.apache.org/**_**** <http://james.apache.org/**_****>
>>>>>>>>>>> **** <http://james.apache.org/**_********<http://james.apache.org/**_******>
>>>>>>>>>>> <http://james.apache.org/****_****<http://james.apache.org/**_****>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>>>>
>>>>>>>>>>> *_** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>> >>
>>>>>>>>>>> _server/**3/config-system.********html<http://james.apache.**
>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>> **** <http://james.apache.org/*******><
>>>>>>>>>>> http://james.apache.org/******* <http://james.apache.org/*****><
>>>>>>>>>>> http://james.apache.org/***>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> *__server/**3/config-system.********html<http://james.apache.*
>>>>>>>>>>> ***
>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>>
>>>>>>>>>>> *__server/**3/config-system.******html<http://james.apache.**
>>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/***
>>>>>>>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>
>>>>>>>>>>>> server/**3/config-system.html<********http://james.apache.org/
>>>>>>>>>>> ******** <http://james.apache.org/******><http://james.apache.**
>>>>>>>>>>> org/**** <http://james.apache.org/****>>
>>>>>>>>>>>
>>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/****
>>>>>>>>>>> ** <http://james.apache.org/****>
>>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> **<__http://james.apache.org/_**
>>>>>>>>>>>> ******_**server/**3/config-**<http://james.apache.org/_******_**server/**3/config-**>
>>>>>>>>>>>>
>>>>>>>>>>> system.**<http://james.apache.**org/_****_**server/**3/config-**
>>>>>>>>>>> system.**<http://james.apache.org/_****_**server/**3/config-system.**>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>> **html<http://james.apache.****org/_**_**server/**3/config-**
>>>>>>>>>>>> system.**html<http://james.**apache.org/_**_**server/**3/**
>>>>>>>>>>>> config-system.**html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.**org/__***
>>>>>>>>>>>> ***server/**3/config-**system.****
>>>>>>>>>>>> html<http://james.apache.org/_****_**server/**3/config-system.*
>>>>>>>>>>>> *** <http://james.apache.org/_**_**server/**3/config-system.**>
>>>>>>>>>>>> html <http://james.apache.org/__****
>>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>> >**>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <http://james.apache.org/_**_******server/**3/config-system.
>>>>>>>>>>>>> **html<http://james.apache.org/_**_****server/**3/config-system.html>
>>>>>>>>>>>>> <http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>> **<http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>>> <http://james.apache.org/_****_server/**3/config-system.**html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <**http://james.apache.org/__******server/**3/config-system.*
>>>>>>>>>>>> *html<http://james.apache.org/__****server/**3/config-system.html>
>>>>>>>>>>>> <http://james.apache.org/_**_**server/**3/config-system.**html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> **<http://james.apache.org/__****server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>>> **<http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> **>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org/**
>>>>>>>>>>>>
>>>>>>>>>>>> server/**3/config-system.html<********http://james.apache.org/
>>>>>>>>>>> **** <http://james.apache.org/**>
>>>>>>>>>>>
>>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/**
>>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> **>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <**
>>>>>>>>>>>> http://james.apache.org/**_******<http://james.apache.org/**_****><
>>>>>>>>>>>> http://james.apache.org/**_****>
>>>>>>>>>>>>
>>>>>>>>>>>> **** <http://james.apache.org/**_********<http://james.apache.org/**_******>
>>>>>>>>>>> <http://james.apache.org/****_****<http://james.apache.org/**_****>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>>>>
>>>>>>>>>>> *_** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>> >>
>>>>>>>>>>> _server/3/config-system.html<******h**ttp://james.apache.org/***
>>>>>>>>>>> *_** <http://james.apache.org/**_**>
>>>>>>>>>>> _**** <http://james.apache.org/**__******<http://james.apache.org/**__****>
>>>>>>>>>>> ><http://james.apache.org/*
>>>>>>>>>>> ***__** <http://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>>>> >>
>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/**__**
>>>>>>>>>>> **** <http://james.apache.org/**__****><
>>>>>>>>>>> http://james.apache.org/****__**<http://james.apache.org/**__**>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/****
>>>>>>>>>>> ** <http://james.apache.org/****>
>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <**ht__tp://james.apache.org/**********server/__3/config-**
>>>>>>>>>>>> system<http://james.apache.org/********server/__3/config-system>
>>>>>>>>>>>> .
>>>>>>>>>>>>
>>>>>>>>>>> ****html<http://james.apache.**org/******server/__3/config-**
>>>>>>>>>>> system.**html<http://james.apache.org/******server/__3/config-system.**html>
>>>>>>>>>>> >
>>>>>>>>>>> <http://james.apache.**org/******server/__3/config-**system.**
>>>>>>>>>>> html<http://james.apache.org/******server/__3/config-system.**
>>>>>>>>>>> html <http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/********server/__3/config-system.html<http://james.apache.org/******server/__3/config-system.html>
>>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> <**http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> **>
>>>>>>>>>>>> **<http://james.apache.org/********server/__3/config-system.**
>>>>>>>>>>>> html<http://james.apache.org/******server/__3/config-system.html>
>>>>>>>>>>>> <http://james.apache.org/******server/__3/config-system.**html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <**http://james.apache.org/*****
>>>>>>>>>>>> *server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> <
>>>>>>>>>>>> http://james.apache.org/**
>>>>>>>>>>>>
>>>>>>>>>>> server/3/config-system.html<******ht**tp://james.apache.org/****
>>>>>>>>>>> ** <http://james.apache.org/****>
>>>>>>>>>>> server/** <http://james.apache.org/****server/**<http://james.apache.org/**server/**>
>>>>>>>>>>> ><
>>>>>>>>>>> http://james.apache.**org/**server/**<http://james.apache.**
>>>>>>>>>>> org/server/** <http://james.apache.org/server/**>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> 3/config-system.html<http://******james.apache.org/server/3/****
>>>>>>>>>>> <http://james.apache.org/**server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>> config-system.html<http://**ja**mes.apache.org/server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>> config-system.html<http://**james.apache.org/server/3/**
>>>>>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> But i could not get
>>>>>>>>>>> connected to
>>>>>>>>>>> jmx
>>>>>>>>>>> on
>>>>>>>>>>> my email server.
>>>>>>>>>>>
>>>>>>>>>>> Note that the server where i
>>>>>>>>>>> have
>>>>>>>>>>> deployed james is on azure
>>>>>>>>>>> cloud
>>>>>>>>>>> PAS
>>>>>>>>>>> network and is Ubunto system.
>>>>>>>>>>> Is there any mechanism where
>>>>>>>>>>> i
>>>>>>>>>>> can
>>>>>>>>>>> observe the message queue
>>>>>>>>>>> contents
>>>>>>>>>>> on
>>>>>>>>>>> local ubunto system using ssh
>>>>>>>>>>> only.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>> Farooq
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 12, 2013 at 11:02
>>>>>>>>>>> PM,
>>>>>>>>>>> Ajay
>>>>>>>>>>> Navgale <
>>>>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>>>>> <mailto:ajay.navgale@******
>>>>>>>>>>> central**
>>>>>>>>>>> ogic.net <http://centralogic.net><ajay.******navgale@**
>>>>>>>>>>> centralogic.net<
>>>>>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>**
>>>>>>>>>>> **>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------- Forwarded
>>>>>>>>>>> message
>>>>>>>>>>> ----------
>>>>>>>>>>>
>>>>>>>>>>> From: Eric Charles <
>>>>>>>>>>> eric@apache.org
>>>>>>>>>>> <mailto:eric@apache.org
>>>>>>>>>>> >>
>>>>>>>>>>>
>>>>>>>>>>> Date: Tue, Feb 12, 2013
>>>>>>>>>>> at
>>>>>>>>>>> 7:52 PM
>>>>>>>>>>> Subject: Re: James Server
>>>>>>>>>>> SMTP
>>>>>>>>>>> Spooling Issue
>>>>>>>>>>> To: James Users List
>>>>>>>>>>> <
>>>>>>>>>>> server-user@james.apache.org
>>>>>>>>>>> <mailto:
>>>>>>>>>>> server-user@james.
>>>>>>>>>>> **
>>>>>>>>>>> apache.org <se...@james.apache.org>********>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>> You mean you the newly
>>>>>>>>>>> spooled
>>>>>>>>>>> mails
>>>>>>>>>>> 'push-out' the remaining
>>>>>>>>>>> ones.
>>>>>>>>>>> After that, the latest
>>>>>>>>>>> one
>>>>>>>>>>> remains
>>>>>>>>>>> stucked in the queu?
>>>>>>>>>>>
>>>>>>>>>>> If such, that's very
>>>>>>>>>>> strange
>>>>>>>>>>> and
>>>>>>>>>>> we
>>>>>>>>>>> never saw that before.
>>>>>>>>>>> Do you use JMX to inspect
>>>>>>>>>>> the
>>>>>>>>>>> queue
>>>>>>>>>>> content/size?
>>>>>>>>>>>
>>>>>>>>>>> Thx, Eric
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 12/02/2013 11:45, Ajay
>>>>>>>>>>> Navgale
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> We are using james
>>>>>>>>>>> 3.0
>>>>>>>>>>> beta4.
>>>>>>>>>>> We have an issue
>>>>>>>>>>> while
>>>>>>>>>>> sending
>>>>>>>>>>> an email. There is
>>>>>>>>>>> always
>>>>>>>>>>> one
>>>>>>>>>>> outgoing
>>>>>>>>>>> mail
>>>>>>>>>>> left in spool and is
>>>>>>>>>>> delivered
>>>>>>>>>>> when any new outgoing
>>>>>>>>>>> mail
>>>>>>>>>>> is
>>>>>>>>>>> to
>>>>>>>>>>> be
>>>>>>>>>>> sent.
>>>>>>>>>>> Now previous mail
>>>>>>>>>>> gets
>>>>>>>>>>> delivered
>>>>>>>>>>> and this recent once
>>>>>>>>>>> sits
>>>>>>>>>>> in
>>>>>>>>>>> the
>>>>>>>>>>> spool.
>>>>>>>>>>> This is happening for
>>>>>>>>>>> Remote
>>>>>>>>>>> delivery.
>>>>>>>>>>>
>>>>>>>>>>> Can anyone throw some
>>>>>>>>>>> light on
>>>>>>>>>>> this.
>>>>>>>>>>>
>>>>>>>>>>> Thanks & Regards,
>>>>>>>>>>> Ajay
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------
>>>>>>>>>>> ****
>>>>>>>>>>> __********--------------------**********--__--**
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --**
>>>>>>>>>>> --**
>>>>>>>>>>>
>>>>>>>>>>> --**---------
>>>>>>>>>>>
>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>>
>>>>>>>>>>> server-user-unsubscribe@james.
>>>>>>>>>>> ****
>>>>>>>>>>> **
>>>>>>>>>>> __********
>>>>>>>>>>> apache.org <
>>>>>>>>>>> http://apache.org>
>>>>>>>>>>> <
>>>>>>>>>>>
>>>>>>>>>>> server-user-**unsubscribe@
>>>>>>>>>>> **__
>>>>>>>>>>> ****
>>>>>>>>>>> **ja**
>>>>>>>>>>> mes.apache.org
>>>>>>>>>>> <http://mes.apache.org
>>>>>>>>>>>
>>>>>>>>>>>> <http:/
>>>>>>>>>>>>
>>>>>>>>>>> ****
>>>>>>>>>>> **/__
>>>>>>>>>>> james.apache.org
>>>>>>>>>>> <http://james.apache.org
>>>>>>>>>>> >>
>>>>>>>>>>> <unsubscribe@
>>>>>>>>>>> **james.apache.__
>>>>>>>>>>> ****
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> **org
>>>>>>>>>>> <http://james.apache.org
>>>>>>>>>>> >
>>>>>>>>>>> <
>>>>>>>>>>> unsubscribe@james.apache.org
>>>>>>>>>>> <mailto:
>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>> **
>>>>>>>>>>> apache.org <un...@james.apache.org>********>>__>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>> ***
>>>>>>>>>>>
>>>>>>>>>>> ***
>>>>>>>>>>>
>>>>>>>>>>> j**
>>>>>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>>>>>> <http://james.apache.org
>>>>>>>>>>>
>>>>>>>>>>>> <**
>>>>>>>>>>>>
>>>>>>>>>>> unsubscribe@__james.apache.org
>>>>>>>>>>> <mailto:
>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>> **
>>>>>>>>>>> apache.org <un...@james.apache.org>********>>
>>>>>>>>>>>
>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>> __*
>>>>>>>>>>>
>>>>>>>>>>> ***
>>>>>>>>>>>
>>>>>>>>>>> j**
>>>>>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>>>>>> <mailto:
>>>>>>>>>>> unsubscribe@james.
>>>>>>>>>>> **
>>>>>>>>>>> apache.org <un...@james.apache.org>**
>>>>>>>>>>> ******><server-user-__**
>>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>>> james.apache.org <server-user-__unsubscribe@****j**
>>>>>>>>>>> ames.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <mailto:server-user-
>>>>>>>>>>>>> **
>>>>>>>>>>>>>
>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>>
>>>>>>>>>>> james.apache.org <server-user-unsubscribe@****jam**es.apache.org
>>>>>>>>>>> <http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> For additional
>>>>>>>>>>> commands,
>>>>>>>>>>> e-mail:
>>>>>>>>>>>
>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>> ****
>>>>>>>>>>> __**
>>>>>>>>>>> **
>>>>>>>>>>>
>>>>>>>>>>> ****org<
>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>> ****__*
>>>>>>>>>>> *****
>>>>>>>>>>>
>>>>>>>>>>> apach**e.org
>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>> http://apache.org>
>>>>>>>>>>> <
>>>>>>>>>>>
>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>> **__***
>>>>>>>>>>> ***
>>>>>>>>>>>
>>>>>>>>>>> apach**
>>>>>>>>>>> e.org
>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>> http://apache.org
>>>>>>>>>>>
>>>>>>>>>>> <
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.
>>>>>>>>>>>>
>>>>>>>>>>> ****
>>>>>>>>>>>
>>>>>>>>>>> apach**
>>>>>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>>>>>> user-help@james.__apache.org
>>>>>>>>>>> <mailto:
>>>>>>>>>>> server-user-help@**
>>>>>>>>>>> james.apache.org <server-user-help@james.******apac**he.org<
>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>> <server-user-help@james.****apac**he.org <http://apache.org><
>>>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------
>>>>>>>>>>> ****
>>>>>>>>>>> **
>>>>>>>>>>> __******----------------------**********--__--**
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --**
>>>>>>>>>>>
>>>>>>>>>>> --**---------
>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>> server-user-unsubscribe@james.**
>>>>>>>>>>> **
>>>>>>>>>>> ****
>>>>>>>>>>> **__******
>>>>>>>>>>> apache.org
>>>>>>>>>>> <http://apache.org>
>>>>>>>>>>> <
>>>>>>>>>>> server-user-**unsubscribe@******
>>>>>>>>>>> **
>>>>>>>>>>> **ja**
>>>>>>>>>>>
>>>>>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>>>>>> <http://james.apache.org><****
>>>>>>>>>>> unsubscribe@__
>>>>>>>>>>> james.apache.org
>>>>>>>>>>> <mailto:unsubscribe@james.******
>>>>>>>>>>> **
>>>>>>>>>>> ap**
>>>>>>>>>>> ache.org<http://apache.org**>
>>>>>>>>>>> <unsubscribe@james.**apache.******org <http://apache.org> <
>>>>>>>>>>> unsubscribe@james.apache.org>******>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>>> __*****
>>>>>>>>>>>
>>>>>>>>>>>> **
>>>>>>>>>>>>
>>>>>>>>>>>> *j**
>>>>>>>>>>>>>
>>>>>>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> unsubscribe@james.**
>>>>>>>>>>> apache.org <un...@james.apache.org>**
>>>>>>>>>>> ******><server-user-__**
>>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>>> james.apache.org <server-user-__unsubscribe@****j**
>>>>>>>>>>> ames.apache.org<http://**james.apache.org<http://james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>>>>>>
>>>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>>
>>>>>>>>>>> james.apache.org <server-user-unsubscribe@****jam**es.apache.org
>>>>>>>>>>> <http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> For additional commands,
>>>>>>>>>>> e-mail:
>>>>>>>>>>>
>>>>>>>>>>> server-user-help@james.apache.***
>>>>>>>>>>> *****
>>>>>>>>>>> **__**
>>>>>>>>>>>
>>>>>>>>>>> ****org<
>>>>>>>>>>> server-user-help@james.**__*****
>>>>>>>>>>> ****
>>>>>>>>>>> *apach**
>>>>>>>>>>>
>>>>>>>>>>> e.org
>>>>>>>>>>> <http://e.org> <
>>>>>>>>>>> http://apache.org>
>>>>>>>>>>> <
>>>>>>>>>>> server-user-help@james.*********
>>>>>>>>>>> *
>>>>>>>>>>> apach**__
>>>>>>>>>>>
>>>>>>>>>>> e.org
>>>>>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>>> <http://apache.org><server-*****
>>>>>>>>>>> *****
>>>>>>>>>>> user-help@james.
>>>>>>>>>>> __apache.org
>>>>>>>>>>> <mailto:server-user-help@*******
>>>>>>>>>>> *
>>>>>>>>>>> jam**
>>>>>>>>>>> es.apache.org <http://james.apache.org><******server-user-**
>>>>>>>>>>> help@james.apache.org <server-user-help@james.****apac**he.org<
>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>> <server-user-help@james.**apac**he.org <http://apache.org><
>>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------**
>>>>>>>>>>> ********
>>>>>>>>>>> __****------------------------**********--__--**
>>>>>>>>>>>
>>>>>>>>>>> --**---------
>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>> server-user-unsubscribe@james.****
>>>>>>>>>>> ******__****
>>>>>>>>>>> apache.org
>>>>>>>>>>> <http://apache.org><
>>>>>>>>>>> server-user-**unsubscribe@__********ja**
>>>>>>>>>>>
>>>>>>>>>>> mes.apache.org<
>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <mailto:unsubscribe@james.********ap**
>>>>>>>>>>> ache.org<
>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>> <unsubscribe@james.**apache.******org <http://apache.org> <
>>>>>>>>>>> unsubscribe@james.apache.org>******>
>>>>>>>>>>>
>>>>>>>>>>> <server-user-__**unsubscribe@********james.apache.org<**
>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>
>>>>>>>>>>> james.apache.org <un...@james.apache.org>****>
>>>>>>>>>>>> <server-user-_**_unsubscribe@******james.apache.org<**
>>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>>> james.apache.org <un...@james.apache.org>**>
>>>>>>>>>>>> <server-user-_**_unsubscribe@****james.apache.org<unsubscribe@*
>>>>>>>>>>>> *james.apache.org <un...@james.apache.org>>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> <mailto:server-user-********
>>>>>>>>>>>>> unsubscr**
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ibe@james.apache.org <un...@james.apache.org>**
>>>>>>>>>>> ****<server-**
>>>>>>>>>>> user-unsubscribe@james.apache.********org<server-user-****
>>>>>>>>>>> unsubscribe@
>>>>>>>>>>> **
>>>>>>>>>>>
>>>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.apache.****
>>>>>>>>>>> ******__****org<
>>>>>>>>>>> server-user-help@james.*********
>>>>>>>>>>> *apach**__
>>>>>>>>>>> e.org<
>>>>>>>>>>>
>>>>>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>>> <http://apache.org>
>>>>>>>>>>> <server-user-help@james.__********apac**
>>>>>>>>>>> he.org<
>>>>>>>>>>> http://apache.org**>
>>>>>>>>>>> <mailto:server-user-help@********jam**
>>>>>>>>>>> es.apache.org<http://**james.****apache.org<http://james.**
>>>>>>>>>>> apache.org <http://james.apache.org>><
>>>>>>>>>>> http://james.apache.org>>
>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org> <
>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>> ------------------------------**********
>>>>>>>>>>> __**--------------------------**********--__--**---------
>>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>> server-user-unsubscribe@james.**********__**
>>>>>>>>>>> apache.org
>>>>>>>>>>> <http://apache.org><server-*********
>>>>>>>>>>> *user-__unsubscribe@james.
>>>>>>>>>>> **
>>>>>>>>>>> apache.org <server-user-__unsubscribe@******j**ames.apache.org<
>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <server-user-__**unsubscribe@****james.apache.org<unsubscribe@**
>>>>>>>>>>> james.apache.org <un...@james.apache.org>>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <mailto:server-user-********unsubscr**
>>>>>>>>>>>>
>>>>>>>>>>>> ibe@james.apache.org**<**unsubsc**ribe@james.apache.org**<
>>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <server-**user-unsubscribe@******james.apache.**org<server-**
>>>>>>>>>>>
>>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**
>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>> >>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> server-user-help@james.apache.********
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> **__**org<server-user-help@**
>>>>>>>>>>> james.__apache.org
>>>>>>>>>>> <mailto:server-user-help@********jam**
>>>>>>>>>>> es.apache.org<
>>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org> <
>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>> ------------------------------****
>>>>>>>>>>> ******__----------------------****--
>>>>>>>>>>> **--**
>>>>>>>>>>> --**
>>>>>>>>>>> --__---------
>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**
>>>>>>>>>>> **
>>>>>>>>>>> ******__
>>>>>>>>>>> apache.org
>>>>>>>>>>> <mailto:server-user-********unsubscr**
>>>>>>>>>>> ibe@james.apache.org****
>>>>>>>>>>> **<
>>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>>> <server-**user-unsubscribe@******james.apache.**org<server-**
>>>>>>>>>>>
>>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**
>>>>>>>>>>> unsubscribe@**
>>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>> >>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>>
>>>>>>>>>>>> ****
>>>>>>>>>>>>
>>>>>>>>>>> __org
>>>>>>>>>>> <mailto:server-user-help@********jam**es.apache.org
>>>>>>>>>>> <http://**
>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <server-user-**help@james.****ap**ache.org <http://apache.org> <
>>>>>>>>>>> help@james.apache.org><
>>>>>>>>>>> server-user-help@**james.**apa**che.org <http://apache.org> <
>>>>>>>>>>> http://james.apache.org><
>>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------**********----------------------**
>>>>>>>>>>> --**
>>>>>>>>>>> --**--**
>>>>>>>>>>> --**---------
>>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**********
>>>>>>>>>>> apache.org<
>>>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>>>
>>>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>> ****
>>>>>>>>>>>>
>>>>>>>>>>>> **
>>>>>>>>>>> **org<server-user-help@james.********apache.org<server-user-****
>>>>>>>>>>> help@
>>>>>>>>>>> **
>>>>>>>>>>> james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ------------------------------**
>>>>>>>>>>> ********----------------------**--*
>>>>>>>>>>> *--**
>>>>>>>>>>> --**
>>>>>>>>>>>
>>>>>>>>>>> --**---------
>>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**********
>>>>>>>>>> apache.org<
>>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>>
>>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> server-user-help@james.apache.***
>>>>>>>>>>> ***
>>>>>>>>>>>
>>>>>>>>>>> ****org<
>>>>>>>>>> server-user-help@james.******apach**e.org <http://apache.org> <
>>>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org><
>>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------**
>>>>>>>>>> ******------------------------**--**
>>>>>>>>>>
>>>>>>>>> --**
>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>> apache.org<
>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> >
>>>>>>>
>>>>>>>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Are you sure the mails in the outgoing queue are 'deliverable' mails
(there is a remote SMTP ready to receive them)?
Thx, Eric
On 07/03/2013 08:13, Farooq Ahmed wrote:
> Hi Eric,
>
> "Could it be that the mail you send to the non-existing id bounce back from
> the remote smtp, and that your mailet config send them again to the remote
> SMTP, and so on... "
> I get following INFO message only in "smtpserver.log" when ever we send
> mails to invalid emaild ids.No error no bounce information is logged by
> James.
>
> INFO 14:07:21,331 | james.smtpserver | Id='632328207' User='
> test4@zoduka.com' Successfully spooled mail
> Mail1362492441321-ccbd5501-6777-42c5-9164-c143c9487c3f from
> test4@zoduka.comon xxx.xxx.xxx.xx/xxx.xxx.xxx.xx for [
> b3bd918c-a03a-453d-901b-bdce5fd0969a@rediffmail.com]
>
> Also
> "bouncing so many times that your outgoing queue is overloaded?"
> We initially sent few 100 emails to incorrect ids and then we stopped after
> stopping what ever was the count of outgoing queue its same after that it
> only increases when we send a new email to valid id. So there seems no
> matter of outgoing queue getting overloaded. But yes there is some thing
> which is waiting to get complete to send emails.
>
> and we have no custom mailets to handle bounced mails nor we have
> customized smtpserver.conf to handle bounce emails.
>
> Regards,
> Farooq
>
> On Thu, Mar 7, 2013 at 1:15 PM, Eric Charles <er...@apache.org> wrote:
>
>> Hi,
>>
>> Could it be that the mail you send to the non-existing id bounce back from
>> the remote smtp, and that your mailet config send them again to the remote
>> SMTP, and so on... bouncing so many times that your outgoing queue is
>> overloaded?
>>
>> Thx, Eric
>>
>>
>>
>> On 06/03/2013 12:27, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> Here is the test scenario.
>>> I have created a new instance of James and the only difference between the
>>> earlier instance and this one is that earlier instance uses java 1.7 and
>>> this one uses java 1.6 , else every thing is same.
>>>
>>> With this difference also i am able to reproduce the issue.
>>>
>>> Initially i sent emails to valid email ids and emails were getting
>>> delivered as expected.
>>> Later i sent email to multiple ids which does not exist, though there mail
>>> providers were valid.
>>>
>>> e.g SomeUniqueID@vsnl.net,
>>> SomeUniqueID@rediffmail.com etc
>>>
>>> After next day i checked bean
>>> org.apache.james:name=queue,**queue=outgoing,type=component
>>>
>>> and there were many mails all having "state = error;".
>>> Now today mail are getting spooled and not delivered, though i can
>>> instantly receiving emails but outgoing emails are getting stucked in
>>> queue.
>>>
>>> I am using james3beta4.
>>> Let me know if you can reproduce using same version.
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org> wrote:
>>>
>>> Hi Farooq,
>>>>
>>>> Unfortunately, I can not reproduce it.
>>>> Any chance for you to write a Java unit test that shows this?
>>>> Thx, Eric
>>>>
>>>>
>>>> On 25/02/2013 05:25, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>>
>>>>> Any further info on this, this issue is still unresolved..
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>>>>> <fa...@centralogic.net>****wrote:
>>>>>
>>>>>
>>>>> We do use to restart the system after that the spooled mails are
>>>>>
>>>>>> delivered
>>>>>> and after restart first mail is sent out with out getting stuck in
>>>>>> outgoing
>>>>>> queue but from second mail onwards one mail always keeps stuck in
>>>>>> outgoing
>>>>>> queue.
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
>>>>>>
>>>>>> Did you already tried a stop/start of James to see if those numbers
>>>>>>
>>>>>>> change?
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>>>
>>>>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>>>>> Queue(ActiveMQ)
>>>>>>>> and
>>>>>>>> Size is also 2 in name=queue,queue=outgoing,******type=component
>>>>>>>> (james)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The only logical relation that i can see between ActiveMQ and James
>>>>>>>> is
>>>>>>>> the
>>>>>>>> outgoing queue size in both is 2. Where as there are no messages in
>>>>>>>> List
>>>>>>>> returned by james bean and ActiveMQ bean shows one message in queue.
>>>>>>>>
>>>>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>>>>> configuration
>>>>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we
>>>>>>>> dont
>>>>>>>> store copy of sent mails.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi Farooq,
>>>>>>>>
>>>>>>>>
>>>>>>>>> Looking at Destination=outgoing,Type=********Queue, the
>>>>>>>>> EnqueueCount/DequeueCount/********QueueSize seem odd (14976 -
>>>>>>>>> 14975 <>
>>>>>>>>>
>>>>>>>>> 2).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Can you link/find some logic between those ActiveMQ numbers and the
>>>>>>>>> numbers shown in the James MBeans?
>>>>>>>>>
>>>>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any
>>>>>>>>> changes
>>>>>>>>> in
>>>>>>>>> the configuration?
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Here you go..
>>>>>>>>>> Attributes Value
>>>>>>>>>> BeanName ConsumerCount
>>>>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>>>>> EnqueueCount
>>>>>>>>>> browse
>>>>>>>>>> Destination=ActiveMQ.DLQ,Type=********Queue 0 0 1
>>>>>>>>>>
>>>>>>>>>> 0
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 0 Shows 1 message in
>>>>>>>>>> outgoing queue,
>>>>>>>>>> invalid recepient
>>>>>>>>>> Destination=outgoing,Type=********Queue 10 5 2
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 14976
>>>>>>>>>>
>>>>>>>>>> 14975 shows 1 message
>>>>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>>>>> Destination=spool,Type=Queue 2 3 0 15146
>>>>>>>>>> 15146
>>>>>>>>>> no emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********TempQueue,Type=Topic 1
>>>>>>>>>>
>>>>>>>>>> 0
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 0 0 146 no
>>>>>>>>>> emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********Queue,Type=Topic 0 0
>>>>>>>>>>
>>>>>>>>>> 0
>>>>>>>>>> 0 6 no emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********Producer.Queue.spool,**
>>>>>>>>>> Type=**
>>>>>>>>>>
>>>>>>>>>> ****Topic
>>>>>>>>>>
>>>>>>>>>> 0
>>>>>>>>>>
>>>>>>>>>> 0 0 0 3 no emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********Producer.Queue.outgoing,****
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Type=**Topic
>>>>>>>>>>
>>>>>>>>>> 0 0 0 0 5 no emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********Consumer.Queue.spool,**
>>>>>>>>>> Type=**
>>>>>>>>>>
>>>>>>>>>> ****Topic
>>>>>>>>>>
>>>>>>>>>> 0
>>>>>>>>>>
>>>>>>>>>> 0 0 0 253212 no emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********Consumer.Queue.outgoing,****
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Type=**Topic
>>>>>>>>>>
>>>>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>>>>> Destination=ActiveMQ.Advisory.********Connection,Type=Topic 0
>>>>>>>>>>
>>>>>>>>>> 0
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 0 0 1 no
>>>>>>>>>> emails
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we
>>>>>>>>>> send
>>>>>>>>>> every 30 sec..
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Farooq
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> All, except the first and the last ones.
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>> Which mbean of activemq would you like me to check from
>>>>>>>>>> the
>>>>>>>>>> following ...
>>>>>>>>>> org.apache.activemq:__********BrokerName=james,__**
>>>>>>>>>> ConnectorName=tcp_//localhost_********__0,Type=Connector
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.Connection,********__Type=Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__********Queue.outgoing,Type=**Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.Consumer.__********Queue.spool,Type=Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.Producer.__********Queue.outgoing,Type=**Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.Producer.__********Queue.spool,Type=Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.Queue,Type=********__Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.Advisory.TempQueue,_********_Type=Topic
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _outgoing,Type=Queue
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>>> ******
>>>>>>>>>> _spool,Type=Queue
>>>>>>>>>> org.apache.activemq:__********
>>>>>>>>>> BrokerName=james,Type=Broker
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Farooq
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>>>>> eric@apache.org
>>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>>
>>>>>>>>>> Any chance to compare those numbers with the ones
>>>>>>>>>> given by
>>>>>>>>>> the activemq
>>>>>>>>>> mbeans?
>>>>>>>>>>
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>>>>>>
>>>>>>>>>> "You mean to 'push out' the queue.
>>>>>>>>>> The mail you send triggers the pending mails to
>>>>>>>>>> go
>>>>>>>>>> out?"
>>>>>>>>>>
>>>>>>>>>> Yes this new mail push the earlier mail out but
>>>>>>>>>> itself
>>>>>>>>>> gets stuck in
>>>>>>>>>> spool,to which a new mail after 30 sec pushes
>>>>>>>>>> out
>>>>>>>>>> and
>>>>>>>>>> that mail gets
>>>>>>>>>> struck
>>>>>>>>>> and soon...
>>>>>>>>>>
>>>>>>>>>> Can you guide me how to figure out the reason
>>>>>>>>>> as to
>>>>>>>>>> why
>>>>>>>>>> the size attribute
>>>>>>>>>> value is 5 and the browse List only contains 3
>>>>>>>>>> mails
>>>>>>>>>> details.
>>>>>>>>>> Also Why The mail which gets stuck in spool its
>>>>>>>>>> count
>>>>>>>>>> is
>>>>>>>>>> incremented in
>>>>>>>>>> attribure Size but its details are not present
>>>>>>>>>> in
>>>>>>>>>> browse
>>>>>>>>>> List..?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Farooq
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Farooq,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Here is the output which i get when i
>>>>>>>>>> use
>>>>>>>>>> Bean
>>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>>> __**queue=outgoing,type=__********component
>>>>>>>>>>
>>>>>>>>>> $>bean
>>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>>> __**queue=outgoing,type=__********component
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> #bean is set to
>>>>>>>>>> org.apache.james:name=queue,**
>>>>>>>>>> queue=outgoing,type=component
>>>>>>>>>> $>info
>>>>>>>>>> #mbean =
>>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>>> __**queue=outgoing,type=__********component
>>>>>>>>>> #class name =
>>>>>>>>>> org.apache.james.queue.****__********
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> library.MailQueueManagement
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> # attributes
>>>>>>>>>> %0 - Size (long, r)
>>>>>>>>>> # operations
>>>>>>>>>> %0 - java.util.List browse()
>>>>>>>>>> %1 - long clear()
>>>>>>>>>> %2 - long flush()
>>>>>>>>>> %3 - long
>>>>>>>>>> removeWithName(java.lang.****_**
>>>>>>>>>> ******_String
>>>>>>>>>> p1)
>>>>>>>>>> %4 - long
>>>>>>>>>> removeWithRecipient(java.lang.****
>>>>>>>>>> ****__****String
>>>>>>>>>> p1)
>>>>>>>>>> %5 - long
>>>>>>>>>> removeWithSender(java.lang.*******
>>>>>>>>>>
>>>>>>>>>> ****__*String
>>>>>>>>>>
>>>>>>>>>> p1)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> #there's no notifications
>>>>>>>>>> $>get Size
>>>>>>>>>> #mbean =
>>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>>> __**queue=outgoing,type=__********component:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Size = 7;
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Cool, it seems like you have found a JXM CLI
>>>>>>>>>> which
>>>>>>>>>> works fine.
>>>>>>>>>> Which one is it?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Let me know if you need any further
>>>>>>>>>> details.
>>>>>>>>>>
>>>>>>>>>> can you educate me as to Size= 7 is the
>>>>>>>>>> no
>>>>>>>>>> of
>>>>>>>>>> mails still in outgoing
>>>>>>>>>> spool
>>>>>>>>>> or is some default size of outgoing
>>>>>>>>>> queue.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> It is the number of pending mails in
>>>>>>>>>> the
>>>>>>>>>> queue.
>>>>>>>>>>
>>>>>>>>>> So you have 7 mails waiting to be sent to
>>>>>>>>>> the
>>>>>>>>>> outside world/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Also note that do deal with this
>>>>>>>>>> spooling
>>>>>>>>>> problem, the workaround that
>>>>>>>>>> we
>>>>>>>>>>
>>>>>>>>>> did temporarily is that we created an
>>>>>>>>>> application that sends an email to
>>>>>>>>>> some email address every 30 sec.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> You mean to 'push out' the queue.
>>>>>>>>>> The mail you send triggers the pending mails
>>>>>>>>>> to go
>>>>>>>>>> out?
>>>>>>>>>>
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Farooq
>>>>>>>>>>
>>>>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric
>>>>>>>>>> Charles
>>>>>>>>>> <eric@apache.org <mailto:
>>>>>>>>>> eric@apache.org>>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Maybe the cloud's firewall blocks
>>>>>>>>>> your
>>>>>>>>>> requests.
>>>>>>>>>>
>>>>>>>>>> For JMX command line, type 'jmx
>>>>>>>>>> cli' in
>>>>>>>>>> google and experiment (tried
>>>>>>>>>> one
>>>>>>>>>> of these long time ago).
>>>>>>>>>>
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 18/02/2013 10:11, Farooq Ahmed
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Eric,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I tried remotely connecting to
>>>>>>>>>> JMX
>>>>>>>>>> using
>>>>>>>>>> Jconsole and remote jmx
>>>>>>>>>> connection
>>>>>>>>>> method specified on
>>>>>>>>>> http://james.apache.org/****
>>>>>>>>>> server/3/config-system.html<__*
>>>>>>>>>> *****
>>>>>>>>>> **ht**tp://
>>>>>>>>>> james.apache.org/****
>>>>>>>>>> <http://james.apache.org/****>
>>>>>>>>>> server/3/config-system.html<***
>>>>>>>>>> *****
>>>>>>>>>> ht__tp://
>>>>>>>>>> james.apache.org/**__**server/******3/config-system.html<http://james.apache.org/**__**server/****3/config-system.html>
>>>>>>>>>> <http:**//james.apache.org/**__****server/**3/config-system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>> <http://**james.apache.org/**_**_**server/**3/config-system.**html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <http://**james.apache.org/**_****_server/3/**config-system.**
>>>>>>>>>> html <http://james.apache.org/**_**_server/3/**config-system.html>
>>>>>>>>>> <http://james.apache.org/****__server/3/**config-system.**html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>>>>>>
>>>>>>>>>> **<http://james.apache.org/**_**_**server/3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/****
>>>>>>>>>>>
>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>
>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <ht**tp://
>>>>>>>>>> james.apache.org/**_**** <http://james.apache.org/**_**>
>>>>>>>>>> **** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>> *_** <http://james.apache.org/**_****>>
>>>>>>>>>> _server/**3/config-system.******html<http://james.apache.org/***
>>>>>>>>>> **** <http://james.apache.org/*****><http://james.apache.org/*****<http://james.apache.org/***>
>>>>>>>>>>>
>>>>>>>>>> *__server/**3/config-system.******html<http://james.apache.**
>>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>>
>>>>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/***
>>>>>>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/****
>>>>>>>>>>>
>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/******<http://james.apache.org/****>
>>>>>>>>>>
>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> **<__http://james.apache.org/_******_**server/**3/config-**
>>>>>>>>>> system.**<http://james.apache.org/_****_**server/**3/config-system.**>
>>>>>>>>>>
>>>>>>>>>>> **html<http://james.apache.**org/_**_**server/**3/config-**
>>>>>>>>>>> system.**html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.**org/__****server/**3/config-**system.**
>>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.**
>>>>>>>>>>> html <http://james.apache.org/__**server/**3/config-system.html>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <http://james.apache.org/_**_****server/**3/config-system.html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>>> **<http://james.apache.org/_**_**server/**3/config-system.html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>>>>>>
>>>>>>>>>>> <**http://james.apache.org/__****server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>> **<http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> **>
>>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/**
>>>>>>>>>>>
>>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/**
>>>>>>>>>>
>>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> **>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <**
>>>>>>>>>>> http://james.apache.org/**_**** <http://james.apache.org/**_**>
>>>>>>>>>>>
>>>>>>>>>> **** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>>>> <http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>>> *_** <http://james.apache.org/**_****>>
>>>>>>>>>> _server/3/config-system.html<****h**ttp://james.apache.org/**_**
>>>>>>>>>> _**** <http://james.apache.org/**__****><http://james.apache.org/*
>>>>>>>>>> ***__** <http://james.apache.org/**__**>>
>>>>>>>>>>
>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>>>
>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/****
>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>>
>>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <**ht__tp://james.apache.org/********server/__3/config-system.
>>>>>>>>>> ****html<http://james.apache.org/******server/__3/config-system.**html>
>>>>>>>>>> <http://james.apache.**org/****server/__3/config-**system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>
>>>>>>>>>>> **>
>>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>>>
>>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/**
>>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>> server/** <http://james.apache.org/**server/**><
>>>>>>>>>> http://james.apache.**org/server/**<http://james.apache.org/server/**>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 3/config-system.html<http://****james.apache.org/server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>>
>>>>>>>>>> config-system.html<http://**james.apache.org/server/3/**
>>>>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> But i could not get connected to
>>>>>>>>>> jmx
>>>>>>>>>> on
>>>>>>>>>> my email server.
>>>>>>>>>>
>>>>>>>>>> Note that the server where i
>>>>>>>>>> have
>>>>>>>>>> deployed james is on azure cloud
>>>>>>>>>> PAS
>>>>>>>>>> network and is Ubunto system.
>>>>>>>>>> Is there any mechanism where i
>>>>>>>>>> can
>>>>>>>>>> observe the message queue
>>>>>>>>>> contents
>>>>>>>>>> on
>>>>>>>>>> local ubunto system using ssh
>>>>>>>>>> only.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Farooq
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 12, 2013 at 11:02
>>>>>>>>>> PM,
>>>>>>>>>> Ajay
>>>>>>>>>> Navgale <
>>>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>>>> <mailto:ajay.navgale@******
>>>>>>>>>> central**
>>>>>>>>>> ogic.net <http://centralogic.net><ajay.****navgale@**
>>>>>>>>>> centralogic.net<
>>>>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>**>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------- Forwarded message
>>>>>>>>>> ----------
>>>>>>>>>>
>>>>>>>>>> From: Eric Charles <
>>>>>>>>>> eric@apache.org
>>>>>>>>>> <ma...@apache.org>>
>>>>>>>>>>
>>>>>>>>>> Date: Tue, Feb 12, 2013 at
>>>>>>>>>> 7:52 PM
>>>>>>>>>> Subject: Re: James Server
>>>>>>>>>> SMTP
>>>>>>>>>> Spooling Issue
>>>>>>>>>> To: James Users List
>>>>>>>>>> <
>>>>>>>>>> server-user@james.apache.org
>>>>>>>>>> <mailto:server-user@james.
>>>>>>>>>> **
>>>>>>>>>> apache.org <se...@james.apache.org>******>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>> You mean you the newly
>>>>>>>>>> spooled
>>>>>>>>>> mails
>>>>>>>>>> 'push-out' the remaining
>>>>>>>>>> ones.
>>>>>>>>>> After that, the latest one
>>>>>>>>>> remains
>>>>>>>>>> stucked in the queu?
>>>>>>>>>>
>>>>>>>>>> If such, that's very strange
>>>>>>>>>> and
>>>>>>>>>> we
>>>>>>>>>> never saw that before.
>>>>>>>>>> Do you use JMX to inspect
>>>>>>>>>> the
>>>>>>>>>> queue
>>>>>>>>>> content/size?
>>>>>>>>>>
>>>>>>>>>> Thx, Eric
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 12/02/2013 11:45, Ajay
>>>>>>>>>> Navgale
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> We are using james 3.0
>>>>>>>>>> beta4.
>>>>>>>>>> We have an issue while
>>>>>>>>>> sending
>>>>>>>>>> an email. There is
>>>>>>>>>> always
>>>>>>>>>> one
>>>>>>>>>> outgoing
>>>>>>>>>> mail
>>>>>>>>>> left in spool and is
>>>>>>>>>> delivered
>>>>>>>>>> when any new outgoing
>>>>>>>>>> mail
>>>>>>>>>> is
>>>>>>>>>> to
>>>>>>>>>> be
>>>>>>>>>> sent.
>>>>>>>>>> Now previous mail gets
>>>>>>>>>> delivered
>>>>>>>>>> and this recent once
>>>>>>>>>> sits
>>>>>>>>>> in
>>>>>>>>>> the
>>>>>>>>>> spool.
>>>>>>>>>> This is happening for
>>>>>>>>>> Remote
>>>>>>>>>> delivery.
>>>>>>>>>>
>>>>>>>>>> Can anyone throw some
>>>>>>>>>> light on
>>>>>>>>>> this.
>>>>>>>>>>
>>>>>>>>>> Thanks & Regards,
>>>>>>>>>> Ajay
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------
>>>>>>>>>> ****
>>>>>>>>>> __********--------------------********--__--**
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --**
>>>>>>>>>> --**
>>>>>>>>>>
>>>>>>>>>> --**---------
>>>>>>>>>>
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>>
>>>>>>>>>> server-user-unsubscribe@james.
>>>>>>>>>> ****
>>>>>>>>>> **
>>>>>>>>>> __********
>>>>>>>>>> apache.org <
>>>>>>>>>> http://apache.org>
>>>>>>>>>> <
>>>>>>>>>> server-user-**unsubscribe@
>>>>>>>>>> **__
>>>>>>>>>> ****
>>>>>>>>>> **ja**
>>>>>>>>>> mes.apache.org
>>>>>>>>>> <http://mes.apache.org
>>>>>>>>>>> <http:/
>>>>>>>>>> ****
>>>>>>>>>> **/__
>>>>>>>>>> james.apache.org
>>>>>>>>>> <http://james.apache.org>>
>>>>>>>>>> <unsubscribe@
>>>>>>>>>> **james.apache.__
>>>>>>>>>> ****
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> **org
>>>>>>>>>> <http://james.apache.org>
>>>>>>>>>> <
>>>>>>>>>> unsubscribe@james.apache.org
>>>>>>>>>> <mailto:unsubscribe@james.
>>>>>>>>>> **
>>>>>>>>>> apache.org <un...@james.apache.org>******>>__>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>> ***
>>>>>>>>>>
>>>>>>>>>> ***
>>>>>>>>>>
>>>>>>>>>> j**
>>>>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>>>>> <http://james.apache.org
>>>>>>>>>>> <**
>>>>>>>>>> unsubscribe@__james.apache.org
>>>>>>>>>> <mailto:unsubscribe@james.
>>>>>>>>>> **
>>>>>>>>>> apache.org <un...@james.apache.org>******>>
>>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>>> __*
>>>>>>>>>>
>>>>>>>>>> ***
>>>>>>>>>>
>>>>>>>>>> j**
>>>>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>>>>> <mailto:unsubscribe@james.
>>>>>>>>>> **
>>>>>>>>>> apache.org <un...@james.apache.org>******><server-user-__**
>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>> james.apache.org <server-user-__unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>
>>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> For additional
>>>>>>>>>> commands,
>>>>>>>>>> e-mail:
>>>>>>>>>>
>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>> ****
>>>>>>>>>> __**
>>>>>>>>>> **
>>>>>>>>>>
>>>>>>>>>> ****org<
>>>>>>>>>> server-user-help@james.
>>>>>>>>>> ****__*
>>>>>>>>>> *****
>>>>>>>>>>
>>>>>>>>>> apach**e.org
>>>>>>>>>> <http://e.org> <
>>>>>>>>>> http://apache.org>
>>>>>>>>>> <
>>>>>>>>>>
>>>>>>>>>> server-user-help@james.
>>>>>>>>>> **__***
>>>>>>>>>> ***
>>>>>>>>>>
>>>>>>>>>> apach**
>>>>>>>>>> e.org
>>>>>>>>>> <http://e.org> <
>>>>>>>>>> http://apache.org
>>>>>>>>>>
>>>>>>>>>> <
>>>>>>>>>>>
>>>>>>>>>>> server-user-help@james.
>>>>>>>>>> ****
>>>>>>>>>>
>>>>>>>>>> apach**
>>>>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>>>>> user-help@james.__apache.org
>>>>>>>>>> <mailto:server-user-help@**
>>>>>>>>>> james.apache.org <server-user-help@james.****apac**he.org<
>>>>>>>>>> http://apache.org**>
>>>>>>>>>> <server-user-help@james.**apac**he.org <http://apache.org><
>>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------
>>>>>>>>>> ****
>>>>>>>>>> **
>>>>>>>>>> __******----------------------********--__--**
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --**
>>>>>>>>>>
>>>>>>>>>> --**---------
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>> server-user-unsubscribe@james.**
>>>>>>>>>> ****
>>>>>>>>>> **__******
>>>>>>>>>> apache.org
>>>>>>>>>> <http://apache.org>
>>>>>>>>>> <
>>>>>>>>>> server-user-**unsubscribe@******
>>>>>>>>>> **ja**
>>>>>>>>>>
>>>>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>>>>> <http://james.apache.org><****
>>>>>>>>>> unsubscribe@__
>>>>>>>>>> james.apache.org
>>>>>>>>>> <mailto:unsubscribe@james.******
>>>>>>>>>> ap**
>>>>>>>>>> ache.org<http://apache.org**>
>>>>>>>>>> <unsubscribe@james.**apache.****org <http://apache.org> <
>>>>>>>>>> unsubscribe@james.apache.org>****>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <server-user-**unsubscribe@__***
>>>>>>>>>>> **
>>>>>>>>>>>
>>>>>>>>>>>> *j**
>>>>>>>>>>>>
>>>>>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>>>>>>
>>>>>>>>>> unsubscribe@james.**
>>>>>>>>>> apache.org <un...@james.apache.org>******><server-user-__**
>>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>>> james.apache.org <server-user-__unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>>
>>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> For additional commands,
>>>>>>>>>> e-mail:
>>>>>>>>>> server-user-help@james.apache.*
>>>>>>>>>> *****
>>>>>>>>>> **__**
>>>>>>>>>>
>>>>>>>>>> ****org<
>>>>>>>>>> server-user-help@james.**__*******
>>>>>>>>>> *apach**
>>>>>>>>>>
>>>>>>>>>> e.org
>>>>>>>>>> <http://e.org> <http://apache.org>
>>>>>>>>>> <
>>>>>>>>>> server-user-help@james.********
>>>>>>>>>> apach**__
>>>>>>>>>>
>>>>>>>>>> e.org
>>>>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>> <http://apache.org><server-********
>>>>>>>>>> user-help@james.
>>>>>>>>>> __apache.org
>>>>>>>>>> <mailto:server-user-help@******
>>>>>>>>>> jam**
>>>>>>>>>> es.apache.org <http://james.apache.org><****server-user-**
>>>>>>>>>> help@james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------********
>>>>>>>>>> __****------------------------********--__--**
>>>>>>>>>>
>>>>>>>>>> --**---------
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>> server-user-unsubscribe@james.**
>>>>>>>>>> ******__****
>>>>>>>>>> apache.org
>>>>>>>>>> <http://apache.org><
>>>>>>>>>> server-user-**unsubscribe@__******ja**
>>>>>>>>>>
>>>>>>>>>> mes.apache.org<
>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>> <mailto:unsubscribe@james.******ap**
>>>>>>>>>> ache.org<
>>>>>>>>>> http://apache.org**>
>>>>>>>>>> <unsubscribe@james.**apache.****org <http://apache.org> <
>>>>>>>>>> unsubscribe@james.apache.org>****>
>>>>>>>>>>
>>>>>>>>>> <server-user-__**unsubscribe@******james.apache.org<**
>>>>>>>>>> unsubscribe@**
>>>>>>>>>>
>>>>>>>>>>> james.apache.org <un...@james.apache.org>**>
>>>>>>>>>>> <server-user-_**_unsubscribe@****james.apache.org<unsubscribe@**
>>>>>>>>>>> james.apache.org <un...@james.apache.org>>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> <mailto:server-user-******unsubscr**
>>>>>>>>>>>
>>>>>>>>>> ibe@james.apache.org <un...@james.apache.org>****<server-**
>>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**unsubscribe@
>>>>>>>>>> **
>>>>>>>>>>
>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> server-user-help@james.apache.**
>>>>>>>>>> ******__****org<
>>>>>>>>>> server-user-help@james.********apach**__
>>>>>>>>>> e.org<
>>>>>>>>>>
>>>>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>>>>> <http://apache.org>
>>>>>>>>>> <server-user-help@james.__******apac**
>>>>>>>>>> he.org<
>>>>>>>>>> http://apache.org**>
>>>>>>>>>> <mailto:server-user-help@******jam**
>>>>>>>>>> es.apache.org<http://**james.**apache.org<http://james.apache.org><
>>>>>>>>>> http://james.apache.org>>
>>>>>>>>>> <server-user-**help@james.**ap**ache.org <http://apache.org> <
>>>>>>>>>> help@james.apache.org><
>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------********
>>>>>>>>>> __**--------------------------********--__--**---------
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>> server-user-unsubscribe@james.********__**
>>>>>>>>>> apache.org
>>>>>>>>>> <http://apache.org><server-*******
>>>>>>>>>> *user-__unsubscribe@james.
>>>>>>>>>> **
>>>>>>>>>> apache.org <server-user-__unsubscribe@****j**ames.apache.org<
>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <mailto:server-user-******unsubscr**
>>>>>>>>>>>
>>>>>>>>>> ibe@james.apache.org**<un...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>> <server-**user-unsubscribe@****james.apache.**org<server-**
>>>>>>>>>>
>>>>>>>>>> user-unsubscribe@james.apache.****org<server-user-unsubscribe@**
>>>>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> server-user-help@james.apache.******
>>>>>>>>>>>
>>>>>>>>>> **__**org<server-user-help@**
>>>>>>>>>> james.__apache.org
>>>>>>>>>> <mailto:server-user-help@******jam**es.apache.org<
>>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>>> <server-user-**help@james.**ap**ache.org <http://apache.org> <
>>>>>>>>>> help@james.apache.org><
>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------**
>>>>>>>>>> ******__----------------------**--
>>>>>>>>>> **--**
>>>>>>>>>> --**
>>>>>>>>>> --__---------
>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**
>>>>>>>>>> ******__
>>>>>>>>>> apache.org
>>>>>>>>>> <mailto:server-user-******unsubscr**ibe@james.apache.org**
>>>>>>>>>> **<
>>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>>> <server-**user-unsubscribe@****james.apache.**org<server-**
>>>>>>>>>>
>>>>>>>>>> user-unsubscribe@james.apache.****org<server-user-unsubscribe@**
>>>>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>>
>>>>>>>>>>> ****
>>>>>>>>>> __org
>>>>>>>>>> <mailto:server-user-help@******jam**es.apache.org<http://**
>>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>>> <server-user-**help@james.**ap**ache.org <http://apache.org> <
>>>>>>>>>> help@james.apache.org><
>>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------********------------------------**
>>>>>>>>>> --**--**
>>>>>>>>>> --**---------
>>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>>>> apache.org<
>>>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.
>>>>>>>>>>> ****
>>>>>>>>>>>
>>>>>>>>>> **
>>>>>>>>>> **org<server-user-help@james.******apache.org<server-user-**help@
>>>>>>>>>> **
>>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> ------------------------------********------------------------*
>>>>>>>>>> *--**
>>>>>>>>>> --**
>>>>>>>>>>
>>>>>>>>>> --**---------
>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>>> apache.org<
>>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.*
>>>>>>>>>> ***
>>>>>>>>>>
>>>>>>>>> ****org<
>>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org> <
>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------******--------------------------**
>>>>>>>> --**
>>>>>>>>
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******
>>>>>>> apache.org<
>>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>> ****org<
>>>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
"Could it be that the mail you send to the non-existing id bounce back from
the remote smtp, and that your mailet config send them again to the remote
SMTP, and so on... "
I get following INFO message only in "smtpserver.log" when ever we send
mails to invalid emaild ids.No error no bounce information is logged by
James.
INFO 14:07:21,331 | james.smtpserver | Id='632328207' User='
test4@zoduka.com' Successfully spooled mail
Mail1362492441321-ccbd5501-6777-42c5-9164-c143c9487c3f from
test4@zoduka.comon xxx.xxx.xxx.xx/xxx.xxx.xxx.xx for [
b3bd918c-a03a-453d-901b-bdce5fd0969a@rediffmail.com]
Also
"bouncing so many times that your outgoing queue is overloaded?"
We initially sent few 100 emails to incorrect ids and then we stopped after
stopping what ever was the count of outgoing queue its same after that it
only increases when we send a new email to valid id. So there seems no
matter of outgoing queue getting overloaded. But yes there is some thing
which is waiting to get complete to send emails.
and we have no custom mailets to handle bounced mails nor we have
customized smtpserver.conf to handle bounce emails.
Regards,
Farooq
On Thu, Mar 7, 2013 at 1:15 PM, Eric Charles <er...@apache.org> wrote:
> Hi,
>
> Could it be that the mail you send to the non-existing id bounce back from
> the remote smtp, and that your mailet config send them again to the remote
> SMTP, and so on... bouncing so many times that your outgoing queue is
> overloaded?
>
> Thx, Eric
>
>
>
> On 06/03/2013 12:27, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> Here is the test scenario.
>> I have created a new instance of James and the only difference between the
>> earlier instance and this one is that earlier instance uses java 1.7 and
>> this one uses java 1.6 , else every thing is same.
>>
>> With this difference also i am able to reproduce the issue.
>>
>> Initially i sent emails to valid email ids and emails were getting
>> delivered as expected.
>> Later i sent email to multiple ids which does not exist, though there mail
>> providers were valid.
>>
>> e.g SomeUniqueID@vsnl.net,
>> SomeUniqueID@rediffmail.com etc
>>
>> After next day i checked bean
>> org.apache.james:name=queue,**queue=outgoing,type=component
>>
>> and there were many mails all having "state = error;".
>> Now today mail are getting spooled and not delivered, though i can
>> instantly receiving emails but outgoing emails are getting stucked in
>> queue.
>>
>> I am using james3beta4.
>> Let me know if you can reproduce using same version.
>>
>> Regards,
>> Farooq
>>
>> On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org> wrote:
>>
>> Hi Farooq,
>>>
>>> Unfortunately, I can not reproduce it.
>>> Any chance for you to write a Java unit test that shows this?
>>> Thx, Eric
>>>
>>>
>>> On 25/02/2013 05:25, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>>
>>>> Any further info on this, this issue is still unresolved..
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>>>> <fa...@centralogic.net>****wrote:
>>>>
>>>>
>>>> We do use to restart the system after that the spooled mails are
>>>>
>>>>> delivered
>>>>> and after restart first mail is sent out with out getting stuck in
>>>>> outgoing
>>>>> queue but from second mail onwards one mail always keeps stuck in
>>>>> outgoing
>>>>> queue.
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>>
>>>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
>>>>>
>>>>> Did you already tried a stop/start of James to see if those numbers
>>>>>
>>>>>> change?
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>>
>>>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>>>> Queue(ActiveMQ)
>>>>>>> and
>>>>>>> Size is also 2 in name=queue,queue=outgoing,******type=component
>>>>>>> (james)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The only logical relation that i can see between ActiveMQ and James
>>>>>>> is
>>>>>>> the
>>>>>>> outgoing queue size in both is 2. Where as there are no messages in
>>>>>>> List
>>>>>>> returned by james bean and ActiveMQ bean shows one message in queue.
>>>>>>>
>>>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>>>> configuration
>>>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we
>>>>>>> dont
>>>>>>> store copy of sent mails.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Farooq,
>>>>>>>
>>>>>>>
>>>>>>>> Looking at Destination=outgoing,Type=********Queue, the
>>>>>>>> EnqueueCount/DequeueCount/********QueueSize seem odd (14976 -
>>>>>>>> 14975 <>
>>>>>>>>
>>>>>>>> 2).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Can you link/find some logic between those ActiveMQ numbers and the
>>>>>>>> numbers shown in the James MBeans?
>>>>>>>>
>>>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any
>>>>>>>> changes
>>>>>>>> in
>>>>>>>> the configuration?
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>>
>>>>>>>>> Here you go..
>>>>>>>>> Attributes Value
>>>>>>>>> BeanName ConsumerCount
>>>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>>>> EnqueueCount
>>>>>>>>> browse
>>>>>>>>> Destination=ActiveMQ.DLQ,Type=********Queue 0 0 1
>>>>>>>>>
>>>>>>>>> 0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 0 Shows 1 message in
>>>>>>>>> outgoing queue,
>>>>>>>>> invalid recepient
>>>>>>>>> Destination=outgoing,Type=********Queue 10 5 2
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 14976
>>>>>>>>>
>>>>>>>>> 14975 shows 1 message
>>>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>>>> Destination=spool,Type=Queue 2 3 0 15146
>>>>>>>>> 15146
>>>>>>>>> no emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********TempQueue,Type=Topic 1
>>>>>>>>>
>>>>>>>>> 0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 0 0 146 no
>>>>>>>>> emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********Queue,Type=Topic 0 0
>>>>>>>>>
>>>>>>>>> 0
>>>>>>>>> 0 6 no emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********Producer.Queue.spool,**
>>>>>>>>> Type=**
>>>>>>>>>
>>>>>>>>> ****Topic
>>>>>>>>>
>>>>>>>>> 0
>>>>>>>>>
>>>>>>>>> 0 0 0 3 no emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********Producer.Queue.outgoing,****
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Type=**Topic
>>>>>>>>>
>>>>>>>>> 0 0 0 0 5 no emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********Consumer.Queue.spool,**
>>>>>>>>> Type=**
>>>>>>>>>
>>>>>>>>> ****Topic
>>>>>>>>>
>>>>>>>>> 0
>>>>>>>>>
>>>>>>>>> 0 0 0 253212 no emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********Consumer.Queue.outgoing,****
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Type=**Topic
>>>>>>>>>
>>>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>>>> Destination=ActiveMQ.Advisory.********Connection,Type=Topic 0
>>>>>>>>>
>>>>>>>>> 0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 0 0 1 no
>>>>>>>>> emails
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we
>>>>>>>>> send
>>>>>>>>> every 30 sec..
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> All, except the first and the last ones.
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>> Which mbean of activemq would you like me to check from
>>>>>>>>> the
>>>>>>>>> following ...
>>>>>>>>> org.apache.activemq:__********BrokerName=james,__**
>>>>>>>>> ConnectorName=tcp_//localhost_********__0,Type=Connector
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.Connection,********__Type=Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.Consumer.__********Queue.outgoing,Type=**Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.Consumer.__********Queue.spool,Type=Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.Producer.__********Queue.outgoing,Type=**Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.Producer.__********Queue.spool,Type=Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.Queue,Type=********__Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.Advisory.TempQueue,_********_Type=Topic
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _outgoing,Type=Queue
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Destination=_
>>>>>>>>> ******
>>>>>>>>> _spool,Type=Queue
>>>>>>>>> org.apache.activemq:__********
>>>>>>>>> BrokerName=james,Type=Broker
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>>>> eric@apache.org
>>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>>
>>>>>>>>> Any chance to compare those numbers with the ones
>>>>>>>>> given by
>>>>>>>>> the activemq
>>>>>>>>> mbeans?
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>>>>>
>>>>>>>>> "You mean to 'push out' the queue.
>>>>>>>>> The mail you send triggers the pending mails to
>>>>>>>>> go
>>>>>>>>> out?"
>>>>>>>>>
>>>>>>>>> Yes this new mail push the earlier mail out but
>>>>>>>>> itself
>>>>>>>>> gets stuck in
>>>>>>>>> spool,to which a new mail after 30 sec pushes
>>>>>>>>> out
>>>>>>>>> and
>>>>>>>>> that mail gets
>>>>>>>>> struck
>>>>>>>>> and soon...
>>>>>>>>>
>>>>>>>>> Can you guide me how to figure out the reason
>>>>>>>>> as to
>>>>>>>>> why
>>>>>>>>> the size attribute
>>>>>>>>> value is 5 and the browse List only contains 3
>>>>>>>>> mails
>>>>>>>>> details.
>>>>>>>>> Also Why The mail which gets stuck in spool its
>>>>>>>>> count
>>>>>>>>> is
>>>>>>>>> incremented in
>>>>>>>>> attribure Size but its details are not present
>>>>>>>>> in
>>>>>>>>> browse
>>>>>>>>> List..?
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi Farooq,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Here is the output which i get when i
>>>>>>>>> use
>>>>>>>>> Bean
>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>> __**queue=outgoing,type=__********component
>>>>>>>>>
>>>>>>>>> $>bean
>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>> __**queue=outgoing,type=__********component
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> #bean is set to
>>>>>>>>> org.apache.james:name=queue,**
>>>>>>>>> queue=outgoing,type=component
>>>>>>>>> $>info
>>>>>>>>> #mbean =
>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>> __**queue=outgoing,type=__********component
>>>>>>>>> #class name =
>>>>>>>>> org.apache.james.queue.****__********
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> library.MailQueueManagement
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> # attributes
>>>>>>>>> %0 - Size (long, r)
>>>>>>>>> # operations
>>>>>>>>> %0 - java.util.List browse()
>>>>>>>>> %1 - long clear()
>>>>>>>>> %2 - long flush()
>>>>>>>>> %3 - long
>>>>>>>>> removeWithName(java.lang.****_**
>>>>>>>>> ******_String
>>>>>>>>> p1)
>>>>>>>>> %4 - long
>>>>>>>>> removeWithRecipient(java.lang.****
>>>>>>>>> ****__****String
>>>>>>>>> p1)
>>>>>>>>> %5 - long
>>>>>>>>> removeWithSender(java.lang.*******
>>>>>>>>>
>>>>>>>>> ****__*String
>>>>>>>>>
>>>>>>>>> p1)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> #there's no notifications
>>>>>>>>> $>get Size
>>>>>>>>> #mbean =
>>>>>>>>> org.apache.james:name=queue,**********
>>>>>>>>> __**queue=outgoing,type=__********component:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Size = 7;
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Cool, it seems like you have found a JXM CLI
>>>>>>>>> which
>>>>>>>>> works fine.
>>>>>>>>> Which one is it?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Let me know if you need any further
>>>>>>>>> details.
>>>>>>>>>
>>>>>>>>> can you educate me as to Size= 7 is the
>>>>>>>>> no
>>>>>>>>> of
>>>>>>>>> mails still in outgoing
>>>>>>>>> spool
>>>>>>>>> or is some default size of outgoing
>>>>>>>>> queue.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> It is the number of pending mails in
>>>>>>>>> the
>>>>>>>>> queue.
>>>>>>>>>
>>>>>>>>> So you have 7 mails waiting to be sent to
>>>>>>>>> the
>>>>>>>>> outside world/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Also note that do deal with this
>>>>>>>>> spooling
>>>>>>>>> problem, the workaround that
>>>>>>>>> we
>>>>>>>>>
>>>>>>>>> did temporarily is that we created an
>>>>>>>>> application that sends an email to
>>>>>>>>> some email address every 30 sec.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> You mean to 'push out' the queue.
>>>>>>>>> The mail you send triggers the pending mails
>>>>>>>>> to go
>>>>>>>>> out?
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric
>>>>>>>>> Charles
>>>>>>>>> <eric@apache.org <mailto:
>>>>>>>>> eric@apache.org>>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Maybe the cloud's firewall blocks
>>>>>>>>> your
>>>>>>>>> requests.
>>>>>>>>>
>>>>>>>>> For JMX command line, type 'jmx
>>>>>>>>> cli' in
>>>>>>>>> google and experiment (tried
>>>>>>>>> one
>>>>>>>>> of these long time ago).
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 18/02/2013 10:11, Farooq Ahmed
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi Eric,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I tried remotely connecting to
>>>>>>>>> JMX
>>>>>>>>> using
>>>>>>>>> Jconsole and remote jmx
>>>>>>>>> connection
>>>>>>>>> method specified on
>>>>>>>>> http://james.apache.org/****
>>>>>>>>> server/3/config-system.html<__*
>>>>>>>>> *****
>>>>>>>>> **ht**tp://
>>>>>>>>> james.apache.org/****
>>>>>>>>> <http://james.apache.org/****>
>>>>>>>>> server/3/config-system.html<***
>>>>>>>>> *****
>>>>>>>>> ht__tp://
>>>>>>>>> james.apache.org/**__**server/******3/config-system.html<http://james.apache.org/**__**server/****3/config-system.html>
>>>>>>>>> <http:**//james.apache.org/**__****server/**3/config-system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>> >
>>>>>>>>> <http://**james.apache.org/**_**_**server/**3/config-system.**html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>>> <http://james.apache.org/****__**server/3/config-system.**html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <http://**james.apache.org/**_****_server/3/**config-system.**
>>>>>>>>> html <http://james.apache.org/**_**_server/3/**config-system.html>
>>>>>>>>> <http://james.apache.org/****__server/3/**config-system.**html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>>>> >
>>>>>>>>> **<http://james.apache.org/**_**_**server/3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> <http://james.apache.org/****
>>>>>>>>>>
>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>
>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <ht**tp://
>>>>>>>>> james.apache.org/**_**** <http://james.apache.org/**_**>
>>>>>>>>> **** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>> ><http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>> *_** <http://james.apache.org/**_****>>
>>>>>>>>> _server/**3/config-system.******html<http://james.apache.org/***
>>>>>>>>> **** <http://james.apache.org/*****><http://james.apache.org/*****<http://james.apache.org/***>
>>>>>>>>> >
>>>>>>>>> *__server/**3/config-system.******html<http://james.apache.**
>>>>>>>>> org/*** <http://james.apache.org/***>
>>>>>>>>>
>>>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/***
>>>>>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> <http://james.apache.org/****
>>>>>>>>>>
>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/******<http://james.apache.org/****>
>>>>>>>>>
>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> **<__http://james.apache.org/_******_**server/**3/config-**
>>>>>>>>> system.**<http://james.apache.org/_****_**server/**3/config-system.**>
>>>>>>>>>
>>>>>>>>>> **html<http://james.apache.**org/_**_**server/**3/config-**
>>>>>>>>>> system.**html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>>>> >
>>>>>>>>>> <http://james.apache.**org/__****server/**3/config-**system.**
>>>>>>>>>> html<http://james.apache.org/_**_**server/**3/config-system.**
>>>>>>>>>> html <http://james.apache.org/__**server/**3/config-system.html>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <http://james.apache.org/_**_****server/**3/config-system.html<http://james.apache.org/_**_**server/**3/config-system.html>
>>>>>>>>>> **<http://james.apache.org/_**_**server/**3/config-system.html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>>>> >
>>>>>>>>>> <**http://james.apache.org/__****server/**3/config-system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>> **<http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> **>
>>>>>>>>>>
>>>>>>>>>> <http://james.apache.org/**
>>>>>>>>>>
>>>>>>>>> server/**3/config-system.html<******http://james.apache.org/**
>>>>>>>>>
>>>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> **>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <**
>>>>>>>>>> http://james.apache.org/**_**** <http://james.apache.org/**_**>
>>>>>>>>>>
>>>>>>>>> **** <http://james.apache.org/**_******<http://james.apache.org/**_****>
>>>>>>>>> ><http://james.apache.org/***** <http://james.apache.org/***>
>>>>>>>>> *_** <http://james.apache.org/**_****>>
>>>>>>>>> _server/3/config-system.html<****h**ttp://james.apache.org/**_**
>>>>>>>>> _**** <http://james.apache.org/**__****><http://james.apache.org/*
>>>>>>>>> ***__** <http://james.apache.org/**__**>>
>>>>>>>>>
>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>>
>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <http://james.apache.org/****
>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>>
>>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <**ht__tp://james.apache.org/********server/__3/config-system.
>>>>>>>>> ****html<http://james.apache.org/******server/__3/config-system.**html>
>>>>>>>>> <http://james.apache.**org/****server/__3/config-**system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>> <http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>> >
>>>>>>>>>> **>
>>>>>>>>>> **<http://james.apache.org/******server/__3/config-system.html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>> >
>>>>>>>>>> <**http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> <http://james.apache.org/**
>>>>>>>>> server/3/config-system.html<****ht**tp://james.apache.org/****
>>>>>>>>> server/** <http://james.apache.org/**server/**><
>>>>>>>>> http://james.apache.**org/server/**<http://james.apache.org/server/**>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>> 3/config-system.html<http://****james.apache.org/server/3/**<http://james.apache.org/server/3/**>
>>>>>>>>>
>>>>>>>>> config-system.html<http://**james.apache.org/server/3/**
>>>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> But i could not get connected to
>>>>>>>>> jmx
>>>>>>>>> on
>>>>>>>>> my email server.
>>>>>>>>>
>>>>>>>>> Note that the server where i
>>>>>>>>> have
>>>>>>>>> deployed james is on azure cloud
>>>>>>>>> PAS
>>>>>>>>> network and is Ubunto system.
>>>>>>>>> Is there any mechanism where i
>>>>>>>>> can
>>>>>>>>> observe the message queue
>>>>>>>>> contents
>>>>>>>>> on
>>>>>>>>> local ubunto system using ssh
>>>>>>>>> only.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Farooq
>>>>>>>>>
>>>>>>>>> On Tue, Feb 12, 2013 at 11:02
>>>>>>>>> PM,
>>>>>>>>> Ajay
>>>>>>>>> Navgale <
>>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>>> <mailto:ajay.navgale@******
>>>>>>>>> central**
>>>>>>>>> ogic.net <http://centralogic.net><ajay.****navgale@**
>>>>>>>>> centralogic.net<
>>>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>**>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------- Forwarded message
>>>>>>>>> ----------
>>>>>>>>>
>>>>>>>>> From: Eric Charles <
>>>>>>>>> eric@apache.org
>>>>>>>>> <ma...@apache.org>>
>>>>>>>>>
>>>>>>>>> Date: Tue, Feb 12, 2013 at
>>>>>>>>> 7:52 PM
>>>>>>>>> Subject: Re: James Server
>>>>>>>>> SMTP
>>>>>>>>> Spooling Issue
>>>>>>>>> To: James Users List
>>>>>>>>> <
>>>>>>>>> server-user@james.apache.org
>>>>>>>>> <mailto:server-user@james.
>>>>>>>>> **
>>>>>>>>> apache.org <se...@james.apache.org>******>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> You mean you the newly
>>>>>>>>> spooled
>>>>>>>>> mails
>>>>>>>>> 'push-out' the remaining
>>>>>>>>> ones.
>>>>>>>>> After that, the latest one
>>>>>>>>> remains
>>>>>>>>> stucked in the queu?
>>>>>>>>>
>>>>>>>>> If such, that's very strange
>>>>>>>>> and
>>>>>>>>> we
>>>>>>>>> never saw that before.
>>>>>>>>> Do you use JMX to inspect
>>>>>>>>> the
>>>>>>>>> queue
>>>>>>>>> content/size?
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 12/02/2013 11:45, Ajay
>>>>>>>>> Navgale
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We are using james 3.0
>>>>>>>>> beta4.
>>>>>>>>> We have an issue while
>>>>>>>>> sending
>>>>>>>>> an email. There is
>>>>>>>>> always
>>>>>>>>> one
>>>>>>>>> outgoing
>>>>>>>>> mail
>>>>>>>>> left in spool and is
>>>>>>>>> delivered
>>>>>>>>> when any new outgoing
>>>>>>>>> mail
>>>>>>>>> is
>>>>>>>>> to
>>>>>>>>> be
>>>>>>>>> sent.
>>>>>>>>> Now previous mail gets
>>>>>>>>> delivered
>>>>>>>>> and this recent once
>>>>>>>>> sits
>>>>>>>>> in
>>>>>>>>> the
>>>>>>>>> spool.
>>>>>>>>> This is happening for
>>>>>>>>> Remote
>>>>>>>>> delivery.
>>>>>>>>>
>>>>>>>>> Can anyone throw some
>>>>>>>>> light on
>>>>>>>>> this.
>>>>>>>>>
>>>>>>>>> Thanks & Regards,
>>>>>>>>> Ajay
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------
>>>>>>>>> ****
>>>>>>>>> __********--------------------********--__--**
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --**
>>>>>>>>> --**
>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>
>>>>>>>>> server-user-unsubscribe@james.
>>>>>>>>> ****
>>>>>>>>> **
>>>>>>>>> __********
>>>>>>>>> apache.org <
>>>>>>>>> http://apache.org>
>>>>>>>>> <
>>>>>>>>> server-user-**unsubscribe@
>>>>>>>>> **__
>>>>>>>>> ****
>>>>>>>>> **ja**
>>>>>>>>> mes.apache.org
>>>>>>>>> <http://mes.apache.org
>>>>>>>>> ><http:/
>>>>>>>>> ****
>>>>>>>>> **/__
>>>>>>>>> james.apache.org
>>>>>>>>> <http://james.apache.org>>
>>>>>>>>> <unsubscribe@
>>>>>>>>> **james.apache.__
>>>>>>>>> ****
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> **org
>>>>>>>>> <http://james.apache.org>
>>>>>>>>> <
>>>>>>>>> unsubscribe@james.apache.org
>>>>>>>>> <mailto:unsubscribe@james.
>>>>>>>>> **
>>>>>>>>> apache.org <un...@james.apache.org>******>>__>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>> ***
>>>>>>>>>
>>>>>>>>> ***
>>>>>>>>>
>>>>>>>>> j**
>>>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>>>> <http://james.apache.org
>>>>>>>>> ><**
>>>>>>>>> unsubscribe@__james.apache.org
>>>>>>>>> <mailto:unsubscribe@james.
>>>>>>>>> **
>>>>>>>>> apache.org <un...@james.apache.org>******>>
>>>>>>>>> <server-user-**unsubscribe@
>>>>>>>>> __*
>>>>>>>>>
>>>>>>>>> ***
>>>>>>>>>
>>>>>>>>> j**
>>>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>>>> <mailto:unsubscribe@james.
>>>>>>>>> **
>>>>>>>>> apache.org <un...@james.apache.org>******><server-user-__**
>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>> james.apache.org <server-user-__unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>
>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> For additional
>>>>>>>>> commands,
>>>>>>>>> e-mail:
>>>>>>>>>
>>>>>>>>> server-user-help@james.apache.
>>>>>>>>> ****
>>>>>>>>> __**
>>>>>>>>> **
>>>>>>>>>
>>>>>>>>> ****org<
>>>>>>>>> server-user-help@james.
>>>>>>>>> ****__*
>>>>>>>>> *****
>>>>>>>>>
>>>>>>>>> apach**e.org
>>>>>>>>> <http://e.org> <
>>>>>>>>> http://apache.org>
>>>>>>>>> <
>>>>>>>>>
>>>>>>>>> server-user-help@james.
>>>>>>>>> **__***
>>>>>>>>> ***
>>>>>>>>>
>>>>>>>>> apach**
>>>>>>>>> e.org
>>>>>>>>> <http://e.org> <
>>>>>>>>> http://apache.org
>>>>>>>>>
>>>>>>>>> <
>>>>>>>>>>
>>>>>>>>>> server-user-help@james.
>>>>>>>>> ****
>>>>>>>>>
>>>>>>>>> apach**
>>>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>>>> user-help@james.__apache.org
>>>>>>>>> <mailto:server-user-help@**
>>>>>>>>> james.apache.org <server-user-help@james.****apac**he.org<
>>>>>>>>> http://apache.org**>
>>>>>>>>> <server-user-help@james.**apac**he.org <http://apache.org><
>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------
>>>>>>>>> ****
>>>>>>>>> **
>>>>>>>>> __******----------------------********--__--**
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --**
>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>> server-user-unsubscribe@james.**
>>>>>>>>> ****
>>>>>>>>> **__******
>>>>>>>>> apache.org
>>>>>>>>> <http://apache.org>
>>>>>>>>> <
>>>>>>>>> server-user-**unsubscribe@******
>>>>>>>>> **ja**
>>>>>>>>>
>>>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>>>> <http://james.apache.org><****
>>>>>>>>> unsubscribe@__
>>>>>>>>> james.apache.org
>>>>>>>>> <mailto:unsubscribe@james.******
>>>>>>>>> ap**
>>>>>>>>> ache.org<http://apache.org**>
>>>>>>>>> <unsubscribe@james.**apache.****org <http://apache.org> <
>>>>>>>>> unsubscribe@james.apache.org>****>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <server-user-**unsubscribe@__***
>>>>>>>>>> **
>>>>>>>>>>
>>>>>>>>>>> *j**
>>>>>>>>>>>
>>>>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>>>>>
>>>>>>>>> unsubscribe@james.**
>>>>>>>>> apache.org <un...@james.apache.org>******><server-user-__**
>>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>>> james.apache.org <server-user-__unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> <mailto:server-user-**
>>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>>
>>>>>>>>> james.apache.org <server-user-unsubscribe@**jam**es.apache.org<http://james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> For additional commands,
>>>>>>>>> e-mail:
>>>>>>>>> server-user-help@james.apache.*
>>>>>>>>> *****
>>>>>>>>> **__**
>>>>>>>>>
>>>>>>>>> ****org<
>>>>>>>>> server-user-help@james.**__*******
>>>>>>>>> *apach**
>>>>>>>>>
>>>>>>>>> e.org
>>>>>>>>> <http://e.org> <http://apache.org>
>>>>>>>>> <
>>>>>>>>> server-user-help@james.********
>>>>>>>>> apach**__
>>>>>>>>>
>>>>>>>>> e.org
>>>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>>>> <http://apache.org><server-********
>>>>>>>>> user-help@james.
>>>>>>>>> __apache.org
>>>>>>>>> <mailto:server-user-help@******
>>>>>>>>> jam**
>>>>>>>>> es.apache.org <http://james.apache.org><****server-user-**
>>>>>>>>> help@james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------********
>>>>>>>>> __****------------------------********--__--**
>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>> server-user-unsubscribe@james.**
>>>>>>>>> ******__****
>>>>>>>>> apache.org
>>>>>>>>> <http://apache.org><
>>>>>>>>> server-user-**unsubscribe@__******ja**
>>>>>>>>>
>>>>>>>>> mes.apache.org<
>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>> <mailto:unsubscribe@james.******ap**
>>>>>>>>> ache.org<
>>>>>>>>> http://apache.org**>
>>>>>>>>> <unsubscribe@james.**apache.****org <http://apache.org> <
>>>>>>>>> unsubscribe@james.apache.org>****>
>>>>>>>>>
>>>>>>>>> <server-user-__**unsubscribe@******james.apache.org<**
>>>>>>>>> unsubscribe@**
>>>>>>>>>
>>>>>>>>>> james.apache.org <un...@james.apache.org>**>
>>>>>>>>>> <server-user-_**_unsubscribe@****james.apache.org<unsubscribe@**
>>>>>>>>>> james.apache.org <un...@james.apache.org>>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> <mailto:server-user-******unsubscr**
>>>>>>>>>>
>>>>>>>>> ibe@james.apache.org <un...@james.apache.org>****<server-**
>>>>>>>>> user-unsubscribe@james.apache.******org<server-user-**unsubscribe@
>>>>>>>>> **
>>>>>>>>>
>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>> >>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> server-user-help@james.apache.**
>>>>>>>>> ******__****org<
>>>>>>>>> server-user-help@james.********apach**__
>>>>>>>>> e.org<
>>>>>>>>>
>>>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>>>> <http://apache.org>
>>>>>>>>> <server-user-help@james.__******apac**
>>>>>>>>> he.org<
>>>>>>>>> http://apache.org**>
>>>>>>>>> <mailto:server-user-help@******jam**
>>>>>>>>> es.apache.org<http://**james.**apache.org<http://james.apache.org><
>>>>>>>>> http://james.apache.org>>
>>>>>>>>> <server-user-**help@james.**ap**ache.org <http://apache.org> <
>>>>>>>>> help@james.apache.org><
>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------********
>>>>>>>>> __**--------------------------********--__--**---------
>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>> server-user-unsubscribe@james.********__**
>>>>>>>>> apache.org
>>>>>>>>> <http://apache.org><server-*******
>>>>>>>>> *user-__unsubscribe@james.
>>>>>>>>> **
>>>>>>>>> apache.org <server-user-__unsubscribe@****j**ames.apache.org<
>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> <mailto:server-user-******unsubscr**
>>>>>>>>>>
>>>>>>>>> ibe@james.apache.org**<un...@james.apache.org>
>>>>>>>>> >
>>>>>>>>> <server-**user-unsubscribe@****james.apache.**org<server-**
>>>>>>>>>
>>>>>>>>> user-unsubscribe@james.apache.****org<server-user-unsubscribe@**
>>>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> server-user-help@james.apache.******
>>>>>>>>>>
>>>>>>>>> **__**org<server-user-help@**
>>>>>>>>> james.__apache.org
>>>>>>>>> <mailto:server-user-help@******jam**es.apache.org<
>>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>>> <server-user-**help@james.**ap**ache.org <http://apache.org> <
>>>>>>>>> help@james.apache.org><
>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------**
>>>>>>>>> ******__----------------------**--
>>>>>>>>> **--**
>>>>>>>>> --**
>>>>>>>>> --__---------
>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**
>>>>>>>>> ******__
>>>>>>>>> apache.org
>>>>>>>>> <mailto:server-user-******unsubscr**ibe@james.apache.org**
>>>>>>>>> **<
>>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>>> <server-**user-unsubscribe@****james.apache.**org<server-**
>>>>>>>>>
>>>>>>>>> user-unsubscribe@james.apache.****org<server-user-unsubscribe@**
>>>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>>
>>>>>>>>>> ****
>>>>>>>>> __org
>>>>>>>>> <mailto:server-user-help@******jam**es.apache.org<http://**
>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>> <server-user-**help@james.**ap**ache.org <http://apache.org> <
>>>>>>>>> help@james.apache.org><
>>>>>>>>> server-user-help@**james.**apache.org <http://james.apache.org><
>>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------********------------------------**
>>>>>>>>> --**--**
>>>>>>>>> --**---------
>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>>> apache.org<
>>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.
>>>>>>>>>> ****
>>>>>>>>>>
>>>>>>>>> **
>>>>>>>>> **org<server-user-help@james.******apache.org<server-user-**help@
>>>>>>>>> **
>>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>> >>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> ------------------------------********------------------------*
>>>>>>>>> *--**
>>>>>>>>> --**
>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>> apache.org<
>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> >
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.*
>>>>>>>>> ***
>>>>>>>>>
>>>>>>>> ****org<
>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org> <
>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>> >
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******--------------------------**
>>>>>>> --**
>>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******
>>>>>> apache.org<
>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>> >
>>>>>>
>>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>> ****org<
>>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>> >
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>> >
>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi,
Could it be that the mail you send to the non-existing id bounce back
from the remote smtp, and that your mailet config send them again to the
remote SMTP, and so on... bouncing so many times that your outgoing
queue is overloaded?
Thx, Eric
On 06/03/2013 12:27, Farooq Ahmed wrote:
> Hi Eric,
>
> Here is the test scenario.
> I have created a new instance of James and the only difference between the
> earlier instance and this one is that earlier instance uses java 1.7 and
> this one uses java 1.6 , else every thing is same.
>
> With this difference also i am able to reproduce the issue.
>
> Initially i sent emails to valid email ids and emails were getting
> delivered as expected.
> Later i sent email to multiple ids which does not exist, though there mail
> providers were valid.
>
> e.g SomeUniqueID@vsnl.net,
> SomeUniqueID@rediffmail.com etc
>
> After next day i checked bean
> org.apache.james:name=queue,queue=outgoing,type=component
>
> and there were many mails all having "state = error;".
> Now today mail are getting spooled and not delivered, though i can
> instantly receiving emails but outgoing emails are getting stucked in queue.
>
> I am using james3beta4.
> Let me know if you can reproduce using same version.
>
> Regards,
> Farooq
>
> On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org> wrote:
>
>> Hi Farooq,
>>
>> Unfortunately, I can not reproduce it.
>> Any chance for you to write a Java unit test that shows this?
>> Thx, Eric
>>
>>
>> On 25/02/2013 05:25, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> Any further info on this, this issue is still unresolved..
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>>> <fa...@centralogic.net>**wrote:
>>>
>>> We do use to restart the system after that the spooled mails are
>>>> delivered
>>>> and after restart first mail is sent out with out getting stuck in
>>>> outgoing
>>>> queue but from second mail onwards one mail always keeps stuck in
>>>> outgoing
>>>> queue.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>>
>>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
>>>>
>>>> Did you already tried a stop/start of James to see if those numbers
>>>>> change?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>>
>>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>>> Queue(ActiveMQ)
>>>>>> and
>>>>>> Size is also 2 in name=queue,queue=outgoing,****type=component (james)
>>>>>>
>>>>>>
>>>>>> The only logical relation that i can see between ActiveMQ and James is
>>>>>> the
>>>>>> outgoing queue size in both is 2. Where as there are no messages in
>>>>>> List
>>>>>> returned by james bean and ActiveMQ bean shows one message in queue.
>>>>>>
>>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>>> configuration
>>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we dont
>>>>>> store copy of sent mails.
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
>>>>>>
>>>>>> Hi Farooq,
>>>>>>
>>>>>>>
>>>>>>> Looking at Destination=outgoing,Type=******Queue, the
>>>>>>> EnqueueCount/DequeueCount/******QueueSize seem odd (14976 - 14975 <>
>>>>>>> 2).
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Can you link/find some logic between those ActiveMQ numbers and the
>>>>>>> numbers shown in the James MBeans?
>>>>>>>
>>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any changes
>>>>>>> in
>>>>>>> the configuration?
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>>>
>>>>>>>> Here you go..
>>>>>>>> Attributes Value
>>>>>>>> BeanName ConsumerCount
>>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>>> EnqueueCount
>>>>>>>> browse
>>>>>>>> Destination=ActiveMQ.DLQ,Type=******Queue 0 0 1
>>>>>>>> 0
>>>>>>>>
>>>>>>>>
>>>>>>>> 0 Shows 1 message in
>>>>>>>> outgoing queue,
>>>>>>>> invalid recepient
>>>>>>>> Destination=outgoing,Type=******Queue 10 5 2
>>>>>>>>
>>>>>>>> 14976
>>>>>>>>
>>>>>>>> 14975 shows 1 message
>>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>>> Destination=spool,Type=Queue 2 3 0 15146 15146
>>>>>>>> no emails
>>>>>>>> Destination=ActiveMQ.Advisory.******TempQueue,Type=Topic 1
>>>>>>>> 0
>>>>>>>>
>>>>>>>>
>>>>>>>> 0 0 146 no
>>>>>>>> emails
>>>>>>>> Destination=ActiveMQ.Advisory.******Queue,Type=Topic 0 0
>>>>>>>> 0
>>>>>>>> 0 6 no emails
>>>>>>>> Destination=ActiveMQ.Advisory.******Producer.Queue.spool,Type=**
>>>>>>>> ****Topic
>>>>>>>>
>>>>>>>> 0
>>>>>>>>
>>>>>>>> 0 0 0 3 no emails
>>>>>>>> Destination=ActiveMQ.Advisory.******Producer.Queue.outgoing,**
>>>>>>>>
>>>>>>>> Type=**Topic
>>>>>>>>
>>>>>>>> 0 0 0 0 5 no emails
>>>>>>>> Destination=ActiveMQ.Advisory.******Consumer.Queue.spool,Type=**
>>>>>>>> ****Topic
>>>>>>>>
>>>>>>>> 0
>>>>>>>>
>>>>>>>> 0 0 0 253212 no emails
>>>>>>>> Destination=ActiveMQ.Advisory.******Consumer.Queue.outgoing,**
>>>>>>>>
>>>>>>>> Type=**Topic
>>>>>>>>
>>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>>> Destination=ActiveMQ.Advisory.******Connection,Type=Topic 0
>>>>>>>> 0
>>>>>>>>
>>>>>>>>
>>>>>>>> 0 0 1 no
>>>>>>>> emails
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we send
>>>>>>>> every 30 sec..
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>> All, except the first and the last ones.
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>> Which mbean of activemq would you like me to check from the
>>>>>>>> following ...
>>>>>>>> org.apache.activemq:__******BrokerName=james,__**
>>>>>>>> ConnectorName=tcp_//localhost_******__0,Type=Connector
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.Connection,******__Type=Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.Consumer.__******Queue.outgoing,Type=Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.Consumer.__******Queue.spool,Type=Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.Producer.__******Queue.outgoing,Type=Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.Producer.__******Queue.spool,Type=Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.Queue,Type=******__Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.Advisory.TempQueue,_******_Type=Topic
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _outgoing,Type=Queue
>>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>>> ******
>>>>>>>> _spool,Type=Queue
>>>>>>>> org.apache.activemq:__******BrokerName=james,Type=Broker
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>>> eric@apache.org
>>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>>
>>>>>>>> Any chance to compare those numbers with the ones
>>>>>>>> given by
>>>>>>>> the activemq
>>>>>>>> mbeans?
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>>>>
>>>>>>>> "You mean to 'push out' the queue.
>>>>>>>> The mail you send triggers the pending mails to go
>>>>>>>> out?"
>>>>>>>>
>>>>>>>> Yes this new mail push the earlier mail out but
>>>>>>>> itself
>>>>>>>> gets stuck in
>>>>>>>> spool,to which a new mail after 30 sec pushes out
>>>>>>>> and
>>>>>>>> that mail gets
>>>>>>>> struck
>>>>>>>> and soon...
>>>>>>>>
>>>>>>>> Can you guide me how to figure out the reason as to
>>>>>>>> why
>>>>>>>> the size attribute
>>>>>>>> value is 5 and the browse List only contains 3
>>>>>>>> mails
>>>>>>>> details.
>>>>>>>> Also Why The mail which gets stuck in spool its
>>>>>>>> count
>>>>>>>> is
>>>>>>>> incremented in
>>>>>>>> attribure Size but its details are not present in
>>>>>>>> browse
>>>>>>>> List..?
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>>>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>>>>>>
>>>>>>>> Hi Farooq,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>>
>>>>>>>> Here is the output which i get when i use
>>>>>>>> Bean
>>>>>>>> org.apache.james:name=queue,********
>>>>>>>> __**queue=outgoing,type=__******component
>>>>>>>>
>>>>>>>> $>bean
>>>>>>>> org.apache.james:name=queue,********
>>>>>>>> __**queue=outgoing,type=__******component
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> #bean is set to
>>>>>>>> org.apache.james:name=queue,**
>>>>>>>> queue=outgoing,type=component
>>>>>>>> $>info
>>>>>>>> #mbean =
>>>>>>>> org.apache.james:name=queue,********
>>>>>>>> __**queue=outgoing,type=__******component
>>>>>>>> #class name =
>>>>>>>> org.apache.james.queue.****__******
>>>>>>>>
>>>>>>>>
>>>>>>>> library.MailQueueManagement
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> # attributes
>>>>>>>> %0 - Size (long, r)
>>>>>>>> # operations
>>>>>>>> %0 - java.util.List browse()
>>>>>>>> %1 - long clear()
>>>>>>>> %2 - long flush()
>>>>>>>> %3 - long
>>>>>>>> removeWithName(java.lang.****_******_String
>>>>>>>> p1)
>>>>>>>> %4 - long
>>>>>>>> removeWithRecipient(java.lang.**
>>>>>>>> ****__****String
>>>>>>>> p1)
>>>>>>>> %5 - long
>>>>>>>> removeWithSender(java.lang.*****
>>>>>>>> ****__*String
>>>>>>>>
>>>>>>>> p1)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> #there's no notifications
>>>>>>>> $>get Size
>>>>>>>> #mbean =
>>>>>>>> org.apache.james:name=queue,********
>>>>>>>> __**queue=outgoing,type=__******component:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Size = 7;
>>>>>>>>
>>>>>>>>
>>>>>>>> Cool, it seems like you have found a JXM CLI
>>>>>>>> which
>>>>>>>> works fine.
>>>>>>>> Which one is it?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Let me know if you need any further details.
>>>>>>>>
>>>>>>>> can you educate me as to Size= 7 is the no
>>>>>>>> of
>>>>>>>> mails still in outgoing
>>>>>>>> spool
>>>>>>>> or is some default size of outgoing queue.
>>>>>>>>
>>>>>>>>
>>>>>>>> It is the number of pending mails in the
>>>>>>>> queue.
>>>>>>>>
>>>>>>>> So you have 7 mails waiting to be sent to the
>>>>>>>> outside world/
>>>>>>>>
>>>>>>>>
>>>>>>>> Also note that do deal with this spooling
>>>>>>>> problem, the workaround that
>>>>>>>> we
>>>>>>>>
>>>>>>>> did temporarily is that we created an
>>>>>>>> application that sends an email to
>>>>>>>> some email address every 30 sec.
>>>>>>>>
>>>>>>>>
>>>>>>>> You mean to 'push out' the queue.
>>>>>>>> The mail you send triggers the pending mails
>>>>>>>> to go
>>>>>>>> out?
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric
>>>>>>>> Charles
>>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>> Maybe the cloud's firewall blocks your
>>>>>>>> requests.
>>>>>>>>
>>>>>>>> For JMX command line, type 'jmx cli' in
>>>>>>>> google and experiment (tried
>>>>>>>> one
>>>>>>>> of these long time ago).
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 18/02/2013 10:11, Farooq Ahmed
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi Eric,
>>>>>>>>
>>>>>>>>
>>>>>>>> I tried remotely connecting to JMX
>>>>>>>> using
>>>>>>>> Jconsole and remote jmx
>>>>>>>> connection
>>>>>>>> method specified on
>>>>>>>> http://james.apache.org/****
>>>>>>>> server/3/config-system.html<__****
>>>>>>>> **ht**tp://
>>>>>>>> james.apache.org/****
>>>>>>>> <http://james.apache.org/****>
>>>>>>>> server/3/config-system.html<******
>>>>>>>> ht__tp://
>>>>>>>> james.apache.org/**__**server/****3/config-system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>>> <http://**james.apache.org/**__**server/**3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>>>>
>>>>>>>> <http://**james.apache.org/**_**_server/3/**config-system.html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> <http://james.apache.org/****
>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>> <ht**tp://james.apache.org/**_**
>>>>>>>> **** <http://james.apache.org/**_****><http://james.apache.org/***
>>>>>>>> *_** <http://james.apache.org/**_**>>
>>>>>>>> _server/**3/config-system.****html<http://james.apache.org/*****<http://james.apache.org/***>
>>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/***
>>>>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> <http://james.apache.org/****
>>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> **<__http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>>> **html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>>> <http://james.apache.**org/__**server/**3/config-**system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>>>>
>>>>>>>>> <http://james.apache.org/_**_**server/**3/config-system.html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>>> <**http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>>>>
>>>>>>>>> **>
>>>>>>>>>
>>>>>>>>> <http://james.apache.org/**
>>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> **>
>>>>>>>>>
>>>>>>>>> <**http://james.apache.org/**_**
>>>>>>>> **** <http://james.apache.org/**_****><http://james.apache.org/***
>>>>>>>> *_** <http://james.apache.org/**_**>>
>>>>>>>> _server/3/config-system.html<**h**ttp://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>>
>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> <http://james.apache.org/****
>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> <**ht__tp://james.apache.org/******server/__3/config-system.**html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>>> <http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>> **>
>>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>> <http://james.apache.org/**
>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**server/**<http://james.apache.org/server/**>
>>>>>>>>
>>>>>>>> 3/config-system.html<http://**james.apache.org/server/3/**
>>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> But i could not get connected to
>>>>>>>> jmx
>>>>>>>> on
>>>>>>>> my email server.
>>>>>>>>
>>>>>>>> Note that the server where i have
>>>>>>>> deployed james is on azure cloud
>>>>>>>> PAS
>>>>>>>> network and is Ubunto system.
>>>>>>>> Is there any mechanism where i can
>>>>>>>> observe the message queue contents
>>>>>>>> on
>>>>>>>> local ubunto system using ssh only.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Tue, Feb 12, 2013 at 11:02 PM,
>>>>>>>> Ajay
>>>>>>>> Navgale <
>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>> <mailto:ajay.navgale@****central**
>>>>>>>> ogic.net <http://centralogic.net><ajay.**navgale@**centralogic.net<
>>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------- Forwarded message
>>>>>>>> ----------
>>>>>>>>
>>>>>>>> From: Eric Charles <
>>>>>>>> eric@apache.org
>>>>>>>> <ma...@apache.org>>
>>>>>>>>
>>>>>>>> Date: Tue, Feb 12, 2013 at
>>>>>>>> 7:52 PM
>>>>>>>> Subject: Re: James Server SMTP
>>>>>>>> Spooling Issue
>>>>>>>> To: James Users List
>>>>>>>> <server-user@james.apache.org
>>>>>>>> <mailto:server-user@james.**
>>>>>>>> apache.org <se...@james.apache.org>****>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>> You mean you the newly spooled
>>>>>>>> mails
>>>>>>>> 'push-out' the remaining ones.
>>>>>>>> After that, the latest one
>>>>>>>> remains
>>>>>>>> stucked in the queu?
>>>>>>>>
>>>>>>>> If such, that's very strange
>>>>>>>> and
>>>>>>>> we
>>>>>>>> never saw that before.
>>>>>>>> Do you use JMX to inspect the
>>>>>>>> queue
>>>>>>>> content/size?
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 12/02/2013 11:45, Ajay
>>>>>>>> Navgale
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>> We are using james 3.0
>>>>>>>> beta4.
>>>>>>>> We have an issue while
>>>>>>>> sending
>>>>>>>> an email. There is always
>>>>>>>> one
>>>>>>>> outgoing
>>>>>>>> mail
>>>>>>>> left in spool and is
>>>>>>>> delivered
>>>>>>>> when any new outgoing mail
>>>>>>>> is
>>>>>>>> to
>>>>>>>> be
>>>>>>>> sent.
>>>>>>>> Now previous mail gets
>>>>>>>> delivered
>>>>>>>> and this recent once sits
>>>>>>>> in
>>>>>>>> the
>>>>>>>> spool.
>>>>>>>> This is happening for
>>>>>>>> Remote
>>>>>>>> delivery.
>>>>>>>>
>>>>>>>> Can anyone throw some
>>>>>>>> light on
>>>>>>>> this.
>>>>>>>>
>>>>>>>> Thanks & Regards,
>>>>>>>> Ajay
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------
>>>>>>>> ****
>>>>>>>> __********--------------------******--__--**
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --**
>>>>>>>> --**
>>>>>>>>
>>>>>>>> --**---------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> server-user-unsubscribe@james.
>>>>>>>> ****
>>>>>>>> **
>>>>>>>> __********
>>>>>>>> apache.org <http://apache.org>
>>>>>>>> <
>>>>>>>> server-user-**unsubscribe@**__
>>>>>>>> ****
>>>>>>>> **ja**
>>>>>>>> mes.apache.org
>>>>>>>> <http://mes.apache.org><http:/
>>>>>>>> ****
>>>>>>>> **/__
>>>>>>>> james.apache.org
>>>>>>>> <http://james.apache.org>>
>>>>>>>> <unsubscribe@**james.apache.__
>>>>>>>> ****
>>>>>>>>
>>>>>>>> **org
>>>>>>>> <http://james.apache.org>
>>>>>>>> <unsubscribe@james.apache.org
>>>>>>>> <mailto:unsubscribe@james.**
>>>>>>>> apache.org <un...@james.apache.org>****>>__>
>>>>>>>>
>>>>>>>>
>>>>>>>> <server-user-**unsubscribe@***
>>>>>>>> ***
>>>>>>>>
>>>>>>>> j**
>>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>>> <http://james.apache.org><**
>>>>>>>> unsubscribe@__james.apache.org
>>>>>>>> <mailto:unsubscribe@james.**
>>>>>>>> apache.org <un...@james.apache.org>****>>
>>>>>>>> <server-user-**unsubscribe@__*
>>>>>>>> ***
>>>>>>>>
>>>>>>>> j**
>>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>>> <mailto:unsubscribe@james.**
>>>>>>>> apache.org <un...@james.apache.org>****><server-user-__**
>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>
>>>>>>>> <mailto:server-user-**
>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>
>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> For additional
>>>>>>>> commands,
>>>>>>>> e-mail:
>>>>>>>>
>>>>>>>> server-user-help@james.apache.
>>>>>>>> ****
>>>>>>>> __**
>>>>>>>> **
>>>>>>>>
>>>>>>>> ****org<
>>>>>>>> server-user-help@james.****__*
>>>>>>>> *****
>>>>>>>>
>>>>>>>> apach**e.org
>>>>>>>> <http://e.org> <
>>>>>>>> http://apache.org>
>>>>>>>> <
>>>>>>>>
>>>>>>>> server-user-help@james.**__***
>>>>>>>> ***
>>>>>>>>
>>>>>>>> apach**
>>>>>>>> e.org
>>>>>>>> <http://e.org> <
>>>>>>>> http://apache.org
>>>>>>>>
>>>>>>>>> <
>>>>>>>>>
>>>>>>>> server-user-help@james.****
>>>>>>>>
>>>>>>>> apach**
>>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>>> user-help@james.__apache.org
>>>>>>>> <mailto:server-user-help@**
>>>>>>>> james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------
>>>>>>>> ****
>>>>>>>> **
>>>>>>>> __******----------------------******--__--**
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --**
>>>>>>>>
>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> server-user-unsubscribe@james.****
>>>>>>>> **__******
>>>>>>>> apache.org
>>>>>>>> <http://apache.org>
>>>>>>>> <
>>>>>>>> server-user-**unsubscribe@******ja**
>>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>>> <http://james.apache.org><****
>>>>>>>> unsubscribe@__
>>>>>>>> james.apache.org
>>>>>>>> <mailto:unsubscribe@james.****ap**
>>>>>>>> ache.org<http://apache.org**>
>>>>>>>> <unsubscribe@james.**apache.**org <http://apache.org> <
>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>
>>>>>>>>
>>>>>>>>> <server-user-**unsubscribe@__***
>>>>>>>>>> *j**
>>>>>>>>>>
>>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>>> unsubscribe@james.**
>>>>>>>> apache.org <un...@james.apache.org>****><server-user-__**
>>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>
>>>>>>>> <mailto:server-user-**
>>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>>
>>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> For additional commands, e-mail:
>>>>>>>> server-user-help@james.apache.****
>>>>>>>> **__**
>>>>>>>>
>>>>>>>> ****org<
>>>>>>>> server-user-help@james.**__*****
>>>>>>>> *apach**
>>>>>>>>
>>>>>>>> e.org
>>>>>>>> <http://e.org> <http://apache.org> <
>>>>>>>> server-user-help@james.******apach**__
>>>>>>>> e.org
>>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>>> <http://apache.org><server-******
>>>>>>>> user-help@james.
>>>>>>>> __apache.org
>>>>>>>> <mailto:server-user-help@****jam**
>>>>>>>> es.apache.org <http://james.apache.org><**server-user-**
>>>>>>>> help@james.apache.org <se...@james.apache.org>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******
>>>>>>>> __****------------------------******--__--**
>>>>>>>>
>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> server-user-unsubscribe@james.******__****
>>>>>>>> apache.org
>>>>>>>> <http://apache.org><
>>>>>>>> server-user-**unsubscribe@__****ja**
>>>>>>>> mes.apache.org<
>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>> <mailto:unsubscribe@james.****ap**ache.org<
>>>>>>>> http://apache.org**>
>>>>>>>> <unsubscribe@james.**apache.**org <http://apache.org> <
>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>
>>>>>>>> <server-user-__**unsubscribe@****james.apache.org<unsubscribe@**
>>>>>>>>> james.apache.org <un...@james.apache.org>>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> <mailto:server-user-****unsubscr**
>>>>>>>> ibe@james.apache.org <un...@james.apache.org>**<server-**
>>>>>>>> user-unsubscribe@james.apache.****org<server-user-unsubscribe@**
>>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>> For additional commands, e-mail:
>>>>>>>> server-user-help@james.apache.******__****org<
>>>>>>>> server-user-help@james.******apach**__e.org<
>>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>>> <http://apache.org>
>>>>>>>> <server-user-help@james.__****apac**he.org<
>>>>>>>> http://apache.org**>
>>>>>>>> <mailto:server-user-help@****jam**
>>>>>>>> es.apache.org<http://**james.apache.org <http://james.apache.org>>
>>>>>>>> <server-user-**help@james.**apache.org <he...@james.apache.org><
>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******
>>>>>>>> __**--------------------------******--__--**---------
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> server-user-unsubscribe@james.******__**apache.org
>>>>>>>> <http://apache.org><server-*****
>>>>>>>> *user-__unsubscribe@james.
>>>>>>>> **
>>>>>>>> apache.org <server-user-__unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> <mailto:server-user-****unsubscr**
>>>>>>>> ibe@james.apache.org**<un...@james.apache.org>
>>>>>>>> <server-**user-unsubscribe@**james.apache.**org<server-**
>>>>>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>>
>>>>>>>>> server-user-help@james.apache.****
>>>>>>>> **__**org<server-user-help@**
>>>>>>>> james.__apache.org
>>>>>>>> <mailto:server-user-help@****jam**es.apache.org<
>>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>>> <server-user-**help@james.**apache.org <he...@james.apache.org><
>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******__------------------------
>>>>>>>> **--**
>>>>>>>> --**
>>>>>>>> --__---------
>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******__
>>>>>>>> apache.org
>>>>>>>> <mailto:server-user-****unsubscr**ibe@james.apache.org**<
>>>>>>>> unsubscribe@james.apache.org>
>>>>>>>> <server-**user-unsubscribe@**james.apache.**org<server-**
>>>>>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> server-user-help@james.apache.
>>>>>>>>>
>>>>>>>> ****
>>>>>>>> __org
>>>>>>>> <mailto:server-user-help@****jam**es.apache.org<http://**
>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>> <server-user-**help@james.**apache.org <he...@james.apache.org><
>>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******--------------------------**--**
>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******
>>>>>>>> apache.org<
>>>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>>> **
>>>>>>>> **org<server-user-help@james.****apache.org<server-user-help@**
>>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******--------------------------**
>>>>>>>> --**
>>>>>>>>
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******
>>>>>>> apache.org<
>>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>> ****org<
>>>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>>
>>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
Here is the test scenario.
I have created a new instance of James and the only difference between the
earlier instance and this one is that earlier instance uses java 1.7 and
this one uses java 1.6 , else every thing is same.
With this difference also i am able to reproduce the issue.
Initially i sent emails to valid email ids and emails were getting
delivered as expected.
Later i sent email to multiple ids which does not exist, though there mail
providers were valid.
e.g SomeUniqueID@vsnl.net,
SomeUniqueID@rediffmail.com etc
After next day i checked bean
org.apache.james:name=queue,queue=outgoing,type=component
and there were many mails all having "state = error;".
Now today mail are getting spooled and not delivered, though i can
instantly receiving emails but outgoing emails are getting stucked in queue.
I am using james3beta4.
Let me know if you can reproduce using same version.
Regards,
Farooq
On Mon, Feb 25, 2013 at 11:52 AM, Eric Charles <er...@apache.org> wrote:
> Hi Farooq,
>
> Unfortunately, I can not reproduce it.
> Any chance for you to write a Java unit test that shows this?
> Thx, Eric
>
>
> On 25/02/2013 05:25, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> Any further info on this, this issue is still unresolved..
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
>> <fa...@centralogic.net>**wrote:
>>
>> We do use to restart the system after that the spooled mails are
>>> delivered
>>> and after restart first mail is sent out with out getting stuck in
>>> outgoing
>>> queue but from second mail onwards one mail always keeps stuck in
>>> outgoing
>>> queue.
>>>
>>> Regards,
>>> Farooq
>>>
>>>
>>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
>>>
>>> Did you already tried a stop/start of James to see if those numbers
>>>> change?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>>
>>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=****
>>>>> Queue(ActiveMQ)
>>>>> and
>>>>> Size is also 2 in name=queue,queue=outgoing,****type=component (james)
>>>>>
>>>>>
>>>>> The only logical relation that i can see between ActiveMQ and James is
>>>>> the
>>>>> outgoing queue size in both is 2. Where as there are no messages in
>>>>> List
>>>>> returned by james bean and ActiveMQ bean shows one message in queue.
>>>>>
>>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>>> configuration
>>>>> files of james for spams, fakeipaddress, baeysian algorithm and we dont
>>>>> store copy of sent mails.
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
>>>>>
>>>>> Hi Farooq,
>>>>>
>>>>>>
>>>>>> Looking at Destination=outgoing,Type=******Queue, the
>>>>>> EnqueueCount/DequeueCount/******QueueSize seem odd (14976 - 14975 <>
>>>>>> 2).
>>>>>>
>>>>>>
>>>>>>
>>>>>> Can you link/find some logic between those ActiveMQ numbers and the
>>>>>> numbers shown in the James MBeans?
>>>>>>
>>>>>> Do you run with the embedded ActiveMQ shipped by default? Any changes
>>>>>> in
>>>>>> the configuration?
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>>
>>>>>>> Here you go..
>>>>>>> Attributes Value
>>>>>>> BeanName ConsumerCount
>>>>>>> ProducerCount QueueSize DequeueCount
>>>>>>> EnqueueCount
>>>>>>> browse
>>>>>>> Destination=ActiveMQ.DLQ,Type=******Queue 0 0 1
>>>>>>> 0
>>>>>>>
>>>>>>>
>>>>>>> 0 Shows 1 message in
>>>>>>> outgoing queue,
>>>>>>> invalid recepient
>>>>>>> Destination=outgoing,Type=******Queue 10 5 2
>>>>>>>
>>>>>>> 14976
>>>>>>>
>>>>>>> 14975 shows 1 message
>>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>>> Destination=spool,Type=Queue 2 3 0 15146 15146
>>>>>>> no emails
>>>>>>> Destination=ActiveMQ.Advisory.******TempQueue,Type=Topic 1
>>>>>>> 0
>>>>>>>
>>>>>>>
>>>>>>> 0 0 146 no
>>>>>>> emails
>>>>>>> Destination=ActiveMQ.Advisory.******Queue,Type=Topic 0 0
>>>>>>> 0
>>>>>>> 0 6 no emails
>>>>>>> Destination=ActiveMQ.Advisory.******Producer.Queue.spool,Type=**
>>>>>>> ****Topic
>>>>>>>
>>>>>>> 0
>>>>>>>
>>>>>>> 0 0 0 3 no emails
>>>>>>> Destination=ActiveMQ.Advisory.******Producer.Queue.outgoing,**
>>>>>>>
>>>>>>> Type=**Topic
>>>>>>>
>>>>>>> 0 0 0 0 5 no emails
>>>>>>> Destination=ActiveMQ.Advisory.******Consumer.Queue.spool,Type=**
>>>>>>> ****Topic
>>>>>>>
>>>>>>> 0
>>>>>>>
>>>>>>> 0 0 0 253212 no emails
>>>>>>> Destination=ActiveMQ.Advisory.******Consumer.Queue.outgoing,**
>>>>>>>
>>>>>>> Type=**Topic
>>>>>>>
>>>>>>> 0 0 0 0 1232626 no emails
>>>>>>> Destination=ActiveMQ.Advisory.******Connection,Type=Topic 0
>>>>>>> 0
>>>>>>>
>>>>>>>
>>>>>>> 0 0 1 no
>>>>>>> emails
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Now I can see the mail stuck in outgoing queue, the one which we send
>>>>>>> every 30 sec..
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>> All, except the first and the last ones.
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>> Which mbean of activemq would you like me to check from the
>>>>>>> following ...
>>>>>>> org.apache.activemq:__******BrokerName=james,__**
>>>>>>> ConnectorName=tcp_//localhost_******__0,Type=Connector
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.Connection,******__Type=Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.Consumer.__******Queue.outgoing,Type=Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.Consumer.__******Queue.spool,Type=Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.Producer.__******Queue.outgoing,Type=Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.Producer.__******Queue.spool,Type=Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.Queue,Type=******__Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.Advisory.TempQueue,_******_Type=Topic
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _outgoing,Type=Queue
>>>>>>> org.apache.activemq:__******BrokerName=james,Destination=_
>>>>>>> ******
>>>>>>> _spool,Type=Queue
>>>>>>> org.apache.activemq:__******BrokerName=james,Type=Broker
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>>> eric@apache.org
>>>>>>> <ma...@apache.org>> wrote:
>>>>>>>
>>>>>>> Any chance to compare those numbers with the ones
>>>>>>> given by
>>>>>>> the activemq
>>>>>>> mbeans?
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>>>
>>>>>>> "You mean to 'push out' the queue.
>>>>>>> The mail you send triggers the pending mails to go
>>>>>>> out?"
>>>>>>>
>>>>>>> Yes this new mail push the earlier mail out but
>>>>>>> itself
>>>>>>> gets stuck in
>>>>>>> spool,to which a new mail after 30 sec pushes out
>>>>>>> and
>>>>>>> that mail gets
>>>>>>> struck
>>>>>>> and soon...
>>>>>>>
>>>>>>> Can you guide me how to figure out the reason as to
>>>>>>> why
>>>>>>> the size attribute
>>>>>>> value is 5 and the browse List only contains 3
>>>>>>> mails
>>>>>>> details.
>>>>>>> Also Why The mail which gets stuck in spool its
>>>>>>> count
>>>>>>> is
>>>>>>> incremented in
>>>>>>> attribure Size but its details are not present in
>>>>>>> browse
>>>>>>> List..?
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>>>>>
>>>>>>> Hi Farooq,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>>
>>>>>>> Here is the output which i get when i use
>>>>>>> Bean
>>>>>>> org.apache.james:name=queue,********
>>>>>>> __**queue=outgoing,type=__******component
>>>>>>>
>>>>>>> $>bean
>>>>>>> org.apache.james:name=queue,********
>>>>>>> __**queue=outgoing,type=__******component
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> #bean is set to
>>>>>>> org.apache.james:name=queue,**
>>>>>>> queue=outgoing,type=component
>>>>>>> $>info
>>>>>>> #mbean =
>>>>>>> org.apache.james:name=queue,********
>>>>>>> __**queue=outgoing,type=__******component
>>>>>>> #class name =
>>>>>>> org.apache.james.queue.****__******
>>>>>>>
>>>>>>>
>>>>>>> library.MailQueueManagement
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> # attributes
>>>>>>> %0 - Size (long, r)
>>>>>>> # operations
>>>>>>> %0 - java.util.List browse()
>>>>>>> %1 - long clear()
>>>>>>> %2 - long flush()
>>>>>>> %3 - long
>>>>>>> removeWithName(java.lang.****_******_String
>>>>>>> p1)
>>>>>>> %4 - long
>>>>>>> removeWithRecipient(java.lang.**
>>>>>>> ****__****String
>>>>>>> p1)
>>>>>>> %5 - long
>>>>>>> removeWithSender(java.lang.*****
>>>>>>> ****__*String
>>>>>>>
>>>>>>> p1)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> #there's no notifications
>>>>>>> $>get Size
>>>>>>> #mbean =
>>>>>>> org.apache.james:name=queue,********
>>>>>>> __**queue=outgoing,type=__******component:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Size = 7;
>>>>>>>
>>>>>>>
>>>>>>> Cool, it seems like you have found a JXM CLI
>>>>>>> which
>>>>>>> works fine.
>>>>>>> Which one is it?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Let me know if you need any further details.
>>>>>>>
>>>>>>> can you educate me as to Size= 7 is the no
>>>>>>> of
>>>>>>> mails still in outgoing
>>>>>>> spool
>>>>>>> or is some default size of outgoing queue.
>>>>>>>
>>>>>>>
>>>>>>> It is the number of pending mails in the
>>>>>>> queue.
>>>>>>>
>>>>>>> So you have 7 mails waiting to be sent to the
>>>>>>> outside world/
>>>>>>>
>>>>>>>
>>>>>>> Also note that do deal with this spooling
>>>>>>> problem, the workaround that
>>>>>>> we
>>>>>>>
>>>>>>> did temporarily is that we created an
>>>>>>> application that sends an email to
>>>>>>> some email address every 30 sec.
>>>>>>>
>>>>>>>
>>>>>>> You mean to 'push out' the queue.
>>>>>>> The mail you send triggers the pending mails
>>>>>>> to go
>>>>>>> out?
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric
>>>>>>> Charles
>>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>> Maybe the cloud's firewall blocks your
>>>>>>> requests.
>>>>>>>
>>>>>>> For JMX command line, type 'jmx cli' in
>>>>>>> google and experiment (tried
>>>>>>> one
>>>>>>> of these long time ago).
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 18/02/2013 10:11, Farooq Ahmed
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>>
>>>>>>> I tried remotely connecting to JMX
>>>>>>> using
>>>>>>> Jconsole and remote jmx
>>>>>>> connection
>>>>>>> method specified on
>>>>>>> http://james.apache.org/****
>>>>>>> server/3/config-system.html<__****
>>>>>>> **ht**tp://
>>>>>>> james.apache.org/****
>>>>>>> <http://james.apache.org/****>
>>>>>>> server/3/config-system.html<******
>>>>>>> ht__tp://
>>>>>>> james.apache.org/**__**server/****3/config-system.html<http://james.apache.org/**__**server/**3/config-system.html>
>>>>>>> <http://**james.apache.org/**__**server/**3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>>> >
>>>>>>> <http://**james.apache.org/**_**_server/3/**config-system.html<http://james.apache.org/**__server/3/**config-system.html>
>>>>>>> **<http://james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>> <http://james.apache.org/****
>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>> <ht**tp://james.apache.org/**_**
>>>>>>> **** <http://james.apache.org/**_****><http://james.apache.org/***
>>>>>>> *_** <http://james.apache.org/**_**>>
>>>>>>> _server/**3/config-system.****html<http://james.apache.org/*****<http://james.apache.org/***>
>>>>>>> *__server/**3/config-system.****html<http://james.apache.org/***
>>>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>> <http://james.apache.org/****
>>>>>>> server/**3/config-system.html<****http://james.apache.org/****
>>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> **<__http://james.apache.org/_****_**server/**3/config-system.**
>>>>>>>> **html<http://james.apache.org/_**_**server/**3/config-system.**html>
>>>>>>>> <http://james.apache.**org/__**server/**3/config-**system.html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>>> >
>>>>>>>> <http://james.apache.org/_**_**server/**3/config-system.html<http://james.apache.org/_**_server/**3/config-system.html>
>>>>>>>> <**http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>>> >
>>>>>>>> **>
>>>>>>>>
>>>>>>>> <http://james.apache.org/**
>>>>>>> server/**3/config-system.html<****http://james.apache.org/**
>>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> **>
>>>>>>>>
>>>>>>>> <**http://james.apache.org/**_**
>>>>>>> **** <http://james.apache.org/**_****><http://james.apache.org/***
>>>>>>> *_** <http://james.apache.org/**_**>>
>>>>>>> _server/3/config-system.html<**h**ttp://james.apache.org/**__****<http://james.apache.org/**__**>
>>>>>>>
>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/**__**
>>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> <http://james.apache.org/****
>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> <**ht__tp://james.apache.org/******server/__3/config-system.**html<http://james.apache.org/****server/__3/config-system.html>
>>>>>>>> <http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>> **>
>>>>>>>> **<http://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>>> <**http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>> >
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>> <http://james.apache.org/**
>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/**server/**<http://james.apache.org/server/**>
>>>>>>>
>>>>>>> 3/config-system.html<http://**james.apache.org/server/3/**
>>>>>>> config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> But i could not get connected to
>>>>>>> jmx
>>>>>>> on
>>>>>>> my email server.
>>>>>>>
>>>>>>> Note that the server where i have
>>>>>>> deployed james is on azure cloud
>>>>>>> PAS
>>>>>>> network and is Ubunto system.
>>>>>>> Is there any mechanism where i can
>>>>>>> observe the message queue contents
>>>>>>> on
>>>>>>> local ubunto system using ssh only.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Tue, Feb 12, 2013 at 11:02 PM,
>>>>>>> Ajay
>>>>>>> Navgale <
>>>>>>> ajay.navgale@centralogic.net
>>>>>>> <mailto:ajay.navgale@****central**
>>>>>>> ogic.net <http://centralogic.net><ajay.**navgale@**centralogic.net<
>>>>>>> ajay**.navgale@centralogic.net <aj...@centralogic.net>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------- Forwarded message
>>>>>>> ----------
>>>>>>>
>>>>>>> From: Eric Charles <
>>>>>>> eric@apache.org
>>>>>>> <ma...@apache.org>>
>>>>>>>
>>>>>>> Date: Tue, Feb 12, 2013 at
>>>>>>> 7:52 PM
>>>>>>> Subject: Re: James Server SMTP
>>>>>>> Spooling Issue
>>>>>>> To: James Users List
>>>>>>> <server-user@james.apache.org
>>>>>>> <mailto:server-user@james.**
>>>>>>> apache.org <se...@james.apache.org>****>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>> You mean you the newly spooled
>>>>>>> mails
>>>>>>> 'push-out' the remaining ones.
>>>>>>> After that, the latest one
>>>>>>> remains
>>>>>>> stucked in the queu?
>>>>>>>
>>>>>>> If such, that's very strange
>>>>>>> and
>>>>>>> we
>>>>>>> never saw that before.
>>>>>>> Do you use JMX to inspect the
>>>>>>> queue
>>>>>>> content/size?
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 12/02/2013 11:45, Ajay
>>>>>>> Navgale
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>> We are using james 3.0
>>>>>>> beta4.
>>>>>>> We have an issue while
>>>>>>> sending
>>>>>>> an email. There is always
>>>>>>> one
>>>>>>> outgoing
>>>>>>> mail
>>>>>>> left in spool and is
>>>>>>> delivered
>>>>>>> when any new outgoing mail
>>>>>>> is
>>>>>>> to
>>>>>>> be
>>>>>>> sent.
>>>>>>> Now previous mail gets
>>>>>>> delivered
>>>>>>> and this recent once sits
>>>>>>> in
>>>>>>> the
>>>>>>> spool.
>>>>>>> This is happening for
>>>>>>> Remote
>>>>>>> delivery.
>>>>>>>
>>>>>>> Can anyone throw some
>>>>>>> light on
>>>>>>> this.
>>>>>>>
>>>>>>> Thanks & Regards,
>>>>>>> Ajay
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------
>>>>>>> ****
>>>>>>> __********--------------------******--__--**
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --**
>>>>>>> --**
>>>>>>>
>>>>>>> --**---------
>>>>>>>
>>>>>>> To unsubscribe, e-mail:
>>>>>>> server-user-unsubscribe@james.
>>>>>>> ****
>>>>>>> **
>>>>>>> __********
>>>>>>> apache.org <http://apache.org>
>>>>>>> <
>>>>>>> server-user-**unsubscribe@**__
>>>>>>> ****
>>>>>>> **ja**
>>>>>>> mes.apache.org
>>>>>>> <http://mes.apache.org><http:/
>>>>>>> ****
>>>>>>> **/__
>>>>>>> james.apache.org
>>>>>>> <http://james.apache.org>>
>>>>>>> <unsubscribe@**james.apache.__
>>>>>>> ****
>>>>>>>
>>>>>>> **org
>>>>>>> <http://james.apache.org>
>>>>>>> <unsubscribe@james.apache.org
>>>>>>> <mailto:unsubscribe@james.**
>>>>>>> apache.org <un...@james.apache.org>****>>__>
>>>>>>>
>>>>>>>
>>>>>>> <server-user-**unsubscribe@***
>>>>>>> ***
>>>>>>>
>>>>>>> j**
>>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>>> <http://james.apache.org><**
>>>>>>> unsubscribe@__james.apache.org
>>>>>>> <mailto:unsubscribe@james.**
>>>>>>> apache.org <un...@james.apache.org>****>>
>>>>>>> <server-user-**unsubscribe@__*
>>>>>>> ***
>>>>>>>
>>>>>>> j**
>>>>>>> ames.apache.org <http://james.apache.org>
>>>>>>> <mailto:unsubscribe@james.**
>>>>>>> apache.org <un...@james.apache.org>****><server-user-__**
>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>> >>
>>>>>>> <mailto:server-user-**
>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>
>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>> >>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> For additional
>>>>>>> commands,
>>>>>>> e-mail:
>>>>>>>
>>>>>>> server-user-help@james.apache.
>>>>>>> ****
>>>>>>> __**
>>>>>>> **
>>>>>>>
>>>>>>> ****org<
>>>>>>> server-user-help@james.****__*
>>>>>>> *****
>>>>>>>
>>>>>>> apach**e.org
>>>>>>> <http://e.org> <
>>>>>>> http://apache.org>
>>>>>>> <
>>>>>>>
>>>>>>> server-user-help@james.**__***
>>>>>>> ***
>>>>>>>
>>>>>>> apach**
>>>>>>> e.org
>>>>>>> <http://e.org> <
>>>>>>> http://apache.org
>>>>>>>
>>>>>>>> <
>>>>>>>>
>>>>>>> server-user-help@james.****
>>>>>>>
>>>>>>> apach**
>>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>>> user-help@james.__apache.org
>>>>>>> <mailto:server-user-help@**
>>>>>>> james.apache.org <server-user-help@james.**apac**he.org<http://apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------
>>>>>>> ****
>>>>>>> **
>>>>>>> __******----------------------******--__--**
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --**
>>>>>>>
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail:
>>>>>>> server-user-unsubscribe@james.****
>>>>>>> **__******
>>>>>>> apache.org
>>>>>>> <http://apache.org>
>>>>>>> <
>>>>>>> server-user-**unsubscribe@******ja**
>>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>>> <http://james.apache.org><****
>>>>>>> unsubscribe@__
>>>>>>> james.apache.org
>>>>>>> <mailto:unsubscribe@james.****ap**
>>>>>>> ache.org<http://apache.org**>
>>>>>>> <unsubscribe@james.**apache.**org <http://apache.org> <
>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>
>>>>>>>
>>>>>>>> <server-user-**unsubscribe@__***
>>>>>>>>> *j**
>>>>>>>>>
>>>>>>>> ames.apache.org <http://james.apache.org> <mailto:
>>>>>>> unsubscribe@james.**
>>>>>>> apache.org <un...@james.apache.org>****><server-user-__**
>>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>> >>
>>>>>>> <mailto:server-user-**
>>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>>>
>>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>> >>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> For additional commands, e-mail:
>>>>>>> server-user-help@james.apache.****
>>>>>>> **__**
>>>>>>>
>>>>>>> ****org<
>>>>>>> server-user-help@james.**__*****
>>>>>>> *apach**
>>>>>>>
>>>>>>> e.org
>>>>>>> <http://e.org> <http://apache.org> <
>>>>>>> server-user-help@james.******apach**__
>>>>>>> e.org
>>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>>> <http://apache.org><server-******
>>>>>>> user-help@james.
>>>>>>> __apache.org
>>>>>>> <mailto:server-user-help@****jam**
>>>>>>> es.apache.org <http://james.apache.org><**server-user-**
>>>>>>> help@james.apache.org <se...@james.apache.org>
>>>>>>> >>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******
>>>>>>> __****------------------------******--__--**
>>>>>>>
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail:
>>>>>>> server-user-unsubscribe@james.******__****
>>>>>>> apache.org
>>>>>>> <http://apache.org><
>>>>>>> server-user-**unsubscribe@__****ja**
>>>>>>> mes.apache.org<
>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>> <mailto:unsubscribe@james.****ap**ache.org<
>>>>>>> http://apache.org**>
>>>>>>> <unsubscribe@james.**apache.**org <http://apache.org> <
>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>
>>>>>>> <server-user-__**unsubscribe@****james.apache.org<unsubscribe@**
>>>>>>>> james.apache.org <un...@james.apache.org>>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> >
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> <mailto:server-user-****unsubscr**
>>>>>>> ibe@james.apache.org <un...@james.apache.org>**<server-**
>>>>>>> user-unsubscribe@james.apache.****org<server-user-unsubscribe@**
>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>> For additional commands, e-mail:
>>>>>>> server-user-help@james.apache.******__****org<
>>>>>>> server-user-help@james.******apach**__e.org<
>>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>>> <http://apache.org>
>>>>>>> <server-user-help@james.__****apac**he.org<
>>>>>>> http://apache.org**>
>>>>>>> <mailto:server-user-help@****jam**
>>>>>>> es.apache.org<http://**james.apache.org <http://james.apache.org>>
>>>>>>> <server-user-**help@james.**apache.org <he...@james.apache.org><
>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******
>>>>>>> __**--------------------------******--__--**---------
>>>>>>> To unsubscribe, e-mail:
>>>>>>> server-user-unsubscribe@james.******__**apache.org
>>>>>>> <http://apache.org><server-*****
>>>>>>> *user-__unsubscribe@james.
>>>>>>> **
>>>>>>> apache.org <server-user-__unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>> <mailto:server-user-****unsubscr**
>>>>>>> ibe@james.apache.org**<un...@james.apache.org>
>>>>>>> <server-**user-unsubscribe@**james.apache.**org<server-**
>>>>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>> For additional commands, e-mail:
>>>>>>>>>
>>>>>>>> server-user-help@james.apache.****
>>>>>>> **__**org<server-user-help@**
>>>>>>> james.__apache.org
>>>>>>> <mailto:server-user-help@****jam**es.apache.org<
>>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>>> <server-user-**help@james.**apache.org <he...@james.apache.org><
>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******__------------------------
>>>>>>> **--**
>>>>>>> --**
>>>>>>> --__---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******__
>>>>>>> apache.org
>>>>>>> <mailto:server-user-****unsubscr**ibe@james.apache.org**<
>>>>>>> unsubscribe@james.apache.org>
>>>>>>> <server-**user-unsubscribe@**james.apache.**org<server-**
>>>>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>> For additional commands, e-mail:
>>>>>>>> server-user-help@james.apache.
>>>>>>>>
>>>>>>> ****
>>>>>>> __org
>>>>>>> <mailto:server-user-help@****jam**es.apache.org<http://**
>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>> <server-user-**help@james.**apache.org <he...@james.apache.org><
>>>>>>> server-user-help@**james.apache.org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******--------------------------**--**
>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******
>>>>>>> apache.org<
>>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>> **
>>>>>>> **org<server-user-help@james.****apache.org<server-user-help@**
>>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******--------------------------**
>>>>>>> --**
>>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******
>>>>>> apache.org<
>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>> >
>>>>>>
>>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>> ****org<
>>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>> >
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>> >
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>> >
>>>>
>>>>
>>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi Farooq,
Unfortunately, I can not reproduce it.
Any chance for you to write a Java unit test that shows this?
Thx, Eric
On 25/02/2013 05:25, Farooq Ahmed wrote:
> Hi Eric,
>
> Any further info on this, this issue is still unresolved..
>
> Regards,
> Farooq
>
> On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
> <fa...@centralogic.net>wrote:
>
>> We do use to restart the system after that the spooled mails are delivered
>> and after restart first mail is sent out with out getting stuck in outgoing
>> queue but from second mail onwards one mail always keeps stuck in outgoing
>> queue.
>>
>> Regards,
>> Farooq
>>
>>
>> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
>>
>>> Did you already tried a stop/start of James to see if those numbers
>>> change?
>>>
>>> Thx, Eric
>>>
>>>
>>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>>
>>>> Hi Eric,
>>>>
>>>> The QueueSize is 2 in mbean Destination=outgoing,Type=**Queue(ActiveMQ)
>>>> and
>>>> Size is also 2 in name=queue,queue=outgoing,**type=component (james)
>>>>
>>>> The only logical relation that i can see between ActiveMQ and James is
>>>> the
>>>> outgoing queue size in both is 2. Where as there are no messages in List
>>>> returned by james bean and ActiveMQ bean shows one message in queue.
>>>>
>>>> we have'nt done any changes in ActiveMQ, but we have changed
>>>> configuration
>>>> files of james for spams, fakeipaddress, baeysian algorithm and we dont
>>>> store copy of sent mails.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
>>>>
>>>> Hi Farooq,
>>>>>
>>>>> Looking at Destination=outgoing,Type=****Queue, the
>>>>> EnqueueCount/DequeueCount/****QueueSize seem odd (14976 - 14975 <> 2).
>>>>>
>>>>>
>>>>> Can you link/find some logic between those ActiveMQ numbers and the
>>>>> numbers shown in the James MBeans?
>>>>>
>>>>> Do you run with the embedded ActiveMQ shipped by default? Any changes in
>>>>> the configuration?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>>
>>>>>> Here you go..
>>>>>> Attributes Value
>>>>>> BeanName ConsumerCount
>>>>>> ProducerCount QueueSize DequeueCount EnqueueCount
>>>>>> browse
>>>>>> Destination=ActiveMQ.DLQ,Type=****Queue 0 0 1 0
>>>>>>
>>>>>> 0 Shows 1 message in
>>>>>> outgoing queue,
>>>>>> invalid recepient
>>>>>> Destination=outgoing,Type=****Queue 10 5 2
>>>>>> 14976
>>>>>>
>>>>>> 14975 shows 1 message
>>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>>> Destination=spool,Type=Queue 2 3 0 15146 15146
>>>>>> no emails
>>>>>> Destination=ActiveMQ.Advisory.****TempQueue,Type=Topic 1 0
>>>>>>
>>>>>> 0 0 146 no
>>>>>> emails
>>>>>> Destination=ActiveMQ.Advisory.****Queue,Type=Topic 0 0 0
>>>>>> 0 6 no emails
>>>>>> Destination=ActiveMQ.Advisory.****Producer.Queue.spool,Type=****Topic
>>>>>> 0
>>>>>>
>>>>>> 0 0 0 3 no emails
>>>>>> Destination=ActiveMQ.Advisory.****Producer.Queue.outgoing,**
>>>>>> Type=**Topic
>>>>>>
>>>>>> 0 0 0 0 5 no emails
>>>>>> Destination=ActiveMQ.Advisory.****Consumer.Queue.spool,Type=****Topic
>>>>>> 0
>>>>>>
>>>>>> 0 0 0 253212 no emails
>>>>>> Destination=ActiveMQ.Advisory.****Consumer.Queue.outgoing,**
>>>>>> Type=**Topic
>>>>>>
>>>>>> 0 0 0 0 1232626 no emails
>>>>>> Destination=ActiveMQ.Advisory.****Connection,Type=Topic 0 0
>>>>>>
>>>>>> 0 0 1 no
>>>>>> emails
>>>>>>
>>>>>>
>>>>>>
>>>>>> Now I can see the mail stuck in outgoing queue, the one which we send
>>>>>> every 30 sec..
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>>> <ma...@apache.org>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>> All, except the first and the last ones.
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>> Which mbean of activemq would you like me to check from the
>>>>>> following ...
>>>>>> org.apache.activemq:__****BrokerName=james,__**
>>>>>> ConnectorName=tcp_//localhost_****__0,Type=Connector
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.Connection,****__Type=Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.Consumer.__****Queue.outgoing,Type=Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.Consumer.__****Queue.spool,Type=Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.Producer.__****Queue.outgoing,Type=Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.Producer.__****Queue.spool,Type=Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.Queue,Type=****__Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.Advisory.TempQueue,_****_Type=Topic
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _outgoing,Type=Queue
>>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>>> _spool,Type=Queue
>>>>>> org.apache.activemq:__****BrokerName=james,Type=Broker
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>>> eric@apache.org
>>>>>> <ma...@apache.org>> wrote:
>>>>>>
>>>>>> Any chance to compare those numbers with the ones given by
>>>>>> the activemq
>>>>>> mbeans?
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>>
>>>>>> "You mean to 'push out' the queue.
>>>>>> The mail you send triggers the pending mails to go
>>>>>> out?"
>>>>>>
>>>>>> Yes this new mail push the earlier mail out but itself
>>>>>> gets stuck in
>>>>>> spool,to which a new mail after 30 sec pushes out and
>>>>>> that mail gets
>>>>>> struck
>>>>>> and soon...
>>>>>>
>>>>>> Can you guide me how to figure out the reason as to
>>>>>> why
>>>>>> the size attribute
>>>>>> value is 5 and the browse List only contains 3 mails
>>>>>> details.
>>>>>> Also Why The mail which gets stuck in spool its count
>>>>>> is
>>>>>> incremented in
>>>>>> attribure Size but its details are not present in
>>>>>> browse
>>>>>> List..?
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>>>>
>>>>>> Hi Farooq,
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>
>>>>>> Here is the output which i get when i use Bean
>>>>>> org.apache.james:name=queue,******
>>>>>> __**queue=outgoing,type=__****component
>>>>>>
>>>>>> $>bean
>>>>>> org.apache.james:name=queue,******
>>>>>> __**queue=outgoing,type=__****component
>>>>>>
>>>>>>
>>>>>>
>>>>>> #bean is set to org.apache.james:name=queue,**
>>>>>> queue=outgoing,type=component
>>>>>> $>info
>>>>>> #mbean =
>>>>>> org.apache.james:name=queue,******
>>>>>> __**queue=outgoing,type=__****component
>>>>>> #class name =
>>>>>> org.apache.james.queue.****__****
>>>>>>
>>>>>> library.MailQueueManagement
>>>>>>
>>>>>>
>>>>>>
>>>>>> # attributes
>>>>>> %0 - Size (long, r)
>>>>>> # operations
>>>>>> %0 - java.util.List browse()
>>>>>> %1 - long clear()
>>>>>> %2 - long flush()
>>>>>> %3 - long
>>>>>> removeWithName(java.lang.****_****_String p1)
>>>>>> %4 - long
>>>>>> removeWithRecipient(java.lang.****__****String
>>>>>> p1)
>>>>>> %5 - long
>>>>>> removeWithSender(java.lang.*******__*String
>>>>>> p1)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> #there's no notifications
>>>>>> $>get Size
>>>>>> #mbean =
>>>>>> org.apache.james:name=queue,******
>>>>>> __**queue=outgoing,type=__****component:
>>>>>>
>>>>>>
>>>>>> Size = 7;
>>>>>>
>>>>>>
>>>>>> Cool, it seems like you have found a JXM CLI which
>>>>>> works fine.
>>>>>> Which one is it?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Let me know if you need any further details.
>>>>>>
>>>>>> can you educate me as to Size= 7 is the no of
>>>>>> mails still in outgoing
>>>>>> spool
>>>>>> or is some default size of outgoing queue.
>>>>>>
>>>>>>
>>>>>> It is the number of pending mails in the
>>>>>> queue.
>>>>>>
>>>>>> So you have 7 mails waiting to be sent to the
>>>>>> outside world/
>>>>>>
>>>>>>
>>>>>> Also note that do deal with this spooling
>>>>>> problem, the workaround that
>>>>>> we
>>>>>>
>>>>>> did temporarily is that we created an
>>>>>> application that sends an email to
>>>>>> some email address every 30 sec.
>>>>>>
>>>>>>
>>>>>> You mean to 'push out' the queue.
>>>>>> The mail you send triggers the pending mails to go
>>>>>> out?
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Farooq
>>>>>>
>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles
>>>>>> <eric@apache.org <ma...@apache.org>>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>> Maybe the cloud's firewall blocks your
>>>>>> requests.
>>>>>>
>>>>>> For JMX command line, type 'jmx cli' in
>>>>>> google and experiment (tried
>>>>>> one
>>>>>> of these long time ago).
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>
>>>>>> I tried remotely connecting to JMX
>>>>>> using
>>>>>> Jconsole and remote jmx
>>>>>> connection
>>>>>> method specified on
>>>>>> http://james.apache.org/****
>>>>>> server/3/config-system.html<__**
>>>>>> **ht**tp://
>>>>>> james.apache.org/****
>>>>>> <http://james.apache.org/****>
>>>>>> server/3/config-system.html<****
>>>>>> ht__tp://
>>>>>> james.apache.org/**__**server/**3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>>> <http://**james.apache.org/**__server/3/**config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>
>>>>>> <http://james.apache.org/****
>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> <ht**tp://james.apache.org/**_****<http://james.apache.org/**_**>
>>>>>> _server/**3/config-system.**html<http://james.apache.org/***
>>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>>>>
>>>>>> <http://james.apache.org/****
>>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>
>>>>>>
>>>>>>> **<__http://james.apache.org/_**_**server/**3/config-system.**html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>>> <http://james.apache.org/_**_server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>>> **>
>>>>>>>
>>>>>> <http://james.apache.org/**
>>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>
>>>>>>
>>>>>>> **>
>>>>>>>
>>>>>> <**http://james.apache.org/**_****<http://james.apache.org/**_**>
>>>>>> _server/3/config-system.html<h**ttp://james.apache.org/**__**
>>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>>>>
>>>>>>
>>>>>> <http://james.apache.org/****
>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>
>>>>>>
>>>>>>> <**ht__tp://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>>> **<http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> <http://james.apache.org/**
>>>>>> server/3/config-system.html<ht**tp://james.apache.org/server/**
>>>>>> 3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> But i could not get connected to jmx
>>>>>> on
>>>>>> my email server.
>>>>>>
>>>>>> Note that the server where i have
>>>>>> deployed james is on azure cloud PAS
>>>>>> network and is Ubunto system.
>>>>>> Is there any mechanism where i can
>>>>>> observe the message queue contents
>>>>>> on
>>>>>> local ubunto system using ssh only.
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay
>>>>>> Navgale <
>>>>>> ajay.navgale@centralogic.net
>>>>>> <mailto:ajay.navgale@**central**
>>>>>> ogic.net <ht...@centralogic.net>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------- Forwarded message
>>>>>> ----------
>>>>>>
>>>>>> From: Eric Charles <
>>>>>> eric@apache.org
>>>>>> <ma...@apache.org>>
>>>>>>
>>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>>> Subject: Re: James Server SMTP
>>>>>> Spooling Issue
>>>>>> To: James Users List
>>>>>> <server-user@james.apache.org
>>>>>> <mailto:server-user@james.**
>>>>>> apache.org <se...@james.apache.org>**>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>> You mean you the newly spooled
>>>>>> mails
>>>>>> 'push-out' the remaining ones.
>>>>>> After that, the latest one remains
>>>>>> stucked in the queu?
>>>>>>
>>>>>> If such, that's very strange and
>>>>>> we
>>>>>> never saw that before.
>>>>>> Do you use JMX to inspect the
>>>>>> queue
>>>>>> content/size?
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 12/02/2013 11:45, Ajay Navgale
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>> We are using james 3.0 beta4.
>>>>>> We have an issue while sending
>>>>>> an email. There is always one
>>>>>> outgoing
>>>>>> mail
>>>>>> left in spool and is delivered
>>>>>> when any new outgoing mail is
>>>>>> to
>>>>>> be
>>>>>> sent.
>>>>>> Now previous mail gets
>>>>>> delivered
>>>>>> and this recent once sits in
>>>>>> the
>>>>>> spool.
>>>>>> This is happening for Remote
>>>>>> delivery.
>>>>>>
>>>>>> Can anyone throw some light on
>>>>>> this.
>>>>>>
>>>>>> Thanks & Regards,
>>>>>> Ajay
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------
>>>>>> ****
>>>>>> __********--------------------****--__--**
>>>>>>
>>>>>>
>>>>>> --**
>>>>>> --**
>>>>>>
>>>>>> --**---------
>>>>>>
>>>>>> To unsubscribe, e-mail:
>>>>>> server-user-unsubscribe@james.**
>>>>>> **
>>>>>> __********
>>>>>> apache.org <http://apache.org>
>>>>>> <
>>>>>> server-user-**unsubscribe@**__**
>>>>>> **ja**
>>>>>> mes.apache.org
>>>>>> <http://mes.apache.org><http:/**
>>>>>> **/__
>>>>>> james.apache.org
>>>>>> <http://james.apache.org>>
>>>>>> <unsubscribe@**james.apache.__**
>>>>>> **org
>>>>>> <http://james.apache.org>
>>>>>> <unsubscribe@james.apache.org
>>>>>> <mailto:unsubscribe@james.**
>>>>>> apache.org <un...@james.apache.org>**>>__>
>>>>>>
>>>>>>
>>>>>> <server-user-**unsubscribe@****
>>>>>> j**
>>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>>> <http://james.apache.org><**
>>>>>> unsubscribe@__james.apache.org
>>>>>> <mailto:unsubscribe@james.**
>>>>>> apache.org <un...@james.apache.org>**>>
>>>>>> <server-user-**unsubscribe@__**
>>>>>> j**
>>>>>> ames.apache.org <http://james.apache.org>
>>>>>> <mailto:unsubscribe@james.**
>>>>>> apache.org <un...@james.apache.org>**><server-user-__**
>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>> <mailto:server-user-**
>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>> james.apache.org <se...@james.apache.org>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> For additional commands,
>>>>>> e-mail:
>>>>>> server-user-help@james.apache.
>>>>>> ****
>>>>>> __**
>>>>>> **
>>>>>>
>>>>>> ****org<
>>>>>> server-user-help@james.****__****
>>>>>> apach**e.org
>>>>>> <http://e.org> <http://apache.org>
>>>>>> <
>>>>>>
>>>>>> server-user-help@james.**__****
>>>>>> apach**
>>>>>> e.org
>>>>>> <http://e.org> <http://apache.org
>>>>>>> <
>>>>>> server-user-help@james.****
>>>>>> apach**
>>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>>> user-help@james.__apache.org
>>>>>> <mailto:server-user-help@**
>>>>>> james.apache.org <se...@james.apache.org>
>>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------**
>>>>>> **
>>>>>> __******----------------------****--__--**
>>>>>>
>>>>>>
>>>>>>
>>>>>> --**
>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail:
>>>>>> server-user-unsubscribe@james.**
>>>>>> **__******
>>>>>> apache.org
>>>>>> <http://apache.org>
>>>>>> <
>>>>>> server-user-**unsubscribe@****ja**
>>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>>> <http://james.apache.org><****
>>>>>> unsubscribe@__
>>>>>> james.apache.org
>>>>>> <mailto:unsubscribe@james.**ap**ache.org<http://apache.org>
>>>>>> <unsubscribe@james.**apache.org <un...@james.apache.org>>
>>>>>>
>>>>>>>
>>>>>>>> <server-user-**unsubscribe@__**j**
>>>>>> ames.apache.org <http://james.apache.org> <mailto:unsubscribe@james.**
>>>>>> apache.org <un...@james.apache.org>**><server-user-__**
>>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>>> james.apache.org <se...@james.apache.org>>
>>>>>> <mailto:server-user-**
>>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>>> james.apache.org <se...@james.apache.org>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> For additional commands, e-mail:
>>>>>> server-user-help@james.apache.**
>>>>>> **__**
>>>>>>
>>>>>> ****org<
>>>>>> server-user-help@james.**__****apach**
>>>>>> e.org
>>>>>> <http://e.org> <http://apache.org> <
>>>>>> server-user-help@james.****apach**__e.org
>>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>>> <http://apache.org><server-****
>>>>>> user-help@james.
>>>>>> __apache.org
>>>>>> <mailto:server-user-help@**jam**
>>>>>> es.apache.org <http://james.apache.org><server-user-**
>>>>>> help@james.apache.org <se...@james.apache.org>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------****
>>>>>> __****------------------------****--__--**
>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail:
>>>>>> server-user-unsubscribe@james.****__****
>>>>>> apache.org
>>>>>> <http://apache.org><
>>>>>> server-user-**unsubscribe@__**ja**mes.apache.org<
>>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>>> <mailto:unsubscribe@james.**ap**ache.org<http://apache.org>
>>>>>> <unsubscribe@james.**apache.org <un...@james.apache.org>>
>>>>>>
>>>>>>> <se...@james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>>>
>>>>>>>
>>>>>> <mailto:server-user-**unsubscr**
>>>>>> ibe@james.apache.org <un...@james.apache.org><server-**
>>>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> For additional commands, e-mail:
>>>>>> server-user-help@james.apache.****__****org<
>>>>>> server-user-help@james.****apach**__e.org<
>>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>>> <http://apache.org>
>>>>>> <server-user-help@james.__**apac**he.org<
>>>>>> http://apache.org**>
>>>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------****
>>>>>> __**--------------------------****--__--**---------
>>>>>> To unsubscribe, e-mail:
>>>>>> server-user-unsubscribe@james.****__**apache.org
>>>>>> <http://apache.org><server-****user-__unsubscribe@james.
>>>>>> **
>>>>>> apache.org <se...@james.apache.org>
>>>>>>>
>>>>>> <ma...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>>> For additional commands, e-mail:
>>>>>> server-user-help@james.apache.**
>>>>>> **__**org<server-user-help@**
>>>>>> james.__apache.org
>>>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------****__--------------------------**
>>>>>> --**
>>>>>> --__---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****__
>>>>>> apache.org
>>>>>> <ma...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.
>>>>>> ****
>>>>>> __org
>>>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>>>
>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>> **org<se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>>
>>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
Any further info on this, this issue is still unresolved..
Regards,
Farooq
On Tue, Feb 19, 2013 at 6:38 PM, Farooq Ahmed
<fa...@centralogic.net>wrote:
> We do use to restart the system after that the spooled mails are delivered
> and after restart first mail is sent out with out getting stuck in outgoing
> queue but from second mail onwards one mail always keeps stuck in outgoing
> queue.
>
> Regards,
> Farooq
>
>
> On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
>
>> Did you already tried a stop/start of James to see if those numbers
>> change?
>>
>> Thx, Eric
>>
>>
>> On 19/02/2013 12:33, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> The QueueSize is 2 in mbean Destination=outgoing,Type=**Queue(ActiveMQ)
>>> and
>>> Size is also 2 in name=queue,queue=outgoing,**type=component (james)
>>>
>>> The only logical relation that i can see between ActiveMQ and James is
>>> the
>>> outgoing queue size in both is 2. Where as there are no messages in List
>>> returned by james bean and ActiveMQ bean shows one message in queue.
>>>
>>> we have'nt done any changes in ActiveMQ, but we have changed
>>> configuration
>>> files of james for spams, fakeipaddress, baeysian algorithm and we dont
>>> store copy of sent mails.
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
>>>
>>> Hi Farooq,
>>>>
>>>> Looking at Destination=outgoing,Type=****Queue, the
>>>> EnqueueCount/DequeueCount/****QueueSize seem odd (14976 - 14975 <> 2).
>>>>
>>>>
>>>> Can you link/find some logic between those ActiveMQ numbers and the
>>>> numbers shown in the James MBeans?
>>>>
>>>> Do you run with the embedded ActiveMQ shipped by default? Any changes in
>>>> the configuration?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>>
>>>>> Here you go..
>>>>> Attributes Value
>>>>> BeanName ConsumerCount
>>>>> ProducerCount QueueSize DequeueCount EnqueueCount
>>>>> browse
>>>>> Destination=ActiveMQ.DLQ,Type=****Queue 0 0 1 0
>>>>>
>>>>> 0 Shows 1 message in
>>>>> outgoing queue,
>>>>> invalid recepient
>>>>> Destination=outgoing,Type=****Queue 10 5 2
>>>>> 14976
>>>>>
>>>>> 14975 shows 1 message
>>>>> in outgoing queue,the one which we sends after every 30 sec
>>>>> Destination=spool,Type=Queue 2 3 0 15146 15146
>>>>> no emails
>>>>> Destination=ActiveMQ.Advisory.****TempQueue,Type=Topic 1 0
>>>>>
>>>>> 0 0 146 no
>>>>> emails
>>>>> Destination=ActiveMQ.Advisory.****Queue,Type=Topic 0 0 0
>>>>> 0 6 no emails
>>>>> Destination=ActiveMQ.Advisory.****Producer.Queue.spool,Type=****Topic
>>>>> 0
>>>>>
>>>>> 0 0 0 3 no emails
>>>>> Destination=ActiveMQ.Advisory.****Producer.Queue.outgoing,**
>>>>> Type=**Topic
>>>>>
>>>>> 0 0 0 0 5 no emails
>>>>> Destination=ActiveMQ.Advisory.****Consumer.Queue.spool,Type=****Topic
>>>>> 0
>>>>>
>>>>> 0 0 0 253212 no emails
>>>>> Destination=ActiveMQ.Advisory.****Consumer.Queue.outgoing,**
>>>>> Type=**Topic
>>>>>
>>>>> 0 0 0 0 1232626 no emails
>>>>> Destination=ActiveMQ.Advisory.****Connection,Type=Topic 0 0
>>>>>
>>>>> 0 0 1 no
>>>>> emails
>>>>>
>>>>>
>>>>>
>>>>> Now I can see the mail stuck in outgoing queue, the one which we send
>>>>> every 30 sec..
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>>
>>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>>> <ma...@apache.org>> wrote:
>>>>>
>>>>> Hi,
>>>>> All, except the first and the last ones.
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>> Which mbean of activemq would you like me to check from the
>>>>> following ...
>>>>> org.apache.activemq:__****BrokerName=james,__**
>>>>> ConnectorName=tcp_//localhost_****__0,Type=Connector
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.Connection,****__Type=Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.Consumer.__****Queue.outgoing,Type=Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.Consumer.__****Queue.spool,Type=Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.Producer.__****Queue.outgoing,Type=Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.Producer.__****Queue.spool,Type=Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.Queue,Type=****__Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.Advisory.TempQueue,_****_Type=Topic
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _ActiveMQ.DLQ,Type=Queue
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _outgoing,Type=Queue
>>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>>> _spool,Type=Queue
>>>>> org.apache.activemq:__****BrokerName=james,Type=Broker
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <
>>>>> eric@apache.org
>>>>> <ma...@apache.org>> wrote:
>>>>>
>>>>> Any chance to compare those numbers with the ones given by
>>>>> the activemq
>>>>> mbeans?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>>
>>>>> "You mean to 'push out' the queue.
>>>>> The mail you send triggers the pending mails to go
>>>>> out?"
>>>>>
>>>>> Yes this new mail push the earlier mail out but itself
>>>>> gets stuck in
>>>>> spool,to which a new mail after 30 sec pushes out and
>>>>> that mail gets
>>>>> struck
>>>>> and soon...
>>>>>
>>>>> Can you guide me how to figure out the reason as to
>>>>> why
>>>>> the size attribute
>>>>> value is 5 and the browse List only contains 3 mails
>>>>> details.
>>>>> Also Why The mail which gets stuck in spool its count
>>>>> is
>>>>> incremented in
>>>>> attribure Size but its details are not present in
>>>>> browse
>>>>> List..?
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>>>
>>>>> Hi Farooq,
>>>>>
>>>>>
>>>>>
>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>>
>>>>> Here is the output which i get when i use Bean
>>>>> org.apache.james:name=queue,******
>>>>> __**queue=outgoing,type=__****component
>>>>>
>>>>> $>bean
>>>>> org.apache.james:name=queue,******
>>>>> __**queue=outgoing,type=__****component
>>>>>
>>>>>
>>>>>
>>>>> #bean is set to org.apache.james:name=queue,**
>>>>> queue=outgoing,type=component
>>>>> $>info
>>>>> #mbean =
>>>>> org.apache.james:name=queue,******
>>>>> __**queue=outgoing,type=__****component
>>>>> #class name =
>>>>> org.apache.james.queue.****__****
>>>>>
>>>>> library.MailQueueManagement
>>>>>
>>>>>
>>>>>
>>>>> # attributes
>>>>> %0 - Size (long, r)
>>>>> # operations
>>>>> %0 - java.util.List browse()
>>>>> %1 - long clear()
>>>>> %2 - long flush()
>>>>> %3 - long
>>>>> removeWithName(java.lang.****_****_String p1)
>>>>> %4 - long
>>>>> removeWithRecipient(java.lang.****__****String
>>>>> p1)
>>>>> %5 - long
>>>>> removeWithSender(java.lang.*******__*String
>>>>> p1)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> #there's no notifications
>>>>> $>get Size
>>>>> #mbean =
>>>>> org.apache.james:name=queue,******
>>>>> __**queue=outgoing,type=__****component:
>>>>>
>>>>>
>>>>> Size = 7;
>>>>>
>>>>>
>>>>> Cool, it seems like you have found a JXM CLI which
>>>>> works fine.
>>>>> Which one is it?
>>>>>
>>>>>
>>>>>
>>>>> Let me know if you need any further details.
>>>>>
>>>>> can you educate me as to Size= 7 is the no of
>>>>> mails still in outgoing
>>>>> spool
>>>>> or is some default size of outgoing queue.
>>>>>
>>>>>
>>>>> It is the number of pending mails in the
>>>>> queue.
>>>>>
>>>>> So you have 7 mails waiting to be sent to the
>>>>> outside world/
>>>>>
>>>>>
>>>>> Also note that do deal with this spooling
>>>>> problem, the workaround that
>>>>> we
>>>>>
>>>>> did temporarily is that we created an
>>>>> application that sends an email to
>>>>> some email address every 30 sec.
>>>>>
>>>>>
>>>>> You mean to 'push out' the queue.
>>>>> The mail you send triggers the pending mails to go
>>>>> out?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Farooq
>>>>>
>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles
>>>>> <eric@apache.org <ma...@apache.org>>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> Maybe the cloud's firewall blocks your
>>>>> requests.
>>>>>
>>>>> For JMX command line, type 'jmx cli' in
>>>>> google and experiment (tried
>>>>> one
>>>>> of these long time ago).
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>>
>>>>> I tried remotely connecting to JMX
>>>>> using
>>>>> Jconsole and remote jmx
>>>>> connection
>>>>> method specified on
>>>>> http://james.apache.org/****
>>>>> server/3/config-system.html<__**
>>>>> **ht**tp://
>>>>> james.apache.org/****
>>>>> <http://james.apache.org/****>
>>>>> server/3/config-system.html<****
>>>>> ht__tp://
>>>>> james.apache.org/**__**server/**3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>>> <http://**james.apache.org/**__server/3/**config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>> >
>>>>> <http://james.apache.org/****
>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>> >
>>>>>
>>>>>>
>>>>>>>
>>>>>
>>>>> <ht**tp://james.apache.org/**_****<http://james.apache.org/**_**>
>>>>> _server/**3/config-system.**html<http://james.apache.org/***
>>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>>> >
>>>>> <http://james.apache.org/****
>>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>> >
>>>>>
>>>>>> **<__http://james.apache.org/_**_**server/**3/config-system.**html<http://james.apache.org/__**server/**3/config-system.html>
>>>>>> <http://james.apache.org/_**_server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>>> **>
>>>>>>
>>>>> <http://james.apache.org/**
>>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>> >
>>>>>
>>>>>> **>
>>>>>>
>>>>> <**http://james.apache.org/**_****<http://james.apache.org/**_**>
>>>>> _server/3/config-system.html<h**ttp://james.apache.org/**__**
>>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>>> >
>>>>>
>>>>> <http://james.apache.org/****
>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>> >
>>>>>
>>>>>> <**ht__tp://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>>> **<http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>>> >
>>>>>>
>>>>>
>>>>> <http://james.apache.org/**
>>>>> server/3/config-system.html<ht**tp://james.apache.org/server/**
>>>>> 3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>> >
>>>>>
>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> But i could not get connected to jmx
>>>>> on
>>>>> my email server.
>>>>>
>>>>> Note that the server where i have
>>>>> deployed james is on azure cloud PAS
>>>>> network and is Ubunto system.
>>>>> Is there any mechanism where i can
>>>>> observe the message queue contents
>>>>> on
>>>>> local ubunto system using ssh only.
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay
>>>>> Navgale <
>>>>> ajay.navgale@centralogic.net
>>>>> <mailto:ajay.navgale@**central**
>>>>> ogic.net <ht...@centralogic.net>
>>>>> >
>>>>>
>>>>>
>>>>>>
>>>>>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ---------- Forwarded message
>>>>> ----------
>>>>>
>>>>> From: Eric Charles <
>>>>> eric@apache.org
>>>>> <ma...@apache.org>>
>>>>>
>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>> Subject: Re: James Server SMTP
>>>>> Spooling Issue
>>>>> To: James Users List
>>>>> <server-user@james.apache.org
>>>>> <mailto:server-user@james.**
>>>>> apache.org <se...@james.apache.org>**>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Hi,
>>>>> You mean you the newly spooled
>>>>> mails
>>>>> 'push-out' the remaining ones.
>>>>> After that, the latest one remains
>>>>> stucked in the queu?
>>>>>
>>>>> If such, that's very strange and
>>>>> we
>>>>> never saw that before.
>>>>> Do you use JMX to inspect the
>>>>> queue
>>>>> content/size?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 12/02/2013 11:45, Ajay Navgale
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> We are using james 3.0 beta4.
>>>>> We have an issue while sending
>>>>> an email. There is always one
>>>>> outgoing
>>>>> mail
>>>>> left in spool and is delivered
>>>>> when any new outgoing mail is
>>>>> to
>>>>> be
>>>>> sent.
>>>>> Now previous mail gets
>>>>> delivered
>>>>> and this recent once sits in
>>>>> the
>>>>> spool.
>>>>> This is happening for Remote
>>>>> delivery.
>>>>>
>>>>> Can anyone throw some light on
>>>>> this.
>>>>>
>>>>> Thanks & Regards,
>>>>> Ajay
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------
>>>>> ****
>>>>> __********--------------------****--__--**
>>>>>
>>>>>
>>>>> --**
>>>>> --**
>>>>>
>>>>> --**---------
>>>>>
>>>>> To unsubscribe, e-mail:
>>>>> server-user-unsubscribe@james.**
>>>>> **
>>>>> __********
>>>>> apache.org <http://apache.org>
>>>>> <
>>>>> server-user-**unsubscribe@**__**
>>>>> **ja**
>>>>> mes.apache.org
>>>>> <http://mes.apache.org><http:/**
>>>>> **/__
>>>>> james.apache.org
>>>>> <http://james.apache.org>>
>>>>> <unsubscribe@**james.apache.__**
>>>>> **org
>>>>> <http://james.apache.org>
>>>>> <unsubscribe@james.apache.org
>>>>> <mailto:unsubscribe@james.**
>>>>> apache.org <un...@james.apache.org>**>>__>
>>>>>
>>>>>
>>>>> <server-user-**unsubscribe@****
>>>>> j**
>>>>> __ames.apache.org <http://j__ames.apache.org>
>>>>> <http://james.apache.org><**
>>>>> unsubscribe@__james.apache.org
>>>>> <mailto:unsubscribe@james.**
>>>>> apache.org <un...@james.apache.org>**>>
>>>>> <server-user-**unsubscribe@__**
>>>>> j**
>>>>> ames.apache.org <http://james.apache.org>
>>>>> <mailto:unsubscribe@james.**
>>>>> apache.org <un...@james.apache.org>**><server-user-__**
>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>> james.apache.org <se...@james.apache.org>>
>>>>> <mailto:server-user-**
>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>> james.apache.org <se...@james.apache.org>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> For additional commands,
>>>>> e-mail:
>>>>> server-user-help@james.apache.
>>>>> ****
>>>>> __**
>>>>> **
>>>>>
>>>>> ****org<
>>>>> server-user-help@james.****__****
>>>>> apach**e.org
>>>>> <http://e.org> <http://apache.org>
>>>>> <
>>>>>
>>>>> server-user-help@james.**__****
>>>>> apach**
>>>>> e.org
>>>>> <http://e.org> <http://apache.org
>>>>> ><
>>>>> server-user-help@james.****
>>>>> apach**
>>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>>> user-help@james.__apache.org
>>>>> <mailto:server-user-help@**
>>>>> james.apache.org <se...@james.apache.org>
>>>>> >>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------**
>>>>> **
>>>>> __******----------------------****--__--**
>>>>>
>>>>>
>>>>>
>>>>> --**
>>>>>
>>>>> --**---------
>>>>> To unsubscribe, e-mail:
>>>>> server-user-unsubscribe@james.**
>>>>> **__******
>>>>> apache.org
>>>>> <http://apache.org>
>>>>> <
>>>>> server-user-**unsubscribe@****ja**
>>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>>> <http://james.apache.org><****
>>>>> unsubscribe@__
>>>>> james.apache.org
>>>>> <mailto:unsubscribe@james.**ap**ache.org<http://apache.org>
>>>>> <unsubscribe@james.**apache.org <un...@james.apache.org>>
>>>>>
>>>>>>
>>>>>>> <server-user-**unsubscribe@__**j**
>>>>> ames.apache.org <http://james.apache.org> <mailto:unsubscribe@james.**
>>>>> apache.org <un...@james.apache.org>**><server-user-__**
>>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>>> james.apache.org <se...@james.apache.org>>
>>>>> <mailto:server-user-**
>>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>>> james.apache.org <se...@james.apache.org>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> For additional commands, e-mail:
>>>>> server-user-help@james.apache.**
>>>>> **__**
>>>>>
>>>>> ****org<
>>>>> server-user-help@james.**__****apach**
>>>>> e.org
>>>>> <http://e.org> <http://apache.org> <
>>>>> server-user-help@james.****apach**__e.org
>>>>> <http://apach__**e.org <http://apach__e.org>>
>>>>> <http://apache.org><server-****
>>>>> user-help@james.
>>>>> __apache.org
>>>>> <mailto:server-user-help@**jam**
>>>>> es.apache.org <http://james.apache.org><server-user-**
>>>>> help@james.apache.org <se...@james.apache.org>>
>>>>>
>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------****
>>>>> __****------------------------****--__--**
>>>>>
>>>>> --**---------
>>>>> To unsubscribe, e-mail:
>>>>> server-user-unsubscribe@james.****__****
>>>>> apache.org
>>>>> <http://apache.org><
>>>>> server-user-**unsubscribe@__**ja**mes.apache.org<
>>>>> http://**james.apache.org <http://james.apache.org>>
>>>>> <mailto:unsubscribe@james.**ap**ache.org<http://apache.org>
>>>>> <unsubscribe@james.**apache.org <un...@james.apache.org>>
>>>>>
>>>>>> <se...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>> >
>>>>>>
>>>>> <mailto:server-user-**unsubscr**
>>>>> ibe@james.apache.org <un...@james.apache.org><server-**
>>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>>>
>>>>>
>>>>> For additional commands, e-mail:
>>>>> server-user-help@james.apache.****__****org<
>>>>> server-user-help@james.****apach**__e.org<
>>>>> http://apach__**e.org <http://apach__e.org>>
>>>>> <http://apache.org>
>>>>> <server-user-help@james.__**apac**he.org<
>>>>> http://apache.org**>
>>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------****
>>>>> __**--------------------------****--__--**---------
>>>>> To unsubscribe, e-mail:
>>>>> server-user-unsubscribe@james.****__**apache.org
>>>>> <http://apache.org><server-****user-__unsubscribe@james.
>>>>> **
>>>>> apache.org <se...@james.apache.org>
>>>>> >
>>>>> <ma...@james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>>> For additional commands, e-mail:
>>>>> server-user-help@james.apache.**
>>>>> **__**org<server-user-help@**
>>>>> james.__apache.org
>>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------****__--------------------------**
>>>>> --**
>>>>> --__---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****__
>>>>> apache.org
>>>>> <ma...@james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>> For additional commands, e-mail: server-user-help@james.apache.
>>>>> ****
>>>>> __org
>>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>> >
>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>> **org<se...@james.apache.org>
>>>>> >
>>>>>
>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>> >
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>> >
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
We do use to restart the system after that the spooled mails are delivered
and after restart first mail is sent out with out getting stuck in outgoing
queue but from second mail onwards one mail always keeps stuck in outgoing
queue.
Regards,
Farooq
On Tue, Feb 19, 2013 at 6:15 PM, Eric Charles <er...@apache.org> wrote:
> Did you already tried a stop/start of James to see if those numbers change?
>
> Thx, Eric
>
>
> On 19/02/2013 12:33, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> The QueueSize is 2 in mbean Destination=outgoing,Type=**Queue(ActiveMQ)
>> and
>> Size is also 2 in name=queue,queue=outgoing,**type=component (james)
>>
>> The only logical relation that i can see between ActiveMQ and James is the
>> outgoing queue size in both is 2. Where as there are no messages in List
>> returned by james bean and ActiveMQ bean shows one message in queue.
>>
>> we have'nt done any changes in ActiveMQ, but we have changed configuration
>> files of james for spams, fakeipaddress, baeysian algorithm and we dont
>> store copy of sent mails.
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
>>
>> Hi Farooq,
>>>
>>> Looking at Destination=outgoing,Type=****Queue, the
>>> EnqueueCount/DequeueCount/****QueueSize seem odd (14976 - 14975 <> 2).
>>>
>>>
>>> Can you link/find some logic between those ActiveMQ numbers and the
>>> numbers shown in the James MBeans?
>>>
>>> Do you run with the embedded ActiveMQ shipped by default? Any changes in
>>> the configuration?
>>>
>>> Thx, Eric
>>>
>>>
>>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>>
>>>> Here you go..
>>>> Attributes Value
>>>> BeanName ConsumerCount
>>>> ProducerCount QueueSize DequeueCount EnqueueCount
>>>> browse
>>>> Destination=ActiveMQ.DLQ,Type=****Queue 0 0 1 0
>>>>
>>>> 0 Shows 1 message in
>>>> outgoing queue,
>>>> invalid recepient
>>>> Destination=outgoing,Type=****Queue 10 5 2
>>>> 14976
>>>>
>>>> 14975 shows 1 message
>>>> in outgoing queue,the one which we sends after every 30 sec
>>>> Destination=spool,Type=Queue 2 3 0 15146 15146
>>>> no emails
>>>> Destination=ActiveMQ.Advisory.****TempQueue,Type=Topic 1 0
>>>>
>>>> 0 0 146 no
>>>> emails
>>>> Destination=ActiveMQ.Advisory.****Queue,Type=Topic 0 0 0
>>>> 0 6 no emails
>>>> Destination=ActiveMQ.Advisory.****Producer.Queue.spool,Type=****Topic
>>>> 0
>>>>
>>>> 0 0 0 3 no emails
>>>> Destination=ActiveMQ.Advisory.****Producer.Queue.outgoing,**
>>>> Type=**Topic
>>>>
>>>> 0 0 0 0 5 no emails
>>>> Destination=ActiveMQ.Advisory.****Consumer.Queue.spool,Type=****Topic
>>>> 0
>>>>
>>>> 0 0 0 253212 no emails
>>>> Destination=ActiveMQ.Advisory.****Consumer.Queue.outgoing,**
>>>> Type=**Topic
>>>>
>>>> 0 0 0 0 1232626 no emails
>>>> Destination=ActiveMQ.Advisory.****Connection,Type=Topic 0 0
>>>>
>>>> 0 0 1 no
>>>> emails
>>>>
>>>>
>>>>
>>>> Now I can see the mail stuck in outgoing queue, the one which we send
>>>> every 30 sec..
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>>
>>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>>> <ma...@apache.org>> wrote:
>>>>
>>>> Hi,
>>>> All, except the first and the last ones.
>>>> Thx, Eric
>>>>
>>>>
>>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>
>>>> Which mbean of activemq would you like me to check from the
>>>> following ...
>>>> org.apache.activemq:__****BrokerName=james,__**
>>>> ConnectorName=tcp_//localhost_****__0,Type=Connector
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.Connection,****__Type=Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.Consumer.__****Queue.outgoing,Type=Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.Consumer.__****Queue.spool,Type=Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.Producer.__****Queue.outgoing,Type=Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.Producer.__****Queue.spool,Type=Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.Queue,Type=****__Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.Advisory.TempQueue,_****_Type=Topic
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _ActiveMQ.DLQ,Type=Queue
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _outgoing,Type=Queue
>>>> org.apache.activemq:__****BrokerName=james,Destination=_****
>>>> _spool,Type=Queue
>>>> org.apache.activemq:__****BrokerName=james,Type=Broker
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <eric@apache.org
>>>> <ma...@apache.org>> wrote:
>>>>
>>>> Any chance to compare those numbers with the ones given by
>>>> the activemq
>>>> mbeans?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>
>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>
>>>> "You mean to 'push out' the queue.
>>>> The mail you send triggers the pending mails to go
>>>> out?"
>>>>
>>>> Yes this new mail push the earlier mail out but itself
>>>> gets stuck in
>>>> spool,to which a new mail after 30 sec pushes out and
>>>> that mail gets
>>>> struck
>>>> and soon...
>>>>
>>>> Can you guide me how to figure out the reason as to why
>>>> the size attribute
>>>> value is 5 and the browse List only contains 3 mails
>>>> details.
>>>> Also Why The mail which gets stuck in spool its count
>>>> is
>>>> incremented in
>>>> attribure Size but its details are not present in
>>>> browse
>>>> List..?
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>>
>>>> Hi Farooq,
>>>>
>>>>
>>>>
>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>
>>>>
>>>> Here is the output which i get when i use Bean
>>>> org.apache.james:name=queue,******
>>>> __**queue=outgoing,type=__****component
>>>>
>>>> $>bean
>>>> org.apache.james:name=queue,******
>>>> __**queue=outgoing,type=__****component
>>>>
>>>>
>>>>
>>>> #bean is set to org.apache.james:name=queue,**
>>>> queue=outgoing,type=component
>>>> $>info
>>>> #mbean =
>>>> org.apache.james:name=queue,******
>>>> __**queue=outgoing,type=__****component
>>>> #class name =
>>>> org.apache.james.queue.****__****
>>>>
>>>> library.MailQueueManagement
>>>>
>>>>
>>>>
>>>> # attributes
>>>> %0 - Size (long, r)
>>>> # operations
>>>> %0 - java.util.List browse()
>>>> %1 - long clear()
>>>> %2 - long flush()
>>>> %3 - long
>>>> removeWithName(java.lang.****_****_String p1)
>>>> %4 - long
>>>> removeWithRecipient(java.lang.****__****String
>>>> p1)
>>>> %5 - long
>>>> removeWithSender(java.lang.*******__*String
>>>> p1)
>>>>
>>>>
>>>>
>>>>
>>>> #there's no notifications
>>>> $>get Size
>>>> #mbean =
>>>> org.apache.james:name=queue,******
>>>> __**queue=outgoing,type=__****component:
>>>>
>>>>
>>>> Size = 7;
>>>>
>>>>
>>>> Cool, it seems like you have found a JXM CLI which
>>>> works fine.
>>>> Which one is it?
>>>>
>>>>
>>>>
>>>> Let me know if you need any further details.
>>>>
>>>> can you educate me as to Size= 7 is the no of
>>>> mails still in outgoing
>>>> spool
>>>> or is some default size of outgoing queue.
>>>>
>>>>
>>>> It is the number of pending mails in the
>>>> queue.
>>>>
>>>> So you have 7 mails waiting to be sent to the
>>>> outside world/
>>>>
>>>>
>>>> Also note that do deal with this spooling
>>>> problem, the workaround that
>>>> we
>>>>
>>>> did temporarily is that we created an
>>>> application that sends an email to
>>>> some email address every 30 sec.
>>>>
>>>>
>>>> You mean to 'push out' the queue.
>>>> The mail you send triggers the pending mails to go
>>>> out?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Farooq
>>>>
>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles
>>>> <eric@apache.org <ma...@apache.org>>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>
>>>> Maybe the cloud's firewall blocks your
>>>> requests.
>>>>
>>>> For JMX command line, type 'jmx cli' in
>>>> google and experiment (tried
>>>> one
>>>> of these long time ago).
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>
>>>>
>>>> I tried remotely connecting to JMX
>>>> using
>>>> Jconsole and remote jmx
>>>> connection
>>>> method specified on
>>>> http://james.apache.org/****
>>>> server/3/config-system.html<__**
>>>> **ht**tp://
>>>> james.apache.org/****
>>>> <http://james.apache.org/****>
>>>> server/3/config-system.html<****
>>>> ht__tp://
>>>> james.apache.org/**__**server/**3/config-system.html<http://james.apache.org/**__**server/3/config-system.html>
>>>> <http://**james.apache.org/**__server/3/**config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>> >
>>>> <http://james.apache.org/****
>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>> >
>>>>
>>>>>
>>>>>>
>>>>
>>>> <ht**tp://james.apache.org/**_****<http://james.apache.org/**_**>
>>>> _server/**3/config-system.**html<http://james.apache.org/***
>>>> *__server/**3/config-system.**html<http://james.apache.org/**__server/**3/config-system.html>
>>>> >
>>>> <http://james.apache.org/****
>>>> server/**3/config-system.html<**http://james.apache.org/****
>>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>> >
>>>>
>>>>> **<__http://james.apache.org/_**_**server/**3/config-system.**html<http://james.apache.org/__**server/**3/config-system.html>
>>>>> <http://james.apache.org/_**_server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>>>> **>
>>>>>
>>>> <http://james.apache.org/**
>>>> server/**3/config-system.html<**http://james.apache.org/**
>>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>> >
>>>>
>>>>> **>
>>>>>
>>>> <**http://james.apache.org/**_****<http://james.apache.org/**_**>
>>>> _server/3/config-system.html<h**ttp://james.apache.org/**__**
>>>> server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>>> >
>>>>
>>>> <http://james.apache.org/****
>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>> >
>>>>
>>>>> <**ht__tp://james.apache.org/****server/__3/config-system.html<http://james.apache.org/**server/__3/config-system.html>
>>>>> **<http://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>>> >
>>>>>
>>>>
>>>> <http://james.apache.org/**
>>>> server/3/config-system.html<ht**tp://james.apache.org/server/**
>>>> 3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>> >
>>>>
>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>> But i could not get connected to jmx on
>>>> my email server.
>>>>
>>>> Note that the server where i have
>>>> deployed james is on azure cloud PAS
>>>> network and is Ubunto system.
>>>> Is there any mechanism where i can
>>>> observe the message queue contents
>>>> on
>>>> local ubunto system using ssh only.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay
>>>> Navgale <
>>>> ajay.navgale@centralogic.net
>>>> <mailto:ajay.navgale@**central**
>>>> ogic.net <ht...@centralogic.net>
>>>> >
>>>>
>>>>
>>>>>
>>>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ---------- Forwarded message
>>>> ----------
>>>>
>>>> From: Eric Charles <
>>>> eric@apache.org
>>>> <ma...@apache.org>>
>>>>
>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>> Subject: Re: James Server SMTP
>>>> Spooling Issue
>>>> To: James Users List
>>>> <server-user@james.apache.org
>>>> <mailto:server-user@james.**
>>>> apache.org <se...@james.apache.org>**>>
>>>>
>>>>
>>>>
>>>>
>>>> Hi,
>>>> You mean you the newly spooled
>>>> mails
>>>> 'push-out' the remaining ones.
>>>> After that, the latest one remains
>>>> stucked in the queu?
>>>>
>>>> If such, that's very strange and we
>>>> never saw that before.
>>>> Do you use JMX to inspect the queue
>>>> content/size?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 12/02/2013 11:45, Ajay Navgale
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>
>>>> We are using james 3.0 beta4.
>>>> We have an issue while sending
>>>> an email. There is always one
>>>> outgoing
>>>> mail
>>>> left in spool and is delivered
>>>> when any new outgoing mail is
>>>> to
>>>> be
>>>> sent.
>>>> Now previous mail gets
>>>> delivered
>>>> and this recent once sits in
>>>> the
>>>> spool.
>>>> This is happening for Remote
>>>> delivery.
>>>>
>>>> Can anyone throw some light on
>>>> this.
>>>>
>>>> Thanks & Regards,
>>>> Ajay
>>>>
>>>>
>>>>
>>>> ------------------------------
>>>> ****
>>>> __********--------------------****--__--**
>>>>
>>>>
>>>> --**
>>>> --**
>>>>
>>>> --**---------
>>>>
>>>> To unsubscribe, e-mail:
>>>> server-user-unsubscribe@james.****
>>>> __********
>>>> apache.org <http://apache.org>
>>>> <
>>>> server-user-**unsubscribe@**__**
>>>> **ja**
>>>> mes.apache.org
>>>> <http://mes.apache.org><http:/**
>>>> **/__
>>>> james.apache.org
>>>> <http://james.apache.org>>
>>>> <unsubscribe@**james.apache.__**
>>>> **org
>>>> <http://james.apache.org>
>>>> <unsubscribe@james.apache.org
>>>> <mailto:unsubscribe@james.**
>>>> apache.org <un...@james.apache.org>**>>__>
>>>>
>>>>
>>>> <server-user-**unsubscribe@****j**
>>>> __ames.apache.org <http://j__ames.apache.org>
>>>> <http://james.apache.org><**
>>>> unsubscribe@__james.apache.org
>>>> <mailto:unsubscribe@james.**
>>>> apache.org <un...@james.apache.org>**>>
>>>> <server-user-**unsubscribe@__**j**
>>>> ames.apache.org <http://james.apache.org>
>>>> <mailto:unsubscribe@james.**
>>>> apache.org <un...@james.apache.org>**><server-user-__**
>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>> james.apache.org <se...@james.apache.org>>
>>>> <mailto:server-user-**
>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>> james.apache.org <se...@james.apache.org>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> For additional commands,
>>>> e-mail:
>>>> server-user-help@james.apache.
>>>> ****
>>>> __**
>>>> **
>>>>
>>>> ****org<
>>>> server-user-help@james.****__****
>>>> apach**e.org
>>>> <http://e.org> <http://apache.org>
>>>> <
>>>>
>>>> server-user-help@james.**__****
>>>> apach**
>>>> e.org
>>>> <http://e.org> <http://apache.org
>>>> ><
>>>> server-user-help@james.****apach**
>>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>>> user-help@james.__apache.org
>>>> <mailto:server-user-help@**
>>>> james.apache.org <se...@james.apache.org>
>>>> >>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****
>>>> __******----------------------****--__--**
>>>>
>>>>
>>>>
>>>> --**
>>>>
>>>> --**---------
>>>> To unsubscribe, e-mail:
>>>> server-user-unsubscribe@james.****__******
>>>> apache.org
>>>> <http://apache.org>
>>>> <
>>>> server-user-**unsubscribe@****ja**
>>>> __mes.apache.org <http://ja__mes.apache.org>
>>>> <http://james.apache.org><****unsubscribe@
>>>> __
>>>> james.apache.org
>>>> <mailto:unsubscribe@james.**ap**ache.org<http://apache.org>
>>>> <unsubscribe@james.**apache.org <un...@james.apache.org>>
>>>>
>>>>>
>>>>>> <server-user-**unsubscribe@__**j**
>>>> ames.apache.org <http://james.apache.org> <mailto:unsubscribe@james.**
>>>> apache.org <un...@james.apache.org>**><server-user-__**
>>>> unsubscribe@james.apache.org <server-user-__unsubscribe@**
>>>> james.apache.org <se...@james.apache.org>>
>>>> <mailto:server-user-**
>>>> unsubscribe@james.apache.org <server-user-unsubscribe@**
>>>> james.apache.org <se...@james.apache.org>>>>
>>>>
>>>>
>>>>
>>>>
>>>> For additional commands, e-mail:
>>>> server-user-help@james.apache.****__**
>>>>
>>>> ****org<
>>>> server-user-help@james.**__****apach**
>>>> e.org
>>>> <http://e.org> <http://apache.org> <
>>>> server-user-help@james.****apach**__e.org<
>>>> http://apach__**e.org <http://apach__e.org>>
>>>> <http://apache.org><server-****
>>>> user-help@james.
>>>> __apache.org
>>>> <mailto:server-user-help@**jam**
>>>> es.apache.org <http://james.apache.org><server-user-**
>>>> help@james.apache.org <se...@james.apache.org>>
>>>>
>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****
>>>> __****------------------------****--__--**
>>>>
>>>> --**---------
>>>> To unsubscribe, e-mail:
>>>> server-user-unsubscribe@james.****__****apache.org
>>>> <http://apache.org><
>>>> server-user-**unsubscribe@__**ja**mes.apache.org<
>>>> http://**james.apache.org <http://james.apache.org>>
>>>> <mailto:unsubscribe@james.**ap**ache.org<http://apache.org>
>>>> <unsubscribe@james.**apache.org <un...@james.apache.org>>
>>>>
>>>>> <se...@james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>> <mailto:server-user-**unsubscr**
>>>> ibe@james.apache.org <un...@james.apache.org><server-**
>>>> user-unsubscribe@james.apache.**org<se...@james.apache.org>
>>>> >
>>>>
>>>>>
>>>>>>
>>>>
>>>> For additional commands, e-mail:
>>>> server-user-help@james.apache.****__****org<
>>>> server-user-help@james.****apach**__e.org<
>>>> http://apach__**e.org <http://apach__e.org>>
>>>> <http://apache.org>
>>>> <server-user-help@james.__**apac**he.org<
>>>> http://apache.org**>
>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>> <se...@james.apache.org>
>>>> >
>>>>
>>>>>
>>>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****
>>>> __**--------------------------****--__--**---------
>>>> To unsubscribe, e-mail:
>>>> server-user-unsubscribe@james.****__**apache.org
>>>> <http://apache.org><server-****user-__unsubscribe@james.**
>>>> apache.org <se...@james.apache.org>
>>>> >
>>>> <ma...@james.apache.org>
>>>> <se...@james.apache.org>
>>>> >
>>>>
>>>>>
>>>>>> For additional commands, e-mail:
>>>> server-user-help@james.apache.**
>>>> **__**org<server-user-help@**
>>>> james.__apache.org
>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>> <se...@james.apache.org>
>>>> >
>>>>
>>>>>
>>>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****__--------------------------**
>>>> --**
>>>> --__---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****__
>>>> apache.org
>>>> <ma...@james.apache.org>
>>>> <se...@james.apache.org>
>>>> >
>>>>
>>>>>
>>>>> For additional commands, e-mail: server-user-help@james.apache.*
>>>> ***
>>>> __org
>>>> <mailto:server-user-help@**jam**es.apache.org<http://james.apache.org>
>>>> <se...@james.apache.org>
>>>> >
>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>> >
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>
>>>> >
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>> >
>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Did you already tried a stop/start of James to see if those numbers change?
Thx, Eric
On 19/02/2013 12:33, Farooq Ahmed wrote:
> Hi Eric,
>
> The QueueSize is 2 in mbean Destination=outgoing,Type=Queue(ActiveMQ) and
> Size is also 2 in name=queue,queue=outgoing,type=component (james)
>
> The only logical relation that i can see between ActiveMQ and James is the
> outgoing queue size in both is 2. Where as there are no messages in List
> returned by james bean and ActiveMQ bean shows one message in queue.
>
> we have'nt done any changes in ActiveMQ, but we have changed configuration
> files of james for spams, fakeipaddress, baeysian algorithm and we dont
> store copy of sent mails.
>
> Regards,
> Farooq
>
> On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
>
>> Hi Farooq,
>>
>> Looking at Destination=outgoing,Type=**Queue, the
>> EnqueueCount/DequeueCount/**QueueSize seem odd (14976 - 14975 <> 2).
>>
>> Can you link/find some logic between those ActiveMQ numbers and the
>> numbers shown in the James MBeans?
>>
>> Do you run with the embedded ActiveMQ shipped by default? Any changes in
>> the configuration?
>>
>> Thx, Eric
>>
>>
>> On 19/02/2013 11:44, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> Here you go..
>>> Attributes Value
>>> BeanName ConsumerCount
>>> ProducerCount QueueSize DequeueCount EnqueueCount
>>> browse
>>> Destination=ActiveMQ.DLQ,Type=**Queue 0 0 1 0
>>> 0 Shows 1 message in
>>> outgoing queue,
>>> invalid recepient
>>> Destination=outgoing,Type=**Queue 10 5 2 14976
>>> 14975 shows 1 message
>>> in outgoing queue,the one which we sends after every 30 sec
>>> Destination=spool,Type=Queue 2 3 0 15146 15146
>>> no emails
>>> Destination=ActiveMQ.Advisory.**TempQueue,Type=Topic 1 0
>>> 0 0 146 no
>>> emails
>>> Destination=ActiveMQ.Advisory.**Queue,Type=Topic 0 0 0
>>> 0 6 no emails
>>> Destination=ActiveMQ.Advisory.**Producer.Queue.spool,Type=**Topic 0
>>> 0 0 0 3 no emails
>>> Destination=ActiveMQ.Advisory.**Producer.Queue.outgoing,Type=**Topic
>>> 0 0 0 0 5 no emails
>>> Destination=ActiveMQ.Advisory.**Consumer.Queue.spool,Type=**Topic 0
>>> 0 0 0 253212 no emails
>>> Destination=ActiveMQ.Advisory.**Consumer.Queue.outgoing,Type=**Topic
>>> 0 0 0 0 1232626 no emails
>>> Destination=ActiveMQ.Advisory.**Connection,Type=Topic 0 0
>>> 0 0 1 no
>>> emails
>>>
>>>
>>>
>>> Now I can see the mail stuck in outgoing queue, the one which we send
>>> every 30 sec..
>>>
>>> Regards,
>>> Farooq
>>>
>>>
>>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>>> <ma...@apache.org>> wrote:
>>>
>>> Hi,
>>> All, except the first and the last ones.
>>> Thx, Eric
>>>
>>>
>>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>
>>> Which mbean of activemq would you like me to check from the
>>> following ...
>>> org.apache.activemq:__**BrokerName=james,__**
>>> ConnectorName=tcp_//localhost_**__0,Type=Connector
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.Connection,**__Type=Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.Consumer.__**Queue.outgoing,Type=Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.Consumer.__**Queue.spool,Type=Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.Producer.__**Queue.outgoing,Type=Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.Producer.__**Queue.spool,Type=Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.Queue,Type=**__Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.Advisory.TempQueue,_**_Type=Topic
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _ActiveMQ.DLQ,Type=Queue
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _outgoing,Type=Queue
>>> org.apache.activemq:__**BrokerName=james,Destination=_**
>>> _spool,Type=Queue
>>> org.apache.activemq:__**BrokerName=james,Type=Broker
>>>
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <eric@apache.org
>>> <ma...@apache.org>> wrote:
>>>
>>> Any chance to compare those numbers with the ones given by
>>> the activemq
>>> mbeans?
>>>
>>> Thx, Eric
>>>
>>>
>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>
>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>
>>> "You mean to 'push out' the queue.
>>> The mail you send triggers the pending mails to go out?"
>>>
>>> Yes this new mail push the earlier mail out but itself
>>> gets stuck in
>>> spool,to which a new mail after 30 sec pushes out and
>>> that mail gets
>>> struck
>>> and soon...
>>>
>>> Can you guide me how to figure out the reason as to why
>>> the size attribute
>>> value is 5 and the browse List only contains 3 mails
>>> details.
>>> Also Why The mail which gets stuck in spool its count is
>>> incremented in
>>> attribure Size but its details are not present in browse
>>> List..?
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>
>>> Hi Farooq,
>>>
>>>
>>>
>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>
>>>
>>> Here is the output which i get when i use Bean
>>> org.apache.james:name=queue,****
>>> __**queue=outgoing,type=__**component
>>>
>>> $>bean
>>> org.apache.james:name=queue,****
>>> __**queue=outgoing,type=__**component
>>>
>>>
>>> #bean is set to org.apache.james:name=queue,**
>>> queue=outgoing,type=component
>>> $>info
>>> #mbean =
>>> org.apache.james:name=queue,****
>>> __**queue=outgoing,type=__**component
>>> #class name =
>>> org.apache.james.queue.****__**
>>> library.MailQueueManagement
>>>
>>>
>>>
>>> # attributes
>>> %0 - Size (long, r)
>>> # operations
>>> %0 - java.util.List browse()
>>> %1 - long clear()
>>> %2 - long flush()
>>> %3 - long
>>> removeWithName(java.lang.****_**_String p1)
>>> %4 - long
>>> removeWithRecipient(java.lang.**__****String p1)
>>> %5 - long
>>> removeWithSender(java.lang.*****__*String p1)
>>>
>>>
>>>
>>> #there's no notifications
>>> $>get Size
>>> #mbean =
>>> org.apache.james:name=queue,****
>>> __**queue=outgoing,type=__**component:
>>>
>>> Size = 7;
>>>
>>>
>>> Cool, it seems like you have found a JXM CLI which
>>> works fine.
>>> Which one is it?
>>>
>>>
>>>
>>> Let me know if you need any further details.
>>>
>>> can you educate me as to Size= 7 is the no of
>>> mails still in outgoing
>>> spool
>>> or is some default size of outgoing queue.
>>>
>>>
>>> It is the number of pending mails in the queue.
>>>
>>> So you have 7 mails waiting to be sent to the
>>> outside world/
>>>
>>>
>>> Also note that do deal with this spooling
>>> problem, the workaround that
>>> we
>>>
>>> did temporarily is that we created an
>>> application that sends an email to
>>> some email address every 30 sec.
>>>
>>>
>>> You mean to 'push out' the queue.
>>> The mail you send triggers the pending mails to go
>>> out?
>>>
>>> Thx, Eric
>>>
>>>
>>>
>>> Regards,
>>>
>>> Farooq
>>>
>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles
>>> <eric@apache.org <ma...@apache.org>> wrote:
>>>
>>> Hi,
>>>
>>>
>>> Maybe the cloud's firewall blocks your
>>> requests.
>>>
>>> For JMX command line, type 'jmx cli' in
>>> google and experiment (tried
>>> one
>>> of these long time ago).
>>>
>>> Thx, Eric
>>>
>>>
>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>
>>>
>>> I tried remotely connecting to JMX using
>>> Jconsole and remote jmx
>>> connection
>>> method specified on
>>> http://james.apache.org/****
>>> server/3/config-system.html<__**ht**tp://
>>> james.apache.org/****
>>> <http://james.apache.org/****>
>>> server/3/config-system.html<**ht__tp://
>>> james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>> <http://james.apache.org/****
>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>
>>>
>>>
>>> <ht**tp://james.apache.org/**_**
>>> _server/**3/config-system.html<http://james.apache.org/**__server/**3/config-system.html>
>>> <http://james.apache.org/****
>>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>> **<__http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>>> <http://james.apache.org/**
>>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>> **>
>>> <**http://james.apache.org/**_**
>>> _server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>>> <http://james.apache.org/****
>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>> <**ht__tp://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>>
>>> <http://james.apache.org/**
>>> server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>
>>>
>>>
>>>
>>>
>>>
>>> But i could not get connected to jmx on
>>> my email server.
>>>
>>> Note that the server where i have
>>> deployed james is on azure cloud PAS
>>> network and is Ubunto system.
>>> Is there any mechanism where i can
>>> observe the message queue contents
>>> on
>>> local ubunto system using ssh only.
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay
>>> Navgale <
>>> ajay.navgale@centralogic.net
>>> <ma...@centralogic.net>
>>>>
>>>
>>>
>>> wrote:
>>>
>>>
>>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>>
>>> From: Eric Charles <eric@apache.org
>>> <ma...@apache.org>>
>>>
>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>> Subject: Re: James Server SMTP
>>> Spooling Issue
>>> To: James Users List
>>> <server-user@james.apache.org
>>> <mailto:server-user@james.**
>>> apache.org <se...@james.apache.org>>>
>>>
>>>
>>>
>>> Hi,
>>> You mean you the newly spooled mails
>>> 'push-out' the remaining ones.
>>> After that, the latest one remains
>>> stucked in the queu?
>>>
>>> If such, that's very strange and we
>>> never saw that before.
>>> Do you use JMX to inspect the queue
>>> content/size?
>>>
>>> Thx, Eric
>>>
>>>
>>> On 12/02/2013 11:45, Ajay Navgale
>>> wrote:
>>>
>>> Hi,
>>>
>>>
>>> We are using james 3.0 beta4.
>>> We have an issue while sending
>>> an email. There is always one
>>> outgoing
>>> mail
>>> left in spool and is delivered
>>> when any new outgoing mail is to
>>> be
>>> sent.
>>> Now previous mail gets delivered
>>> and this recent once sits in the
>>> spool.
>>> This is happening for Remote
>>> delivery.
>>>
>>> Can anyone throw some light on
>>> this.
>>>
>>> Thanks & Regards,
>>> Ajay
>>>
>>>
>>>
>>> ------------------------------**
>>> __********--------------------**--__--**
>>>
>>> --**
>>> --**
>>>
>>> --**---------
>>>
>>> To unsubscribe, e-mail:
>>> server-user-unsubscribe@james.**
>>> __********
>>> apache.org <http://apache.org>
>>> <
>>> server-user-**unsubscribe@**__**ja**
>>> mes.apache.org
>>> <http://mes.apache.org><http:/**/__
>>> james.apache.org
>>> <http://james.apache.org>>
>>> <unsubscribe@**james.apache.__**org
>>> <http://james.apache.org>
>>> <unsubscribe@james.apache.org
>>> <mailto:unsubscribe@james.**
>>> apache.org <un...@james.apache.org>>>__>
>>>
>>>
>>> <server-user-**unsubscribe@**j**
>>> __ames.apache.org <http://j__ames.apache.org>
>>> <http://james.apache.org><**
>>> unsubscribe@__james.apache.org
>>> <mailto:unsubscribe@james.**
>>> apache.org <un...@james.apache.org>>>
>>> <server-user-**unsubscribe@__j**
>>> ames.apache.org <http://james.apache.org>
>>> <mailto:unsubscribe@james.**
>>> apache.org <un...@james.apache.org>><server-user-__**
>>> unsubscribe@james.apache.org <se...@james.apache.org>
>>> <mailto:server-user-**
>>> unsubscribe@james.apache.org <se...@james.apache.org>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> For additional commands,
>>> e-mail:
>>> server-user-help@james.apache.**
>>> __**
>>> **
>>>
>>> ****org<
>>> server-user-help@james.****__**
>>> apach**e.org
>>> <http://e.org> <http://apache.org> <
>>>
>>> server-user-help@james.**__**apach**
>>> e.org
>>> <http://e.org> <http://apache.org><
>>> server-user-help@james.**apach**
>>> __e.org <http://apach__e.org> <http://apache.org><server-**
>>> user-help@james.__apache.org
>>> <mailto:server-user-help@**
>>> james.apache.org <se...@james.apache.org>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**
>>> __******----------------------**--__--**
>>>
>>>
>>> --**
>>>
>>> --**---------
>>> To unsubscribe, e-mail:
>>> server-user-unsubscribe@james.**__******
>>> apache.org
>>> <http://apache.org>
>>> <
>>> server-user-**unsubscribe@**ja**
>>> __mes.apache.org <http://ja__mes.apache.org>
>>> <http://james.apache.org><**unsubscribe@__
>>> james.apache.org
>>> <ma...@james.apache.org>
>>>>>
>>> <server-user-**unsubscribe@__j**
>>> ames.apache.org <http://james.apache.org> <mailto:unsubscribe@james.**
>>> apache.org <un...@james.apache.org>><server-user-__**
>>> unsubscribe@james.apache.org <se...@james.apache.org>
>>> <mailto:server-user-**
>>> unsubscribe@james.apache.org <se...@james.apache.org>>>
>>>
>>>
>>>
>>>
>>> For additional commands, e-mail:
>>> server-user-help@james.apache.**__**
>>>
>>> ****org<
>>> server-user-help@james.**__**apach**e.org
>>> <http://e.org> <http://apache.org> <
>>> server-user-help@james.**apach**__e.org<http://apach__e.org>
>>> <http://apache.org><server-**user-help@james.
>>> __apache.org
>>> <ma...@james.apache.org>
>>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**
>>> __****------------------------**--__--**
>>>
>>> --**---------
>>> To unsubscribe, e-mail:
>>> server-user-unsubscribe@james.**__****apache.org
>>> <http://apache.org><
>>> server-user-**unsubscribe@__ja**mes.apache.org<http://james.apache.org>
>>> <ma...@james.apache.org>
>>>> <se...@james.apache.org>
>>> <ma...@james.apache.org>
>>>>>
>>>
>>>
>>> For additional commands, e-mail:
>>> server-user-help@james.apache.**__****org<
>>> server-user-help@james.**apach**__e.org<http://apach__e.org>
>>> <http://apache.org>
>>> <server-user-help@james.__apac**he.org<http://apache.org>
>>> <ma...@james.apache.org>
>>>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**
>>> __**--------------------------**--__--**---------
>>> To unsubscribe, e-mail:
>>> server-user-unsubscribe@james.**__**apache.org
>>> <http://apache.org><server-**user-__unsubscribe@james.**
>>> apache.org <se...@james.apache.org>
>>> <ma...@james.apache.org>
>>>>>
>>> For additional commands, e-mail:
>>> server-user-help@james.apache.**__**org<server-user-help@**
>>> james.__apache.org
>>> <ma...@james.apache.org>
>>>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**__----------------------------**
>>> --__---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**__apache.org
>>> <ma...@james.apache.org>
>>>>
>>> For additional commands, e-mail: server-user-help@james.apache.**
>>> __org
>>> <ma...@james.apache.org>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
The QueueSize is 2 in mbean Destination=outgoing,Type=Queue(ActiveMQ) and
Size is also 2 in name=queue,queue=outgoing,type=component (james)
The only logical relation that i can see between ActiveMQ and James is the
outgoing queue size in both is 2. Where as there are no messages in List
returned by james bean and ActiveMQ bean shows one message in queue.
we have'nt done any changes in ActiveMQ, but we have changed configuration
files of james for spams, fakeipaddress, baeysian algorithm and we dont
store copy of sent mails.
Regards,
Farooq
On Tue, Feb 19, 2013 at 5:31 PM, Eric Charles <er...@apache.org> wrote:
> Hi Farooq,
>
> Looking at Destination=outgoing,Type=**Queue, the
> EnqueueCount/DequeueCount/**QueueSize seem odd (14976 - 14975 <> 2).
>
> Can you link/find some logic between those ActiveMQ numbers and the
> numbers shown in the James MBeans?
>
> Do you run with the embedded ActiveMQ shipped by default? Any changes in
> the configuration?
>
> Thx, Eric
>
>
> On 19/02/2013 11:44, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> Here you go..
>> Attributes Value
>> BeanName ConsumerCount
>> ProducerCount QueueSize DequeueCount EnqueueCount
>> browse
>> Destination=ActiveMQ.DLQ,Type=**Queue 0 0 1 0
>> 0 Shows 1 message in
>> outgoing queue,
>> invalid recepient
>> Destination=outgoing,Type=**Queue 10 5 2 14976
>> 14975 shows 1 message
>> in outgoing queue,the one which we sends after every 30 sec
>> Destination=spool,Type=Queue 2 3 0 15146 15146
>> no emails
>> Destination=ActiveMQ.Advisory.**TempQueue,Type=Topic 1 0
>> 0 0 146 no
>> emails
>> Destination=ActiveMQ.Advisory.**Queue,Type=Topic 0 0 0
>> 0 6 no emails
>> Destination=ActiveMQ.Advisory.**Producer.Queue.spool,Type=**Topic 0
>> 0 0 0 3 no emails
>> Destination=ActiveMQ.Advisory.**Producer.Queue.outgoing,Type=**Topic
>> 0 0 0 0 5 no emails
>> Destination=ActiveMQ.Advisory.**Consumer.Queue.spool,Type=**Topic 0
>> 0 0 0 253212 no emails
>> Destination=ActiveMQ.Advisory.**Consumer.Queue.outgoing,Type=**Topic
>> 0 0 0 0 1232626 no emails
>> Destination=ActiveMQ.Advisory.**Connection,Type=Topic 0 0
>> 0 0 1 no
>> emails
>>
>>
>>
>> Now I can see the mail stuck in outgoing queue, the one which we send
>> every 30 sec..
>>
>> Regards,
>> Farooq
>>
>>
>> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Hi,
>> All, except the first and the last ones.
>> Thx, Eric
>>
>>
>> On 19/02/2013 10:57, Farooq Ahmed wrote:
>>
>> Hi Eric,
>>
>> Which mbean of activemq would you like me to check from the
>> following ...
>> org.apache.activemq:__**BrokerName=james,__**
>> ConnectorName=tcp_//localhost_**__0,Type=Connector
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.Connection,**__Type=Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.Consumer.__**Queue.outgoing,Type=Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.Consumer.__**Queue.spool,Type=Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.Producer.__**Queue.outgoing,Type=Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.Producer.__**Queue.spool,Type=Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.Queue,Type=**__Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.Advisory.TempQueue,_**_Type=Topic
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _ActiveMQ.DLQ,Type=Queue
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _outgoing,Type=Queue
>> org.apache.activemq:__**BrokerName=james,Destination=_**
>> _spool,Type=Queue
>> org.apache.activemq:__**BrokerName=james,Type=Broker
>>
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <eric@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Any chance to compare those numbers with the ones given by
>> the activemq
>> mbeans?
>>
>> Thx, Eric
>>
>>
>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>
>> Hi Eric,
>>
>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>
>> "You mean to 'push out' the queue.
>> The mail you send triggers the pending mails to go out?"
>>
>> Yes this new mail push the earlier mail out but itself
>> gets stuck in
>> spool,to which a new mail after 30 sec pushes out and
>> that mail gets
>> struck
>> and soon...
>>
>> Can you guide me how to figure out the reason as to why
>> the size attribute
>> value is 5 and the browse List only contains 3 mails
>> details.
>> Also Why The mail which gets stuck in spool its count is
>> incremented in
>> attribure Size but its details are not present in browse
>> List..?
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
>> <eric@apache.org <ma...@apache.org>> wrote:
>>
>> Hi Farooq,
>>
>>
>>
>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>
>> Hi Eric,
>>
>>
>> Here is the output which i get when i use Bean
>> org.apache.james:name=queue,****
>> __**queue=outgoing,type=__**component
>>
>> $>bean
>> org.apache.james:name=queue,****
>> __**queue=outgoing,type=__**component
>>
>>
>> #bean is set to org.apache.james:name=queue,**
>> queue=outgoing,type=component
>> $>info
>> #mbean =
>> org.apache.james:name=queue,****
>> __**queue=outgoing,type=__**component
>> #class name =
>> org.apache.james.queue.****__**
>> library.MailQueueManagement
>>
>>
>>
>> # attributes
>> %0 - Size (long, r)
>> # operations
>> %0 - java.util.List browse()
>> %1 - long clear()
>> %2 - long flush()
>> %3 - long
>> removeWithName(java.lang.****_**_String p1)
>> %4 - long
>> removeWithRecipient(java.lang.**__****String p1)
>> %5 - long
>> removeWithSender(java.lang.*****__*String p1)
>>
>>
>>
>> #there's no notifications
>> $>get Size
>> #mbean =
>> org.apache.james:name=queue,****
>> __**queue=outgoing,type=__**component:
>>
>> Size = 7;
>>
>>
>> Cool, it seems like you have found a JXM CLI which
>> works fine.
>> Which one is it?
>>
>>
>>
>> Let me know if you need any further details.
>>
>> can you educate me as to Size= 7 is the no of
>> mails still in outgoing
>> spool
>> or is some default size of outgoing queue.
>>
>>
>> It is the number of pending mails in the queue.
>>
>> So you have 7 mails waiting to be sent to the
>> outside world/
>>
>>
>> Also note that do deal with this spooling
>> problem, the workaround that
>> we
>>
>> did temporarily is that we created an
>> application that sends an email to
>> some email address every 30 sec.
>>
>>
>> You mean to 'push out' the queue.
>> The mail you send triggers the pending mails to go
>> out?
>>
>> Thx, Eric
>>
>>
>>
>> Regards,
>>
>> Farooq
>>
>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles
>> <eric@apache.org <ma...@apache.org>> wrote:
>>
>> Hi,
>>
>>
>> Maybe the cloud's firewall blocks your
>> requests.
>>
>> For JMX command line, type 'jmx cli' in
>> google and experiment (tried
>> one
>> of these long time ago).
>>
>> Thx, Eric
>>
>>
>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>
>> Hi Eric,
>>
>>
>> I tried remotely connecting to JMX using
>> Jconsole and remote jmx
>> connection
>> method specified on
>> http://james.apache.org/****
>> server/3/config-system.html<__**ht**tp://
>> james.apache.org/****
>> <http://james.apache.org/****>
>> server/3/config-system.html<**ht__tp://
>> james.apache.org/**__**server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>> <http://james.apache.org/****
>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>> >>
>>
>>
>> <ht**tp://james.apache.org/**_**
>> _server/**3/config-system.html<http://james.apache.org/**__server/**3/config-system.html>
>> <http://james.apache.org/****
>> server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>> >**<__http://james.apache.org/__**server/**3/config-system.html<http://james.apache.org/__server/**3/config-system.html>
>> <http://james.apache.org/**
>> server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>> >**>
>> <**http://james.apache.org/**_**
>> _server/3/config-system.html<http://james.apache.org/**__server/3/config-system.html>
>> <http://james.apache.org/****
>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>> ><**ht__tp://james.apache.org/**server/__3/config-system.html<http://james.apache.org/server/__3/config-system.html>
>>
>> <http://james.apache.org/**
>> server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>> >>
>>
>>
>>
>>
>>
>> But i could not get connected to jmx on
>> my email server.
>>
>> Note that the server where i have
>> deployed james is on azure cloud PAS
>> network and is Ubunto system.
>> Is there any mechanism where i can
>> observe the message queue contents
>> on
>> local ubunto system using ssh only.
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay
>> Navgale <
>> ajay.navgale@centralogic.net
>> <ma...@centralogic.net>
>> >
>>
>>
>> wrote:
>>
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>>
>> From: Eric Charles <eric@apache.org
>> <ma...@apache.org>>
>>
>> Date: Tue, Feb 12, 2013 at 7:52 PM
>> Subject: Re: James Server SMTP
>> Spooling Issue
>> To: James Users List
>> <server-user@james.apache.org
>> <mailto:server-user@james.**
>> apache.org <se...@james.apache.org>>>
>>
>>
>>
>> Hi,
>> You mean you the newly spooled mails
>> 'push-out' the remaining ones.
>> After that, the latest one remains
>> stucked in the queu?
>>
>> If such, that's very strange and we
>> never saw that before.
>> Do you use JMX to inspect the queue
>> content/size?
>>
>> Thx, Eric
>>
>>
>> On 12/02/2013 11:45, Ajay Navgale
>> wrote:
>>
>> Hi,
>>
>>
>> We are using james 3.0 beta4.
>> We have an issue while sending
>> an email. There is always one
>> outgoing
>> mail
>> left in spool and is delivered
>> when any new outgoing mail is to
>> be
>> sent.
>> Now previous mail gets delivered
>> and this recent once sits in the
>> spool.
>> This is happening for Remote
>> delivery.
>>
>> Can anyone throw some light on
>> this.
>>
>> Thanks & Regards,
>> Ajay
>>
>>
>>
>> ------------------------------**
>> __********--------------------**--__--**
>>
>> --**
>> --**
>>
>> --**---------
>>
>> To unsubscribe, e-mail:
>> server-user-unsubscribe@james.**
>> __********
>> apache.org <http://apache.org>
>> <
>> server-user-**unsubscribe@**__**ja**
>> mes.apache.org
>> <http://mes.apache.org><http:/**/__
>> james.apache.org
>> <http://james.apache.org>>
>> <unsubscribe@**james.apache.__**org
>> <http://james.apache.org>
>> <unsubscribe@james.apache.org
>> <mailto:unsubscribe@james.**
>> apache.org <un...@james.apache.org>>>__>
>>
>>
>> <server-user-**unsubscribe@**j**
>> __ames.apache.org <http://j__ames.apache.org>
>> <http://james.apache.org><**
>> unsubscribe@__james.apache.org
>> <mailto:unsubscribe@james.**
>> apache.org <un...@james.apache.org>>>
>> <server-user-**unsubscribe@__j**
>> ames.apache.org <http://james.apache.org>
>> <mailto:unsubscribe@james.**
>> apache.org <un...@james.apache.org>><server-user-__**
>> unsubscribe@james.apache.org <se...@james.apache.org>
>> <mailto:server-user-**
>> unsubscribe@james.apache.org <se...@james.apache.org>>>
>>
>>
>>
>>
>>
>>
>> For additional commands,
>> e-mail:
>> server-user-help@james.apache.**
>> __**
>> **
>>
>> ****org<
>> server-user-help@james.****__**
>> apach**e.org
>> <http://e.org> <http://apache.org> <
>>
>> server-user-help@james.**__**apach**
>> e.org
>> <http://e.org> <http://apache.org><
>> server-user-help@james.**apach**
>> __e.org <http://apach__e.org> <http://apache.org><server-**
>> user-help@james.__apache.org
>> <mailto:server-user-help@**
>> james.apache.org <se...@james.apache.org>>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------**
>> __******----------------------**--__--**
>>
>>
>> --**
>>
>> --**---------
>> To unsubscribe, e-mail:
>> server-user-unsubscribe@james.**__******
>> apache.org
>> <http://apache.org>
>> <
>> server-user-**unsubscribe@**ja**
>> __mes.apache.org <http://ja__mes.apache.org>
>> <http://james.apache.org><**unsubscribe@__
>> james.apache.org
>> <ma...@james.apache.org>
>> >>
>> <server-user-**unsubscribe@__j**
>> ames.apache.org <http://james.apache.org> <mailto:unsubscribe@james.**
>> apache.org <un...@james.apache.org>><server-user-__**
>> unsubscribe@james.apache.org <se...@james.apache.org>
>> <mailto:server-user-**
>> unsubscribe@james.apache.org <se...@james.apache.org>>>
>>
>>
>>
>>
>> For additional commands, e-mail:
>> server-user-help@james.apache.**__**
>>
>> ****org<
>> server-user-help@james.**__**apach**e.org
>> <http://e.org> <http://apache.org> <
>> server-user-help@james.**apach**__e.org<http://apach__e.org>
>> <http://apache.org><server-**user-help@james.
>> __apache.org
>> <ma...@james.apache.org>
>> >>
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------**
>> __****------------------------**--__--**
>>
>> --**---------
>> To unsubscribe, e-mail:
>> server-user-unsubscribe@james.**__****apache.org
>> <http://apache.org><
>> server-user-**unsubscribe@__ja**mes.apache.org<http://james.apache.org>
>> <ma...@james.apache.org>
>> ><se...@james.apache.org>
>> <ma...@james.apache.org>
>> >>
>>
>>
>> For additional commands, e-mail:
>> server-user-help@james.apache.**__****org<
>> server-user-help@james.**apach**__e.org<http://apach__e.org>
>> <http://apache.org>
>> <server-user-help@james.__apac**he.org<http://apache.org>
>> <ma...@james.apache.org>
>> >>>
>>
>>
>>
>>
>> ------------------------------**
>> __**--------------------------**--__--**---------
>> To unsubscribe, e-mail:
>> server-user-unsubscribe@james.**__**apache.org
>> <http://apache.org><server-**user-__unsubscribe@james.**
>> apache.org <se...@james.apache.org>
>> <ma...@james.apache.org>
>> >>
>> For additional commands, e-mail:
>> server-user-help@james.apache.**__**org<server-user-help@**
>> james.__apache.org
>> <ma...@james.apache.org>
>> >>
>>
>>
>>
>>
>> ------------------------------**__----------------------------**
>> --__---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**__apache.org
>> <ma...@james.apache.org>
>> >
>> For additional commands, e-mail: server-user-help@james.apache.**
>> __org
>> <ma...@james.apache.org>
>> >
>>
>>
>>
>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi Farooq,
Looking at Destination=outgoing,Type=Queue, the
EnqueueCount/DequeueCount/QueueSize seem odd (14976 - 14975 <> 2).
Can you link/find some logic between those ActiveMQ numbers and the
numbers shown in the James MBeans?
Do you run with the embedded ActiveMQ shipped by default? Any changes in
the configuration?
Thx, Eric
On 19/02/2013 11:44, Farooq Ahmed wrote:
> Hi Eric,
>
> Here you go..
> Attributes Value
> BeanName ConsumerCount
> ProducerCount QueueSize DequeueCount EnqueueCount browse
> Destination=ActiveMQ.DLQ,Type=Queue 0 0 1 0 0 Shows 1 message in
> outgoing queue,
> invalid recepient
> Destination=outgoing,Type=Queue 10 5 2 14976 14975 shows 1 message
> in outgoing queue,the one which we sends after every 30 sec
> Destination=spool,Type=Queue 2 3 0 15146 15146 no emails
> Destination=ActiveMQ.Advisory.TempQueue,Type=Topic 1 0 0 0 146 no
> emails
> Destination=ActiveMQ.Advisory.Queue,Type=Topic 0 0 0 0 6 no emails
> Destination=ActiveMQ.Advisory.Producer.Queue.spool,Type=Topic 0
> 0 0 0 3 no emails
> Destination=ActiveMQ.Advisory.Producer.Queue.outgoing,Type=Topic
> 0 0 0 0 5 no emails
> Destination=ActiveMQ.Advisory.Consumer.Queue.spool,Type=Topic 0
> 0 0 0 253212 no emails
> Destination=ActiveMQ.Advisory.Consumer.Queue.outgoing,Type=Topic
> 0 0 0 0 1232626 no emails
> Destination=ActiveMQ.Advisory.Connection,Type=Topic 0 0 0 0 1 no
> emails
>
>
>
> Now I can see the mail stuck in outgoing queue, the one which we send
> every 30 sec..
>
> Regards,
> Farooq
>
>
> On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <eric@apache.org
> <ma...@apache.org>> wrote:
>
> Hi,
> All, except the first and the last ones.
> Thx, Eric
>
>
> On 19/02/2013 10:57, Farooq Ahmed wrote:
>
> Hi Eric,
>
> Which mbean of activemq would you like me to check from the
> following ...
> org.apache.activemq:__BrokerName=james,__ConnectorName=tcp_//localhost___0,Type=Connector
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.Connection,__Type=Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.Consumer.__Queue.outgoing,Type=Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.Consumer.__Queue.spool,Type=Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.Producer.__Queue.outgoing,Type=Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.Producer.__Queue.spool,Type=Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.Queue,Type=__Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.Advisory.TempQueue,__Type=Topic
> org.apache.activemq:__BrokerName=james,Destination=__ActiveMQ.DLQ,Type=Queue
> org.apache.activemq:__BrokerName=james,Destination=__outgoing,Type=Queue
> org.apache.activemq:__BrokerName=james,Destination=__spool,Type=Queue
> org.apache.activemq:__BrokerName=james,Type=Broker
>
> Regards,
> Farooq
>
> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <eric@apache.org
> <ma...@apache.org>> wrote:
>
> Any chance to compare those numbers with the ones given by
> the activemq
> mbeans?
>
> Thx, Eric
>
>
> On 19/02/2013 10:42, Farooq Ahmed wrote:
>
> Hi Eric,
>
> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>
> "You mean to 'push out' the queue.
> The mail you send triggers the pending mails to go out?"
>
> Yes this new mail push the earlier mail out but itself
> gets stuck in
> spool,to which a new mail after 30 sec pushes out and
> that mail gets
> struck
> and soon...
>
> Can you guide me how to figure out the reason as to why
> the size attribute
> value is 5 and the browse List only contains 3 mails
> details.
> Also Why The mail which gets stuck in spool its count is
> incremented in
> attribure Size but its details are not present in browse
> List..?
>
> Regards,
> Farooq
>
> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles
> <eric@apache.org <ma...@apache.org>> wrote:
>
> Hi Farooq,
>
>
>
> On 18/02/2013 12:39, Farooq Ahmed wrote:
>
> Hi Eric,
>
>
> Here is the output which i get when i use Bean
> org.apache.james:name=queue,**__**queue=outgoing,type=__component
>
> $>bean
> org.apache.james:name=queue,**__**queue=outgoing,type=__component
>
> #bean is set to org.apache.james:name=queue,**
> queue=outgoing,type=component
> $>info
> #mbean =
> org.apache.james:name=queue,**__**queue=outgoing,type=__component
> #class name =
> org.apache.james.queue.****__library.MailQueueManagement
>
>
> # attributes
> %0 - Size (long, r)
> # operations
> %0 - java.util.List browse()
> %1 - long clear()
> %2 - long flush()
> %3 - long
> removeWithName(java.lang.****__String p1)
> %4 - long
> removeWithRecipient(java.lang.__****String p1)
> %5 - long
> removeWithSender(java.lang.***__*String p1)
>
>
> #there's no notifications
> $>get Size
> #mbean =
> org.apache.james:name=queue,**__**queue=outgoing,type=__component:
> Size = 7;
>
>
> Cool, it seems like you have found a JXM CLI which
> works fine.
> Which one is it?
>
>
>
> Let me know if you need any further details.
>
> can you educate me as to Size= 7 is the no of
> mails still in outgoing
> spool
> or is some default size of outgoing queue.
>
>
> It is the number of pending mails in the queue.
>
> So you have 7 mails waiting to be sent to the
> outside world/
>
>
> Also note that do deal with this spooling
> problem, the workaround that
> we
>
> did temporarily is that we created an
> application that sends an email to
> some email address every 30 sec.
>
>
> You mean to 'push out' the queue.
> The mail you send triggers the pending mails to go out?
>
> Thx, Eric
>
>
>
> Regards,
>
> Farooq
>
> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles
> <eric@apache.org <ma...@apache.org>> wrote:
>
> Hi,
>
>
> Maybe the cloud's firewall blocks your requests.
>
> For JMX command line, type 'jmx cli' in
> google and experiment (tried
> one
> of these long time ago).
>
> Thx, Eric
>
>
> On 18/02/2013 10:11, Farooq Ahmed wrote:
>
> Hi Eric,
>
>
> I tried remotely connecting to JMX using
> Jconsole and remote jmx
> connection
> method specified on
> http://james.apache.org/****
> server/3/config-system.html<__ht**tp://james.apache.org/****
> <http://james.apache.org/****>
> server/3/config-system.html<ht__tp://james.apache.org/**__server/3/config-system.html
> <http://james.apache.org/**server/3/config-system.html>>
>
>
> <ht**tp://james.apache.org/**__server/**3/config-system.html
> <http://james.apache.org/**server/**3/config-system.html><__http://james.apache.org/__server/**3/config-system.html
> <http://james.apache.org/server/**3/config-system.html>>
> <**http://james.apache.org/**__server/3/config-system.html
> <http://james.apache.org/**server/3/config-system.html><ht__tp://james.apache.org/server/__3/config-system.html
> <http://james.apache.org/server/3/config-system.html>>
>
>
>
>
>
> But i could not get connected to jmx on
> my email server.
>
> Note that the server where i have
> deployed james is on azure cloud PAS
> network and is Ubunto system.
> Is there any mechanism where i can
> observe the message queue contents
> on
> local ubunto system using ssh only.
>
> Regards,
> Farooq
>
> On Tue, Feb 12, 2013 at 11:02 PM, Ajay
> Navgale <
> ajay.navgale@centralogic.net
> <ma...@centralogic.net>
>
> wrote:
>
>
>
>
>
> ---------- Forwarded message ----------
>
> From: Eric Charles <eric@apache.org
> <ma...@apache.org>>
> Date: Tue, Feb 12, 2013 at 7:52 PM
> Subject: Re: James Server SMTP
> Spooling Issue
> To: James Users List
> <server-user@james.apache.org
> <ma...@james.apache.org>>
>
>
> Hi,
> You mean you the newly spooled mails
> 'push-out' the remaining ones.
> After that, the latest one remains
> stucked in the queu?
>
> If such, that's very strange and we
> never saw that before.
> Do you use JMX to inspect the queue
> content/size?
>
> Thx, Eric
>
>
> On 12/02/2013 11:45, Ajay Navgale wrote:
>
> Hi,
>
>
> We are using james 3.0 beta4.
> We have an issue while sending
> an email. There is always one
> outgoing
> mail
> left in spool and is delivered
> when any new outgoing mail is to be
> sent.
> Now previous mail gets delivered
> and this recent once sits in the
> spool.
> This is happening for Remote
> delivery.
>
> Can anyone throw some light on this.
>
> Thanks & Regards,
> Ajay
>
>
>
> ------------------------------__********----------------------__--**
> --**
> --**
>
> --**---------
>
> To unsubscribe, e-mail:
> server-user-unsubscribe@james.__********
> apache.org <http://apache.org>
> <
> server-user-**unsubscribe@**__ja**mes.apache.org
> <http://mes.apache.org><http://__james.apache.org
> <http://james.apache.org>>
> <unsubscribe@**james.apache.__org
> <http://james.apache.org>
> <unsubscribe@james.apache.org
> <ma...@james.apache.org>>__>
>
>
> <server-user-**unsubscribe@**j__ames.apache.org
> <http://james.apache.org><unsubscribe@__james.apache.org
> <ma...@james.apache.org>>
> <server-user-**unsubscribe@__james.apache.org
> <ma...@james.apache.org><server-user-__unsubscribe@james.apache.org
> <ma...@james.apache.org>>
>
>
>
>
>
>
> For additional commands,
> e-mail:
> server-user-help@james.apache.__**
> **
>
> ****org<
> server-user-help@james.****__apach**e.org
> <http://e.org> <http://apache.org> <
>
> server-user-help@james.**__apach**e.org
> <http://e.org> <http://apache.org><
> server-user-help@james.**apach__e.org <http://apache.org><server-user-help@james.__apache.org
> <ma...@james.apache.org>>
>
>
>
>
>
>
>
>
>
>
> ------------------------------__******------------------------__--**
>
> --**
>
> --**---------
> To unsubscribe, e-mail:
> server-user-unsubscribe@james.__******apache.org
> <http://apache.org>
> <
> server-user-**unsubscribe@**ja__mes.apache.org
> <http://james.apache.org><unsubscribe@__james.apache.org
> <ma...@james.apache.org>>
> <server-user-**unsubscribe@__james.apache.org <ma...@james.apache.org><server-user-__unsubscribe@james.apache.org
> <ma...@james.apache.org>>
>
>
>
>
> For additional commands, e-mail:
> server-user-help@james.apache.__**
>
> ****org<
> server-user-help@james.**__apach**e.org
> <http://e.org> <http://apache.org> <
> server-user-help@james.**apach__e.org
> <http://apache.org><server-user-help@james.__apache.org
> <ma...@james.apache.org>>
>
>
>
>
>
>
>
> ------------------------------__****--------------------------__--**
>
> --**---------
> To unsubscribe, e-mail:
> server-user-unsubscribe@james.__****apache.org
> <http://apache.org><
> server-user-**unsubscribe@__james.apache.org
> <ma...@james.apache.org><server-user-__unsubscribe@james.apache.org
> <ma...@james.apache.org>>
>
>
> For additional commands, e-mail:
> server-user-help@james.apache.__****org<
> server-user-help@james.**apach__e.org
> <http://apache.org>
> <server-user-help@james.__apache.org
> <ma...@james.apache.org>>>
>
>
>
>
> ------------------------------__**----------------------------__--**---------
> To unsubscribe, e-mail:
> server-user-unsubscribe@james.__**apache.org
> <http://apache.org><server-user-__unsubscribe@james.apache.org
> <ma...@james.apache.org>>
> For additional commands, e-mail:
> server-user-help@james.apache.__**org<server-user-help@james.__apache.org
> <ma...@james.apache.org>>
>
>
>
>
> ------------------------------__------------------------------__---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.__apache.org
> <ma...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.__org
> <ma...@james.apache.org>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
Here you go..
Attributes Value BeanName ConsumerCount
ProducerCount QueueSize DequeueCount EnqueueCount browse
Destination=ActiveMQ.DLQ,Type=Queue 0 0 1 0 0 Shows 1 message in outgoing
queue,
invalid recepient Destination=outgoing,Type=Queue 10 5 2 14976 14975 shows
1 message in outgoing queue,the one which we sends after every 30 sec
Destination=spool,Type=Queue 2 3 0 15146 15146 no emails
Destination=ActiveMQ.Advisory.TempQueue,Type=Topic 1 0 0 0 146 no emails
Destination=ActiveMQ.Advisory.Queue,Type=Topic 0 0 0 0 6 no emails
Destination=ActiveMQ.Advisory.Producer.Queue.spool,Type=Topic 0 0 0 0 3 no
emails Destination=ActiveMQ.Advisory.Producer.Queue.outgoing,Type=Topic 0 0
0 0 5 no emails
Destination=ActiveMQ.Advisory.Consumer.Queue.spool,Type=Topic 0 0 0 0 253212 no
emails Destination=ActiveMQ.Advisory.Consumer.Queue.outgoing,Type=Topic 0 0
0 0 1232626 no emails Destination=ActiveMQ.Advisory.Connection,Type=Topic 0
0 0 0 1 no emails
Now I can see the mail stuck in outgoing queue, the one which we send every
30 sec..
Regards,
Farooq
On Tue, Feb 19, 2013 at 4:38 PM, Eric Charles <er...@apache.org> wrote:
> Hi,
> All, except the first and the last ones.
> Thx, Eric
>
>
> On 19/02/2013 10:57, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> Which mbean of activemq would you like me to check from the following ...
>> org.apache.activemq:**BrokerName=james,**ConnectorName=tcp_//localhost_**
>> 0,Type=Connector
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.Connection,**Type=Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.Consumer.**Queue.outgoing,Type=Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.Consumer.**Queue.spool,Type=Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.Producer.**Queue.outgoing,Type=Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.Producer.**Queue.spool,Type=Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.Queue,Type=**Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.Advisory.TempQueue,**Type=Topic
>> org.apache.activemq:**BrokerName=james,Destination=**
>> ActiveMQ.DLQ,Type=Queue
>> org.apache.activemq:**BrokerName=james,Destination=**outgoing,Type=Queue
>> org.apache.activemq:**BrokerName=james,Destination=**spool,Type=Queue
>> org.apache.activemq:**BrokerName=james,Type=Broker
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <er...@apache.org> wrote:
>>
>> Any chance to compare those numbers with the ones given by the activemq
>>> mbeans?
>>>
>>> Thx, Eric
>>>
>>>
>>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>>
>>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>>
>>>> "You mean to 'push out' the queue.
>>>> The mail you send triggers the pending mails to go out?"
>>>>
>>>> Yes this new mail push the earlier mail out but itself gets stuck in
>>>> spool,to which a new mail after 30 sec pushes out and that mail gets
>>>> struck
>>>> and soon...
>>>>
>>>> Can you guide me how to figure out the reason as to why the size
>>>> attribute
>>>> value is 5 and the browse List only contains 3 mails details.
>>>> Also Why The mail which gets stuck in spool its count is incremented in
>>>> attribure Size but its details are not present in browse List..?
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles <er...@apache.org> wrote:
>>>>
>>>> Hi Farooq,
>>>>
>>>>>
>>>>>
>>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>>>
>>>>>> Here is the output which i get when i use Bean
>>>>>> org.apache.james:name=queue,******queue=outgoing,type=**component
>>>>>>
>>>>>> $>bean org.apache.james:name=queue,******queue=outgoing,type=**
>>>>>> component
>>>>>>
>>>>>> #bean is set to org.apache.james:name=queue,**
>>>>>> queue=outgoing,type=component
>>>>>> $>info
>>>>>> #mbean = org.apache.james:name=queue,******queue=outgoing,type=**
>>>>>> component
>>>>>> #class name = org.apache.james.queue.******
>>>>>> library.MailQueueManagement
>>>>>>
>>>>>>
>>>>>> # attributes
>>>>>> %0 - Size (long, r)
>>>>>> # operations
>>>>>> %0 - java.util.List browse()
>>>>>> %1 - long clear()
>>>>>> %2 - long flush()
>>>>>> %3 - long removeWithName(java.lang.******String p1)
>>>>>> %4 - long removeWithRecipient(java.lang.******String p1)
>>>>>> %5 - long removeWithSender(java.lang.******String p1)
>>>>>>
>>>>>>
>>>>>> #there's no notifications
>>>>>> $>get Size
>>>>>> #mbean = org.apache.james:name=queue,******queue=outgoing,type=**
>>>>>> component:
>>>>>> Size = 7;
>>>>>>
>>>>>>
>>>>>> Cool, it seems like you have found a JXM CLI which works fine.
>>>>> Which one is it?
>>>>>
>>>>>
>>>>>
>>>>> Let me know if you need any further details.
>>>>>
>>>>>> can you educate me as to Size= 7 is the no of mails still in outgoing
>>>>>> spool
>>>>>> or is some default size of outgoing queue.
>>>>>>
>>>>>>
>>>>>> It is the number of pending mails in the queue.
>>>>>>
>>>>> So you have 7 mails waiting to be sent to the outside world/
>>>>>
>>>>>
>>>>> Also note that do deal with this spooling problem, the workaround
>>>>> that
>>>>> we
>>>>>
>>>>> did temporarily is that we created an application that sends an email
>>>>>> to
>>>>>> some email address every 30 sec.
>>>>>>
>>>>>>
>>>>>> You mean to 'push out' the queue.
>>>>> The mail you send triggers the pending mails to go out?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>> Farooq
>>>>>>
>>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>>> Maybe the cloud's firewall blocks your requests.
>>>>>>>
>>>>>>> For JMX command line, type 'jmx cli' in google and experiment (tried
>>>>>>> one
>>>>>>> of these long time ago).
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>>>>
>>>>>>> Hi Eric,
>>>>>>>
>>>>>>>
>>>>>>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>>>>>>> connection
>>>>>>>> method specified on http://james.apache.org/****
>>>>>>>> server/3/config-system.html<**ht**tp://james.apache.org/****
>>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>> >
>>>>>>>>
>>>>>>>>>
>>>>>>>>> <ht**tp://james.apache.org/****server/**3/config-system.html<http://james.apache.org/**server/**3/config-system.html>
>>>>>>>> <**http://james.apache.org/**server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>>> >
>>>>>>>> <**http://james.apache.org/****server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>> <ht**tp://james.apache.org/server/**3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>> >
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> But i could not get connected to jmx on my email server.
>>>>>>>>
>>>>>>>> Note that the server where i have deployed james is on azure cloud
>>>>>>>> PAS
>>>>>>>> network and is Ubunto system.
>>>>>>>> Is there any mechanism where i can observe the message queue
>>>>>>>> contents
>>>>>>>> on
>>>>>>>> local ubunto system using ssh only.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Farooq
>>>>>>>>
>>>>>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>>>>>>> ajay.navgale@centralogic.net
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> ---------- Forwarded message ----------
>>>>>>>>
>>>>>>>>> From: Eric Charles <er...@apache.org>
>>>>>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>>>>>> Subject: Re: James Server SMTP Spooling Issue
>>>>>>>>> To: James Users List <se...@james.apache.org>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>>>>>>> After that, the latest one remains stucked in the queu?
>>>>>>>>>
>>>>>>>>> If such, that's very strange and we never saw that before.
>>>>>>>>> Do you use JMX to inspect the queue content/size?
>>>>>>>>>
>>>>>>>>> Thx, Eric
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We are using james 3.0 beta4.
>>>>>>>>>> We have an issue while sending an email. There is always one
>>>>>>>>>> outgoing
>>>>>>>>>> mail
>>>>>>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>>>>>>> sent.
>>>>>>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>>>>>>> spool.
>>>>>>>>>> This is happening for Remote delivery.
>>>>>>>>>>
>>>>>>>>>> Can anyone throw some light on this.
>>>>>>>>>>
>>>>>>>>>> Thanks & Regards,
>>>>>>>>>> Ajay
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------**
>>>>>>>>>> ********----------------------**--**
>>>>>>>>>> --**
>>>>>>>>>> --**
>>>>>>>>>>
>>>>>>>>>> --**---------
>>>>>>>>>>
>>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.**********
>>>>>>>>> apache.org
>>>>>>>>> <
>>>>>>>>> server-user-**unsubscribe@****ja**mes.apache.org<http://**
>>>>>>>>> james.apache.org <http://james.apache.org>>
>>>>>>>>> <unsubscribe@**james.apache.**org <http://james.apache.org> <
>>>>>>>>> unsubscribe@james.apache.org>**>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> <server-user-**unsubscribe@**j**ames.apache.org<http://james.apache.org>
>>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> <se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.
>>>>>>>>>> ****
>>>>>>>>>> **
>>>>>>>>>>
>>>>>>>>>> ****org<
>>>>>>>>> server-user-help@james.******apach**e.org <http://apache.org> <
>>>>>>>>>
>>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org><
>>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------********------------------------
>>>>>>>>> **--**
>>>>>>>>>
>>>>>>>> --**
>>>>>>>>
>>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>> apache.org
>>>>>>> <
>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>> <se...@james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>>> **
>>>>>>>>
>>>>>>> ****org<
>>>>>>> server-user-help@james.****apach**e.org <http://apache.org> <
>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******--------------------------**
>>>>>> --**
>>>>>>
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******apache.org
>>>>> <
>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>> ****org<
>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>> >>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>> >
>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi,
All, except the first and the last ones.
Thx, Eric
On 19/02/2013 10:57, Farooq Ahmed wrote:
> Hi Eric,
>
> Which mbean of activemq would you like me to check from the following ...
> org.apache.activemq:BrokerName=james,ConnectorName=tcp_//localhost_0,Type=Connector
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Connection,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Consumer.Queue.outgoing,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Consumer.Queue.spool,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Producer.Queue.outgoing,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Producer.Queue.spool,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Queue,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.TempQueue,Type=Topic
> org.apache.activemq:BrokerName=james,Destination=ActiveMQ.DLQ,Type=Queue
> org.apache.activemq:BrokerName=james,Destination=outgoing,Type=Queue
> org.apache.activemq:BrokerName=james,Destination=spool,Type=Queue
> org.apache.activemq:BrokerName=james,Type=Broker
>
> Regards,
> Farooq
>
> On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <er...@apache.org> wrote:
>
>> Any chance to compare those numbers with the ones given by the activemq
>> mbeans?
>>
>> Thx, Eric
>>
>>
>> On 19/02/2013 10:42, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>>
>>> "You mean to 'push out' the queue.
>>> The mail you send triggers the pending mails to go out?"
>>>
>>> Yes this new mail push the earlier mail out but itself gets stuck in
>>> spool,to which a new mail after 30 sec pushes out and that mail gets
>>> struck
>>> and soon...
>>>
>>> Can you guide me how to figure out the reason as to why the size attribute
>>> value is 5 and the browse List only contains 3 mails details.
>>> Also Why The mail which gets stuck in spool its count is incremented in
>>> attribure Size but its details are not present in browse List..?
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles <er...@apache.org> wrote:
>>>
>>> Hi Farooq,
>>>>
>>>>
>>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>>
>>>>> Here is the output which i get when i use Bean
>>>>> org.apache.james:name=queue,****queue=outgoing,type=component
>>>>>
>>>>> $>bean org.apache.james:name=queue,****queue=outgoing,type=component
>>>>> #bean is set to org.apache.james:name=queue,**
>>>>> queue=outgoing,type=component
>>>>> $>info
>>>>> #mbean = org.apache.james:name=queue,****queue=outgoing,type=component
>>>>> #class name = org.apache.james.queue.****library.MailQueueManagement
>>>>>
>>>>> # attributes
>>>>> %0 - Size (long, r)
>>>>> # operations
>>>>> %0 - java.util.List browse()
>>>>> %1 - long clear()
>>>>> %2 - long flush()
>>>>> %3 - long removeWithName(java.lang.****String p1)
>>>>> %4 - long removeWithRecipient(java.lang.****String p1)
>>>>> %5 - long removeWithSender(java.lang.****String p1)
>>>>>
>>>>> #there's no notifications
>>>>> $>get Size
>>>>> #mbean = org.apache.james:name=queue,****queue=outgoing,type=component:
>>>>> Size = 7;
>>>>>
>>>>>
>>>> Cool, it seems like you have found a JXM CLI which works fine.
>>>> Which one is it?
>>>>
>>>>
>>>>
>>>> Let me know if you need any further details.
>>>>> can you educate me as to Size= 7 is the no of mails still in outgoing
>>>>> spool
>>>>> or is some default size of outgoing queue.
>>>>>
>>>>>
>>>>> It is the number of pending mails in the queue.
>>>> So you have 7 mails waiting to be sent to the outside world/
>>>>
>>>>
>>>> Also note that do deal with this spooling problem, the workaround that
>>>> we
>>>>
>>>>> did temporarily is that we created an application that sends an email to
>>>>> some email address every 30 sec.
>>>>>
>>>>>
>>>> You mean to 'push out' the queue.
>>>> The mail you send triggers the pending mails to go out?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>>
>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>>
>>>>>> Maybe the cloud's firewall blocks your requests.
>>>>>>
>>>>>> For JMX command line, type 'jmx cli' in google and experiment (tried
>>>>>> one
>>>>>> of these long time ago).
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>>>
>>>>>> Hi Eric,
>>>>>>
>>>>>>>
>>>>>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>>>>>> connection
>>>>>>> method specified on http://james.apache.org/****
>>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>>>>
>>>>>>> <ht**tp://james.apache.org/**server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>>> <**http://james.apache.org/**server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>> But i could not get connected to jmx on my email server.
>>>>>>>
>>>>>>> Note that the server where i have deployed james is on azure cloud PAS
>>>>>>> network and is Ubunto system.
>>>>>>> Is there any mechanism where i can observe the message queue contents
>>>>>>> on
>>>>>>> local ubunto system using ssh only.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Farooq
>>>>>>>
>>>>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>>>>>> ajay.navgale@centralogic.net
>>>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> ---------- Forwarded message ----------
>>>>>>>> From: Eric Charles <er...@apache.org>
>>>>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>>>>> Subject: Re: James Server SMTP Spooling Issue
>>>>>>>> To: James Users List <se...@james.apache.org>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>>>>>> After that, the latest one remains stucked in the queu?
>>>>>>>>
>>>>>>>> If such, that's very strange and we never saw that before.
>>>>>>>> Do you use JMX to inspect the queue content/size?
>>>>>>>>
>>>>>>>> Thx, Eric
>>>>>>>>
>>>>>>>>
>>>>>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>>> We are using james 3.0 beta4.
>>>>>>>>> We have an issue while sending an email. There is always one
>>>>>>>>> outgoing
>>>>>>>>> mail
>>>>>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>>>>>> sent.
>>>>>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>>>>>> spool.
>>>>>>>>> This is happening for Remote delivery.
>>>>>>>>>
>>>>>>>>> Can anyone throw some light on this.
>>>>>>>>>
>>>>>>>>> Thanks & Regards,
>>>>>>>>> Ajay
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------********------------------------**
>>>>>>>>> --**
>>>>>>>>> --**
>>>>>>>>>
>>>>>>>>> --**---------
>>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>>> apache.org
>>>>>>>> <
>>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>>
>>>>>>>> <se...@james.apache.org>
>>>>>>>> <se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>>>> **
>>>>>>>>>
>>>>>>>> ****org<
>>>>>>>> server-user-help@james.****apach**e.org <http://apache.org> <
>>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------******--------------------------**
>>>>>>> --**
>>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******apache.org
>>>>>> <
>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>> ****org<
>>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
Which mbean of activemq would you like me to check from the following ...
org.apache.activemq:BrokerName=james,ConnectorName=tcp_//localhost_0,Type=Connector
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Connection,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Consumer.Queue.outgoing,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Consumer.Queue.spool,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Producer.Queue.outgoing,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Producer.Queue.spool,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.Queue,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.Advisory.TempQueue,Type=Topic
org.apache.activemq:BrokerName=james,Destination=ActiveMQ.DLQ,Type=Queue
org.apache.activemq:BrokerName=james,Destination=outgoing,Type=Queue
org.apache.activemq:BrokerName=james,Destination=spool,Type=Queue
org.apache.activemq:BrokerName=james,Type=Broker
Regards,
Farooq
On Tue, Feb 19, 2013 at 4:16 PM, Eric Charles <er...@apache.org> wrote:
> Any chance to compare those numbers with the ones given by the activemq
> mbeans?
>
> Thx, Eric
>
>
> On 19/02/2013 10:42, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>>
>> "You mean to 'push out' the queue.
>> The mail you send triggers the pending mails to go out?"
>>
>> Yes this new mail push the earlier mail out but itself gets stuck in
>> spool,to which a new mail after 30 sec pushes out and that mail gets
>> struck
>> and soon...
>>
>> Can you guide me how to figure out the reason as to why the size attribute
>> value is 5 and the browse List only contains 3 mails details.
>> Also Why The mail which gets stuck in spool its count is incremented in
>> attribure Size but its details are not present in browse List..?
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles <er...@apache.org> wrote:
>>
>> Hi Farooq,
>>>
>>>
>>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>>
>>>> Here is the output which i get when i use Bean
>>>> org.apache.james:name=queue,****queue=outgoing,type=component
>>>>
>>>> $>bean org.apache.james:name=queue,****queue=outgoing,type=component
>>>> #bean is set to org.apache.james:name=queue,**
>>>> queue=outgoing,type=component
>>>> $>info
>>>> #mbean = org.apache.james:name=queue,****queue=outgoing,type=component
>>>> #class name = org.apache.james.queue.****library.MailQueueManagement
>>>>
>>>> # attributes
>>>> %0 - Size (long, r)
>>>> # operations
>>>> %0 - java.util.List browse()
>>>> %1 - long clear()
>>>> %2 - long flush()
>>>> %3 - long removeWithName(java.lang.****String p1)
>>>> %4 - long removeWithRecipient(java.lang.****String p1)
>>>> %5 - long removeWithSender(java.lang.****String p1)
>>>>
>>>> #there's no notifications
>>>> $>get Size
>>>> #mbean = org.apache.james:name=queue,****queue=outgoing,type=component:
>>>> Size = 7;
>>>>
>>>>
>>> Cool, it seems like you have found a JXM CLI which works fine.
>>> Which one is it?
>>>
>>>
>>>
>>> Let me know if you need any further details.
>>>> can you educate me as to Size= 7 is the no of mails still in outgoing
>>>> spool
>>>> or is some default size of outgoing queue.
>>>>
>>>>
>>>> It is the number of pending mails in the queue.
>>> So you have 7 mails waiting to be sent to the outside world/
>>>
>>>
>>> Also note that do deal with this spooling problem, the workaround that
>>> we
>>>
>>>> did temporarily is that we created an application that sends an email to
>>>> some email address every 30 sec.
>>>>
>>>>
>>> You mean to 'push out' the queue.
>>> The mail you send triggers the pending mails to go out?
>>>
>>> Thx, Eric
>>>
>>>
>>>
>>> Regards,
>>>> Farooq
>>>>
>>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>>>>
>>>> Hi,
>>>>
>>>>>
>>>>> Maybe the cloud's firewall blocks your requests.
>>>>>
>>>>> For JMX command line, type 'jmx cli' in google and experiment (tried
>>>>> one
>>>>> of these long time ago).
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>>
>>>>> Hi Eric,
>>>>>
>>>>>>
>>>>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>>>>> connection
>>>>>> method specified on http://james.apache.org/****
>>>>>> server/3/config-system.html<ht**tp://james.apache.org/****
>>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>>> >
>>>>>> <ht**tp://james.apache.org/**server/**3/config-system.html<http://james.apache.org/server/**3/config-system.html>
>>>>>> <**http://james.apache.org/**server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>> >
>>>>>>
>>>>>>
>>>>>>>
>>>>>> But i could not get connected to jmx on my email server.
>>>>>>
>>>>>> Note that the server where i have deployed james is on azure cloud PAS
>>>>>> network and is Ubunto system.
>>>>>> Is there any mechanism where i can observe the message queue contents
>>>>>> on
>>>>>> local ubunto system using ssh only.
>>>>>>
>>>>>> Regards,
>>>>>> Farooq
>>>>>>
>>>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>>>>> ajay.navgale@centralogic.net
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------- Forwarded message ----------
>>>>>>> From: Eric Charles <er...@apache.org>
>>>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>>>> Subject: Re: James Server SMTP Spooling Issue
>>>>>>> To: James Users List <se...@james.apache.org>
>>>>>>>
>>>>>>>
>>>>>>> Hi,
>>>>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>>>>> After that, the latest one remains stucked in the queu?
>>>>>>>
>>>>>>> If such, that's very strange and we never saw that before.
>>>>>>> Do you use JMX to inspect the queue content/size?
>>>>>>>
>>>>>>> Thx, Eric
>>>>>>>
>>>>>>>
>>>>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>>
>>>>>>>> We are using james 3.0 beta4.
>>>>>>>> We have an issue while sending an email. There is always one
>>>>>>>> outgoing
>>>>>>>> mail
>>>>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>>>>> sent.
>>>>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>>>>> spool.
>>>>>>>> This is happening for Remote delivery.
>>>>>>>>
>>>>>>>> Can anyone throw some light on this.
>>>>>>>>
>>>>>>>> Thanks & Regards,
>>>>>>>> Ajay
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------********------------------------**
>>>>>>>> --**
>>>>>>>> --**
>>>>>>>>
>>>>>>>> --**---------
>>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.********
>>>>>>> apache.org
>>>>>>> <
>>>>>>> server-user-**unsubscribe@**ja**mes.apache.org<http://james.apache.org>
>>>>>>> <unsubscribe@**james.apache.org <un...@james.apache.org>>
>>>>>>>
>>>>>>> <se...@james.apache.org>
>>>>>>> <se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>>>> **
>>>>>>>>
>>>>>>> ****org<
>>>>>>> server-user-help@james.****apach**e.org <http://apache.org> <
>>>>>>> server-user-help@james.**apach**e.org <http://apache.org><
>>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******--------------------------**
>>>>>> --**
>>>>>>
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******apache.org
>>>>> <
>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>> ****org<
>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>> >>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>> >
>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Any chance to compare those numbers with the ones given by the activemq
mbeans?
Thx, Eric
On 19/02/2013 10:42, Farooq Ahmed wrote:
> Hi Eric,
>
> i have used jmxterm-1.0-alpha-4-uber jmx cli,
>
> "You mean to 'push out' the queue.
> The mail you send triggers the pending mails to go out?"
>
> Yes this new mail push the earlier mail out but itself gets stuck in
> spool,to which a new mail after 30 sec pushes out and that mail gets struck
> and soon...
>
> Can you guide me how to figure out the reason as to why the size attribute
> value is 5 and the browse List only contains 3 mails details.
> Also Why The mail which gets stuck in spool its count is incremented in
> attribure Size but its details are not present in browse List..?
>
> Regards,
> Farooq
>
> On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles <er...@apache.org> wrote:
>
>> Hi Farooq,
>>
>>
>> On 18/02/2013 12:39, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> Here is the output which i get when i use Bean
>>> org.apache.james:name=queue,**queue=outgoing,type=component
>>>
>>> $>bean org.apache.james:name=queue,**queue=outgoing,type=component
>>> #bean is set to org.apache.james:name=queue,**
>>> queue=outgoing,type=component
>>> $>info
>>> #mbean = org.apache.james:name=queue,**queue=outgoing,type=component
>>> #class name = org.apache.james.queue.**library.MailQueueManagement
>>> # attributes
>>> %0 - Size (long, r)
>>> # operations
>>> %0 - java.util.List browse()
>>> %1 - long clear()
>>> %2 - long flush()
>>> %3 - long removeWithName(java.lang.**String p1)
>>> %4 - long removeWithRecipient(java.lang.**String p1)
>>> %5 - long removeWithSender(java.lang.**String p1)
>>> #there's no notifications
>>> $>get Size
>>> #mbean = org.apache.james:name=queue,**queue=outgoing,type=component:
>>> Size = 7;
>>>
>>
>> Cool, it seems like you have found a JXM CLI which works fine.
>> Which one is it?
>>
>>
>>
>>> Let me know if you need any further details.
>>> can you educate me as to Size= 7 is the no of mails still in outgoing
>>> spool
>>> or is some default size of outgoing queue.
>>>
>>>
>> It is the number of pending mails in the queue.
>> So you have 7 mails waiting to be sent to the outside world/
>>
>>
>> Also note that do deal with this spooling problem, the workaround that we
>>> did temporarily is that we created an application that sends an email to
>>> some email address every 30 sec.
>>>
>>
>> You mean to 'push out' the queue.
>> The mail you send triggers the pending mails to go out?
>>
>> Thx, Eric
>>
>>
>>
>>> Regards,
>>> Farooq
>>>
>>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>>>
>>> Hi,
>>>>
>>>> Maybe the cloud's firewall blocks your requests.
>>>>
>>>> For JMX command line, type 'jmx cli' in google and experiment (tried one
>>>> of these long time ago).
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>>
>>>> Hi Eric,
>>>>>
>>>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>>>> connection
>>>>> method specified on http://james.apache.org/****
>>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>>> <ht**tp://james.apache.org/server/**3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>>>>
>>>>>
>>>>> But i could not get connected to jmx on my email server.
>>>>>
>>>>> Note that the server where i have deployed james is on azure cloud PAS
>>>>> network and is Ubunto system.
>>>>> Is there any mechanism where i can observe the message queue contents on
>>>>> local ubunto system using ssh only.
>>>>>
>>>>> Regards,
>>>>> Farooq
>>>>>
>>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>>>> ajay.navgale@centralogic.net
>>>>>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>> ---------- Forwarded message ----------
>>>>>> From: Eric Charles <er...@apache.org>
>>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>>> Subject: Re: James Server SMTP Spooling Issue
>>>>>> To: James Users List <se...@james.apache.org>
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>>>> After that, the latest one remains stucked in the queu?
>>>>>>
>>>>>> If such, that's very strange and we never saw that before.
>>>>>> Do you use JMX to inspect the queue content/size?
>>>>>>
>>>>>> Thx, Eric
>>>>>>
>>>>>>
>>>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>>
>>>>>>> We are using james 3.0 beta4.
>>>>>>> We have an issue while sending an email. There is always one outgoing
>>>>>>> mail
>>>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>>>> sent.
>>>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>>>> spool.
>>>>>>> This is happening for Remote delivery.
>>>>>>>
>>>>>>> Can anyone throw some light on this.
>>>>>>>
>>>>>>> Thanks & Regards,
>>>>>>> Ajay
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******--------------------------**
>>>>>>> --**
>>>>>>>
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******apache.org
>>>>>> <
>>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>>> <se...@james.apache.org>
>>>>>>>
>>>>>>
>>>>>>>
>>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>>> ****org<
>>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
i have used jmxterm-1.0-alpha-4-uber jmx cli,
"You mean to 'push out' the queue.
The mail you send triggers the pending mails to go out?"
Yes this new mail push the earlier mail out but itself gets stuck in
spool,to which a new mail after 30 sec pushes out and that mail gets struck
and soon...
Can you guide me how to figure out the reason as to why the size attribute
value is 5 and the browse List only contains 3 mails details.
Also Why The mail which gets stuck in spool its count is incremented in
attribure Size but its details are not present in browse List..?
Regards,
Farooq
On Tue, Feb 19, 2013 at 3:30 PM, Eric Charles <er...@apache.org> wrote:
> Hi Farooq,
>
>
> On 18/02/2013 12:39, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> Here is the output which i get when i use Bean
>> org.apache.james:name=queue,**queue=outgoing,type=component
>>
>> $>bean org.apache.james:name=queue,**queue=outgoing,type=component
>> #bean is set to org.apache.james:name=queue,**
>> queue=outgoing,type=component
>> $>info
>> #mbean = org.apache.james:name=queue,**queue=outgoing,type=component
>> #class name = org.apache.james.queue.**library.MailQueueManagement
>> # attributes
>> %0 - Size (long, r)
>> # operations
>> %0 - java.util.List browse()
>> %1 - long clear()
>> %2 - long flush()
>> %3 - long removeWithName(java.lang.**String p1)
>> %4 - long removeWithRecipient(java.lang.**String p1)
>> %5 - long removeWithSender(java.lang.**String p1)
>> #there's no notifications
>> $>get Size
>> #mbean = org.apache.james:name=queue,**queue=outgoing,type=component:
>> Size = 7;
>>
>
> Cool, it seems like you have found a JXM CLI which works fine.
> Which one is it?
>
>
>
>> Let me know if you need any further details.
>> can you educate me as to Size= 7 is the no of mails still in outgoing
>> spool
>> or is some default size of outgoing queue.
>>
>>
> It is the number of pending mails in the queue.
> So you have 7 mails waiting to be sent to the outside world/
>
>
> Also note that do deal with this spooling problem, the workaround that we
>> did temporarily is that we created an application that sends an email to
>> some email address every 30 sec.
>>
>
> You mean to 'push out' the queue.
> The mail you send triggers the pending mails to go out?
>
> Thx, Eric
>
>
>
>> Regards,
>> Farooq
>>
>> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>>
>> Hi,
>>>
>>> Maybe the cloud's firewall blocks your requests.
>>>
>>> For JMX command line, type 'jmx cli' in google and experiment (tried one
>>> of these long time ago).
>>>
>>> Thx, Eric
>>>
>>>
>>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>>
>>> Hi Eric,
>>>>
>>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>>> connection
>>>> method specified on http://james.apache.org/****
>>>> server/3/config-system.html<http://james.apache.org/**server/3/config-system.html>
>>>> <ht**tp://james.apache.org/server/**3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>>> >
>>>>
>>>> But i could not get connected to jmx on my email server.
>>>>
>>>> Note that the server where i have deployed james is on azure cloud PAS
>>>> network and is Ubunto system.
>>>> Is there any mechanism where i can observe the message queue contents on
>>>> local ubunto system using ssh only.
>>>>
>>>> Regards,
>>>> Farooq
>>>>
>>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>>> ajay.navgale@centralogic.net
>>>>
>>>> wrote:
>>>>>
>>>>>
>>>>
>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Eric Charles <er...@apache.org>
>>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>>> Subject: Re: James Server SMTP Spooling Issue
>>>>> To: James Users List <se...@james.apache.org>
>>>>>
>>>>>
>>>>> Hi,
>>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>>> After that, the latest one remains stucked in the queu?
>>>>>
>>>>> If such, that's very strange and we never saw that before.
>>>>> Do you use JMX to inspect the queue content/size?
>>>>>
>>>>> Thx, Eric
>>>>>
>>>>>
>>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>>
>>>>>> We are using james 3.0 beta4.
>>>>>> We have an issue while sending an email. There is always one outgoing
>>>>>> mail
>>>>>> left in spool and is delivered when any new outgoing mail is to be
>>>>>> sent.
>>>>>> Now previous mail gets delivered and this recent once sits in the
>>>>>> spool.
>>>>>> This is happening for Remote delivery.
>>>>>>
>>>>>> Can anyone throw some light on this.
>>>>>>
>>>>>> Thanks & Regards,
>>>>>> Ajay
>>>>>>
>>>>>>
>>>>>> ------------------------------******--------------------------**
>>>>>> --**
>>>>>>
>>>>> --**---------
>>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.******apache.org
>>>>> <
>>>>> server-user-**unsubscribe@**james.apache.org<un...@james.apache.org>
>>>>> <se...@james.apache.org>
>>>>> >
>>>>>
>>>>>>
>>>>>> For additional commands, e-mail: server-user-help@james.apache.**
>>>>> ****org<
>>>>> server-user-help@james.**apach**e.org <http://apache.org> <
>>>>> server-user-help@james.**apache.org<se...@james.apache.org>
>>>>> >>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>> >
>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi Farooq,
On 18/02/2013 12:39, Farooq Ahmed wrote:
> Hi Eric,
>
> Here is the output which i get when i use Bean
> org.apache.james:name=queue,queue=outgoing,type=component
>
> $>bean org.apache.james:name=queue,queue=outgoing,type=component
> #bean is set to org.apache.james:name=queue,queue=outgoing,type=component
> $>info
> #mbean = org.apache.james:name=queue,queue=outgoing,type=component
> #class name = org.apache.james.queue.library.MailQueueManagement
> # attributes
> %0 - Size (long, r)
> # operations
> %0 - java.util.List browse()
> %1 - long clear()
> %2 - long flush()
> %3 - long removeWithName(java.lang.String p1)
> %4 - long removeWithRecipient(java.lang.String p1)
> %5 - long removeWithSender(java.lang.String p1)
> #there's no notifications
> $>get Size
> #mbean = org.apache.james:name=queue,queue=outgoing,type=component:
> Size = 7;
Cool, it seems like you have found a JXM CLI which works fine.
Which one is it?
>
> Let me know if you need any further details.
> can you educate me as to Size= 7 is the no of mails still in outgoing spool
> or is some default size of outgoing queue.
>
It is the number of pending mails in the queue.
So you have 7 mails waiting to be sent to the outside world/
> Also note that do deal with this spooling problem, the workaround that we
> did temporarily is that we created an application that sends an email to
> some email address every 30 sec.
You mean to 'push out' the queue.
The mail you send triggers the pending mails to go out?
Thx, Eric
>
> Regards,
> Farooq
>
> On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
>
>> Hi,
>>
>> Maybe the cloud's firewall blocks your requests.
>>
>> For JMX command line, type 'jmx cli' in google and experiment (tried one
>> of these long time ago).
>>
>> Thx, Eric
>>
>>
>> On 18/02/2013 10:11, Farooq Ahmed wrote:
>>
>>> Hi Eric,
>>>
>>> I tried remotely connecting to JMX using Jconsole and remote jmx
>>> connection
>>> method specified on http://james.apache.org/**server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>>> But i could not get connected to jmx on my email server.
>>>
>>> Note that the server where i have deployed james is on azure cloud PAS
>>> network and is Ubunto system.
>>> Is there any mechanism where i can observe the message queue contents on
>>> local ubunto system using ssh only.
>>>
>>> Regards,
>>> Farooq
>>>
>>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>>> ajay.navgale@centralogic.net
>>>
>>>> wrote:
>>>>
>>>
>>>
>>>>
>>>> ---------- Forwarded message ----------
>>>> From: Eric Charles <er...@apache.org>
>>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>>> Subject: Re: James Server SMTP Spooling Issue
>>>> To: James Users List <se...@james.apache.org>
>>>>
>>>>
>>>> Hi,
>>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>>> After that, the latest one remains stucked in the queu?
>>>>
>>>> If such, that's very strange and we never saw that before.
>>>> Do you use JMX to inspect the queue content/size?
>>>>
>>>> Thx, Eric
>>>>
>>>>
>>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> We are using james 3.0 beta4.
>>>>> We have an issue while sending an email. There is always one outgoing
>>>>> mail
>>>>> left in spool and is delivered when any new outgoing mail is to be sent.
>>>>> Now previous mail gets delivered and this recent once sits in the spool.
>>>>> This is happening for Remote delivery.
>>>>>
>>>>> Can anyone throw some light on this.
>>>>>
>>>>> Thanks & Regards,
>>>>> Ajay
>>>>>
>>>>>
>>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>>>>
>>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>>
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
Here is the output which i get when i use Bean
org.apache.james:name=queue,queue=outgoing,type=component
$>bean org.apache.james:name=queue,queue=outgoing,type=component
#bean is set to org.apache.james:name=queue,queue=outgoing,type=component
$>info
#mbean = org.apache.james:name=queue,queue=outgoing,type=component
#class name = org.apache.james.queue.library.MailQueueManagement
# attributes
%0 - Size (long, r)
# operations
%0 - java.util.List browse()
%1 - long clear()
%2 - long flush()
%3 - long removeWithName(java.lang.String p1)
%4 - long removeWithRecipient(java.lang.String p1)
%5 - long removeWithSender(java.lang.String p1)
#there's no notifications
$>get Size
#mbean = org.apache.james:name=queue,queue=outgoing,type=component:
Size = 7;
Let me know if you need any further details.
can you educate me as to Size= 7 is the no of mails still in outgoing spool
or is some default size of outgoing queue.
Also note that do deal with this spooling problem, the workaround that we
did temporarily is that we created an application that sends an email to
some email address every 30 sec.
Regards,
Farooq
On Mon, Feb 18, 2013 at 4:19 PM, Eric Charles <er...@apache.org> wrote:
> Hi,
>
> Maybe the cloud's firewall blocks your requests.
>
> For JMX command line, type 'jmx cli' in google and experiment (tried one
> of these long time ago).
>
> Thx, Eric
>
>
> On 18/02/2013 10:11, Farooq Ahmed wrote:
>
>> Hi Eric,
>>
>> I tried remotely connecting to JMX using Jconsole and remote jmx
>> connection
>> method specified on http://james.apache.org/**server/3/config-system.html<http://james.apache.org/server/3/config-system.html>
>> But i could not get connected to jmx on my email server.
>>
>> Note that the server where i have deployed james is on azure cloud PAS
>> network and is Ubunto system.
>> Is there any mechanism where i can observe the message queue contents on
>> local ubunto system using ssh only.
>>
>> Regards,
>> Farooq
>>
>> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <
>> ajay.navgale@centralogic.net
>>
>>> wrote:
>>>
>>
>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Eric Charles <er...@apache.org>
>>> Date: Tue, Feb 12, 2013 at 7:52 PM
>>> Subject: Re: James Server SMTP Spooling Issue
>>> To: James Users List <se...@james.apache.org>
>>>
>>>
>>> Hi,
>>> You mean you the newly spooled mails 'push-out' the remaining ones.
>>> After that, the latest one remains stucked in the queu?
>>>
>>> If such, that's very strange and we never saw that before.
>>> Do you use JMX to inspect the queue content/size?
>>>
>>> Thx, Eric
>>>
>>>
>>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>>
>>> Hi,
>>>>
>>>> We are using james 3.0 beta4.
>>>> We have an issue while sending an email. There is always one outgoing
>>>> mail
>>>> left in spool and is delivered when any new outgoing mail is to be sent.
>>>> Now previous mail gets delivered and this recent once sits in the spool.
>>>> This is happening for Remote delivery.
>>>>
>>>> Can anyone throw some light on this.
>>>>
>>>> Thanks & Regards,
>>>> Ajay
>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>> --**---------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.****apache.org<
>>> server-user-**unsubscribe@james.apache.org<se...@james.apache.org>
>>> >
>>> For additional commands, e-mail: server-user-help@james.apache.****org<
>>> server-user-help@james.**apache.org <se...@james.apache.org>>
>>>
>>>
>>>
>>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi,
Maybe the cloud's firewall blocks your requests.
For JMX command line, type 'jmx cli' in google and experiment (tried one
of these long time ago).
Thx, Eric
On 18/02/2013 10:11, Farooq Ahmed wrote:
> Hi Eric,
>
> I tried remotely connecting to JMX using Jconsole and remote jmx connection
> method specified on http://james.apache.org/server/3/config-system.html
> But i could not get connected to jmx on my email server.
>
> Note that the server where i have deployed james is on azure cloud PAS
> network and is Ubunto system.
> Is there any mechanism where i can observe the message queue contents on
> local ubunto system using ssh only.
>
> Regards,
> Farooq
>
> On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <ajay.navgale@centralogic.net
>> wrote:
>
>>
>>
>> ---------- Forwarded message ----------
>> From: Eric Charles <er...@apache.org>
>> Date: Tue, Feb 12, 2013 at 7:52 PM
>> Subject: Re: James Server SMTP Spooling Issue
>> To: James Users List <se...@james.apache.org>
>>
>>
>> Hi,
>> You mean you the newly spooled mails 'push-out' the remaining ones.
>> After that, the latest one remains stucked in the queu?
>>
>> If such, that's very strange and we never saw that before.
>> Do you use JMX to inspect the queue content/size?
>>
>> Thx, Eric
>>
>>
>> On 12/02/2013 11:45, Ajay Navgale wrote:
>>
>>> Hi,
>>>
>>> We are using james 3.0 beta4.
>>> We have an issue while sending an email. There is always one outgoing mail
>>> left in spool and is delivered when any new outgoing mail is to be sent.
>>> Now previous mail gets delivered and this recent once sits in the spool.
>>> This is happening for Remote delivery.
>>>
>>> Can anyone throw some light on this.
>>>
>>> Thanks & Regards,
>>> Ajay
>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
>> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Farooq Ahmed <fa...@centralogic.net>.
Hi Eric,
I tried remotely connecting to JMX using Jconsole and remote jmx connection
method specified on http://james.apache.org/server/3/config-system.html
But i could not get connected to jmx on my email server.
Note that the server where i have deployed james is on azure cloud PAS
network and is Ubunto system.
Is there any mechanism where i can observe the message queue contents on
local ubunto system using ssh only.
Regards,
Farooq
On Tue, Feb 12, 2013 at 11:02 PM, Ajay Navgale <ajay.navgale@centralogic.net
> wrote:
>
>
> ---------- Forwarded message ----------
> From: Eric Charles <er...@apache.org>
> Date: Tue, Feb 12, 2013 at 7:52 PM
> Subject: Re: James Server SMTP Spooling Issue
> To: James Users List <se...@james.apache.org>
>
>
> Hi,
> You mean you the newly spooled mails 'push-out' the remaining ones.
> After that, the latest one remains stucked in the queu?
>
> If such, that's very strange and we never saw that before.
> Do you use JMX to inspect the queue content/size?
>
> Thx, Eric
>
>
> On 12/02/2013 11:45, Ajay Navgale wrote:
>
>> Hi,
>>
>> We are using james 3.0 beta4.
>> We have an issue while sending an email. There is always one outgoing mail
>> left in spool and is delivered when any new outgoing mail is to be sent.
>> Now previous mail gets delivered and this recent once sits in the spool.
>> This is happening for Remote delivery.
>>
>> Can anyone throw some light on this.
>>
>> Thanks & Regards,
>> Ajay
>>
>>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: server-user-unsubscribe@james.**apache.org<se...@james.apache.org>
> For additional commands, e-mail: server-user-help@james.apache.**org<se...@james.apache.org>
>
>
>
Re: James Server SMTP Spooling Issue
Posted by Eric Charles <er...@apache.org>.
Hi,
You mean you the newly spooled mails 'push-out' the remaining ones.
After that, the latest one remains stucked in the queu?
If such, that's very strange and we never saw that before.
Do you use JMX to inspect the queue content/size?
Thx, Eric
On 12/02/2013 11:45, Ajay Navgale wrote:
> Hi,
>
> We are using james 3.0 beta4.
> We have an issue while sending an email. There is always one outgoing mail
> left in spool and is delivered when any new outgoing mail is to be sent.
> Now previous mail gets delivered and this recent once sits in the spool.
> This is happening for Remote delivery.
>
> Can anyone throw some light on this.
>
> Thanks & Regards,
> Ajay
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: James Server SMTP Spooling Issue
Posted by Phillip Odam <ph...@nitorgroup.com>.
Hi Ajay
Firstly, you are not alone. While I have not experienced an issue with
the outgoing queue I have had issues with the incoming.
In my case the class org.apache.james.queue.jms.JMSMailQueue handles
retrieving mail from the incoming spool, however despite the routine
checking the queue every ten seconds the mail item can remain stuck in
the spool until another email is sent which pushes the stuck item out of
the queue. So far I have not discovered what causes this blockage in the
queue to occur or disappear as sending another email while it pushes the
blockage out results in the new email being stuck in the queue.
What you may find useful is raising the log level on activemq - *without
restarting james*. Connect up jvisualvm/jconsole to dynamically reload
the log4j config for activemq. MBean of interest -
org.apache.activemq.james.Broker, Operation reloadLog4jProperties.
When a blockage is discovered changing the number of spool threads,
delivery threads etc seems to at times help. But this may just be
because you're stopping and restarting the server and not due to the
configuration change.
I am interested to hear how this goes for you as I'm in a similar
situation and the issues may well be related.
Thanks
Phillip
On 2/12/13 6:45 AM, Ajay Navgale wrote:
> Hi,
>
> We are using james 3.0 beta4.
> We have an issue while sending an email. There is always one outgoing mail
> left in spool and is delivered when any new outgoing mail is to be sent.
> Now previous mail gets delivered and this recent once sits in the spool.
> This is happening for Remote delivery.
>
> Can anyone throw some light on this.
>
> Thanks & Regards,
> Ajay
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org