Lumia message delivery messages

Hello
In the messaging settings, I put on the delivery notifications.
Now it sends me a message every time I send a message with the words that the message I sent is delivered. Isn't that something we used to have TEN years ago???
It should just "notify" us that a message is or isn't delivered, not really sending us a big old "delivery message"?
My suggestion would be to give delivered messages a green border, pending messages an orange one and failed messages a red one. Or something like that.
Your opinions?

What's more worrying is that no1 find this feature necessary.
I turn off delivery reports for the first time after like 10 years! Only because its annoying to receive a "delivery text"

Similar Messages

Text message DELIVERY

I had a Samsung Smooth and when I sent a test message that phone would show when the text message was received by the phone sent to.
I just upgraded to the LG Cosmos and when I send a text message the information shows when sent but not when received by the number sent to.
Is there a way to set the phone to show when the message is received?

GO TO MENU, MESSAGING, NEW MESSAGE, SETTINGS (WHICH IS THE LEFT SOFT KEY), AND THEN CHOOSE DELIVERY RECEIPT

When I send e-mail messages with file by using a POP3 in Exchange 2010 I received delivered message with file. How I can disable this functions that file do not include to delivery message. I use Exchange 2010 only local users.

When I send e-mail messages with file by using a POP3 in Exchange 2010 I received delivered message with file. How I can disable this functions that file do not include to delivery message. I use Exchange 2010 only local users.

I think there is not native rule for this, but you could try a transport rule which removes all attachments over a very small file size like 1KB.
http://blogs.technet.com/b/exchange/archive/2009/05/11/3407435.aspx
CRM Advisor

Change the SMTP 550 non delivery message

Hi,
I want to change the texte of the non delivery report (SMTP code 550) send by the email appliance.
What is the simple way to do that ?
Moreover, i would like to know how long the applicance will keep the message in queue in case of my internal email server will be out of order ?
Where can i see/change this setting ?
Thanks.

You can set the 550 from the appliance, Mail Policies > Mail Flow Policies > Choose Policy Name. From there, see the DHAP section:
To answer the second part of your question...
By default, mail is queued for 72 hours (259200 seconds) OR 100 retry attempts before it bounces to the original sender.
This setting is configurable from the command line (CLI): type bounceconfig and edit the default settings. Also, you can modify this from the GUI interface by going to "Network > Bounce Profiles" and click on the Default profile.
Also, the queue could fill up if there is too much mail. However, if the system reaches its storage limit, it will soft bounce further attempts by other mail servers to deliver more messages. This ensures that no messages will get lost, as these mail servers will reattempt message delivery as well until the ESA accepts messages again.
Note: If you plan to shut down your internal mail server for maintenance for a longer period (more than a couple hours), best practice is to suspend the incoming listeners on your ESA as well (suspendlisteners). As mentioned before, in this case any connection attempts will be soft bounced, and retried later. This way, you leave the task of storing the messages to the sending mail server, which will prevent the mail queue on your email appliances filling up quickly. No messages will be lost however, once you got your internal mail server back into service, also resume the listeners on your ESA (resume), to allow delivery from remote hosts again.
I hope this helps!
-Robert
(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)

JMS Provider Responsibilities For Concurrent Message Delivery

