Menu
▾
▴
fetchmail-users — User questions and discussion
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(16) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(8) |
Aug
(21) |
Sep
(17) |
Oct
(35) |
Nov
(39) |
Dec
(55) |
| 2006 |
Jan
(70) |
Feb
(11) |
Mar
(55) |
Apr
(27) |
May
(73) |
Jun
(47) |
Jul
(63) |
Aug
(27) |
Sep
(52) |
Oct
(39) |
Nov
(87) |
Dec
(15) |
| 2007 |
Jan
(23) |
Feb
(46) |
Mar
(108) |
Apr
(63) |
May
(54) |
Jun
(34) |
Jul
(29) |
Aug
(103) |
Sep
(46) |
Oct
(69) |
Nov
(29) |
Dec
(17) |
| 2008 |
Jan
(45) |
Feb
(32) |
Mar
(25) |
Apr
(17) |
May
(39) |
Jun
(20) |
Jul
(64) |
Aug
(31) |
Sep
(38) |
Oct
(20) |
Nov
(42) |
Dec
(50) |
| 2009 |
Jan
(10) |
Feb
(38) |
Mar
(3) |
Apr
(29) |
May
(41) |
Jun
(31) |
Jul
(21) |
Aug
(53) |
Sep
(49) |
Oct
(26) |
Nov
(28) |
Dec
(15) |
| 2010 |
Jan
(83) |
Feb
(38) |
Mar
(33) |
Apr
(44) |
May
(9) |
Jun
(16) |
Jul
(35) |
Aug
(38) |
Sep
(11) |
Oct
(35) |
Nov
(68) |
Dec
(19) |
| 2011 |
Jan
(16) |
Feb
(69) |
Mar
(42) |
Apr
(54) |
May
(56) |
Jun
(29) |
Jul
|
Aug
(65) |
Sep
(3) |
Oct
(39) |
Nov
(33) |
Dec
(4) |
| 2012 |
Jan
(31) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(38) |
Jun
(39) |
Jul
(14) |
Aug
(31) |
Sep
(8) |
Oct
(32) |
Nov
(12) |
Dec
(16) |
| 2013 |
Jan
(40) |
Feb
(22) |
Mar
(21) |
Apr
(15) |
May
(13) |
Jun
(9) |
Jul
(34) |
Aug
(10) |
Sep
(10) |
Oct
|
Nov
(7) |
Dec
(1) |
| 2014 |
Jan
(25) |
Feb
(9) |
Mar
(8) |
Apr
(12) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(27) |
Oct
(25) |
Nov
(18) |
Dec
(3) |
| 2015 |
Jan
(18) |
Feb
(13) |
Mar
(4) |
Apr
(19) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(6) |
Oct
(4) |
Nov
(19) |
Dec
(6) |
| 2016 |
Jan
|
Feb
(8) |
Mar
(14) |
Apr
|
May
(11) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(17) |
Feb
(35) |
Mar
|
Apr
(4) |
May
(8) |
Jun
(2) |
Jul
(16) |
Aug
|
Sep
(5) |
Oct
(11) |
Nov
(15) |
Dec
(10) |
| 2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
|
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(14) |
Mar
(33) |
Apr
(17) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
(22) |
Oct
(13) |
Nov
|
Dec
|
| 2020 |
Jan
(36) |
Feb
(19) |
Mar
(31) |
Apr
(2) |
May
(22) |
Jun
(7) |
Jul
(25) |
Aug
(9) |
Sep
(17) |
Oct
(52) |
Nov
(13) |
Dec
(9) |
| 2021 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(15) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(23) |
Sep
(3) |
Oct
(8) |
Nov
(28) |
Dec
(9) |
| 2022 |
Jan
(38) |
Feb
(2) |
Mar
(56) |
Apr
(24) |
May
(29) |
Jun
(22) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2024 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(10) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
(1) |
Nov
|
Dec
|
|
From: Ralph C. <ra...@in...> - 2019-03-12 15:26:23
|
Hi,
I've just added another host and user to my .fetchmailrc.
poll foo via mail.foo.example proto pop3
user "ralph@foo.example" is ralph password "letmein"
ssl sslcertck sslproto "TLS1" sslcommonname "bar.foo.example"
`fetchmail -c foo' successfully establishes a TLS1.2 connection, but
after a flurry of encrypted application data, `Encrypted Alert' packets
are exchanged and the connection closed. Dropping the -c gives the same
behaviour. If I keep -c and change "TLS1" to "SSL23" then it doesn't
happen
tshark(1) shows
client → server TCP 74 55162 → 995 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 SACK_PERM=1 TSval=2667494347 TSecr=0 WS=128
server → client TCP 74 995 → 55162 [SYN, ACK] Seq=0 Ack=1 Win=28960 Len=0 MSS=1460 SACK_PERM=1 TSval=1576881705 TSecr=2667494347 WS=128
client → server TCP 66 55162 → 995 [ACK] Seq=1 Ack=1 Win=64256 Len=0 TSval=2667494357 TSecr=1576881705
client → server TLSv1 583 Client Hello
server → client TCP 66 995 → 55162 [ACK] Seq=1 Ack=518 Win=30080 Len=0 TSval=1576881772 TSecr=2667494403
server → client TLSv1.2 1506 Server Hello
client → server TCP 66 55162 → 995 [ACK] Seq=518 Ack=1441 Win=64128 Len=0 TSval=2667494427 TSecr=1576881774
server → client TCP 1506 995 → 55162 [ACK] Seq=1441 Ack=518 Win=30080 Len=1440 TSval=1576881774 TSecr=2667494403 [TCP segment of a reassembled PDU]
client → server TCP 66 55162 → 995 [ACK] Seq=518 Ack=2881 Win=64128 Len=0 TSval=2667494428 TSecr=1576881774
server → client TCP 1506 995 → 55162 [ACK] Seq=2881 Ack=518 Win=30080 Len=1440 TSval=1576881774 TSecr=2667494403 [TCP segment of a reassembled PDU]
client → server TCP 66 55162 → 995 [ACK] Seq=518 Ack=4321 Win=64128 Len=0 TSval=2667494430 TSecr=1576881774
server → client TLSv1.2 710 Certificate, Server Key Exchange, Server Hello Done
client → server TCP 66 55162 → 995 [ACK] Seq=518 Ack=4965 Win=64128 Len=0 TSval=2667494430 TSecr=1576881774
client → server TLSv1.2 192 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
server → client TLSv1.2 292 New Session Ticket, Change Cipher Spec, Encrypted Handshake Message
client → server TCP 66 55162 → 995 [ACK] Seq=644 Ack=5191 Win=64128 Len=0 TSval=2667494490 TSecr=1576881797
server → client TLSv1.2 115 Application Data
client → server TCP 66 55162 → 995 [ACK] Seq=644 Ack=5240 Win=64128 Len=0 TSval=2667494501 TSecr=1576881849
client → server TLSv1.2 101 Application Data
server → client TLSv1.2 184 Application Data
client → server TLSv1.2 141 Application Data
server → client TLSv1.2 100 Application Data
client → server TLSv1.2 114 Application Data
server → client TLSv1.2 111 Application Data
client → server TLSv1.2 101 Application Data
server → client TLSv1.2 104 Application Data
client → server TLSv1.2 101 Application Data
server → client TLSv1.2 113 Application Data
server → client TLSv1.2 97 Encrypted Alert
client → server TLSv1.2 97 Encrypted Alert
client → server TCP 66 55162 → 995 [RST, ACK] Seq=903 Ack=5554 Win=64128 Len=0 TSval=2667494589 TSecr=1576881935
server → client TCP 60 995 → 55162 [RST] Seq=5554 Win=0 Len=0
Using s_client(1), I see the server is Dovecot.
Anyone have ideas as to the cause?
--
Cheers, Ralph.
|
|
From: Gene H. <ghe...@sh...> - 2019-03-06 19:59:34
|
On Wednesday 06 March 2019 13:42:48 sup...@gm... wrote: > On Wednesday, 6 March 2019 18:13:51 GMT Gene Heskett wrote: > > On Wednesday 06 March 2019 12:09:21 sup...@gm... wrote: > > > On Wednesday, 6 March 2019 16:31:27 GMT Gene Heskett wrote: > > > > On Wednesday 06 March 2019 05:37:32 Matthias Andree wrote: > > > > > Am 06.03.19 um 05:48 schrieb Globe Trotter via Fetchmail-users: > > > > > > Thank you very much. I find Yahoo Mail reponse settings to > > > > > > be very difficult to handle/change. I will see if I can > > > > > > switch my e-mail accounts. Till then, I will respond using > > > > > > top-posting I guess. > > > > > > > > > > No you don't. If you find the webmail interface is getting in > > > > > your way, don't use it. Yahoo offers IMAP access AFAICT. > > > > > > > > > > Please fix your mail setup *before* you post again. > > > > > > > > > > (I wonder why people especially on a fetchmail list would > > > > > resort to using crappy webmail interfaces.) > > > > > > > > Good question. Boggles the mind a bit. > > > > > > > > > _______________________________________________ > > > > > Fetchmail-users mailing list > > > > > Fet...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/fetchmail-users > > > > > > > > Cheers, Gene Heskett > > > > > > Because their fetchmail is broken? > > > > No, because while the info to fix it is I believe contained in this > > thread, the OP hasn't fixed it yet. I am a member of a couple yahoo > > groups, and peoples inability to learn that the arrow keys on their > > keyboards will put the curser nearly anyplace in the message so they > > can type their reply so as to create the email according to list > > customs or even the RFC's is what boggles what little mind I have > > left at my age. > > > > We won't get into just how broken the yahoo web mail is, its a well > > established fact, and will not be fixed because Marisa fired all the > > tech help 2+ years ago. And so far, kmail here has not been given > > any problems submitting to those groups thru the server at my ISP. > > Sucking from them is entirely at my ISP's discretion because I > > actually pull from Shentels dovecot server, not yahoo's. Thats what > > ISP's are for. Isn't it? > > > > Cheers, Gene Heskett > > TLDR! let's be a little less grumpy please > Chuckle, at my years, both sides of the bed are the wrong side. You will also learn that but it might take another 60 years. :) > > > > _______________________________________________ > 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: <sup...@gm...> - 2019-03-06 18:43:00
|
On Wednesday, 6 March 2019 18:13:51 GMT Gene Heskett wrote: > On Wednesday 06 March 2019 12:09:21 sup...@gm... wrote: > > On Wednesday, 6 March 2019 16:31:27 GMT Gene Heskett wrote: > > > On Wednesday 06 March 2019 05:37:32 Matthias Andree wrote: > > > > Am 06.03.19 um 05:48 schrieb Globe Trotter via Fetchmail-users: > > > > > Thank you very much. I find Yahoo Mail reponse settings to be > > > > > very difficult to handle/change. I will see if I can switch my > > > > > e-mail accounts. Till then, I will respond using top-posting I > > > > > guess. > > > > > > > > No you don't. If you find the webmail interface is getting in your > > > > way, don't use it. Yahoo offers IMAP access AFAICT. > > > > > > > > Please fix your mail setup *before* you post again. > > > > > > > > (I wonder why people especially on a fetchmail list would resort > > > > to using crappy webmail interfaces.) > > > > > > Good question. Boggles the mind a bit. > > > > > > > _______________________________________________ > > > > Fetchmail-users mailing list > > > > Fet...@li... > > > > https://lists.sourceforge.net/lists/listinfo/fetchmail-users > > > > > > Cheers, Gene Heskett > > > > Because their fetchmail is broken? > > No, because while the info to fix it is I believe contained in this > thread, the OP hasn't fixed it yet. I am a member of a couple yahoo > groups, and peoples inability to learn that the arrow keys on their > keyboards will put the curser nearly anyplace in the message so they can > type their reply so as to create the email according to list customs or > even the RFC's is what boggles what little mind I have left at my age. > > We won't get into just how broken the yahoo web mail is, its a well > established fact, and will not be fixed because Marisa fired all the > tech help 2+ years ago. And so far, kmail here has not been given any > problems submitting to those groups thru the server at my ISP. Sucking > from them is entirely at my ISP's discretion because I actually pull > from Shentels dovecot server, not yahoo's. Thats what ISP's are for. > Isn't it? > > Cheers, Gene Heskett TLDR! let's be a little less grumpy please |
|
From: Gene H. <ghe...@sh...> - 2019-03-06 18:14:00
|
On Wednesday 06 March 2019 12:09:21 sup...@gm... wrote: > On Wednesday, 6 March 2019 16:31:27 GMT Gene Heskett wrote: > > On Wednesday 06 March 2019 05:37:32 Matthias Andree wrote: > > > Am 06.03.19 um 05:48 schrieb Globe Trotter via Fetchmail-users: > > > > Thank you very much. I find Yahoo Mail reponse settings to be > > > > very difficult to handle/change. I will see if I can switch my > > > > e-mail accounts. Till then, I will respond using top-posting I > > > > guess. > > > > > > No you don't. If you find the webmail interface is getting in your > > > way, don't use it. Yahoo offers IMAP access AFAICT. > > > > > > Please fix your mail setup *before* you post again. > > > > > > (I wonder why people especially on a fetchmail list would resort > > > to using crappy webmail interfaces.) > > > > Good question. Boggles the mind a bit. > > > > > _______________________________________________ > > > Fetchmail-users mailing list > > > Fet...@li... > > > https://lists.sourceforge.net/lists/listinfo/fetchmail-users > > > > Cheers, Gene Heskett > > Because their fetchmail is broken? > No, because while the info to fix it is I believe contained in this thread, the OP hasn't fixed it yet. I am a member of a couple yahoo groups, and peoples inability to learn that the arrow keys on their keyboards will put the curser nearly anyplace in the message so they can type their reply so as to create the email according to list customs or even the RFC's is what boggles what little mind I have left at my age. We won't get into just how broken the yahoo web mail is, its a well established fact, and will not be fixed because Marisa fired all the tech help 2+ years ago. And so far, kmail here has not been given any problems submitting to those groups thru the server at my ISP. Sucking from them is entirely at my ISP's discretion because I actually pull from Shentels dovecot server, not yahoo's. Thats what ISP's are for. Isn't it? 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: <sup...@gm...> - 2019-03-06 17:09:32
|
On Wednesday, 6 March 2019 16:31:27 GMT Gene Heskett wrote: > On Wednesday 06 March 2019 05:37:32 Matthias Andree wrote: > > Am 06.03.19 um 05:48 schrieb Globe Trotter via Fetchmail-users: > > > Thank you very much. I find Yahoo Mail reponse settings to be very > > > difficult to handle/change. I will see if I can switch my e-mail > > > accounts. Till then, I will respond using top-posting I guess. > > > > No you don't. If you find the webmail interface is getting in your > > way, don't use it. Yahoo offers IMAP access AFAICT. > > > > Please fix your mail setup *before* you post again. > > > > (I wonder why people especially on a fetchmail list would resort to > > using crappy webmail interfaces.) > > Good question. Boggles the mind a bit. > > > _______________________________________________ > > Fetchmail-users mailing list > > Fet...@li... > > https://lists.sourceforge.net/lists/listinfo/fetchmail-users > > Cheers, Gene Heskett Because their fetchmail is broken? |
|
From: Gene H. <ghe...@sh...> - 2019-03-06 16:31:35
|
On Wednesday 06 March 2019 05:37:32 Matthias Andree wrote: > Am 06.03.19 um 05:48 schrieb Globe Trotter via Fetchmail-users: > > Thank you very much. I find Yahoo Mail reponse settings to be very > > difficult to handle/change. I will see if I can switch my e-mail > > accounts. Till then, I will respond using top-posting I guess. > > No you don't. If you find the webmail interface is getting in your > way, don't use it. Yahoo offers IMAP access AFAICT. > > Please fix your mail setup *before* you post again. > > (I wonder why people especially on a fetchmail list would resort to > using crappy webmail interfaces.) > Good question. Boggles the mind a bit. > > _______________________________________________ > 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: Matthias A. <mat...@gm...> - 2019-03-06 15:03:56
|
Am 06.03.19 um 12:57 schrieb Ralph Corderoy: > Hi Matthias, > >> (I wonder why people especially on a fetchmail list would resort to >> using crappy webmail interfaces.) > Perhaps he has to resort to that until he can get fetchmail working > again with OAuth2? :-) > Yahoo has this misleadingly named "less secure app" switch, too. |
|
From: Ralph C. <ra...@in...> - 2019-03-06 11:58:05
|
Hi Matthias, > (I wonder why people especially on a fetchmail list would resort to > using crappy webmail interfaces.) Perhaps he has to resort to that until he can get fetchmail working again with OAuth2? :-) -- Cheers, Ralph. |
|
From: Matthias A. <mat...@gm...> - 2019-03-06 10:37:41
|
Am 06.03.19 um 05:48 schrieb Globe Trotter via Fetchmail-users: > Thank you very much. I find Yahoo Mail reponse settings to be very difficult to handle/change. I will see if I can switch my e-mail accounts. Till then, I will respond using top-posting I guess. No you don't. If you find the webmail interface is getting in your way, don't use it. Yahoo offers IMAP access AFAICT. Please fix your mail setup *before* you post again. (I wonder why people especially on a fetchmail list would resort to using crappy webmail interfaces.) |
|
From: Globe T. <its...@ya...> - 2019-03-06 04:48:50
|
Thank you very much. I find Yahoo Mail reponse settings to be very difficult to handle/change. I will see if I can switch my e-mail accounts. Till then, I will respond using top-posting I guess. I very much appreciate your and Matthias's points here and am very thankful for all the help that you have provided so far. Best wishes! On Tuesday, March 5, 2019, 8:36:53 PM CST, Carlos E. R. <rob...@te...> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Content-ID: <alp...@mi...linor> El 2019-03-04 a las 16:47 -0000, Globe Trotter via Fetchmail-users escribió: > On Monday, March 4, 2019, 7:18:01 AM CST, Ralph Corderoy <...@inputplus.co.uk> wrote: Globe Trotter, I don't know what mail program you are using, but it is broken. Please use another. First, the text of the post to which you are replying to must have each line preceded by '>' that both humans and machines know it is from previous emails. (and lines that already start with '>' should get added one more '>') Second, you can not have a line starting with "-- " and then write your answer below it, because normal mail programs think that is your signature, paint it in another colour, and remove it (everything after the line) when replying. A good mail program would have either removed the previouse signature or preceded it with the '>' symbol. This is the same thing Matthias Andree told you, in more words :-) If this is the doing of yahoo webmail, then either don't use it, or add the required symbols manually yourself. Thank you! Otherwise, both reading your replies and answering is more difficult for others. - -- Cheers Carlos E. R. (from openSUSE Leap 15.0 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXH8yBRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcy5kA/2L5WCMvTjLCChOtUCUs oJGMZOsj/3qNvaYZrGxAF/uEAP9syyoTWaC+eLXCU11FFGFRHAXsQZVm26MaKSzE z8tQOA== =K6/r -----END PGP SIGNATURE----- _______________________________________________ Fetchmail-users mailing list Fet...@li... https://lists.sourceforge.net/lists/listinfo/fetchmail-users |
|
From: Carlos E. R. <rob...@te...> - 2019-03-06 02:36:19
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Content-ID: <alp...@mi...linor>
El 2019-03-04 a las 16:47 -0000, Globe Trotter via Fetchmail-users escribió:
> On Monday, March 4, 2019, 7:18:01 AM CST, Ralph Corderoy <...@inputplus.co.uk> wrote:
Globe Trotter,
I don't know what mail program you are using, but it is broken. Please use
another.
First, the text of the post to which you are replying to must have each
line preceded by '>' that both humans and machines know it is from
previous emails.
(and lines that already start with '>' should get added one more '>')
Second, you can not have a line starting with "-- " and then write your
answer below it, because normal mail programs think that is your
signature, paint it in another colour, and remove it (everything
after the line) when replying.
A good mail program would have either removed the previouse signature or
preceded it with the '>' symbol.
This is the same thing Matthias Andree told you, in more words :-)
If this is the doing of yahoo webmail, then either don't use it, or add
the required symbols manually yourself.
Thank you!
Otherwise, both reading your replies and answering is more difficult for
others.
- --
Cheers
Carlos E. R.
(from openSUSE Leap 15.0 x86_64 (Minas Tirith))
-----BEGIN PGP SIGNATURE-----
iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCXH8yBRwccm9iaW4ubGlz
dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcy5kA/2L5WCMvTjLCChOtUCUs
oJGMZOsj/3qNvaYZrGxAF/uEAP9syyoTWaC+eLXCU11FFGFRHAXsQZVm26MaKSzE
z8tQOA==
=K6/r
-----END PGP SIGNATURE-----
|
|
From: Matthias A. <mat...@gm...> - 2019-03-04 17:07:35
|
Am 04.03.19 um 14:08 schrieb Ralph Corderoy: > Hi Globe, > >>> It's from yacc(1), which may be provided by bison(1) on your system. >>> I'm guessing `%destructor' is not understood by your yacc or bison. >> Thanks! How do I fix it? > Matthias has since said bison is required so have ./configure prefer > bison over byacc. I now see README.git says bison is required. > Arguably, the configure script shouldn't settle for byacc if it's not > suitable. > > If ./configure doesn't allow that, then consider temporarily > uninstalling the byacc package. > Configure should automatically prefer Bison over Yacc; in doubt, "rm -f config.cache" and then re-configure. Quoting autoconf.info on Fedora Linux 29 (autoconf 2.69): > -- Macro: AC_PROG_YACC > If `bison' is found, set output variable `YACC' to `bison -y'. > Otherwise, if `byacc' is found, set `YACC' to `byacc'. Otherwise > set `YACC' to `yacc'. The result of this test can be influenced > by setting the variable `YACC' or the cache variable > `ac_cv_prog_YACC'. |
|
From: Matthias A. <mat...@gm...> - 2019-03-04 17:06:00
|
Globe Trotter, Please pay attention to your quoting and replies. Do not put your answer inside or below the signature. |
|
From: Globe T. <its...@ya...> - 2019-03-04 16:47:42
|
On Monday, March 4, 2019, 7:18:01 AM CST, Ralph Corderoy <ra...@in...> wrote:
Hi Globe,
> > It's from yacc(1), which may be provided by bison(1) on your system.
> > I'm guessing `%destructor' is not understood by your yacc or bison.
>
> Thanks! How do I fix it?
Matthias has since said bison is required so have ./configure prefer
bison over byacc. I now see README.git says bison is required.
Arguably, the configure script shouldn't settle for byacc if it's not
suitable.
If ./configure doesn't allow that, then consider temporarily
uninstalling the byacc package.
--
Cheers, Ralph.
Thanks! I will try this. The installation instructions from the github download said that I should have a working yacc so I installed it. It appears to not be needed. I will correct this and test. Thanks again!
|
|
From: Ralph C. <ra...@in...> - 2019-03-04 13:18:07
|
Hi Globe, > > It's from yacc(1), which may be provided by bison(1) on your system. > > I'm guessing `%destructor' is not understood by your yacc or bison. > > Thanks! How do I fix it? Matthias has since said bison is required so have ./configure prefer bison over byacc. I now see README.git says bison is required. Arguably, the configure script shouldn't settle for byacc if it's not suitable. If ./configure doesn't allow that, then consider temporarily uninstalling the byacc package. -- Cheers, Ralph. |
|
From: Globe T. <its...@ya...> - 2019-03-04 12:59:25
|
On Sunday, March 3, 2019, 4:07:59 AM CST, Ralph Corderoy <ra...@in...> wrote:
Hi Globe,
> /bin/sh ./ylwrap rcfile_y.y y.tab.c rcfile_y.c y.tab.h `echo rcfile_y.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output rcfile_y.output -- yacc -d
> yacc: e - line 85 of "/home/Downloads/fetchmail-git-78304ad9cb94fb3baa50819f2d529937f5f0052e/rcfile_y.y", syntax error
> %destructor { free ($$); } STRING
> ^
> make: *** [Makefile:1282: rcfile_y.c] Error 1
>
> What is the syntax error from? How do I fix it?
It's from yacc(1), which may be provided by bison(1) on your system.
I'm guessing `%destructor' is not understood by your yacc or bison.
--
Cheers, Ralph.
Ralph,
Thanks! How do I fix it?
Best wishes.
|
|
From: Matthias A. <mat...@gm...> - 2019-03-04 11:03:51
|
Am 03.03.19 um 14:27 schrieb Globe Trotter via Fetchmail-users: > HI, Thanks! yacc on Fedora 29 is provided by byacc. My version of byacc is: > Name : byacc > Version : 1.9.20170709 > Release : 6.fc29 > Architecture : x86_64 > Size : 252 k > Source : byacc-1.9.20170709-6.fc29.src.rpm > > and my version of bison-devel is: > > Name : bison-devel > Version : 3.0.5 > Release : 1.fc29 > Architecture : x86_64 > Size : 40 k > Source : bison-3.0.5-1.fc29.src.rpm Use GNU Bison. Fetchmail doesn't build with Yacc. |
|
From: Globe T. <its...@ya...> - 2019-03-03 13:28:04
|
HI, Thanks! yacc on Fedora 29 is provided by byacc. My version of byacc is:
Name : byacc
Version : 1.9.20170709
Release : 6.fc29
Architecture : x86_64
Size : 252 k
Source : byacc-1.9.20170709-6.fc29.src.rpm
and my version of bison-devel is:
Name : bison-devel
Version : 3.0.5
Release : 1.fc29
Architecture : x86_64
Size : 40 k
Source : bison-3.0.5-1.fc29.src.rpm
Thanks again!
On Sunday, March 3, 2019, 4:07:59 AM CST, Ralph Corderoy <ra...@in...> wrote:
Hi Globe,
> /bin/sh ./ylwrap rcfile_y.y y.tab.c rcfile_y.c y.tab.h `echo rcfile_y.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output rcfile_y.output -- yacc -d
> yacc: e - line 85 of "/home/Downloads/fetchmail-git-78304ad9cb94fb3baa50819f2d529937f5f0052e/rcfile_y.y", syntax error
> %destructor { free ($$); } STRING
> ^
> make: *** [Makefile:1282: rcfile_y.c] Error 1
>
> What is the syntax error from? How do I fix it?
It's from yacc(1), which may be provided by bison(1) on your system.
I'm guessing `%destructor' is not understood by your yacc or bison.
--
Cheers, Ralph.
|
|
From: Globe T. <its...@ya...> - 2019-03-03 13:27:26
|
Hi,
Thanks! I am on Fedora 29 which uses:
Name : byacc
Version : 1.9.20170709
Release : 6.fc29
Architecture : x86_64
Size : 252 k
Source : byacc-1.9.20170709-6.fc29.src.rpm
Is there a more recent version?
Many thanks!
On Sunday, March 3, 2019, 6:19:52 AM CST, Jerry <je...@se...> wrote:
On Sat, 2 Mar 2019 22:51:44 +0000 (UTC), Globe Trotter via
Fetchmail-users stated:
> I was trying to compile the version of fetchmail and I had the
> following questions:
>1. Is any option needed to get the contributed OAuth2 support working?
>Any option in the configure script. 2. I configured with
>
>./configure --with-ssl
>
>and everything went without a hitch.
>But when I tried to make, I got:
>/bin/sh ./ylwrap rcfile_y.y y.tab.c rcfile_y.c y.tab.h `echo
>rcfile_y.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e
>s/c++$/h++/ -e s/c$/h/` y.output rcfile_y.output -- yacc -d yacc: e -
>line 85 of
>"/home/Downloads/fetchmail-git-78304ad9cb94fb3baa50819f2d529937f5f0052e/rcfile_y.y",
>syntax error %destructor { free ($$); } STRING ^ make: ***
>[Makefile:1282: rcfile_y.c] Error 1
>
>What is the syntax error from? How do I fix it?
What version of "yacc" are you using?
--
Jerry
|
|
From: Jerry <je...@se...> - 2019-03-03 12:49:15
|
On Sat, 2 Mar 2019 22:51:44 +0000 (UTC), Globe Trotter via
Fetchmail-users stated:
> I was trying to compile the version of fetchmail and I had the
> following questions:
>1. Is any option needed to get the contributed OAuth2 support working?
>Any option in the configure script. 2. I configured with
>
>./configure --with-ssl
>
>and everything went without a hitch.
>But when I tried to make, I got:
>/bin/sh ./ylwrap rcfile_y.y y.tab.c rcfile_y.c y.tab.h `echo
>rcfile_y.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e
>s/c++$/h++/ -e s/c$/h/` y.output rcfile_y.output -- yacc -d yacc: e -
>line 85 of
>"/home/Downloads/fetchmail-git-78304ad9cb94fb3baa50819f2d529937f5f0052e/rcfile_y.y",
>syntax error %destructor { free ($$); } STRING ^ make: ***
>[Makefile:1282: rcfile_y.c] Error 1
>
>What is the syntax error from? How do I fix it?
What version of "yacc" are you using?
--
Jerry
|
|
From: Ralph C. <ra...@in...> - 2019-03-03 10:08:06
|
Hi Globe,
> /bin/sh ./ylwrap rcfile_y.y y.tab.c rcfile_y.c y.tab.h `echo rcfile_y.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output rcfile_y.output -- yacc -d
> yacc: e - line 85 of "/home/Downloads/fetchmail-git-78304ad9cb94fb3baa50819f2d529937f5f0052e/rcfile_y.y", syntax error
> %destructor { free ($$); } STRING
> ^
> make: *** [Makefile:1282: rcfile_y.c] Error 1
>
> What is the syntax error from? How do I fix it?
It's from yacc(1), which may be provided by bison(1) on your system.
I'm guessing `%destructor' is not understood by your yacc or bison.
--
Cheers, Ralph.
|
|
From: Globe T. <its...@ya...> - 2019-03-02 22:51:57
|
I was trying to compile the version of fetchmail and I had the following questions:
1. Is any option needed to get the contributed OAuth2 support working? Any option in the configure script.
2. I configured with
./configure --with-ssl
and everything went without a hitch.
But when I tried to make, I got:
/bin/sh ./ylwrap rcfile_y.y y.tab.c rcfile_y.c y.tab.h `echo rcfile_y.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e s/c++$/h++/ -e s/c$/h/` y.output rcfile_y.output -- yacc -d
yacc: e - line 85 of "/home/Downloads/fetchmail-git-78304ad9cb94fb3baa50819f2d529937f5f0052e/rcfile_y.y", syntax error
%destructor { free ($$); } STRING
^
make: *** [Makefile:1282: rcfile_y.c] Error 1
What is the syntax error from? How do I fix it?
Thanks!
On Thursday, February 28, 2019, 2:55:09 PM CST, Globe Trotter via Fetchmail-users <fet...@li...> wrote:
Hi,
I am very grateful to you for pointing this out to me. I have downloaded the master branch and will compile and try out. But before that, would you or anyone else know of an example .fetchmailrc for how to modify the lines to accommodate this support? How do the lines change to use the token?
Many thanks again!
On Wednesday, February 27, 2019, 5:44:20 PM CST, Matthias Andree <mat...@gm...> wrote:
Am 27.02.19 um 07:14 schrieb Globe Trotter via Fetchmail-users:
> but I was hoping (and wondering how) to continue to use fetchmail. I found this webpage: Setting Up OAUTH2 Support for Fetchmail and Postfix but I am having trouble figuring out how to specify tokens. We do not have password two-factor authentication.
There is contributed OAuth2 suppor OAuth2 suppor OAuth2 support in the "master" branch in Git, see
https://gitlab.com/fetchmail/fetchmail/commits/master/contrib/README - I
haven't tested it. Feedback solicited.
_______________________________________________
Fetchmail-users mailing list
Fet...@li...
https://lists.sourceforge.net/lists/listinfo/fetchmail-users
_______________________________________________
Fetchmail-users mailing list
Fet...@li...
https://lists.sourceforge.net/lists/listinfo/fetchmail-users
|
|
From: mario c. <ml...@ma...> - 2019-03-02 17:14:04
|
Hi ok, I'll report on the courier ml and update thanks for your help mario On Sat, 2019-03-02 at 11:04 +0000, Ralph Corderoy wrote: > Hi mario, > > > reading message my...@my...@pop3.mydomain.net:1 of 1 (3054 octets) > > About to rewrite Return-Path: <>... > > ...rewritten version is Return-Path: <>. > > About to rewrite From: <myf...@re...>... > > ...rewritten version is From: <myf...@re...>. > > About to rewrite To: <my...@my...>... > > ...rewritten version is To: <my...@my...>. > > fetchmail: about to deliver with: /usr/lib/courier/bin/sendmail -i -f > > '<>' -- 'my...@my...' > > #****************************517 Syntax error. > > ***********.*********************** > > fetchmail: Error writing to MDA: Broken pipe not flushed > > fetchmail: POP3> QUIT > > fetchmail: POP3< +OK Logging out. > > So it's Courier's sendmail that's giving the `517 Syntax error'. > Google suggests this is quite common. > https://www.courier-mta.org/FAQ.html#esmtperr explicitly mentions 517. > http://courier-mail-server.10983.n7.nabble.com/More-information-re-517-syntax-error-td3484.html > suggests local configuration can play a part if Courier has to make up > an email address. > > The typical cause seems to be an email address with just a hostname, > i.e. not `.' after the `@'. If Courier's logs don't help pin-point the > problem then you may have to > > strace -ffe %desc -s 4096 -o st fetchmail ...your-normal-arguments > > and then look at st.* afterwards. Search for `517' and you'll find the > error message from Courier as it's read by fetchmail. See what was > being given to Courier in the run up to that. > |
|
From: Ralph C. <ra...@in...> - 2019-03-02 11:04:40
|
Hi mario, > reading message my...@my...@pop3.mydomain.net:1 of 1 (3054 octets) > About to rewrite Return-Path: <>... > ...rewritten version is Return-Path: <>. > About to rewrite From: <myf...@re...>... > ...rewritten version is From: <myf...@re...>. > About to rewrite To: <my...@my...>... > ...rewritten version is To: <my...@my...>. > fetchmail: about to deliver with: /usr/lib/courier/bin/sendmail -i -f > '<>' -- 'my...@my...' > #****************************517 Syntax error. > ***********.*********************** > fetchmail: Error writing to MDA: Broken pipe not flushed > fetchmail: POP3> QUIT > fetchmail: POP3< +OK Logging out. So it's Courier's sendmail that's giving the `517 Syntax error'. Google suggests this is quite common. https://www.courier-mta.org/FAQ.html#esmtperr explicitly mentions 517. http://courier-mail-server.10983.n7.nabble.com/More-information-re-517-syntax-error-td3484.html suggests local configuration can play a part if Courier has to make up an email address. The typical cause seems to be an email address with just a hostname, i.e. not `.' after the `@'. If Courier's logs don't help pin-point the problem then you may have to strace -ffe %desc -s 4096 -o st fetchmail ...your-normal-arguments and then look at st.* afterwards. Search for `517' and you'll find the error message from Courier as it's read by fetchmail. See what was being given to Courier in the run up to that. -- Cheers, Ralph. |
|
From: mario c. <ml...@ma...> - 2019-03-01 22:06:06
|
On Thu, 2019-02-28 at 00:31 +0200, Peter Pentchev wrote: > On Wed, Feb 27, 2019 at 10:37:30PM +0100, mario chiari wrote: > > On Tue, 2019-02-26 at 16:37 +0000, Ralph Corderoy wrote: > > > > > Could you also run and post the output of the second command that > Ralf quoted from the documentation, please? > > env LC_ALL=C fetchmail -vvv --nodetach --nosyslog > Hi Peter, All here a section of the output (personal data changed), the message which fails is a return receipt: fetchmail: POP3> USER my...@my... fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< +OK Logged in. fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 1 3054 fetchmail: POP3> LAST fetchmail: POP3< -ERR Unknown command: LAST fetchmail: Unknown command: LAST fetchmail: POP3> UIDL fetchmail: POP3< +OK fetchmail: POP3< 1 1551.......6270.*****.ad.myprovider.it,S=2963 fetchmail: 1 is unseen fetchmail: POP3< . 1 message for my...@my... at pop3.mydomain.net (3054 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 3054 fetchmail: POP3> TOP 1 99999999 fetchmail: POP3< +OK reading message my...@my...@pop3.mydomain.net:1 of 1 (3054 octets) About to rewrite Return-Path: <>... ...rewritten version is Return-Path: <>. About to rewrite From: <myf...@re...>... ...rewritten version is From: <myf...@re...>. About to rewrite To: <my...@my...>... ...rewritten version is To: <my...@my...>. fetchmail: about to deliver with: /usr/lib/courier/bin/sendmail -i -f '<>' -- 'my...@my...' #****************************517 Syntax error. ***********.***********************fetchmail: Error writing to MDA: Broken pipe not flushed fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out. thanks regards mario |
18 messages has been excluded from this view by a project administrator.
