From: Paul L. <pa...@sq...> - 2010-02-12 17:20:50
Attachments:
squirrelmail-gmail-configuration.diff
|
All, It has come to my attention that we could add a list of required configuration settings for using Gmail as the IMAP/SMTP server behind SquirrelMail. Google is a fairly controversial company, second only to Microsoft these days, so I'm not sure if we want to do that or not. OTOH, we list exchange and some other IMAP servers that represent for-profit entities, which is why I think ultimately, it's probably OK. Gmail is somewhat non-standard in that it's a hosted IMAP server, but it is an IMAP server nonetheless. If we add Gmail, we need at least one Gmail-specific fix in the code, wherein when FETCHing a message body, their IMAP server does not set the Seen flag. The fix is simple. Thoughts? Below are the settings that I fiddled with and seemed to work for the most part. Attached is the full proposed patch for STABLE. Please help fix and test. imap_server_type = gmail default_folder_prefix = <none> (is set to empty string) trash_folder = [Gmail]/Trash sent_folder = [Gmail]/Sent Mail draft_folder = [Gmail]/Drafts show_prefix_option = false default_sub_of_inbox = false show_contain_subfolders_option = false optional_delimiter = / delete_folder = true force_username_lowercase = false domain = gmail.com imapServerAddress = imap.gmail.com imapPort = 993 use_imap_tls = true imap_auth_mech = login smtpServerAddress = smtp.gmail.com smtpPort = 465 use_smtp_tls = true smtp_auth_mech = login pop_before_smtp = false useSendmail = false -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Tomas K. <to...@us...> - 2010-02-12 17:35:15
|
2010.02.12 19:20 Paul Lesniewski rašė: > If we add Gmail, we need at least one Gmail-specific fix in the > code, wherein when FETCHing a message body, their IMAP server does not > set the Seen flag. The fix is simple. Fix is really simple and does not require changes in source. It is called "contact software vendor and ask to fix their stuff". Code should not introduce fixes for third party bugs that violate standards. If you add fixes for gmail, you will have to add fixes for any other broken IMAP server. > trash_folder = [Gmail]/Trash > sent_folder = [Gmail]/Sent Mail > draft_folder = [Gmail]/Drafts Gmail system folder names are localized and depend on translation selected by end user. -- Tomas |
From: Paul L. <pa...@sq...> - 2010-02-12 19:37:35
|
On Fri, Feb 12, 2010 at 9:33 AM, Tomas Kuliavas <to...@us...> wrote: > 2010.02.12 19:20 Paul Lesniewski rašė: >> If we add Gmail, we need at least one Gmail-specific fix in the >> code, wherein when FETCHing a message body, their IMAP server does not >> set the Seen flag. The fix is simple. > > Fix is really simple and does not require changes in source. It is called > "contact software vendor and ask to fix their stuff". Code should not > introduce fixes for third party bugs that violate standards. > > If you add fixes for gmail, you will have to add fixes for any other > broken IMAP server. > >> trash_folder = [Gmail]/Trash >> sent_folder = [Gmail]/Sent Mail >> draft_folder = [Gmail]/Drafts > > Gmail system folder names are localized and depend on translation selected > by end user. Good catch. Each time a user changes language settings in Gmail, the Drafts, Sent and Trash folder names are changed. Thus, there is probably no way for SquirrelMail to know what to expect when logging in for the names of these folders. So the compromise I propose is to include "auto_create_special = false" in the presets and add a warning about this issue (e.g., it's prudent for the user to change the SquirrelMail language to match and adjust the Draft/Sent/Trash folder settings in Options-->Folder Preferences). This will create a situation where those special folders are recognized when both interface languages are set to English and otherwise, the user has to do some manual setup on their own. Aside from not adding Gmail, I don't see any other viable configuration. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Michael A. P. I. <sha...@gm...> - 2010-02-12 20:00:55
|
On Fri, 12 Feb 2010 12:20:23 -0500, Paul Lesniewski <pa...@sq...> wrote: > It has come to my attention that we could add a list of required > configuration settings for using Gmail as the IMAP/SMTP server behind > SquirrelMail. That would be cool. However, there are a few things *in general* that come to mind: 1. Gmail IMAP is funky on how you do things. It's best for users to read through <http://operawiki.info/GmailImap> to understand how Gmail IMAP works. If you try to use it with SM in a traditional IMAP way, you'll have problems (unless you install the Gmail labs imap extension, but even then, it's kind of buggy). 2. In Europe I believe, the [Gmail] folder will be [GoogleMail] instead. And, some other folders might have different names depending on the locale. I think Gmail's IMAP server supports the XLIST command exactly for this. But, you might not have to worry about that unless you're doing something GMAIL-specific in the code. 3. The Gmail IMAP and SMTP servers require ssl/tls, so it's not going to work at all unless the SM server supports that, afaik. 4. Once a month or so, the Gmail IMAP server will start sending system failure codes when you try to select a folder and do other things. For example: status "mailbox" (UIDNEXT UIDVALIDITY) NO System Error (Failure) Some IMAP clients choke on that. Not sure if SM would. -- Michael |
From: Paul L. <pa...@sq...> - 2010-02-12 21:46:03
|
On Fri, Feb 12, 2010 at 12:00 PM, Michael A. Puls II <sha...@gm...> wrote: > On Fri, 12 Feb 2010 12:20:23 -0500, Paul Lesniewski > <pa...@sq...> wrote: > >> It has come to my attention that we could add a list of required >> configuration settings for using Gmail as the IMAP/SMTP server behind >> SquirrelMail. > > That would be cool. However, there are a few things *in general* that come > to mind: > > 1. Gmail IMAP is funky on how you do things. It's best for users to read > through <http://operawiki.info/GmailImap> to understand how Gmail IMAP > works. If you try to use it with SM in a traditional IMAP way, you'll have > problems (unless you install the Gmail labs imap extension, but even then, > it's kind of buggy). What problems specifically? I have tested it, and aside from the names of the special folders, I don't see any big issues. They seem to be mostly RFC-compliant. I skimmed the page link you sent, but don't see any real "problems" per se, at least for SM being used by someone familiar with how Gmail's labels system works. > 2. In Europe I believe, the [Gmail] folder will be [GoogleMail] instead. > And, some other folders might have different names depending on the > locale. I think Gmail's IMAP server supports the XLIST command exactly for > this. But, you might not have to worry about that unless you're doing > something GMAIL-specific in the code. I think it's [Google Mail], but anyhow, thanks for the note - I think I saw XLIST mentioned before but I didn't pay much attention... but it could be something we could implement easily as an alternative if mentioned in the capabilities response. > 3. The Gmail IMAP and SMTP servers require ssl/tls, so it's not going to > work at all unless the SM server supports that, afaik. Yes. SquirrelMail's configtest script already warns the administrator about this if it's an issue. FWIW, you need at PHP 4.3.0 and the openssl extension compiled in. > 4. Once a month or so, the Gmail IMAP server will start sending system > failure codes when you try to select a folder and do other things. For > example: > > status "mailbox" (UIDNEXT UIDVALIDITY) > NO System Error (Failure) > > Some IMAP clients choke on that. Not sure if SM would. Can't do anything about Gmail's problems.... :-) -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Michael A. P. I. <sha...@gm...> - 2010-02-13 12:49:58
|
On Fri, 12 Feb 2010 16:37:38 -0500, Paul Lesniewski <pa...@sq...> wrote: > On Fri, Feb 12, 2010 at 12:00 PM, Michael A. Puls II > <sha...@gm...> wrote: >> On Fri, 12 Feb 2010 12:20:23 -0500, Paul Lesniewski >> <pa...@sq...> wrote: >> >>> It has come to my attention that we could add a list of required >>> configuration settings for using Gmail as the IMAP/SMTP server behind >>> SquirrelMail. >> >> That would be cool. However, there are a few things *in general* that >> come >> to mind: >> >> 1. Gmail IMAP is funky on how you do things. It's best for users to read >> through <http://operawiki.info/GmailImap> to understand how Gmail IMAP >> works. If you try to use it with SM in a traditional IMAP way, you'll >> have >> problems (unless you install the Gmail labs imap extension, but even >> then, >> it's kind of buggy). > > What problems specifically? I have tested it, and aside from the > names of the special folders, I don't see any big issues. They seem > to be mostly RFC-compliant. I skimmed the page link you sent, but > don't see any real "problems" per se, at least for SM being used by > someone familiar with how Gmail's labels system works. To have actions sync with the webmail interface properly, you have to: 1. Move to [Gmail]/Trash when you want to delete a message. 2. Mark a message as \Deleted and Expunge it if you want to remove a label (Inbox is a label too and so is [Gmail]/Starred). As an alternative, you can move the message to [Gmail]/All Mail and Gmail will do the right thing. (Will have to double-check this works for unstarring though) 3. To add another label to a message, you have to copy it to another label folder. 4. To change a label you have to move the message to another label folder. 5. To star a message, you have to copy it to [Gmail]/Starred or add \Flagged to the message. 6. To mark a message as spam, you have to move it to [Gmail]/Spam. 7. To clear [Gmail]/Spam and [Gmail]/Trash, you have to mark all messages in them as \Deleted and expunge them. 8. To undelete a message from [Gmail]/Trash, you have to move it back to the where it was at. If you don't know/remember where it was at, you have to move it to the Inbox label. Then, all labels for the message will be restored. And, if you remember that it didn't have an Inbox label when you deleted it, you'll need to move it to [Gmail]/All Mail to get rid of the Inbox label. #1 and #7 won't be a problem if [Gmail]/Trash is set as your trash folder. With #2, you can't do the former by default (or at all exactly without UID Expunge or a fallback), but you can do the latter. However, the user has to know that they need to move to [Gmail]/All Mail. And, I'd have to double-check that moving from [Gmail]/Starred to [Gmail/All Mail *just* removes the starred copy. Otherwise, you'd want to just mark the starred copy as \Deleted and expunge it. But, doing that by moving the starred copy to [Gmail]/Trash and emptying [Gmail]/Trash might be interpreted as you wanting to remove the message completely everywhere. For #3, not sure how SM can do that right now. For #5, not sure how SM can do that. But, I think if you move a message to [Gmail]/Starred instead of just copying to it, Gmail might fallback and undestand what you mean. If not though, it's going to remove all your labels from the message. Also, since there's an extra copy of the message for each label (including Inbox) that you have applied to the message, if you do a search in all folders for a message, you could get 0-N duplicates. Users might not understand why this happens and will think it's an SM bug. So, yes, you're right. If the user understands everything, they'll pretty much be fine. However, if they don't, they're going to think that SM is being weird and buggy when it's not. The reason I mention this is that on the Opera forums, users come in complaining left and right about duplicates with Gmail IMAP and things not working like regular IMAP. There were so many that didn't understand it (and thought it was a bug in Opera) that a page was put up on the Opera Wiki. Now, SM doesn't have a global All Messages filter, so some of these problems are less of an issue with SM. But, just wanted to give you a heads up. -- Michael |
From: Michael A. P. I. <sha...@gm...> - 2010-02-13 14:21:11
|
On Fri, 12 Feb 2010 16:37:38 -0500, Paul Lesniewski <pa...@sq...> wrote: > On Fri, Feb 12, 2010 at 12:00 PM, Michael A. Puls II > <sha...@gm...> wrote: >> On Fri, 12 Feb 2010 12:20:23 -0500, Paul Lesniewski >> <pa...@sq...> wrote: >> 2. In Europe I believe, the [Gmail] folder will be [GoogleMail] instead. >> And, some other folders might have different names depending on the >> locale. I think Gmail's IMAP server supports the XLIST command exactly >> for >> this. But, you might not have to worry about that unless you're doing >> something GMAIL-specific in the code. > > I think it's [Google Mail], but anyhow, thanks for the note - I think > I saw XLIST mentioned before but I didn't pay much attention... but it > could be something we could implement easily as an alternative if > mentioned in the capabilities response. O.K. >> 3. The Gmail IMAP and SMTP servers require ssl/tls, so it's not going to >> work at all unless the SM server supports that, afaik. > > Yes. SquirrelMail's configtest script already warns the administrator > about this if it's an issue. FWIW, you need at PHP 4.3.0 and the > openssl extension compiled in. Cool. Thanks. >> 4. Once a month or so, the Gmail IMAP server will start sending system >> failure codes when you try to select a folder and do other things. For >> example: >> >> status "mailbox" (UIDNEXT UIDVALIDITY) >> NO System Error (Failure) >> >> Some IMAP clients choke on that. Not sure if SM would. > > Can't do anything about Gmail's problems.... :-) Understood. It's just that I've seen it crash Thunderbird and freeze Opera with 100% cpu usage. Just not sure how SM would handle that. Hopefully better. -- Michael |
From: Alexandros V. <av...@no...> - 2010-02-13 09:38:59
|
On Fri, 12 Feb 2010 15:00:44 -0500 "Michael A. Puls II" <sha...@gm...> wrote: > 2. In Europe I believe, the [Gmail] folder will be [GoogleMail] > instead. And, some other folders might have different names depending > on the locale. I think Gmail's IMAP server supports the XLIST command > exactly for this. But, you might not have to worry about that unless > you're doing something GMAIL-specific in the code. FYI: (note the current version of the draft is http://www.ietf.org/id/draft-ietf-morg-list-specialuse-01.txt ) From: Barry Leiba <bar...@gm...> To: mo...@ie... Subject: [MORG] New WG document:draft-ietf-morg-list-specialuse-00 Date: Mon, 25 Jan 2010 20:57:43 -0500 Reply-To: bar...@co... Sender: mor...@ie... > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This draft is a work item of the Message Organization > Working Group of the IETF. > > Title : IMAP LIST extension for special-use mailboxes > Author(s) : B. Leiba, J. Nicolson > Filename : draft-ietf-morg-list-specialuse-00.txt > Pages : 9 > Date : 2010-01-25 > > Some IMAP message stores include special-use mailboxes, such as those > used to hold draft messages or sent messages. Many mail clients > allow users to specify where draft or sent messages should be put, > but configuring them requires that the user know which mailboxes the > server has set aside for these purposes. This extension adds new > mailbox flags that a server MAY include in IMAP LIST command > responses to identify special-use mailboxes to the client, easing > configuration. ... > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-morg-list-specialuse-00.txt At the Hiroshima meeting, the working group agreed to add this document to its list of work items. It is a standards-track version of gmail's "XLIST" extension, which has been implemented by several mail clients already. Google has said they would alter their implementation to confirm to a standards-track version. Please review this new draft and comment on it. Barry, MORG secretary |
From: Michael A. P. I. <sha...@gm...> - 2010-02-13 13:01:27
|
On Sat, 13 Feb 2010 04:38:44 -0500, Alexandros Vellis <av...@no...> wrote: > On Fri, 12 Feb 2010 15:00:44 -0500 > "Michael A. Puls II" <sha...@gm...> wrote: > >> 2. In Europe I believe, the [Gmail] folder will be [GoogleMail] >> instead. And, some other folders might have different names depending >> on the locale. I think Gmail's IMAP server supports the XLIST command >> exactly for this. But, you might not have to worry about that unless >> you're doing something GMAIL-specific in the code. > > FYI: > > (note the current version of the draft is > http://www.ietf.org/id/draft-ietf-morg-list-specialuse-01.txt ) Thanks So, in Gmail, it'd map to something like this: "[Gmail]/All Mail" \All \Archive "[Gmail]/Trash" \Trash "[Gmail]/Spam" \Junk "[Gmail]/Sent Mail" \Sent "[Gmail]/Drafts" \Draft "[Gmail]/Starred" \Flagged "Inbox" \Inbox , but would do so regardless of the actual folder names? If so, that sounds useful so you can always and easily detect the right folders to put the corresponding messages in or perform actions with. -- Michael |
From: Michael P. <mi...@wi...> - 2010-02-12 20:33:29
|
This is an interesting issue. Even when my Iphone connects, it has a different idea of what special folders are. And the language issue is another one. I think it behooves the clients to create some form of 'translation' layer for the standardized IMAP names. (Oh, I don't think there is a standard yet :) On February 12, 2010, Paul Lesniewski wrote: > On Fri, Feb 12, 2010 at 9:33 AM, Tomas Kuliavas > > <to...@us...> wrote: > > 2010.02.12 19:20 Paul Lesniewski rašė: > >> If we add Gmail, we need at least one Gmail-specific fix in the > >> code, wherein when FETCHing a message body, their IMAP server does not > >> set the Seen flag. The fix is simple. > > > > Fix is really simple and does not require changes in source. It is called > > "contact software vendor and ask to fix their stuff". Code should not > > introduce fixes for third party bugs that violate standards. > > > > If you add fixes for gmail, you will have to add fixes for any other > > broken IMAP server. > > > >> trash_folder = [Gmail]/Trash > >> sent_folder = [Gmail]/Sent Mail > >> draft_folder = [Gmail]/Drafts > > > > Gmail system folder names are localized and depend on translation > > selected by end user. > > Good catch. Each time a user changes language settings in Gmail, the > Drafts, Sent and Trash folder names are changed. Thus, there is > probably no way for SquirrelMail to know what to expect when logging > in for the names of these folders. > > So the compromise I propose is to include "auto_create_special = > false" in the presets and add a warning about this issue (e.g., it's > prudent for the user to change the SquirrelMail language to match and > adjust the Draft/Sent/Trash folder settings in Options-->Folder > Preferences). This will create a situation where those special > folders are recognized when both interface languages are set to > English and otherwise, the user has to do some manual setup on their > own. Aside from not adding Gmail, I don't see any other viable > configuration. > -- "Products, Services and Support..." ------------------------------------------------------------------------ Michael Peddemors - President/CEO - Wizard IT Services "Servicing the ISP, Telco and Enterprise Markets since 1997" ------------------------------------------------------------------------ A Wizard IT Company - For More Info http://www.wizard.ca "Wizard IT" is a company TradeMark of Wizard Tower TechnoServices Ltd. ------------------------------------------------------------------------ 604-589-0037 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. |
From: Paul L. <pa...@sq...> - 2010-02-16 08:50:47
|
On Fri, Feb 12, 2010 at 12:06 PM, Michael Peddemors <mi...@wi...> wrote: > This is an interesting issue. Even when my Iphone connects, it has a > different idea of what special folders are. And the language issue is another > one. I think it behooves the clients to create some form of 'translation' > layer for the standardized IMAP names. (Oh, I don't think there is a standard > yet :) Google implemented it as "XLIST", and it is on a standards track now with the link Alexandros sent: http://www.ietf.org/id/draft-ietf-morg-list-specialuse-01.txt Nothing to do with an abstraction of language per se... > On February 12, 2010, Paul Lesniewski wrote: >> On Fri, Feb 12, 2010 at 9:33 AM, Tomas Kuliavas >> >> <to...@us...> wrote: >> > 2010.02.12 19:20 Paul Lesniewski rašė: >> >> If we add Gmail, we need at least one Gmail-specific fix in the >> >> code, wherein when FETCHing a message body, their IMAP server does not >> >> set the Seen flag. The fix is simple. >> > >> > Fix is really simple and does not require changes in source. It is called >> > "contact software vendor and ask to fix their stuff". Code should not >> > introduce fixes for third party bugs that violate standards. >> > >> > If you add fixes for gmail, you will have to add fixes for any other >> > broken IMAP server. >> > >> >> trash_folder = [Gmail]/Trash >> >> sent_folder = [Gmail]/Sent Mail >> >> draft_folder = [Gmail]/Drafts >> > >> > Gmail system folder names are localized and depend on translation >> > selected by end user. >> >> Good catch. Each time a user changes language settings in Gmail, the >> Drafts, Sent and Trash folder names are changed. Thus, there is >> probably no way for SquirrelMail to know what to expect when logging >> in for the names of these folders. >> >> So the compromise I propose is to include "auto_create_special = >> false" in the presets and add a warning about this issue (e.g., it's >> prudent for the user to change the SquirrelMail language to match and >> adjust the Draft/Sent/Trash folder settings in Options-->Folder >> Preferences). This will create a situation where those special >> folders are recognized when both interface languages are set to >> English and otherwise, the user has to do some manual setup on their >> own. Aside from not adding Gmail, I don't see any other viable >> configuration. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Uwe S. <us...@ub...> - 2010-02-19 09:18:14
|
Hello everyone, > All, [...] > If we add Gmail, we need at least one Gmail-specific fix in the > code, wherein when FETCHing a message body, their IMAP server does not > set the Seen flag. The fix is simple. > > Thoughts? [...] I have seen this fix in the 1.5 branch already, and it can easily be adopted to earlier versions... One of the reasons I really like Squirrelmail is the way it deals with mails containg [message/rfc822] attachments, such as mailman digests in mime format. Squirrel makes it really easy to open and answer single attached messages. But just this feature does not work when Squirrel connects to gmail... the parts of the mail are shown when opening the "main" message - the first attached messages are still there but the last two messages appear to be empty (although the contents is shown when opening the "details"). Best regards from Berlin, Germany, Uwe -- View this message in context: http://old.nabble.com/Gmail-tp27566733p27651467.html Sent from the squirrelmail-devel mailing list archive at Nabble.com. |
From: Paul L. <pa...@sq...> - 2010-02-19 19:20:56
|
> [...] > >> If we add Gmail, we need at least one Gmail-specific fix in the >> code, wherein when FETCHing a message body, their IMAP server does not >> set the Seen flag. The fix is simple. >> >> Thoughts? > [...] > > I have seen this fix in the 1.5 branch already, and it can easily be adopted > to earlier versions... It's in 1.4 as well. > One of the reasons I really like Squirrelmail is the way it deals with mails > containg [message/rfc822] attachments, such as mailman digests in mime > format. Squirrel makes it really easy to open and answer single attached > messages. > > But just this feature does not work when Squirrel connects to gmail... the > parts of the mail are shown when opening the "main" message - the first > attached messages are still there but the last two messages appear to be > empty (although the contents is shown when opening the "details"). I don't entirely understand your explanation. Maybe a screenshot would help. Also, if you can forward the full message source, we can use that to try to test and see what's happening. Keep in mind that this may be another example of Google having a slightly non-standard IMAP implementation and if the fix is complicated, we may not be willing to implement it.... Thanks for testing and feedback! -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Uwe S. <us...@ub...> - 2010-02-19 20:45:15
|
Hello Paul, thanks a lot for your immediate response... >> [...] >> >> One of the reasons I really like Squirrelmail is the way it deals with >> mails >> containg [message/rfc822] attachments, such as mailman digests in mime >> format. Squirrel makes it really easy to open and answer single attached >> messages. >> >> But just this feature does not work when Squirrel connects to gmail... >> the >> parts of the mail are shown when opening the "main" message - the first >> attached messages are still there but the last two messages appear to be >> empty (although the contents is shown when opening the "details"). > > I don't entirely understand your explanation. Maybe a screenshot > would help. Also, if you can forward the full message source, we can > use that to try to test and see what's happening. Keep in mind that > this may be another example of Google having a slightly non-standard > IMAP implementation and if the fix is complicated, we may not be > willing to implement it.... > > Thanks for testing and feedback! [...] Well, I *do* think that it's Google who causes the problem... but anyway I would appreciate your help in finding a workaround. I have just uploaded a plain text mailfile with a mailman digest containing three single messages. Hmmm, I don't see the file here, hope it works... Accessing this file by my own uw-imap or dovecot works fine. BTW: Squirrel produces this kind of mails itself by "forward as attachment". Best regards, Uwe http://old.nabble.com/file/p27660029/test-msg test-msg -- View this message in context: http://old.nabble.com/Gmail-tp27566733p27660029.html Sent from the squirrelmail-devel mailing list archive at Nabble.com. |
From: Petrus4 <p.s...@gm...> - 2012-05-02 20:22:36
|
HI Paul, I am testing SM 1.5.1 and have noticed that the Seen Flag works from Gmail --> SM but not the other way around. Do you know of a fix for this? Paul Lesniewski wrote: > >> [...] >> >>> If we add Gmail, we need at least one Gmail-specific fix in the >>> code, wherein when FETCHing a message body, their IMAP server does not >>> set the Seen flag. The fix is simple. >>> >>> Thoughts? >> [...] >> >> I have seen this fix in the 1.5 branch already, and it can easily be >> adopted >> to earlier versions... > > It's in 1.4 as well. > >> One of the reasons I really like Squirrelmail is the way it deals with >> mails >> containg [message/rfc822] attachments, such as mailman digests in mime >> format. Squirrel makes it really easy to open and answer single attached >> messages. >> >> But just this feature does not work when Squirrel connects to gmail... >> the >> parts of the mail are shown when opening the "main" message - the first >> attached messages are still there but the last two messages appear to be >> empty (although the contents is shown when opening the "details"). > > I don't entirely understand your explanation. Maybe a screenshot > would help. Also, if you can forward the full message source, we can > use that to try to test and see what's happening. Keep in mind that > this may be another example of Google having a slightly non-standard > IMAP implementation and if the fix is complicated, we may not be > willing to implement it.... > > Thanks for testing and feedback! > > -- > Paul Lesniewski > SquirrelMail Team > Please support Open Source Software by donating to SquirrelMail! > http://squirrelmail.org/donate_paul_lesniewski.php > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > ----- > squirrelmail-devel mailing list > Posting guidelines: http://squirrelmail.org/postingguidelines > List address: squ...@li... > List archives: http://news.gmane.org/gmane.mail.squirrelmail.devel > List info (subscribe/unsubscribe/change options): > https://lists.sourceforge.net/lists/listinfo/squirrelmail-devel > > -- View this message in context: http://old.nabble.com/Gmail-tp27566733p33763393.html Sent from the squirrelmail-devel mailing list archive at Nabble.com. |
From: Petrus4 <p.s...@gm...> - 2012-05-02 20:30:58
|
HI Paul, I am testing SM 1.5.1 and have noticed that the Seen Flag works from Gmail --> SM but not the other way around. Do you know of a fix for this? Woops .. I just tested again after seeing this behaviour 4 or 5 times and now it is working as it should. strange... -- View this message in context: http://old.nabble.com/Gmail-tp27566733p33763394.html Sent from the squirrelmail-devel mailing list archive at Nabble.com. |