Re: [SM-USERS] Why have an user mailing list?
On 17.09.2015 22:32, André Z. D. A. wrote: > "You get what you pay for". Maybe I'm opting for the wrong webmail client. "You get what you pay for" applies not only to the software, but also to the support. You don't pay anyone (on this list, at least) for support, so you are not entitled to a solution that works for you. That doesn't mean there are no volunteers who would help if they could. You have seen that Dave tried to help by pointing out that logging the traffic between SquirrelMail and your IMAP server might be helpful? So you are not in a situation where this is possible -- tough luck. Some problems cannot be solved without closely looking at them. [You might get a bit further, by the way, by letting SquirrelMail go over an IMAP proxy to reach the Domino server and let the IMAP proxy log the protocol traffic between both. The IMAP proxy distributed by the SquirrelMail people can do protocol logging.[1]] [1] http://squirrelmail.org/download.php#imap_proxy This will be the same for any other webmail client. Maybe you can find one that doesn't stumble over that particular problem, but with all open source webmail systems you will encounter the same situation -- unless you pay for support, it is unlikely that someone puts in hours to help you. There is paid support for SquirrelMail available, by the way. See the web site for details. > And an user list is good to exist. But users are needed. And developers and > other people involved with the deeper parts of its working should help when > needed. Somewhere it is written: "Wait a few days for an answer". There is a > problem I wrote here months ago, nothing followed that message. That is a bit > disapointing. It didn't even need to be the solution, initially. But with my > knowledge I cannot solve it, and in some aspects I know more than the average > user should know, and this list name points that it is aimed for those. There we are again. You are not entitled to *any* help from this list. All free help you get is out of kindness, not out of any obligation. And that there was none does not mean nobody looked at your question; I know I did -- and had no idea. The name of the list is a bit unfortunate indeed and has led to misunderstandings in a few cases. On the SquirrelMail website it says: "Despite its name, this list is intended for supporting administrators and not end users."[2] Something like "squirrelmail operators" might be clearer today, but the name is there as it is, and I suspect the SquirrelMail people don't want to go through all the hassle to rename it; as there are third-party archives involved, this is not a trivial task. [2] http://squirrelmail.org/docs/admin/admin-12.html Regards, Juergen. -- - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Why have an user mailing list?
On Thu, 2015-09-17 at 18:25 -0300, André Z. D. A. wrote: > > > On Thu, 2015-09-17 at 06:32 -0300, André Z. D. A. wrote: > > ...snipped for brevity... > > Which should be something like this, in English: > > > > === > > ERROR: > > Error: request can't be completed. > > Request: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE > > BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance > > Priority Content-Type)]) > > Informed reason: FETCH token is invalid > > === > > > > That's not a valid FETCH command that Squirrelmail is sending. It's not > > including the sequence set (which messages to fetch those data items > > for). > > Really!? That's a surprise I would never think about. Yes, it should be something like: FETCH 1:* (FLAGS UID RFC822.SIZE INTERNALDATE... > > I assume that either your Domino server responded to a prior command > > (LIST probably) with something that Squirrelmail wasn't expecting or > > couldn't parse, or maybe there's just a very odd bug in Squirrelmail. > > I can make most tests within my server (with Squirrelmail in). I just cannot > make tests that are either expeting to log the servers (IMAP or SMTP) > internally, because they are external and inaccessible directly by me or by > the other Squirrelmail users. I can't imagine what a test could be, from SM. > I can make a setup where I can alter squirrel source code to log each > commands it sends. Would it be useful? And what should I look for, to log? > And what information can be needed (I don't know protocol details, so I would > need a help with this kind of things). If you don't have access to the server, you could set up the SquirrelMail imapproxy and use that to get protocol logs. Or if it's a test server you should be able to stick some debugging code into the SquirrelMail source and figure out what's going on. I think the above FETCH happens in the sqimap_get_small_header_list() function in functions/imap_messages.php. Figure out what the passed value of $msg_list is and why $msgs_str ends up being a null string. hth, Dave -- - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Why have an user mailing list?
Thanks a lot for these pointers, Dave! In the server I use can do both thing you suggested: patch SM and use an imap proxy. I'll try these and in after I get some results I will write again (either to ask or to inform what I've found). Thank you again, bye > On Thu, 2015-09-17 at 18:25 -0300, André Z. D. A. wrote: > >>> On Thu, 2015-09-17 at 06:32 -0300, André Z. D. A. wrote: >>> > > ...snipped for brevity... > >>> Which should be something like this, in English: >>> >>> === >>> ERROR: >>> Error: request can't be completed. >>> Request: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE >>> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance >>> Priority Content-Type)]) >>> Informed reason: FETCH token is invalid >>> === >>> >>> That's not a valid FETCH command that Squirrelmail is sending. It's not >>> including the sequence set (which messages to fetch those data items >>> for). >> >> Really!? That's a surprise I would never think about. > > Yes, it should be something like: > > FETCH 1:* (FLAGS UID RFC822.SIZE INTERNALDATE... > >>> I assume that either your Domino server responded to a prior command >>> (LIST probably) with something that Squirrelmail wasn't expecting or >>> couldn't parse, or maybe there's just a very odd bug in Squirrelmail. >> >> I can make most tests within my server (with Squirrelmail in). I just cannot >> make tests that are either expeting to log the servers (IMAP or SMTP) >> internally, because they are external and inaccessible directly by me or by >> the other Squirrelmail users. I can't imagine what a test could be, from SM. >> I can make a setup where I can alter squirrel source code to log each >> commands it sends. Would it be useful? And what should I look for, to log? >> And what information can be needed (I don't know protocol details, so I >> would need a help with this kind of things). > > If you don't have access to the server, you could set up the > SquirrelMail imapproxy and use that to get protocol logs. Or if it's a > test server you should be able to stick some debugging code into the > SquirrelMail source and figure out what's going on. > > I think the above FETCH happens in the sqimap_get_small_header_list() > function in functions/imap_messages.php. Figure out what the passed > value of $msg_list is and why $msgs_str ends up being a null string. > > hth, > > Dave > -- > - > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squirrelmail-users@lists.sourceforge.net > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users -- - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Why have an user mailing list?
It is kind of hard to provide support, as an admin for these SM setups without having any documentation about some aspects, for me and for the users. "Oh, there is a list", some may say. Yes, there is. But... you know. For example, the message filter. I have read and reread the documentation that exist. And it didn't work. I can't even be sure if it is some server problem, some configuration problem, or some user (me, specifically) problem. If I knew the problem, I would even contribute to make better documentation or anything that's being need. But when all of us keep silence about the problems we may not know, and don't take 5 or 10 minutes to say anything that has not got a good enough volunteer to solve, we make people that could help the project, as a whole, go away - both as users and as potential contributors. > On 17.09.2015 22:32, André Z. D. A. wrote: > >> "You get what you pay for". Maybe I'm opting for the wrong webmail client. > > "You get what you pay for" applies not only to the software, but also to > the support. You don't pay anyone (on this list, at least) for support, > so you are not entitled to a solution that works for you. > > That doesn't mean there are no volunteers who would help if they could. > You have seen that Dave tried to help by pointing out that logging the > traffic between SquirrelMail and your IMAP server might be helpful? So > you are not in a situation where this is possible -- tough luck. Some > problems cannot be solved without closely looking at them. > > [You might get a bit further, by the way, by letting SquirrelMail go > over an IMAP proxy to reach the Domino server and let the IMAP proxy log > the protocol traffic between both. The IMAP proxy distributed by the > SquirrelMail people can do protocol logging.[1]] > > [1] http://squirrelmail.org/download.php#imap_proxy > > This will be the same for any other webmail client. Maybe you can find > one that doesn't stumble over that particular problem, but with all open > source webmail systems you will encounter the same situation -- unless > you pay for support, it is unlikely that someone puts in hours to help you. > > There is paid support for SquirrelMail available, by the way. See the > web site for details. > >> And an user list is good to exist. But users are needed. And developers and >> other people involved with the deeper parts of its working should help when >> needed. Somewhere it is written: "Wait a few days for an answer". There is a >> problem I wrote here months ago, nothing followed that message. That is a >> bit disapointing. It didn't even need to be the solution, initially. But >> with my knowledge I cannot solve it, and in some aspects I know more than >> the average user should know, and this list name points that it is aimed for >> those. > > There we are again. You are not entitled to *any* help from this list. > All free help you get is out of kindness, not out of any obligation. > And that there was none does not mean nobody looked at your question; I > know I did -- and had no idea. > > The name of the list is a bit unfortunate indeed and has led to > misunderstandings in a few cases. On the SquirrelMail website it says: > "Despite its name, this list is intended for supporting administrators > and not end users."[2] Something like "squirrelmail operators" might be > clearer today, but the name is there as it is, and I suspect the > SquirrelMail people don't want to go through all the hassle to rename > it; as there are third-party archives involved, this is not a trivial task. > > [2] http://squirrelmail.org/docs/admin/admin-12.html > > Regards, Juergen. > > -- > - > squirrelmail-users mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squirrelmail-users@lists.sourceforge.net > List archives: http://news.gmane.org/gmane.mail.squirrelmail.user > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-users -- - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
