Check the permissions on your transports directory, esp. the gateway named directory. I have seen, atleast on Linux, where some folders are not given the proper permissions to be able to write the new users directory thus not allowing them to complete registration.
On Wed, 2007-07-18 at 10:57 +0100, Justin Hawkins wrote: > > I have the MSN transport successfully setup, with ejabberd. > > > > Some of my users have an issue where the transport does not > > automatically log on when they login to their jabber account. > > > > I have narrowed this down to the fact that they cannot get a 'from' > > subscription to the MSN transport JID. I'm led to believe this is what > > is necessary to make the transport log on when the jabber account logs on. > > > > Although the users affected can login manually, this only works in > > clients such as Psi, which provide this option. Many others don't (for > > instance ichat). > > > > Anecdotal evidence suggests that no new user, since some point in the > > past has been able to do this. My account continues to work fine, as do > > others, but new users (even a brand new jabber account setup from > > scratch) cannot get the subscription. > > > > In their client the authorisation request does not seem to have any affect. > > > > I can see (using the ejabberd web console) that their subscription is > > either "to" or "none", but unfortunately I cannot see any way to fix it > > for them manually. > > > > I also have the pyicq transport running on the same system, this is not > > having this issue. > > > > Any ideas where to look? > > Hi guys, > > I've investigated a few things with no luck. > > I believe if I could manually tweak the ejabberd tables to change the > user's subscription then things would start working, however this is a > scary prospect (ejabberd sure ain't sql, and playing with the tables > behind it's back is certainly 'unsupported' at best :-) > > Plus, I certainly don't want to have to do this for each new user! > > Because pyicq works fine, I still believe this is (even if indirectly) a > pymsn problem. > > I'm not trying to say 'hey, fix it' but I would sure appreciate a > pointer as to what debugging information would be useful, or other stuff > I can look at. > > > pkg_info | egrep 'ejabberd|pymsn|pyicq' > ejabberd-1.1.2_2 Free and Open Source distributed fault-tolerant > Jabber serv > jabber-pyicq-transport-0.7b_2 Python ICQ-Transport for Jabber > jabber-pymsn-transport-0.11.2_2,1 Python MSN-Transport for Jabber > > > uname -s -r > FreeBSD 5.3-RELEASE > > Regards, > > Justin > > _______________________________________________ > py-transports mailing list > py-transports@blathersource.org > http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports -- CONFIDENTIALITY This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof. ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina-SCI Corporation (or any of its subsidiaries), or any other person or entity. _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
