Messages are remaining in my Outbox

Hello, last night I tried to set up my mail application, but now I tried to send an e-mail and I am getting the following message:
"This message could not be delivered and will remain in your Outbox until it can be delivered.
The sender address ******@yahoo.com was rejected by the server"
Does anybody know what I should do? Everything worked fine on my last computer but apple recently replaced it with this one; so, the software is a bit newer. Please somebody help me if you can. : ) Thanks so much!!
iBook G4 Mac OS X (10.4.3)

Hi David - great stuff. I got it working with your help
I connected my Mac to my modem directly and I could send emails of various sizes including 1 MB!
So I hooked my VoIP adapter back into the loop and sending failed again. I unplugged it again and hooked my router up and sending failed as well. I tried just the modem on its own and sending worked again. So I looked at all modem settings and noticed that the MTU size on the WAN port had changed from the default 1500 to 1458 bytes. I changed it back to 1500 - sending still working - even up to 10 MB! I wired my VoIP adapter and I could still send small to very large email. Finally I had all 3 devices (modem, VoIP, router) connected and everything is working fine from Mail and Thunderbird I could even switch my modem network configuration back on an move it above the Ethernet connection and sending is still working.
Thanks for your help.
Cheers
Michael

Similar Messages

Outbound messages are being sent to Outbox

In the last couple of days Mail is sending any outbound message to the Outbox. When it does this I get the following: Cannot send mail. A copy has been placed in your Outbox? The recipient (lists email address) was rejected by the server. There is an OK tap at the bottom.
I am on a different Wi-Fi network than at home. I have not had problems like this on the home Wi-Fi network.
Retiredmac

This could be a situation with the Wi-Fi network you are connecting to when you get the message. Or it might be something in your iPad.
Reboot your iPad. Press and hold the Home and Sleep buttons simultaneously ignoring the red slider until the Apple logo appears. Let go of the buttons and let the iPad restart. See if that fixes your problem. If not then I suspect something in the particular Wi-Fi network.

HT1277 my messages are stuck in my outbox and wont go out

I dont get any dialogue error box, just the icon that its working on it but messages won´t go out.
Hope someone can help.
THANKS

Select Window ▹ Connection Doctor from the Mail menu bar. You should see a green dot next to each of the mail servers you've defined. Is that what you see? If not, click the Show Details button. A drawer opens at the bottom of the window. If there's text in that drawer, please post it. If not, click Check Again and post the text that appears. Edit out any personal information before posting.

Gmail sent messages are being continously moved to Outbox in OS X mail.

Gmail sent messages are being moved to Outbox in OS X mail. You can not be sure whether they have been sent or going to be sent anyway. No network problems or SMTP problems exist, a variety of IOS and Windows equipment uses gmail without glitches.(OS X 10.9.2)

This stopped happening as mysteriously as it started for me. The only change made on my end is that I added some seemingly unrelated filter Rules - around the same time (i can't be entirely certain if it stopped before or after the Rule changes) the proble with sent messages being marked as unread stopped. I doubt that the Rules actually had a direct effect, though perhaps it altered the structure of memory enough to stop the bug from occurring (something which I've seen many times in my 40 years of programming).

How to remove a message area

Hello,
I am using the following code to display error message. That works perfectly fine.
The only problem I have is once there is no error message the message area remains
at the top of the window and the the focus is always automatically set to the message area.
Is there a way to remove/reset the message handler?
I tried    lr_message_manager->clear_messages( INCLUDING_PERMANENT_MSG = abap_true )
but this didn't help.
Thanks and regards,
Christoph
get message manager
lr_current_controller ?= wd_this->wd_get_api( ).
lr_message_manager = lr_current_controller->get_message_manager( ).
if lt_messages is initial.
   lr_message_manager->clear_messages( INCLUDING_PERMANENT_MSG = abap_true ).
