Menu
▾
▴
fetchmail-users
|
From: Carlos E. R. <car...@op...> - 2015-11-17 14:17:33
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I finally got my IEEE mail setup in Thunderbird. It is using a
GoogleApps account (thunderbird recognizes the ieee email address and
sets it up from data in its database, something that did not happen
previously).
I would like to set it up also using fetchmail, but I don't know if it
is possible.
The settings in Thunderbird are:
Connection security: SSL/TLS
Authentication method: OAuth2
I'm not familiar with this "OAuth2". I don't see it in "man fetchmail",
but maybe my version is old:
cer@Telcontar:~> fetchmail -V
This is fetchmail release 6.3.26+POP2+GSS+RPA+NTLM+SDPS+SSL+OPIE+NLS+KRB5.
Ideas? A link to somewhere is fine (rtfm :-) )
(notice that it is not a pure gmail account, but an ieee account using
google apps (GoogleApps@IEEE) backend. Thus setting in gmail their “less
secure authentication” option will not work, I'm afraid.)
What works is what I was doing previously: redirect mail to another
(plain) account elsewhere.
- --
Cheers,
Carlos E. R.
(from openSUSE 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlZLNvQACgkQtTMYHG2NR9VlvACZAW2qDXeOFAFlQO4Z2Nq/2sn0
E30An1ZXQN94P/zjdexFHHUMyvl6e4I2
=ClQX
-----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2015-11-18 08:23:35
|
Am 17.11.2015 um 15:17 schrieb Carlos E. R.: > I finally got my IEEE mail setup in Thunderbird. It is using a > GoogleApps account (thunderbird recognizes the ieee email address and > sets it up from data in its database, something that did not happen > previously). > > I would like to set it up also using fetchmail, but I don't know if it > is possible. > > The settings in Thunderbird are: > > Connection security: SSL/TLS > Authentication method: OAuth2 > > I'm not familiar with this "OAuth2". I don't see it in "man fetchmail", > but maybe my version is old: > > cer@Telcontar:~> fetchmail -V > This is fetchmail release 6.3.26+POP2+GSS+RPA+NTLM+SDPS+SSL+OPIE+NLS+KRB5. > > > Ideas? A link to somewhere is fine (rtfm :-) ) Fetchmail does not support OAuth2. The relevant RFC 6749, reads: > This specification is designed for use with HTTP ([RFC2616]). The > use of OAuth over any protocol other than HTTP is out of scope. <http://tools.ietf.org/html/rfc6749> First, Is configuring "access for less secure apps" on the Google end an option, and would it help? Fetchmail does not talk HTTP, and OAuth2 is breaking media. Checking Google's SASL XOAUTH2 spec, it seems we'd need to write an HTML client, a JSON parser, perhaps a cookie handler, a callback to the user (which is incompatible with cron rigging and daemon mode setups) per the "limited-input devices" MSC on https://developers.google.com/identity/protocols/OAuth2. I think the only chance is if someone provides an open-source and compatibly-licensed OAuth2 implementation including fetchmail integration code for the master branch, that has a third-party public audit report, and a sustainable plausible support offer for the OAuth2 code -- but even then I might as well steer clear of such contributions given the experience I've made with the MAPI code. MAPI was offered as a summer of code project, with moderate code quality, relying on OpenConnect and no support for integration or maintenance, and no-one ever responded with a test account I could use to complete the integration. The contributed code wouldn't even compile for me. I received two updates, but ultimately, the MAPI contribution was buried in the BRANCH_MAPI branch, without even a proper funeral. I don't like the idea of adding such complex matters to fetchmail that make it a web browser, that takes it way out of scope I'm afraid. If Google want to force you to use a browser, that's fine - only fetchmail won't be that browser. I think the utmost I'd consider is making an alternative to "plugin" but for SASL authentication, so an external command (perhaps an ECMAScript or Python or Ruby stuff) can cough up the credentials for a particular SASL dialogue. It would require someone to provide a sound design for a protocol between fetchmail and that program. |
|
From: Gene H. <ghe...@wd...> - 2015-11-18 13:01:58
|
On Wednesday 18 November 2015 03:23:25 Matthias Andree wrote: > Am 17.11.2015 um 15:17 schrieb Carlos E. R.: > > I finally got my IEEE mail setup in Thunderbird. It is using a > > GoogleApps account (thunderbird recognizes the ieee email address > > and sets it up from data in its database, something that did not > > happen previously). > > > > I would like to set it up also using fetchmail, but I don't know if > > it is possible. > > > > The settings in Thunderbird are: > > > > Connection security: SSL/TLS > > Authentication method: OAuth2 > > > > I'm not familiar with this "OAuth2". I don't see it in "man > > fetchmail", but maybe my version is old: > > > > cer@Telcontar:~> fetchmail -V > > This is fetchmail release > > 6.3.26+POP2+GSS+RPA+NTLM+SDPS+SSL+OPIE+NLS+KRB5. > > > > > > Ideas? A link to somewhere is fine (rtfm :-) ) > > Fetchmail does not support OAuth2. The relevant RFC 6749, reads: > > This specification is designed for use with HTTP ([RFC2616]). > > The use of OAuth over any protocol other than HTTP is out of scope. > > <http://tools.ietf.org/html/rfc6749> > > > First, Is configuring "access for less secure apps" on the Google end > an option, and would it help? > > > Fetchmail does not talk HTTP, and OAuth2 is breaking media. Checking > Google's SASL XOAUTH2 spec, it seems we'd need to write an HTML > client, a JSON parser, perhaps a cookie handler, a callback to the > user (which is incompatible with cron rigging and daemon mode setups) > per the "limited-input devices" MSC on > https://developers.google.com/identity/protocols/OAuth2. > > I think the only chance is if someone provides an open-source and > compatibly-licensed OAuth2 implementation including fetchmail > integration code for the master branch, that has a third-party public > audit report, and a sustainable plausible support offer for the OAuth2 > code -- but even then I might as well steer clear of such > contributions given the experience I've made with the MAPI code. > > MAPI was offered as a summer of code project, with moderate code > quality, relying on OpenConnect and no support for integration or > maintenance, and no-one ever responded with a test account I could use > to complete the integration. The contributed code wouldn't even > compile for me. I received two updates, but ultimately, the MAPI > contribution was buried in the BRANCH_MAPI branch, without even a > proper funeral. > > I don't like the idea of adding such complex matters to fetchmail that > make it a web browser, that takes it way out of scope I'm afraid. > > If Google want to force you to use a browser, that's fine - only > fetchmail won't be that browser. > > I think the utmost I'd consider is making an alternative to "plugin" > but for SASL authentication, so an external command (perhaps an > ECMAScript or Python or Ruby stuff) can cough up the credentials for a > particular SASL dialogue. It would require someone to provide a sound > design for a protocol between fetchmail and that program. > This is off-topic, but since you didn't mention it (and I no longer use it) fetchmail does (or did when I commented out that stanza) work with pop.gmail.com. Using ssl on port 995. But today I'd expect the ssl is being rejected. Enabled it, password problem. I didn't change it. pop.gmail.com has more warts than I am willing to tolerate anyway, so scrooooem. > > ---------------------------------------------------------------------- >-------- _______________________________________________ > Fetchmail-users mailing list > Fet...@li... > https://lists.sourceforge.net/lists/listinfo/fetchmail-users Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> |
|
From: Carlos E. R. <car...@op...> - 2015-11-18 16:09:31
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-18 09:23, Matthias Andree wrote: > Am 17.11.2015 um 15:17 schrieb Carlos E. R.: > > First, Is configuring "access for less secure apps" on the Google > end an option, and would it help? Maybe. I'll try. This oauth thing is new to me: other accounts I have with gmail work fine with fetchmail, so I assume that "less secure setting" is enabled, but newer accounts get it automatically. > Fetchmail does not talk HTTP, and OAuth2 is breaking media. > Checking Google's SASL XOAUTH2 spec, it seems we'd need to write an > HTML client, a JSON parser, perhaps a cookie handler, a callback to > the user (which is incompatible with cron rigging and daemon mode > setups) per the "limited-input devices" MSC on > https://developers.google.com/identity/protocols/OAuth2. ... (long quote removed) I see. Thanks for the extensive explanation :-) > If Google want to force you to use a browser, that's fine - only > fetchmail won't be that browser. No, I don't want that either! Fetchmail is a wonderful app as it is. I just was not aware of what this oauth2 is. I guess it works with Thunderbird because it has access to a browser internally. I got a pop-up message the first time with some info. I should have taken a photo. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZMoq0ACgkQtTMYHG2NR9VjAwCeMlkU5KkLTdBmkBSKQ7zAsLyK H7YAn2Qh1kY2jl3BGNL5FIV0t/dVEEVd =pPMR -----END PGP SIGNATURE----- |
|
From: Carlos E. R. <car...@op...> - 2015-11-18 16:18:53
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-17 19:52, PepeLuis wrote: > Hi Carlos, by your name, i think that you are a spanish speaker. If > this is the case, you can write me in spanish Thank you, but no need - I have few difficulties with English :-) I mean, some times I may not understand fully some expression, or I use the wrong wording. But I make do ;-) > -- OAuth2 support was introduced in Thunderbird only 4 or 5 months > ago. As far as i know, fetchmail does not support OAuth/OAuth2 > > If you want to use fetchmail, you must access to your IEEE account > by IMAP protocol. > > According to: > https://sites.google.com/a/ieee.org/gapps-help/home/universal-imap-setting > > IEEE accounts can be accesed by IMAP. Ah, thanks, I just read that. > But I think that IMAP setting is disabled by default, you must > activate it in your account, following instructions: > https://supportcenter.ieee.org/app/answers/detail/a_id/718/~/how-do-i-enable-imap-on-my-googleapps@ieee-account%3F I > see. I'll try. Mmm... I'm thinking that maybe the next hurdle will be postfix. :-} - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZMpOAACgkQtTMYHG2NR9VcmwCghIQqoh2EW5m5FO+ZAlnweUWw u48AoIN5s40ZpCBhBCKM6O9I63E4s3hM =5wlk -----END PGP SIGNATURE----- |
|
From: grarpamp <gra...@gm...> - 2015-11-19 06:45:04
|
On Wed, Nov 18, 2015 at 8:01 AM, Gene Heskett <ghe...@wd...> wrote: > pop.gmail.com. Using ssl on port 995. But today I'd expect the ssl is > being rejected. Enabled it, password problem. I didn't change it. It works fine, expect to update fingerprints often, you may get punted to the webUI once in a while, there's some "my device" toggle for that, tor works, IMAP foldering is weird, new accounts require a blood sample, new users should at least look around, technically and philosophically, before picking them as mail provider. |
|
From: Gene H. <ghe...@wd...> - 2015-11-19 07:38:51
|
On Thursday 19 November 2015 01:44:19 grarpamp wrote: > On Wed, Nov 18, 2015 at 8:01 AM, Gene Heskett <ghe...@wd...> wrote: > > pop.gmail.com. Using ssl on port 995. But today I'd expect the ssl > > is being rejected. Enabled it, password problem. I didn't change it. > > It works fine, expect to update fingerprints often, you may get punted > to the webUI once in a while, there's some "my device" toggle for > that, tor works, IMAP foldering is weird, new accounts require a blood > sample, new users should at least look around, technically and > philosophically, before picking them as mail provider. > Like I said, I don't use it anymore. Life is too short to put up with the crap gmail subjects its users to. Mine anyway. I've used up my 3 score and 10, 11 years ago. I guess that make me an old fart. Thats how I ask for the discount at a fast food place too. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> |
|
From: Carlos E. R. <car...@op...> - 2015-11-19 13:50:10
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-19 07:44, grarpamp wrote: > On Wed, Nov 18, 2015 at 8:01 AM, Gene Heskett <....@wdtv.com> wrote: >> pop.gmail.com. Using ssl on port 995. But today I'd expect the ssl is >> being rejected. Enabled it, password problem. I didn't change it. > > It works fine, expect to update fingerprints often, you may get punted to the > webUI once in a while, there's some "my device" toggle for that, tor works, > IMAP foldering is weird, new accounts require a blood sample, new users > should at least look around, technically and philosophically, before picking > them as mail provider. I have been fetching mail from two gmail accounts with fetchmail (imap) without problems, for ages: poll imap.gmail.com with interval 0 proto imap timeout 50, and tracepolls user ....@gmail.com, with password ...., is ... here, expunge 20, and ssl, and fetchall - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZN04UACgkQtTMYHG2NR9UbAwCfURYmzmPWGRdOU14jEe3eCfS+ T8kAniq27f7eZ9V0Kk89Z2vwinKZHSAC =oLyo -----END PGP SIGNATURE----- |
|
From: Carlos E. R. <car...@op...> - 2015-12-03 16:08:54
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2015-11-18 at 17:09 +0100, Carlos E. R. wrote: > On 2015-11-18 09:23, Matthias Andree wrote: >> Am 17.11.2015 um 15:17 schrieb Carlos E. R.: > > >> >> First, Is configuring "access for less secure apps" on the Google >> end an option, and would it help? > > Maybe. I'll try. This oauth thing is new to me: other accounts I have > with gmail work fine with fetchmail, so I assume that "less secure > setting" is enabled, but newer accounts get it automatically. Finally I got around to setting it up. Short answer: solved :-) Thankyou! :-) Longer answer: the setting for ieee accounts is hidden, or at least I was unable to find it. However, once opened the account at the web interface (http://email.ieee.org), try to find the setting somewhere at Settings -> Accounts and Import -> Google Account settings -> ?? I couldn't find it. Some settings are disabled by admin. However, at <https://support.google.com/accounts/answer/6010255?hl=en> there is an explanation and a direct link to <https://www.google.com/settings/security/lesssecureapps>, which works. The fetchmail setting would thus be something like this: poll imap.gmail.com with interval 0 proto imap timeout 50, and tracepolls user LO...@ie..., with password PASS, is LOCAL here, expunge 20, and ssl, keep ("keep" is for repeated testing, later remove) In case this may help someone later, here I paste a partial log: <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - 6.3.26 querying imap.gmail.com (protocol IMAP) at 2015-12-03T16:45:35 CET: poll started <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - Trying to connect to 74.125.206.109/993...connected. <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - Server certificate: <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - Issuer Organization: Google Inc <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - Issuer CommonName: Google Internet Authority G2 <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - Subject CommonName: imap.gmail.com <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - Subject Alternative Name: imap.gmail.com <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - imap.gmail.com key fingerprint: BA:04:49:B3:08:5C:E3:F3:4B:F6:4C:29:0C:4C:8B:E5 <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * OK Gimap ready for requests from 88.20.209.188 m.....wma <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP> A0001 CAPABILITY <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER AUTH=XOAUTH <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< A0001 OK Thats all she wrote! m....wma <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP> A0002 LOGIN "NA...@ie..." * <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 UIDPLUS COMPRESS=DEFLATE ENABLE MOVE CONDSTORE ESEARCH UTF8=ACCEPT LIST-EXTENDED LIST-STATUS <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< A0002 OK NA...@ie... authenticated (Success) <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP> A0003 SELECT "INBOX" <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $NotPhishing $Phishing NonJunk) <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen $NotPhishing $Phishing NonJunk \*)] Flags permitted. <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * OK [UIDVALIDITY 1] UIDs valid. <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * 381 EXISTS <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * 0 RECENT <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * OK [UIDNEXT 403] Predicted next UID. <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * OK [HIGHESTMODSEQ 35629] <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< A0003 OK [READ-WRITE] INBOX selected. (Success) <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP> A0004 SEARCH UNSEEN UNDELETED <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< * SEARCH 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 266 267 268 269 270 271 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 354 355 356 357 358 361 364 365 366 368 369 370 371 372 378 379 380 381 <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - IMAP< A0004 OK SEARCH completed (Success) <2.6> 2015-12-03 16:45:35 Telcontar fetchmail 15176 - - 381 messages (26 seen) for NA...@ie... at imap.gmail.com. ... (cut) - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZgaQkACgkQtTMYHG2NR9UiFQCfQy3Xxw7tYFKSmcELusQFv8qf dKgAoIAESgXHlmW7fAuyQvZA8XscFQMD =VeQU -----END PGP SIGNATURE----- |
|
From: Matthias A. <mat...@gm...> - 2015-12-04 01:17:25
|
Am 03.12.2015 um 17:08 schrieb Carlos E. R.: > > > On Wednesday, 2015-11-18 at 17:09 +0100, Carlos E. R. wrote: >> On 2015-11-18 09:23, Matthias Andree wrote: >>> Am 17.11.2015 um 15:17 schrieb Carlos E. R.: > > >>> >>> First, Is configuring "access for less secure apps" on the Google >>> end an option, and would it help? > >> Maybe. I'll try. This oauth thing is new to me: other accounts I have >> with gmail work fine with fetchmail, so I assume that "less secure >> setting" is enabled, but newer accounts get it automatically. > > Finally I got around to setting it up. Short answer: solved :-) > > Thankyou! :-) Thanks for the feedback, I have added a paragraph to <http://www.fetchmail.info/fetchmail-FAQ.html#I9>. I also figured that Google seems to have added a few settings so that people can model Google's behaviour more towards how POP3 and IMAP4rev1 were originally conceived. That would be in GMail's Settings -> Forwarding and POP/IMAP: POP Download: 1. Enable POP for *all* mail 2. When messages are accessed with POP: [keep Gmail's copy in the Inbox] IMAP Access: * Status: Enable IMAP * When I mark a message in IMAP as deleted: (*) Auto-Expunge off - Wait for the client to update the server * When a message is marked as deleted and expunged from the last visible IMAP folder: (*) Immediately delete the message forever * Folder Size Limits: (*) Do not limit... |
|
From: Carlos E. R. <car...@op...> - 2015-12-04 14:45:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-12-04 02:17, Matthias Andree wrote: > > Thanks for the feedback, I have added a paragraph to > <http://www.fetchmail.info/fetchmail-FAQ.html#I9>. :-) This page contains general info about enabling IMAP on gmail: https://support.google.com/mail/answer/77695# This other is specific for ieee users, but the info might help others "Gapp" users (google app users): https://sites.google.com/a/ieee.org/gapps-help/home/universal-imap-setting > I also figured that Google seems to have added a few settings so > that people can model Google's behaviour more towards how POP3 and > IMAP4rev1 were originally conceived. > > That would be in GMail's Settings -> Forwarding and POP/IMAP: > > POP Download: 1. Enable POP for *all* mail 2. When messages are > accessed with POP: [keep Gmail's copy in the Inbox] > > IMAP Access: * Status: Enable IMAP * When I mark a message in IMAP > as deleted: (*) Auto-Expunge off - Wait for the client to update > the server * When a message is marked as deleted and expunged from > the last visible IMAP folder: (*) Immediately delete the message > forever * Folder Size Limits: (*) Do not limit... Ah, yes. Although I don't "immediately delete". I often access email with Thunderbird, too, seems better to not delete immediately, dunno. I find imap more reliable with gmail and fetchmail. With 'pop3' it is more difficult to detect seen mail, it is possible to fetch again thousands of past mails. I don't have any problem with fetchmail to get gmail posts via imap from several accounts, for some years. Works perfect here :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZhpwwACgkQtTMYHG2NR9WWJACdE18cVEs6TL+H74XradLKa9D7 zCIAoIeZwF4egZD3P/ZmuzweRiKsmnY5 =tdXN -----END PGP SIGNATURE----- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X