I had actually considered the regex approach looking for "https://"; as well. I think I went with the one I did mainly because it seemed less intrusive (thus less likely to break other people's config files) than the patch I submitted. I'll happily look into the regex approach if that's what you'd rather have.
now, I think as we "went that way" for the other issues, black/white lists, prefered-smsc-id, etc. this would be the better way to go.
Obviously it would be a "add-on" in the first place, in order not to break configs. Afterwards we'd cut out the "old way" support in order to have it one way.
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