else.
LOOP AT lt_messages INTO lr_message.
report message
    CALL METHOD lr_message_manager->report_t100_message
      EXPORTING
        view = 'FOUNDATION'
        msgid = lr_message->mv_msgid
        msgno = lr_message->mv_msgno
        msgty = lr_message->mv_msgty
        p1    = lr_message->mv_msgv1
        p2    = lr_message->mv_msgv2
        p3    = lr_message->mv_msgv3
        p4    = lr_message->mv_msgv4.
ENDLOOP.
endif.

Hi Lekha,
I tried your approach and its not working.
I also tried to do this dynamically in WDDOMODIFYVIEW:
    data:   lr_message_area       TYPE REF TO CL_WD_MESSAGE_AREA.
    lr_message_area ?= view->get_element( id = 'MESSAGES' ).
    lr_message_area->set_visible( '01' ).   " 01 is invisible 02 is visible
but nothing works
The message area remains showing 'No Messages' and the only way to get rid of it is to click on the show list button and reset the log.
When I do create a test application the message areas works fine but in the whole application it remains. I have no idea what's causing this.
What I do in the application is basically the following.
The business object has its own message handler and in the WDDOMODIFYVIEW of the view containing the message area I read this message handler and if there are messages I do the following:
get message manager
lr_current_controller ?= wd_this->wd_get_api( ).
lr_message_manager = lr_current_controller->get_message_manager( ).
lt_messages gets filled from the business object
LOOP AT lt_messages INTO lr_message.
report message
      CALL METHOD lr_message_manager->report_t100_message
        EXPORTING
          msgid = lr_message->mv_msgid
          msgno = lr_message->mv_msgno
          msgty = lr_message->mv_msgty
          p1    = lr_message->mv_msgv1
          p2    = lr_message->mv_msgv2
          p3    = lr_message->mv_msgv3
          p4    = lr_message->mv_msgv4.
    ENDLOOP.
If there are no messages in lt_messages I just want to get rid of the message area.

TS3276 my emails are stuck in the outbox. how do i fix this?

I need help with me email. My messages are stuck in the outbox.

Please describe in detail what happened when you took all the applicable steps in the support article. That's the starting point for any further efforts to solve the problem.

In Business workflow outbox 2 days messages are missed

Hi All
In Business workflow outbox 2 days messages are missed, i.e in the entire January 12th and 13th dates only
what might the problem and how to solve this please help me
Thanks in advance
Jaya Naidu

First, have him go to Mail>Preferences>Accounts
Then have him locate his account and your account on the left.
Have him click and drag the .mac account below his account in the list.
This will solve the default setting of mail going out from your account when he clicks on the Inbox.
Removing the smtp server for .mac may not even work for him, especially if the account is active.
Instead click on "advanced" and there should be a check box for "enable this account", deselect the box. This disables the account without deleting any mail.

MDB cannot loads enitities if more than 10 concurrent messages are sent tog