Hi,
(This question pertains to the JMS api, outside a j2ee container)
Is it JMS-provider dependent on how concurrent message delivery is implemented? In other words, the code below sets up multiple consumers (on a topic), each with their own unique session and MessageListener and then a separate producer (with its own session) sends a message to the topic and I observer that only (4) onMessage() calls can execute concurrently. When one onMessage() method exits, that same thread gets assigned to execute another onMessage().
The only thing I could find on the matter in the spec was section in 4.4.15 Concurrent Message Delivery and it's pretty vague.
It's really important because of the acknowledgment mode. If it turns out that I need to delegate the real work that would be done in the onMessage() to another thread that I must manage (create, pool, etc), then once the onMessage() method completes (i.e., after it does the delegation to another thread), the message is deemed successfully consumed and will not be re-delivered again (and that's a problem if the custom thread fails for any reason). Of course, this assumes I'm using AUTO_ACKNOWLEDGE as the acknowledgment mode (which seems to make sense since using CLIENT_ACKNOWLEDGE mode will automatically acknowledge the receipt of all messages that have been consumed by the corresponding session and that's not good).
My JMS Provider is WL 9.1 and the trival sample code I'm using as my test follows below. I also show the ouput from running the example.
thanks for any help or suggestions,
mike
--- begin TopicExample.java ---
import java.io.*;
import java.util.*;
import javax.naming.*;
import javax.jms.*;
import javax.rmi.PortableRemoteObject;
class TopicExample {
public final static String JMS_PROVIDER_URL = "t3://localhost:8001";
public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
public final static String JMS_FACTORY="CConFac";
public final static String TOPIC="CTopic";
public final static int NUM_CONSUMERS = 10;
public static void main(String[] args) throws Exception {
InitialContext ctx = getInitialContext(JMS_PROVIDER_URL);
ConnectionFactory jmsFactory;
Connection jmsConnection;
Session jmsReaderSession[] = new Session[10];
Session jmsWriterSession;
TextMessage jmsMessage;
Destination jmsDestination;
MessageProducer jmsProducer;
MessageConsumer jmsConsumer[] = new MessageConsumer[10];
MessageListener ml;
try
// Create connection
jmsFactory = (ConnectionFactory)
PortableRemoteObject.narrow(ctx.lookup(JMS_FACTORY), ConnectionFactory.class);
jmsConnection = jmsFactory.createConnection();
// Obtain topic
jmsDestination = (Destination) PortableRemoteObject.narrow(ctx.lookup(TOPIC), Destination.class);
// Reader session and consumer
for (int i=0; i<NUM_CONSUMERS; i++)
jmsReaderSession[i] = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
jmsConsumer[i] = jmsReaderSession.createConsumer(jmsDestination);
jmsConsumer[i].setMessageListener(
new MessageListener()
public void onMessage(Message msg) {
try {
String msgText;
if (msg instanceof TextMessage) {
msgText = ((TextMessage)msg).getText();
} else {
msgText = msg.toString();
System.out.println("JMS Message Received: "+ msgText );
System.out.println("press <return> to exit onMessage");
char c = getChar();
System.out.println("Exiting onMessage");
} catch (JMSException jmse) {
System.err.println("An exception occurred: "+jmse.getMessage());
// Writer session and producer
jmsWriterSession = jmsConnection.createSession(false, Session.AUTO_ACKNOWLEDGE);
jmsProducer = jmsWriterSession.createProducer(jmsDestination);
jmsMessage = jmsWriterSession.createTextMessage();
jmsMessage.setText("Hello World from Java!");
jmsConnection.start();
jmsProducer.send(jmsMessage);
char c = '\u0000';
while (!((c == 'q') || (c == 'Q'))) {
System.out.println("type q then <return> to exit main");
c = getChar();
for (int i=0; i<NUM_CONSUMERS; i++)
jmsReaderSession[i].close();
jmsWriterSession.close();
jmsConnection.close();
System.out.println("INFO: Completed normally");
} finally {
protected static InitialContext getInitialContext(String url)
throws NamingException
Hashtable<String,String> env = new Hashtable<String,String>();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, url);
return new InitialContext(env);
static public char getChar()
char ch = '\u0000';
try {
ch = (char) System.in.read();
System.out.flush();
} catch (IOException i) {
return ch;
--- end code --
Running the example:
prompt>java TopicExample
JMS Message Received: Hello World from Java!
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
press <return> to exit onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
type q then <return> to exit main
[you see, only 4 onMessage() calls execute concurrently. Now I press <return>]
Exiting onMessage
JMS Message Received: Hello World from Java!
press <return> to exit onMessage
[now once the thread executing the onMessage() completes, the JMS providor assigns it to execute another onMessage() until all 10 onMessage() exections complete).

I am too facing the same issue. but in my case I start getting this problem when the message size is about 1 MB itself.
Any help is appraciated.
Regards,
ved

Message Delivery Restrictions failed in Exchange 2010

Hi everyone
For a customer, I wanted to restrict the use of a distribution group so that only a few selected people can send to the list. When I tried adding these users under Mail Flow Settings -> Message Delivery Restrictions, it gave me the following error:
Microsoft Exchange Error
The following error(s) occurred while saving changes:
Set-DistributionGroup
Failed
Error:
Couldn't find object "<domain>/Users/Administrator". Please make sure that it was spelled correctly or specify a different object. Reason: The recipient <domain>/Users/Administrator isn't the expected type.
OK
I know of the problem when a user is disabled, but never have seen this one before. The administrator account is active and in use (I logged in with the administrator account to add the users).
Anyone who knows what to do?
Thanks!

That's what the error is saying - the administrator account has no mailbox, and I suspect that the EMC expects the account you are placing in that area to have one.
It's not the administrator that I want to add to the list, but the users of the board. But I'll try to create a mailbox for the administrator, for the sake of science :)
Unfortunately not, that's what I thought at first too, but I double checked and no mailbox for the administrator can be found.
Was the administrator account mail-enabled in the past however? I wonder if it was set as delegate or had send on behalf rights for one of the users you are trying to add and its ghost entry is still there.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.
Any way how I can check this? As for as I know, the administrator account never had "send on behalf rights", but of course I don't know what they've been doing in all the time since I left.

Stop all Message delivery until start-up class executes

          On fail-over, I need to be able to keep any messages from topics/queues from being
          sent to the destinations until a start-up class has been executed and initialized
          the application. The problem is that the mdb's get deployed prior to the start-up
          class and immediately receive messages. This causes problems since the mdb's
          rely on the start-up class executing prior to onMessage().
          Is there a way to disable message delivery on start-up, prior to the deployment
          of the mdb's? I have implemented a temporary solution of checking to see if the
          start-up class has been bootstrapped, and if no, do a thread sleep for a specified
          time period and repeat...


I had the same issue. We wrote a startup class that spawns a new thread to
          make a JMX call to see if the server is up. Once the server is up, the
          thread would deploy the MDB using JMX.
          Adarsh
          Looks like you came up with a good workaround.
          "Josh Zook" <[email protected]> wrote in message
          news:3cbd9fff$[email protected]..
          >
          > On fail-over, I need to be able to keep any messages from topics/queues
          from being
          > sent to the destinations until a start-up class has been executed and
          initialized
          > the application. The problem is that the mdb's get deployed prior to the
          start-up
          > class and immediately receive messages. This causes problems since the
          mdb's
          > rely on the start-up class executing prior to onMessage().
          >
          > Is there a way to disable message delivery on start-up, prior to the
          deployment
          > of the mdb's? I have implemented a temporary solution of checking to see
          if the
          > start-up class has been bootstrapped, and if no, do a thread sleep for a
          specified
          > time period and repeat...

Guarranteed Message Delivery with OSB 11g

Hi,
I'm currently working on a scenario with OSB that requires me to set up guaranteed message delivery. The business scenario is that on one end I have a flat file polling service and I have to transform this data into XML and store it to DB. Concisely, this is the scenario: Flat File -> Proxy -> Business -> JMS Queue -> Proxy -> Business -> DB. The entire process works fine till the time I turn the DB off. In that case, I get a load of erro in the log, and the message in the Queue sits there indefinitely, Even after the DB has been restarted. The only way the message gets stored into DB is by performing a complete server restart, which, needless to say is not acceptable. Stopping and starting the proxy and business services do not work, either.
I'm using an XA data source for the DB connection pool and the default XA Connection Factory for OSB JMS transport. After delivery failure the message sits in the queue with "receiving transaction" state string. On inspection of the server logs I found that WebLogic can't connect with the datasource even when the database is completely restarted. It requires a server restart for the connection pool to work properly again.
Could anybody please provide some insight as to what I'm doing wrong?

Jms:///CF/QName works when we OSB clusterOSB JMS transport is implemented as Weblogic MDB's under the hood. From weblogic 9x onwards , mdbs bind to co-hosted destinations by default.
So if you have a distributed destination and mdb's are deployed to the same cluster ( happens when jms proxy service is deployed to the cluster) , then it is guaranteed behaviour that the mdb on ms1 binds to dd member on ms1 and mdb on ms2 binds to dd member on ms2. So you will end up seeing 16 consumers ( by default, if you have not configured any work manager to restrict concurrent threads) on each of the dd member.
we have both BPEL and OSB cluster so when BPEL posting a message how to avoid the racing condition in OSB . as both will look for same QUEUE..Make sure the connection factory used by bpel has load balancing turned on and server affinity turned off. This will ensure a pretty load balanced distribution of the messages to the dd members in the cluster which will be then processed by the proxy service hosted on the same managed server instance.

Dynamic Distribution Groups - Message Delivery Restrict to Security Group

Hi,
I have created a dynamic distribution group and want to restrict mail delivery to only accept messages from members of a security group. How do I achieve this?
The idea is the DDG's are set with their criteria and if anyone leaves/joins the relevant SG then they will have permission to send to those DDG's.
Thanks in advance.

Hi ,
In exchange management console it is very simple to provide the access.Please follow steps.
1.Open the Exchange Management Console (EMC)
2.Locate the distribution list .
3.Right-click on it and select Properties
4.Open the Mail Flow Settings tab
4.Select Message Delivery Restrictions
5.Then select the option only senders in the following list and add the DL that you would like to provide access to send email to that group.
Thanks & Regards S.Nithyanandham

How to differ large message delivery

Hi,
I would like to differ large message delivery during night. For instance message size above 4 Mo be processed at midnight to avoid network saturation.
I could not find any answers in documentation. I have got an idea to retarget messages over 4Mo with alternatechannel keyword. But how to hold channel processing until the night ?
Thanks,

Sorry solution was in documentation, my question is how to "delay" a message delivery !
You can delay a big mail by retargetting messages in a special channel and then stop this channel until off-hours time.
Documentation 819-0105
In the following channel block example, large messages over 5,000 blocks, that
would have gone out the tcp_local channel to the Internet, instead go out the
tcp_big channel:
tcp_local smtp ... rest of keywords ... alternatechannel tcp_big
alternateblocklimit 5
tcp-daemon
tcp_big smtp ...rest of keywords...
tcp-big-daemon
Here are some examples of how the alternate* channel keywords can be used:
� If you want to deliver large messages at a delayed or an off-hours time, you can
control when the alternatechannel (for example, tcp_big) runs.
One method is to use the imsimta qm utility�s STOP channel_name and START
channel_name commands, executing these commands periodically via your own
custom periodic job that is run by the Job Controller or via a cron job.
Hope this could help someone.

How can I have message delivery for Iphone ios7.1

How can I have message delivery for Iphone ios7.1

There is no option in the mail application to request a read receipt - if that is what you are asking.

Want to get the failure delivery message

import java.util.Properties;
import javax.mail.*;
import javax.mail.internet.*;
import java.util.*;
public class ReplyExample {
     public static void main (String args[]) throws Exception {
String host = "127.0.0.1";
String from = "[email protected]";
String to = "[email protected]";
String reply = "[email protected]";
// Get system properties
Properties props = System.getProperties();
// Setup mail server
props.put("mail.smtp.host", host);
// Get session
Session session = Session.getInstance(props, null);
// Define message
MimeMessage message = new MimeMessage(session);
     message.setFrom(new InternetAddress(from));
     message.addRecipient(Message.RecipientType.TO,new InternetAddress(to));
     message.setReplyTo(new InternetAddress[]{new InternetAddress(reply)});
     message.setSubject("Hello JavaMail");
message.setText("Welcome to JavaMail");
// Send message
Transport.send(message);
Why i am not getting the failure delivery message?

If the above mentioned code is wrong then kindly let me know to the exact code.
Waiting for your quick responce.

Biztalk message delivery throtlling Reson -3 Unprocesssed message

Hi,
I have ran the MBV report and i see that throttling on one of the delivery throttling on one of the host
can you let me know what is the possible cause for this?

Hi Sujith,
Message delivery throttling for a particular host can because of many reasons.
It could be due to:
Imbalanced message delivery rate (input rate exceeds output rate)
High in-process message count
Process memory pressure
System memory pressure
High thread count
User override on delivery
Did you receive any other critical warnings other than the host throttling?
I would recommend you to run Perfmon and find the exact cause of Host throttling.
How to? Refer:
Throttling
Based on the results you can refer to this great article on TechNet by Tord for the recommendations.
Microsoft BizTalk Automatic Throttling
and
How BizTalk Server Implements Host Throttling
Rachit
Please mark as answer or vote as helpful if my reply does

Message Delivery restrictions on users in database

Hi, I want to remove all delivery restrictions for all users in a specific database. Does someone have a script to do this please? Server is Exchange 2013 and the database name is College. Thanks

Hi,
We can use the following command to remove message delivery restrictions for all users on a specific database.
Get-Mailbox -database “College” | set-mailbox -AcceptMessagesOnlyFrom $null -AcceptMessagesOnlyFromDLMembers $null -RejectMessagesFrom $null -RejectMessagesFromDLMembers $null –RequireSenderAuthenticationEnabled
$false
Also we need to check what Willard Martin said.
Best Regards.

Reliable message delivery

Hi,
I am trying to configure Realiable Message Delivery in a Composite Application in OpenESB.
In CASA editor I do "Clone WSDL Port to edit" and then I change Server and Client configuration to enable "Realiable Message Delivery".
My configuration is the following:
- Server configuration
     I've enabled "Reliable message delivery"
- Client configuration
     RM Resend Interval (ms) : 2000
     RM Close Timeout (ms): 0
     RM ACK Request Interval (ms): 200
But when a failure occurs it does not try to resend the message.
Must I configure anything else?
Thanks.

OSB has reliable messaging as one of the transport options.
You can great some proxies to manage this reliability.
Have a look at this note
http://otndnld.oracle.co.jp/document/products/osb/docs10gr3/pdf/wstransport.pdf
cheers
James

Lumia message delivery messages

Similar Messages

Maybe you are looking for