Re: [imp] Imp 4.2 weirdness
On Jul 10, 2008, at 5:48 PM, Chuck Hagenbuch wrote: Quoting Kevin Konowalec <[EMAIL PROTECTED]>: To which I responded "Ah HAH!". So I looked in the permissions setup, where I had added two permissions settings (max_recipients and max_timelimit). Sure enough in the Mail (imp) permission for all authenticated users, all 4 checkboxes (show, read, edit, delete) were unchecked. I checked "read" and saved it and immediately things went back to normal. So my questions are: 1) Did this actually solve the problem or am I going to piss off my users again when I put it back into production tomorrow morning? You may piss them off, but not because of this. :) That's more likely than not. It's definitely a weird feeling to have 75000 people simultaneously curse your name ;) 2) Why would users be able to work normally for so long before horde decided it wanted to enforce the permissions? Should they not have been failing right from the get-go? Had you added the permissions before, did you add it at some point after launch? When you added the max_* permissions the parent permission would be autocreated; that's when you would have had trouble. No I had added the permissions prior to launch, which is why it was so odd that it wouldn't fail right from the get-go. 3) What are all the various permissions for (show, read, edit, delete)? Which ones should be set? For an application, the only relevant ones are show and read. Show means you can see that the application is installed; read means you can use it. Should both show and read be explicitly set or does read imply show? Thanks!! K -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
Re: [imp] Imp 4.2 weirdness
Quoting Kevin Konowalec <[EMAIL PROTECTED]>: To which I responded "Ah HAH!". So I looked in the permissions setup, where I had added two permissions settings (max_recipients and max_timelimit). Sure enough in the Mail (imp) permission for all authenticated users, all 4 checkboxes (show, read, edit, delete) were unchecked. I checked "read" and saved it and immediately things went back to normal. So my questions are: 1) Did this actually solve the problem or am I going to piss off my users again when I put it back into production tomorrow morning? You may piss them off, but not because of this. :) 2) Why would users be able to work normally for so long before horde decided it wanted to enforce the permissions? Should they not have been failing right from the get-go? Had you added the permissions before, did you add it at some point after launch? When you added the max_* permissions the parent permission would be autocreated; that's when you would have had trouble. 3) What are all the various permissions for (show, read, edit, delete)? Which ones should be set? For an application, the only relevant ones are show and read. Show means you can see that the application is installed; read means you can use it. -chuck -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
[imp] Imp 4.2 weirdness
So we put horde 3.2/imp 4.2 into production. It ran fine for an hour or two... and then suddenly users were no longer able to access Imp. They'd just get a blank screen where the inbox should be. Logging into Horde was fine - you'd get the sidebar with the options and what not (no Imp though) and the "problem report" button at the top (and believe me... people used that one a LOT). We reverted to the old cluster so we could test the new one further. I turned on debug logging and saw the following: User [EMAIL PROTECTED] does not have READ permission for imp I immediately assumed it was a database error of some kind. But then one of my colleagues found the following snippet in /horde/lib/Horde/ Registry.php line 818: * If permissions checking is requested, return an error if the * current user does not have read perms to the application being * loaded. We allow access: * * - To all admins. * - To all authenticated users if no permission is set on $app. * - To anyone who is allowed by an explicit ACL on $app. */ To which I responded "Ah HAH!". So I looked in the permissions setup, where I had added two permissions settings (max_recipients and max_timelimit). Sure enough in the Mail (imp) permission for all authenticated users, all 4 checkboxes (show, read, edit, delete) were unchecked. I checked "read" and saved it and immediately things went back to normal. So my questions are: 1) Did this actually solve the problem or am I going to piss off my users again when I put it back into production tomorrow morning? 2) Why would users be able to work normally for so long before horde decided it wanted to enforce the permissions? Should they not have been failing right from the get-go? 3) What are all the various permissions for (show, read, edit, delete)? Which ones should be set? Thanks K -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
[imp] Multiple autocomplete address books
I have three address books successfully working simultaneously in Turba, but Imp only sees the first one listed in the sources.php file. Is there a setting other than those below I need to enable to get Imp's autocomplete feature to see the other two address books? Re- arranging the Turba sources.php file does actually affect the imp autocomplete, but only one source ever works at any given time. I'm using Horde Webmail 1.1, below is the relevant section of Imp's prefs.php: // address book(s) to use when expanding addresses // You can provide default values this way (note the \t and the double quotes): // 'value' => "source_one\tsource_two" // refer to turba/config/sources.php for possible source values $_prefs['search_sources'] = array( 'value' => "marlboroldap\tlocalsql\tfavorites", 'locked' => true, 'shared' => false, 'type' => 'implicit'); // field(s) to use when expanding addresses // This depends on the search_sources preference if you want to provide // default values: // 'value' => "source_one\tfield_one\tfield_two\nsource_two \tfield_three" // will search the fields 'field_one' and 'field_two' in source_one and // 'field_three' in source_two. // refer to turba/config/sources.php for possible source and field values $_prefs['search_fields'] = array( 'value' => "localsql\tname\temail\nmarlboroldap\tname\temail \nfavorites\tname\temail", 'locked' => true, 'shared' => false, 'type' => 'implicit'); // address book to use for adding addresses // put $cfgSources array element name in the value field. // Setting value to localsql would allow you to add contacts to MySQL database // See turba/config/sources.php for more info $_prefs['add_source'] = array( 'value' => 'localsql', 'locked' => true, 'shared' => false, 'type' => 'implicit' ); Thanks for any insight, Elliot -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
Re: [imp] Why would dimp be slower to generate message list than imp?
Quoting gimili <[EMAIL PROTECTED]>: Why would dimp be *significantly* slower to generate message list than imp on a large mailbox? DIMP isn't slower per se - both DIMP and IMP use the exact same functions to generate the message lists. However, DIMP processes a larger chunk of messages at a time than IMP does. In a typical mailbox, IMP displays by default 20 messages per page while DIMP downloads, by default, 7 times the size of the current viewport (if the current viewport is 20 messages, DIMP downloads the message information for 140 messages). The tradeoff is slightly slower initial display in DIMP for subsequent instantaneous scrolling through the mailbox (at least the portion that is loaded) while in IMP, you would have to wait for each subsequent page to load which takes much longer and also hammers the server (a single request for message info 140 messages is more than 700% more efficient than 7 requests for 20 messages each). I also find if I delete a message it just puts a line through it whereas this works perfectly in imp. This sounds like the bug that was discovered immediately after 1.0 was released and has already been fixed for 1.0.1. michael -- ___ Michael Slusarz [EMAIL PROTECTED] -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
Re: [imp] Marking a message as unseen
I am dumped back in the containing folder. On Jul 10, 2008, at 11:55 AM, John H. Bennett III wrote: Could I get someone to verify the following behavior please? Open a message in imp, then mark it as unseen? Do you move to the next message or do see the same message you just marked? I stay at the message I just marked. In the previous version, you were moved to the next message, which is what I would prefer. I am trying to see if I missed a setting somewhere that I can't see, or if there was a change in how this works, or if this is a bug. TIA, John -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED] -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
[imp] Marking a message as unseen
Could I get someone to verify the following behavior please? Open a message in imp, then mark it as unseen? Do you move to the next message or do see the same message you just marked? I stay at the message I just marked. In the previous version, you were moved to the next message, which is what I would prefer. I am trying to see if I missed a setting somewhere that I can't see, or if there was a change in how this works, or if this is a bug. TIA, John -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
[imp] Problem logging into Gmail Imap
Hi there, Fresh installation of Horde Groupware 1.1.1 with IMP H3 4.2 and dimp h3 1.0 running on IIS6 all with no problems. Tested IMP with AOL imap and functioned as expected with no problems Then went to test with Gmail imap and receive the following error when attempting to login - Error connecting to IMAP server: [0] The operation completed successfully. . IMAP is enabled in Gmail settings. IMAP functions with outlook. Also ran IMP test script and was successful in receiving settings for the Gmail IMAP. Any help appreciated. -- IMP mailing list - Join the hunt: http://horde.org/bounties/#imp Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: [EMAIL PROTECTED]