Hello,
I have seen a weird behavior of the MDB in Jboss or perhaps in transaction management.
Here is a my scenario
I have a session bean sb, an entity bean e and a message driven bean mb
When a request comes to sb , it persists a new entity e and send a message (primary key) to mb
mb then loads e from the database using one of the findByXX method and does something else.
If 10 concurrent request comes to sb, 10 different entities are persisted and 10 different messages are sent to mb
mb are able to load 10 different e from the database
Everything works fine as long as there are 10 concurrent request. If there are 13 concurrent request, then one or two mb
cannot load e from the database. It seems that the session bean has persisted the entities but some of them are still unload able from mb. They have been persisted , (I saw in the logs), but mb cannot load them.
Initially I thought that a transaction mishap might be happening, so instead of persisting the entity and sending the message in one method in sb , I separated these two tasks in two methods a and b, in which both a and b uses RequiresNew transaction attribute. But the problem still remains. Please note if the number of parallel request are less than 10 then everything works fine. Is there something I am missing or is Jboss doing something buggy?
The above situation is reproducible .
Here is some more information about the problem along with some code snapshots. Note that the code is trimmed for clarity purposes.
Request is a simple entity (e as mentioned in the problem before) that is persisted in session bean . Here is a trimmed snapshot
Request.java
package gov.fnal.ms.dm.entity;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
@Entity
@NamedQueries({@NamedQuery(name = "Request.findById", query = "SELECT r FROM Request r WHERE r.id = :id"),
@NamedQuery(name = "Request.findAll", query = "SELECT r FROM Request r"),
@Table(name = "cms_dbs_migration.Request")
@SequenceGenerator(name="seq", sequenceName="cms_dbs_migration.SEQ_REQUEST")
public class Request implements Serializable {
private String detail;
@Id
@GeneratedValue(strategy = GenerationType.AUTO, generator="seq")
@Column(nullable = false)
private Long id;
private String notify;
.....The session bean is MSSessionEJBBean.
MSSessionEJBBean.java
@Stateless(name="MSSessionEJB")
@WebService(endpointInterface = "gov.fnal.ms.dm.session.MSSessionEJBWS")
public class MSSessionEJBBean implements MSSessionEJB, MSSessionEJBLocal, MSSessionEJBWS {
@PersistenceContext(unitName="dm")
private EntityManager em;
.......    The methods that is called concurrently in this bean is
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequest(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
Request r = addRequestUnit(srcUrl, dstUrl, path, dn, withParents, withForce, notify);
if (r != null) sendToQueue(r.getId());
return r;
}    It first adds the request entity and then sends a message to the queue in separate methods each using TransactionAttributeType.REQUIRES_NEW (I don't think this TransactionAttributeType is needed . I was just playing to see if this resolves the problem)
Here is the method that actually persist the entity
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequestUnit(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
....// Does something before persisting
Request r = new Request();
r.setNotify(notify);
r.setPath(path);
r.setPerson(p);
r.setWithForce(withForce);
r.setWithParents(withParents);
r.setProgress(new Integer(0));
r.setStatus("Queued");
r.setDetail("Waiting to be Picked up");
em.persist(r);
System.out.println("Request Entity persisted");
System.out.println("ID is " + r.getId());
return r;
}I can see that the log files has messages
*{color:#800000}"Request Entity persisted" "ID is " 12 (or some other number){color}*
. So it is safe to assume that the request entity is persisted properly before the message is sent to the queue. Here is how the message is sent to the queue
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
private void sendToQueue(long rId) throws Exception {
QueueSession session = null;
QueueConnection conn = null;
try {
conn = factory.createQueueConnection();
session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
MapMessage mapMsg = session.createMapMessage();
mapMsg.setLong("request", rId);
session.createSender(queueRequest).send(mapMsg);
} finally {
if (session != null) session.close();
if(conn != null) try {
conn.close();
}catch(Exception e) {e.printStackTrace();}
System.out.println("Message sent to queue");
}I can see the message
{color:#800000}*"Message sent to queue"*{color}
in the log file right after I see the
*{color:#800000}
"Request Entity persisted"{color}*
message. So it correct to assume that the message is infact sent to the queue.
Here is the md bean that gets the message from the queue and process it
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/requestmdb")
public class RequestMessageDrivenBean implements MessageListener {
@EJB
private MSSessionEJBLocal ejbObj;
public void onMessage(Message message) {
try{
System.out.println("Message recived ");
if(message instanceof MapMessage) {
System.out.println("This is a instance of MapMessage");
MapMessage mMsg = (MapMessage) message;
long rId = mMsg.getLong("request");
List<Request> rList = ejbObj.getRequestById(new Long(rId));
System.out.println("rList size is " + rList.size());
for(Request r: rList) {
//Does something and print something in logs
System.out.println("Finsihed onMessage");
}catch(Exception e) {
System.out.println(e.getMessage());
}    One thing to note here is that getRequestById is another method in the same session bean MSSessionEJB. Can that be the reason for not loading the request from the database when many concurrent request are present? Here is what it does
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public List<Request> getRequestById(Long id) throws Exception {
System.out.println("Inside getRequestById id is " + id);
return em.createNamedQuery("Request.findById")
.setParameter("id", id)
.getResultList();
}    In the logs I do see
{color:#800000}*"This is a instance of MapMessage"*{color}
and I do see the correct Rid that was persisted before in the log
*{color:#800000}
"inside getRequestById id is 12"{color}*
. Finally I do see
*{color:#800000}
"Finsihed onMessage"{color}*
for all the request no matter how many are sent concurrently.
*{color:#ff0000}Here is where the problem is . rList size is 1 for most of the cases but it returns 0 when the number of concurrent message exceeds 10.*
*{color}*
So you see there is no exception per se, just that entity does not get loaded from the database. I would like to mention this again, it does work properly when the number of concurrent request are less than 10. All the invocation of onMessage in MB are able to load the entity properly in that case. Its only when the number of concurrent request increases more than 10, the onMessage is unable to load the entity and the rList is 0.
FYI I am using jboss-4.2.2.GA on RedHat enterprise linux 4 with jdk1.6.0_04
Please let me know if there is more information required on this.
Thank you

Hello,
I have seen a weird behavior of the MDB in Jboss or perhaps in transaction management.
Here is a my scenario
I have a session bean sb, an entity bean e and a message driven bean mb
When a request comes to sb , it persists a new entity e and send a message (primary key) to mb
mb then loads e from the database using one of the findByXX method and does something else.
If 10 concurrent request comes to sb, 10 different entities are persisted and 10 different messages are sent to mb
mb are able to load 10 different e from the database
Everything works fine as long as there are 10 concurrent request. If there are 13 concurrent request, then one or two mb
cannot load e from the database. It seems that the session bean has persisted the entities but some of them are still unload able from mb. They have been persisted , (I saw in the logs), but mb cannot load them.
Initially I thought that a transaction mishap might be happening, so instead of persisting the entity and sending the message in one method in sb , I separated these two tasks in two methods a and b, in which both a and b uses RequiresNew transaction attribute. But the problem still remains. Please note if the number of parallel request are less than 10 then everything works fine. Is there something I am missing or is Jboss doing something buggy?
The above situation is reproducible .
Here is some more information about the problem along with some code snapshots. Note that the code is trimmed for clarity purposes.
Request is a simple entity (e as mentioned in the problem before) that is persisted in session bean . Here is a trimmed snapshot
Request.java
package gov.fnal.ms.dm.entity;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
@Entity
@NamedQueries({@NamedQuery(name = "Request.findById", query = "SELECT r FROM Request r WHERE r.id = :id"),
@NamedQuery(name = "Request.findAll", query = "SELECT r FROM Request r"),
@Table(name = "cms_dbs_migration.Request")
@SequenceGenerator(name="seq", sequenceName="cms_dbs_migration.SEQ_REQUEST")
public class Request implements Serializable {
private String detail;
@Id
@GeneratedValue(strategy = GenerationType.AUTO, generator="seq")
@Column(nullable = false)
private Long id;
private String notify;
.....The session bean is MSSessionEJBBean.
MSSessionEJBBean.java
@Stateless(name="MSSessionEJB")
@WebService(endpointInterface = "gov.fnal.ms.dm.session.MSSessionEJBWS")
public class MSSessionEJBBean implements MSSessionEJB, MSSessionEJBLocal, MSSessionEJBWS {
@PersistenceContext(unitName="dm")
private EntityManager em;
.......    The methods that is called concurrently in this bean is
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequest(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
Request r = addRequestUnit(srcUrl, dstUrl, path, dn, withParents, withForce, notify);
if (r != null) sendToQueue(r.getId());
return r;
}    It first adds the request entity and then sends a message to the queue in separate methods each using TransactionAttributeType.REQUIRES_NEW (I don't think this TransactionAttributeType is needed . I was just playing to see if this resolves the problem)
Here is the method that actually persist the entity
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public Request addRequestUnit(String srcUrl, String dstUrl, String path,
String dn, String withParents, String withForce, String notify) throws
Exception {
....// Does something before persisting
Request r = new Request();
r.setNotify(notify);
r.setPath(path);
r.setPerson(p);
r.setWithForce(withForce);
r.setWithParents(withParents);
r.setProgress(new Integer(0));
r.setStatus("Queued");
r.setDetail("Waiting to be Picked up");
em.persist(r);
System.out.println("Request Entity persisted");
System.out.println("ID is " + r.getId());
return r;
}I can see that the log files has messages
*{color:#800000}"Request Entity persisted" "ID is " 12 (or some other number){color}*
. So it is safe to assume that the request entity is persisted properly before the message is sent to the queue. Here is how the message is sent to the queue
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
private void sendToQueue(long rId) throws Exception {
QueueSession session = null;
QueueConnection conn = null;
try {
conn = factory.createQueueConnection();
session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
MapMessage mapMsg = session.createMapMessage();
mapMsg.setLong("request", rId);
session.createSender(queueRequest).send(mapMsg);
} finally {
if (session != null) session.close();
if(conn != null) try {
conn.close();
}catch(Exception e) {e.printStackTrace();}
System.out.println("Message sent to queue");
}I can see the message
{color:#800000}*"Message sent to queue"*{color}
in the log file right after I see the
*{color:#800000}
"Request Entity persisted"{color}*
message. So it correct to assume that the message is infact sent to the queue.
Here is the md bean that gets the message from the queue and process it
@MessageDriven(activationConfig =
@ActivationConfigProperty(propertyName="destinationType",
propertyValue="javax.jms.Queue"),
@ActivationConfigProperty(propertyName="destination",
propertyValue="queue/requestmdb")
public class RequestMessageDrivenBean implements MessageListener {
@EJB
private MSSessionEJBLocal ejbObj;
public void onMessage(Message message) {
try{
System.out.println("Message recived ");
if(message instanceof MapMessage) {
System.out.println("This is a instance of MapMessage");
MapMessage mMsg = (MapMessage) message;
long rId = mMsg.getLong("request");
List<Request> rList = ejbObj.getRequestById(new Long(rId));
System.out.println("rList size is " + rList.size());
for(Request r: rList) {
//Does something and print something in logs
System.out.println("Finsihed onMessage");
}catch(Exception e) {
System.out.println(e.getMessage());
}    One thing to note here is that getRequestById is another method in the same session bean MSSessionEJB. Can that be the reason for not loading the request from the database when many concurrent request are present? Here is what it does
@TransactionAttribute(TransactionAttributeType.REQUIRES_NEW)
public List<Request> getRequestById(Long id) throws Exception {
System.out.println("Inside getRequestById id is " + id);
return em.createNamedQuery("Request.findById")
.setParameter("id", id)
.getResultList();
}    In the logs I do see
{color:#800000}*"This is a instance of MapMessage"*{color}
and I do see the correct Rid that was persisted before in the log
*{color:#800000}
"inside getRequestById id is 12"{color}*
. Finally I do see
*{color:#800000}
"Finsihed onMessage"{color}*
for all the request no matter how many are sent concurrently.
*{color:#ff0000}Here is where the problem is . rList size is 1 for most of the cases but it returns 0 when the number of concurrent message exceeds 10.*
*{color}*
So you see there is no exception per se, just that entity does not get loaded from the database. I would like to mention this again, it does work properly when the number of concurrent request are less than 10. All the invocation of onMessage in MB are able to load the entity properly in that case. Its only when the number of concurrent request increases more than 10, the onMessage is unable to load the entity and the rList is 0.
FYI I am using jboss-4.2.2.GA on RedHat enterprise linux 4 with jdk1.6.0_04
Please let me know if there is more information required on this.
Thank you

Messages are Holding in message monitoring tool

Hi All,
I am facing the problem with messages which are in holding state.
My scenario is file to proxy. The file content contains of EDI. my scenario is already gone to production last year.
and its working fine. Used java mappings for validation of EDI file. its running successfully.
where as in Dev system till october first i used to load the files in FTP inbox folder and messages were processed successfully.
But from october first week when i load the files in FTP inbox, file has been picking succesfully and can see the logs in sender comm channel but the i can see that my interface is in holding state in message monitoring tool and its not going to receiver comm channel. I have loaded 5 files and all are in holding state.
even i have cancelled first error message and tried to resend the next message swhich is in holding state, but this is not happening.
i am using EOIO queue.
when i cancel the error message remaining messages should processed automatically but its not getting processed here.
sequencing of the interface triggering is
1. Interface_1
2. Interface_2
3. Interface_3
4. Interface_4
Here i am stucking up with the first interface itself.Here only first interface is in holding state.
can any one advise what could be the problem..
I m on SP 10.
Thanks,
Bhaskar

Hi Abhijit,
Even after unchecking the checkbox maintain order at runtime, its not working.
i think there is no disturbed in message processing sequence.
my first sender interface itself going into hold state.
i have cancelled the hold message, even after that remaining messages are processing automatically.
and also i could not fine any messages in SMQ1 and SMQ2.
I also deresister and registered te queues and activated.
Kindly advise what would be the problem..
in production its working fine and development its not working fine.
Thanks,
Bhaskar

Not all messages are delivered to Mail

It's so frustrating! My web-based version of my POP account receives messages that Mail doesn't. It has nothing to do with junk filters or rules; the mail just never arrives. There's no particular domain after the '@' that doesn't arrive, although I first noticed it when someone with a gmail account tried to email me. Furthermore, I sent an email with my own gmail account to my pop account in question and it never arrived in Mail! Is something corrupted in my Mail app?
I'd really appreciate your feedback on this.
adrian

Try the following.
Quit Mail first and using the Finder, go to Home > Library > Mail > this account named folder (named by the user name and incoming mail server for the account) > MessageUidsAlreadyDownloaded.
Delete the MessageUidsAlreadyDownloaded file and empty the Trash.
Launch Mail and if successful, any previously downloaded messages that remain on the server will be downloaded again in addition to all messages available not yet downloaded by Mail.
If not successful and although I haven't experienced the same, it has been reported by others here that certain spam messages or legit messages than contain unusual formatted HTML sometimes "clog" the receipt of all messages available at the incoming mail server. Look for and delete all spam messages that are available at the incoming mail server for the account via webmail access.

Messages are no longer sent

I've suddenly got this problem where messages are not sent - they just go to my Outbox and stay there. Mail then says that these will be sent later, but they never go.
I've not altered any settings and I can sent mail from another computer, so It's not my router or ISP.
Any ideas?

Kevin,
This is sounding like an issue with MTU (maximum transmission unit), and could require setting to new, lower values in the Mac and PC. Because the laptop is wireless it does not come into play. Another thing to check, is whether there are any Firmware updates needed for you Dlink router. While bad cables from the router to the computer could also impact this, since you have two computers cabled to the router it is unlikely that both are bad.
The ability to send without attachments, but not with attachments is often MTU; however, if not using the SMTP of you ISP, then bad relaying from another SMTP can look like this.
See the KB article linked below for how to change on the Mac (and test with values lower than 1500 for MTU -- start with 1492, and decrement by a 100 for testing:
http://docs.info.apple.com/article.html?artnum=107962
The articles linked below speak of MTU, and Dlink routers, and may be helpful:
http://www.dslreports.com/faq/7121
and
http://support.dlink.com/faq/view.asp?prod_id=997&question=General-Routers
All the best, and keep us posted.
Ernie

Text Messages are automatically getting deleted

Hi,
Am using BB curve 9300 3G, and OS 6.0...
Around 2 months back, i was having issue with my BB so sent it to service center.... When it came back, the OS was upgraded to 6.0 from 5.0...all is fine except now the text messages are getting deleted after few days...what remains is the name of the sender in green with no message in it...
Even in settings, I have kept "forever" in the tab "Days to keep messages"
Looking forward for a reply...
with regards
Abhik Das
with regards
simply abhik...
Please click "Accept as Solution" if your issue has been solved and to give thanks/appreciation, click thumbs up...
For BB OS update: http://us.blackberry.com/software/smartphones/update.html
BB Simulators: http://us.blackberry.com/sites/developers/resources/simulators.html

Hi,
In my case,there is no such apps installed and in my device memory,there's 30+ mb left unused,hence memory wnt be the root cause for my case either...
Strange is tht,today is 13th of june n when I woke up, I saw the text messages of 5th june got deleted...so,only 8 days old messages r there in my BB...thts really annoying...!!!
Regards
Abhik
with regards
simply abhik...
Please click "Accept as Solution" if your issue has been solved and to give thanks/appreciation, click thumbs up...
For BB OS update: http://us.blackberry.com/software/smartphones/update.html
BB Simulators: http://us.blackberry.com/sites/developers/resources/simulators.html

Unsent message do not show in outbox

when the sending progress bar is on and the messages are nto going out , there is no outbox to check whcih ones are pending .
Message was edited by: [email protected]

Did you accidentally Hide them? So they don't show in the event - look for option to un-hide photos
I know its there just don't want to open Iphoto while I am on-line as it persists in connecting to apple and I only use it off-line.

Ensuring messages are being persisted.

I'm running IMQ 3.5 SP1 with Java 1.4.2_02 on RedHat Linux.
I have set imq.persist.file.sync.enabled=true in /opt/imq/lib/props/broker/default.properties, but I have noticed that performance improves when there my durable subscribers are not connected to their topics.
So my question is: how can I verify that message persistance is enabled? It's not mentioned when querying the broker.
Thanks, Zac.

This seems strange to me; if steps aren't taken
(routing and acking) when a durable subscriber is
inactive until it becomes active again, why
can't these steps be taken by a different thread
outside of the publishing process? That it takes
longer when all parts of the system are active seems
less-than-ideal.They are handled by different threads but work still needs
to be performed by the JVM. My point is an active durable
subscriber requires the broker to do more work than if the
durable was inactive. Threads help manage that work but
it doesn't make the cost of performing that work go to zero.
>
[testing if the messages are being persisted]If my durable subscribers are active - the condition
I'm interested in - then won't the messages have been
delivered to the subscribers already? There would be
no persisted messages remaining after stopping the
broker .If your durable subscriber has acknowledged the message
then the broker will not longer be maintaining the persistent
copy.
Here's one way to test persistence:
1) Start your durable subscriber (it subsribes to a topic)
2) Kill your durable subscriber (the subscription remains,
the broker see it as an inactive durable sub)
3) Send some persistent messages to the topic the durable is
subscribed to.
4) Restart the broker.
5) Restart your durable subscriber. If the messages were persisted
they would be delivered to the durable sub. If they weren't then
they were lost when the broker was restarted.
Chris

Help! The network@etp messages are not automatically deleting in outlook

My redirector was working fine and all of a sudden the network@etp messages are not automatically deleting from my inbox. I am still receiving my emails on my blackberry but these network messages are cluttering my inbox in outlook. When I shut down the redirector and restart it the network messages that were in my inbox are deleted but then when a new message comes in the new network message for that emails remains in outlook. Does anyone know how to fix this?

Hi Vinod,
You issue might be related to this:
"By default, the out-of-office reply to Internet recipients (external senders) is turned off. Many administrators do not allow out-of-office replies to be sent outside the Exchange Server organization, so that unauthorized people do not
know when users are out of the office. "
You might want to follow the steps in below KB article to turn on out-of-office replies to the Internet or contact your administrator to check so:
http://support.microsoft.com/kb/323665/en-us
Hope it helps and feel free to post back.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Messages are remaining in my Outbox

Similar Messages

Maybe you are looking for