I wrote a messaging_mms module for sending MMS messages. It has dependencies on SMS Framework (to store user phone numbers) and Mimemail module (to send via email gateways).

I was planning on maintaining it myself on cvs.drupal.org rather than contributing it to the messaging project as a sub-module, in part due to SMS Framework being fairly unstable, with API differences between the 6.x-1.x-dev and 6.x-2.x-dev branches; also because it needs more work to support other (non-email) types of gateways. But thought I would make a note of it in this issue queue in case anyone else is working on MMS.

Comments

jose reyero’s picture

This looks like a great one!

I really want it one way or another into messaging. But I think the better way to do it would be first to add MMS support to SMS framework, then have only the integration part in messaging.

As I think you know, we are adding (still experimental) attachments support to messaging so this ideally would integrate with that, using any mail method available that supports attachment and maybe sending normal sms if the message has no files/sending mms if it has some file we can send through mms... Yes, I know that may need some api extension too, but we can easily do that...

Related (messaging attachments), #371596: Including file attachments in messages

Does this make sense for you? (I have to admit I don't know too much abt sms, specially since my iPhone doesn't support it :-( )

About maintaining the module, I know creating a new project in drupal.org means a lot of overhead. So would you prefer being added as maintainer to either messaging or notifications_extra (that's the place for experimental stuff till we have it tested enough for the main packages...) and maintaining your own sub-module there?

Whatever, thanks a lot for this module, and also for all the good patches you've been posting so far.

mfb’s picture

I'd *love* for SMS Framework to support MMS. I already have some working glue modules for sending and receiving MMS via e-mail gateways. Probably I should go ahead and post them to the SMS Framework issue queue (at #373307: MMS support) for review.

I don't really mind maintaining the module myself but if you want to make it part of messaging that would be great. Maybe there could be some way to indicate that a messaging submodule is still in testing? Not sure if notifications_extra is right since this isn't specific to notifications. but, up to you.

I forgot to mention one thing, when sending MMS via email gateways, there's a dependency on a little API module not yet on cvs.drupal.org, I am calling it mms_email_gateway. It allows us rewrite the gateway address for some carriers, which use different gateways for SMS and MMS. This is the case for three carriers in the US, one in Colombia and probably others we'll find soon as our project expands. This module should presumably go in SMS Framework as part of the MMS support.

Apparently MMS will soon be fully supported on the iPhone (finally!)

jose reyero’s picture

Yes, I want to make it part of messaging eventually. But atm, if we add here stuff that needs complex set up and has other external dependencies, this issue tracker may end up flooded with support requests, that's something we don't want to happen.

(We'll be doing one more maintenance release in the next days)

I agree notifications_extra may not be the ideal place, but that would be only an interim solution to make the stuff easily available, while skpping the overhead of creating one more module, we already have enough of them :-)

I think the best way to proceed here would be to first add MMS support in SMS framework then add the Messaging module here. This may take a bit longer but doing it right will save everybody a lot of headaches.

In the meanwhile if you think making the module available some other way makes sense, you also have commit rights for notifications_extra. We can always rename the package to 'Notifications & Messaging Add-ons' :-)
Or if you think it makes more sense as a stand alone module, that's an option too, just I think that would create lots of extra work for everybody in the long term.

So should we give a try to getting it into SMS Framework first?

xiong’s picture

I would love it to be into SMS Framework :)

jose reyero’s picture

Status: Needs work » Postponed

Waiting for this to be supported by SMS framework

socialnicheguru’s picture

subscribing. any new options?