How does the mail parser handle LoginShare users

[Chris Boulton]

Just a quick query regarding this, because at the moment we're having a few issues.

We've our own LoginShare setup to integrate Kayako SupportSuite in to our client area for logging in - this aspect of the application seems to work fine.

What I'm wondering though, is how the mail parser handles this for incoming tickets where a ticket has been received from a user who previously does not exist in SupportSuite.

Does it connect to the LoginShare to grab the customer ID from our database? (as would happen during the login process - loginapi_moduleid and loginapi_userid are populated with the values from our database) or does it just insert in to the users table without a login share reference?

The reason I'm asking is because we're having customers having difficulty logging in through our ticket system to see tickets they've just submitted - and from what I can tell, this is a possible cause of that.

(Usually I'd just dig through the code myself, but at the moment I don't have the time to do so)

Input is very much appreciated.

Thanks

[craigbrass]

LoginShare and Mail Parser don't really integrate. It just creates the user a new account in Kayako.

[Chris Boulton]

I figured as much. Seems like a bit of a half implementation to me and it looks like I'm going to have something in to get this all to work properly.

What I'd love to be able to do is have a lookup-user-by-email method or similar, in the login shares that if present is called by the mail parser before creating an account.

[top_cat]

Originally Posted by Chris Boulton

I figured as much. Seems like a bit of a half implementation to me and it looks like I'm going to have something in to get this all to work properly.

What I'd love to be able to do is have a lookup-user-by-email method or similar, in the login shares that if present is called by the mail parser before creating an account.

I am having the same problem. Did you manage to find a way around this?

Thanks