| CC to Option for all incoming Messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| David Chkhartishvili New member Username: Datoch Post Number: 41 Registered: 06-2004 |
Hi Bryce, Is it possible to copy all incoming messages addressed to particular prefix copy to MM7 link as well? Thanks, David | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6793 Registered: 10-2002 |
Hi David, No, it's not. I know we've considered this, and come fairly close to implementing an "AutoBCC" option in the past. But for one reason or another, it hasn't made the cut. What are you looking to accomplish? We might want to revisit this issue. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 42 Registered: 06-2004 |
Bryce, We're going to implement Unified Messaging solution, which means that subscribers will have one inbox for voice mail, email, mms... That's why we need all messages sent to subscribers to be copied to UM inbox. This can be done via IMAP, MM4 or MM7. Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6805 Registered: 10-2002 |
David, It sounds like an "Auto BCC" option might work for that requirement. We will have to do some more investigation to determine feasability and the amount of development effort required. My thinking is that there could be a configuration setting where an extra BCC recipient was inserted into every message. Conceptually, this doesn't sound very difficult. However, I seem to recall that we were considering adding this in an earlier version, but then didn't because of unexpected complications. If I recall correctly, it was a relatively simple issue to add a BCC recipient if it was another phone number (which could be routed via MM4 or MM7), but there were complications if the added BCC recipient was an e-mail address. Would such a BCC option work for this UM solution? To clarify, I'd want to understand a little bit more about how this would work. If the MMSC had a single address "Auto BCC" option, where all messages processed by the MMSC get BCC'd to the "Auto BCC" address ... would that work? Assume the messages get routed to the UM via SMTP, MM7, MM4 ... would the UM solution parse the original recipients from the To/CC display header? Or, would messages have to be copied to a unique BCC address for each recipient? That is, does the UM solution expect to receive messages addressed directly to each recipient phone number instead of it parsing the display headers? The latter would be considerably more difficult. So I think we should understand what the UM solution expects before we spend too much time evaluating the development effort. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 43 Registered: 06-2004 |
Hi Bryce, Messages have to be copied to a unique BCC address for each recipient and SMTP is preferred. If you cannot copy over SMTP, than additional development to be done on UM side side to accept MM7 or MM4. | |||
| David Chkhartishvili New member Username: Datoch Post Number: 44 Registered: 06-2004 |
Hi Bryce, Any news regarding this issue? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6853 Registered: 10-2002 |
Hi David, Unfortunately, this unique address for each recipient makes things more complicated. Currently, the thinking is that in order to implement this in a timely fashion, we'd have to charge a custom development fee. That's why I was trying to think of a simpler approach. I've currently got a list of about 20 issues under consideration in the short term development queue. A couple of these items have been addressed in just this past week, awaiting testing. But this one is getting pushed back because of the complexity. Thinking about it again just now, I got a fresh idea of what an INI file parameter would look like, and how it should be evaluated, and what actions should be taken based upon the setting. But there is an added consideration for SMTP in that currently full To/Cc information is not included for messages routed to SMTP, and that needs to be cleaned up if we do this implementation, as otherwise there may be problems with the e-mail message having no "To:" header. (Some internal changes in the SMTP handler that were made for the initial NowSMS 2006 release should help make this To/Cc handling a relatively simple matter.) This added analysis might help get this item selected for implementation out of this short term queue. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 45 Registered: 06-2004 |
Bryce, This is not so urgent issue. I just wanted to make sure that this is possible. Is 1 month enough time to implement feature? Thanks | |||
| David Chkhartishvili New member Username: Datoch Post Number: 49 Registered: 06-2004 |
Hi Bryce, Did you make any decision regarding this feature? BR, David | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7142 Registered: 10-2002 |
Hi David, A belated follow-up (I know we've traded some e-mails on this subject in the interim) ... We've added an AutoBCC facility where any submitted messages are automatically BCC'd to a configured address. That address could be routed via SMTP/MM7/MM4/whatever. That's the good news. The bad news ... well, it's not really bad news ... it is just a caution ... is that the new version that implements this change contains some internal changes that I would still consider to be in "test", which particuarly impact operator MMSC configurations. We have made changes to the "MMSC Users" database structure to address performance concerns. The existing implementation provides sufficient performance for user lookup/validation. However, the performance for adding new users is not very good. When users are configured to be automatically provisioned the first time that they send an MMS, it is not a major problem. There is potential for performance bottlenecks if you have a thousand new customers added in an hour or so. So far we haven't seen this cause a problem in the real world. But, this is an area that we have wanted to improve for quite some time. The new version changes the format of the "MMSC Users" database. Instead of using a proprietary format (MMSCUSERS.D2A and MMSCUSERS.D2I), the users are stored in an SQLite database (MMSCUSERS.DB) which offers better performance, particularly for new user additions. The first time the new version of the MMSC is started, it converts the database. This conversion process can take an hour to two on larger systems, however the system operates normally during this time period. The only concern is that the MMSC should not be restarted during this time period until the conversion is complete. The update is available for download at http://www.nowsms.com/download/nowsms2007.zip. And the "AutoBCC" feature is described in the associated text file. Before you consider updating your system to this version, you might want to consider sending me your "MMSC Users" files, so that I can test them and make sure that the conversion will go ok. If you want to do this, ZIP up "MMSCUSERS.D2A" and "MMSCUSERS.D2I" and e-mail them to nowsms@now.co.uk with "Attention: Bryce" on the subject line. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 50 Registered: 06-2004 |
Hi Bryce, As I mentioned earlier, we're going to use this feature for "unified inbox", meaning that every incoming mms message will be copied to subscribers inbox. But current solution is not suitable for us, because original recipient(s) address is not visible, thus we're not able to deposit message to unified inbox. We would like to see autocc option rather than autobcc. Thanks, David | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7143 Registered: 10-2002 |
Hi David, No, I think it should work correctly. At least it has the potential to. The extra address is added as a BCC ... so the original recipient addresses are always visible. It is the added BCC that is not visible. -bn | |||
| David Chkhartishvili Frequent Contributor Username: Datoch Post Number: 51 Registered: 06-2004 |
Hi Bryce, I was not clear enough. xx@xx.com is configured address for autobcc. Every message is copied to that address. We're going to retrieve messages addressed to xx@xx.com and deposit them to subscribers unified inbox. But we can't do this in current setup, because messages addressed to xx@xx.com are BCCs, thus original recipient(s) address not visible. BR, David | |||
| David Chkhartishvili Frequent Contributor Username: Datoch Post Number: 52 Registered: 06-2004 |
Hi Bryce, Is that possible? to make autocc instead of autobcc? Thanks, David | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7163 Registered: 10-2002 |
Hi David, Sorry for the delay. We've been very busy finalising the new release. But all of the major work is done, and I got a week of vacation to recover (could have used two, but oh well). I'm still confused about what the problem is with BCC ... because to me it does what you ask. It probably would help to explain it with an example, because I know I tend to get confused thinking abstract. Let's say that 1000 sends an MMS message to 1001 and 1002. And let's say that you have an AutoBCC=xx@xx.com entry under [MMSC] in MMSC.INI. What happens is that xx@xx.com is added as a BCC recipient to the message. 1001 receives the message, and can see that the message was addressed to 1001 and 1002. It cannot see that the message was sent to xx@xx.com. 1002 receives the message, and can see that the message was addressed to 1001 and 1002. It cannot see that the message was sent to xx@xx.com. xx@xx.com receives the message, and it sees 1001 and 1002 in the "To:" header, but it does not see itself in the "To:" header. If we made it AutoCC instead of AutoBCC ... the only change is that 1001 and 1002 would also see "xx@xx.com" in the recipient list. (And of course, "xx@xx.com" would see itself in the recipient list of the message that it receives.) At least that is how it is supposed to work ... and it works if the AutoBCC recipient is an MMS recipient routed via MM4 or MM7. But it doesn't work if the AutoBCC recipient is an e-mail address. The MMS to e-mail facility does not support To/Cc. Oddly enough, I mentioned that as a concern earlier in this thread, but forgot about it when I ok'd this to be added. We'll get that oversight corrected shortly. -bn | |||
| Michael New member Username: Michael123 Post Number: 7 Registered: 02-2007 |
Hi Bryce, We are going to enable AutoBCC future on our system (via MM7). Which is the latest working update we need to install? Thanks, Michael | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7425 Registered: 10-2002 |
Hi Michael, The AutoBCC capability is definitely in the 2007.06.27 release that is the current download. -bn | |||
