On Wed, 10 Dec 2008 10:38:43 +0100 Gro-Anita Hillestad Vindheim gro-anita.vindheim@ntnu.no wrote:

in our test-soon-to-be-production-NAV (3.4.4), we send SMS by using the HttpGetDispatcher.

From smsd.conf: dispatcher1: HttpGetDispatcher dispatcher2: GammuDispatcher

My username is the only user allowed to get SMS from this test-NAV. (Alert profiles, group SMS)

Still, other users keep getting SMS.

As far as I know, the objective of the SMS group is to limit the number of users receiving SMS (cost-perspective).

Has anyone else similar experiences? It this a known bug?

It is not a known bug, and it cannot possibly be related to what SMS dispatcher plugin you are using, since the enforcing of this privilege takes place in the AlertEngine, not in the the SMS daemon. The SMS daemon will happily dispatch anything placed in the SMS queue, so you should be having the same problem with the GammuDispatcher.

However, I just tried to grok the old AlertEngine code, and I cannot actually see the alert_by privilege being enforced anywhere at all :-P

The 3.4 AlertEngine tries to extract some information about a user's "alerttype" privilege (a privilege that doesn't exist), but this information is not used anywhere in AlertEngine.

This would be another grave example of the many disassociations between Alert Profiles and Alert Engine in NAV <= 3.4, which is why we rewrote them to share the same API in NAV 3.5.

I'd encourage you to file a bug for this at Launchpad, but I must add that we have no concrete plans of doing any more releases in the 3.4 series :-/