From bogus@does.not.exist.com Thu Apr 4 09:44:58 2019 From: bogus@does.not.exist.com () Date: Thu, 04 Apr 2019 07:44:58 -0000 Subject: No subject Message-ID: From papaoz at earthlink.net Tue Apr 2 01:40:42 2019 From: papaoz at earthlink.net (Papa Oz.) Date: Mon, 1 Apr 2019 19:40:42 -0400 Subject: [Users] Deleting messages previously retained on POP server Message-ID: <20190401194042.5def80f0@HPL-XFCE-64-18> Claws newbie here. I finally had to give up on Eudora. I prefer POP to IMAP. I have several machines. Each can read the mail. All are set to leave mail on the server. One is designated to archive all the mail. On that machine I want to selectively mark messages to be deleted from the server, but I want to keep them on the client. I suppose I could set up the archiver to always delete from the server, but there are two reasons I would prefer not to do that. First, since the archiver fetches periodically, it would delete messages before the other machines could look at them. And second, occasionally a message needs to be reported to the ISP as spam or objectionable, and for that I need it on the ISP site. I downloaded some old archives of this list and poked around a lot. I saw some discussions that were sort of similar but not precisely. Could anyone please give me a clue as to how to selectively delete messages from the server that have been fetched but left on the server? Many thanks. From pf at pfortin.com Tue Apr 2 02:48:47 2019 From: pf at pfortin.com (Pierre Fortin) Date: Mon, 1 Apr 2019 20:48:47 -0400 Subject: [Users] Deleting messages previously retained on POP server In-Reply-To: <20190401194042.5def80f0@HPL-XFCE-64-18> References: <20190401194042.5def80f0@HPL-XFCE-64-18> Message-ID: <20190401204847.669d0a55@pfortin.com> On Mon, 1 Apr 2019 19:40:42 -0400 Papa Oz. wrote: >Claws newbie here. I finally had to give up on Eudora. > >I prefer POP to IMAP. Ditto. >I have several machines. Each can read the mail. All are set to leave >mail on the server. One is designated to archive all the mail. On >that machine I want to selectively mark messages to be deleted from the >server, but I want to keep them on the client. > >I suppose I could set up the archiver to always delete from the server, >but there are two reasons I would prefer not to do that. First, since >the archiver fetches periodically, it would delete messages before the >other machines could look at them. And second, occasionally a message >needs to be reported to the ISP as spam or objectionable, and for that >I need it on the ISP site. > >I downloaded some old archives of this list and poked around a lot. I >saw some discussions that were sort of similar but not precisely. >Could anyone please give me a clue as to how to selectively delete >messages from the server that have been fetched but left on the >server? Many thanks. Sounds like you're not taking advantage of a special resource: time! Set archiver to collect messages on regular basis; but only delete after N days (mine is set to 10 days). All other machines have no problem getting their copy of the messages, unless one or more is down, on vacation, in for repair, whatever for more than those 10 days. No need to manually worry about messages on server; they all end up on archiver and other clients have plenty of time to get their copy. From codejodler at gmx.ch Tue Apr 2 02:59:23 2019 From: codejodler at gmx.ch (Michael) Date: Tue, 2 Apr 2019 02:59:23 +0200 Subject: [Users] Deleting messages previously retained on POP server In-Reply-To: <20190401204847.669d0a55@pfortin.com> References: <20190401194042.5def80f0@HPL-XFCE-64-18> <20190401204847.669d0a55@pfortin.com> Message-ID: <20190402025923.177b7d69@gandalf.lan3> Piere: > On Mon, 1 Apr 2019 19:40:42 -0400 Papa Oz. wrote: > > >Claws newbie here. I finally had to give up on Eudora. > > > >I prefer POP to IMAP. > Ditto. > > >I have several machines. Each can read the mail. All are set to leave > >mail on the server. One is designated to archive all the mail. On > >that machine I want to selectively mark messages to be deleted from the > >server, but I want to keep them on the client. > > > >I suppose I could set up the archiver to always delete from the server, > >but there are two reasons I would prefer not to do that. First, since > >the archiver fetches periodically, it would delete messages before the > >other machines could look at them. And second, occasionally a message > >needs to be reported to the ISP as spam or objectionable, and for that > >I need it on the ISP site. > > > >I downloaded some old archives of this list and poked around a lot. I > >saw some discussions that were sort of similar but not precisely. > >Could anyone please give me a clue as to how to selectively delete > >messages from the server that have been fetched but left on the > >server? Many thanks. > > Sounds like you're not taking advantage of a special resource: time! > > Set archiver to collect messages on regular basis; but only delete after > N days (mine is set to 10 days). All other machines have no problem > getting their copy of the messages, unless one or more is down, on > vacation, in for repair, whatever for more than those 10 days. > > No need to manually worry about messages on server; they all end up on > archiver and other clients have plenty of time to get their copy. But if there was a reason for his approach .... would it be possible ? From noreply at thewildbeast.co.uk Tue Apr 2 09:39:41 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 02 Apr 2019 07:39:41 +0000 Subject: [Users] [Bug 3986] IMAP quick search using non-ASCII characters creates an infinite loop In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3986 simon.legner at gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.legner at gmail.com --- Comment #7 from simon.legner at gmail.com --- Could it be that those changed reintroduced bug 2744? -- You are receiving this mail because: You are the assignee for the bug. From ticho at claws-mail.org Tue Apr 2 10:05:13 2019 From: ticho at claws-mail.org (Andrej Kacian) Date: Tue, 2 Apr 2019 10:05:13 +0200 Subject: [Users] [Bug 4192] Make "Subject" (or provide option to configure) a stretchable column In-Reply-To: <20190330181631.73e778c0@acer-suse.lan> References: <20190330181631.73e778c0@acer-suse.lan> Message-ID: <20190402100513.7cbbe787@hiker> On Sat, 30 Mar 2019 18:16:31 +0000 Dave Howorth wrote: > On Sat, 30 Mar 2019 13:09:13 +0000 > noreply at thewildbeast.co.uk wrote: > > > https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4192 > > > > --- Comment #1 from Andrej Kacian --- > > Unfortunately, this is a limitation of the widget we're using for > > the message list. Only the last column can stretch automatically > > when the widget gets resized. > > It's still a valid bug though. I made the same point some while ago in > connection with deeply nested threads consuming all the subject width. Agreed, that's why I left it open (although perhaps it can be marked as duplicate of some older ticket, I wouldn't be surprised if there is one mentioning this already). > Is there an upstream bug/enhancement request for the required > flexibility? Or are there alternative widgets or the option of making > the subject the last column? It is something that I want to fix, eventually, since it does bother me. However, the widget in question is quite complicated and I have never felt courageous enough to dig deep enough into it to fix this. Regards, -- Andrej Kacian From noreply at thewildbeast.co.uk Tue Apr 2 10:10:19 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 02 Apr 2019 08:10:19 +0000 Subject: [Users] [Bug 4190] bsfilter error In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4190 --- Comment #1 from Andrej Kacian --- If you run that bsfilter command yourself in a terminal, does it also fail? If so, try adding -v or -d options to it to increase verbosity, and it should tell you what is going on. -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Apr 2 12:48:36 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 02 Apr 2019 10:48:36 +0000 Subject: [Users] [Bug 4190] bsfilter error In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4190 --- Comment #2 from MNatiello --- Created attachment 1970 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1970&action=edit output of running bsfilter from terminal -- You are receiving this mail because: You are the assignee for the bug. From noreply at thewildbeast.co.uk Tue Apr 2 13:02:34 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 02 Apr 2019 11:02:34 +0000 Subject: [Users] [Bug 4190] bsfilter error In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4190 --- Comment #3 from MNatiello --- Thank you for answering. Bsfilter behaves differently now, without my intervention. If I run bsfilter --insert-flag --insert-probability --homedir '/MYDIR/.claws-mail' -v -d -su '/MYDIR/.claws-mail/imapcache/MYSERVER/MYACCOUNT/INBOX/29328' it does not finish with error. The output is in the attached file. Running the plug-in on claws-mail with: bsfilter -v -d --insert-flag --insert-probability (it figures out the other stuff automatically, I hope) it does not give error and it moves the mail to Trash as expected. However, the --insert-probability and --insert-flag options do nothing. Both on a terminal and on the plug-in. The mail did not get an X-Spam-Probability line at all, the same with X-Spam-Flag. I think this is an improper behaviour, so I wonder if it is working correctly. Another strange thing is that the filter never marks something as spam "spontaneously". Despite having used it for a week or so, it never detects spam. I don't know if it is too soon, but it has seen a few hundred mails so far. -- You are receiving this mail because: You are the assignee for the bug. From jn.ml.clwm.729 at letterboxes.org Tue Apr 2 13:17:49 2019 From: jn.ml.clwm.729 at letterboxes.org (Jeremy Nicoll) Date: Tue, 02 Apr 2019 07:17:49 -0400 Subject: [Users] Deleting messages previously retained on POP server In-Reply-To: <20190401194042.5def80f0@HPL-XFCE-64-18> References: <20190401194042.5def80f0@HPL-XFCE-64-18> Message-ID: <669f1f51-0c8f-48f4-abca-565e87fc161a@www.fastmail.com> On Tue, 2 Apr 2019, at 00:41, Papa Oz. wrote: > Claws newbie here. I finally had to give up on Eudora. > > I prefer POP to IMAP. > > I have several machines. Each can read the mail. All are set to leave > mail on the server. One is designated to archive all the mail. On > that machine I want to selectively mark messages to be deleted from the > server, but I want to keep them on the client. It's been a long time since I did something like this, but when I did it was with programmes I wrote myself, which issued a series of POP commands to the server. If you're looking for a way for Claws to do it for you, I've no idea if that's easy to organise. My programmes relied on the POP sessions issuing a "UIDL" command at the start, which caused the server to return a list of unique ids corresponding to all the messages stored there at that point. So you'd see a list like 1 uid5458475 2 uid8232323 3 uid19822222 ... meaning that at that point the mailbox contained messages with those specified uids. Commands issued to the POP server, eg to retrieve (ie download) a message use the other number, eg RETR 2 fetches the second message, ie the one with uid value: uid8232323 So it's possible for you to maintain your own list of the uid values of the messages that you have downloaded, either by writing all the code to do the downloading of messages, and storing UIDL values, or - if eg Claws already issues a UIDL command, by your program reading the Claws log to find out on each connection what the Claws session actually did. Later, on a deletions session you again issue UIDL and get eg 1 uid... 2 uid... 3 uid... 4 uid... 5 uid19822222 6 uid5458475 7 uid... You check each entry that's shown there and see that the ones for, for example, messages 5 and 6 were seen on a download session earlier, so they are safe to delete, and you issue DELE 5 DELE 6 and check that the server receives the commands ok, and later ends the session ok. (Both are necessary because in POP a DELE command only asks the server to mark an item for future deletion, and the delete is not done until the whole session ends cleanly. That means it's possible to 'cancel' such delete requests by failing to end the session cleanly, which is sometimes useful. [Years ago, there were some non-RFC-compliant POP servers around that did not work that way, and immediately deleted messages when a DELE request was sent.] I don't know if that's useful. You'll find a full description at: https://tools.ietf.org/html/rfc1939 -- Jeremy Nicoll - my opinions are my own. From codejodler at gmx.ch Tue Apr 2 14:19:34 2019 From: codejodler at gmx.ch (Michael) Date: Tue, 2 Apr 2019 14:19:34 +0200 Subject: [Users] Deleting messages previously retained on POP server In-Reply-To: <20190402025923.177b7d69@gandalf.lan3> References: <20190401194042.5def80f0@HPL-XFCE-64-18> <20190401204847.669d0a55@pfortin.com> <20190402025923.177b7d69@gandalf.lan3> Message-ID: <20190402141934.36e63efc@gandalf.lan3> > Piere: > > > On that machine I want to selectively mark messages to be deleted from > > > the server, but I want to keep them on the client. > > > > Set archiver to collect messages on regular basis; but only delete after > > N days (mine is set to 10 days). All other machines have no problem > > getting their copy of the messages, unless one or more is down, on > > vacation, in for repair, whatever for more than those 10 days. > > But if there was a reason for his approach .... would it be possible ? I guess the settings about how many days to keep and if and when to delete, which are per-account now, can not be done per-folder ? Because then i could just move the messages into my special 'trash' folder ... Or maybe there is a workaround like maintaining a second account to the same mailbox which is IMAP, but do not download anything there, then move the messages-to-delete into the IMAPs trash, and set it up that they get deleted automaticly (e.g. when closing claws) from the server ? Complicated but at least still only just one action per mail. From whyskyhigh at yahoo.de Tue Apr 2 14:04:34 2019 From: whyskyhigh at yahoo.de (whyskyhigh at yahoo.de) Date: Tue, 2 Apr 2019 14:04:34 +0200 Subject: [Users] newbie In-Reply-To: References: Message-ID: <20190402140434.0a75a964.whyskyhigh@yahoo.de> hello we do use claws. until last week no problem. but another computer got a new linux. we did install claws but we cannot reach the www. firefox is running. regards sophie account is look like the other claws. From cyaniventer at riseup.net Tue Apr 2 17:47:44 2019 From: cyaniventer at riseup.net (Cyaniventer) Date: Tue, 2 Apr 2019 21:17:44 +0530 Subject: [Users] newbie In-Reply-To: <20190402140434.0a75a964.whyskyhigh@yahoo.de> References: <20190402140434.0a75a964.whyskyhigh@yahoo.de> Message-ID: <20190402211744.3a7ac461@lolcathost> On Tue, 2 Apr 2019 14:04:34 +0200 "whyskyhigh at yahoo.de" wrote: > hello > we do use claws. > until last week > no problem. > > but another computer got a new linux. > we did install claws but we cannot reach the www. What version of claws-mail are you running? What operating system are you using? (might help) You should include more information because that'll help others when they try to answer your queries. > account is look like the other claws. I would make a dummy account somewhere and test it, maybe your mailserver has some issues? Does this happen with other mailservers too? Did you try using other account? Check if Claws Mail is in offline mode, click on file (top bar) and look for offline mode. If there is a tick mark beside offline mode then click on it to disable offline mode. -- Cyaniventer BBBB 882A 5A00 FCB6 8704 E9BC 757D E342 DB4E 576C From claws at thewildbeast.co.uk Tue Apr 2 19:42:38 2019 From: claws at thewildbeast.co.uk (Paul) Date: Tue, 2 Apr 2019 17:42:38 -0000 Subject: [Users] newbie In-Reply-To: <20190402140434.0a75a964.whyskyhigh@yahoo.de> References: <20190402140434.0a75a964.whyskyhigh@yahoo.de> Message-ID: <20190402184238.1aa58082@localhost> On Tue, 2 Apr 2019 14:04:34 +0200 "whyskyhigh at yahoo.de" wrote: > but another computer got a new linux. > we did install claws but we cannot reach the www. > firefox is running. I assume that you mean that clicking on a link does not open it in firefox. Go to /Configuration/Preferences/Message View/External Programs Uncheck 'Use system defaults if possible'. For 'Web browser' enter: firefox '%s' with regards Paul From noreply at thewildbeast.co.uk Mon Apr 29 16:49:15 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 29 Apr 2019 14:49:15 +0000 Subject: [Users] [Bug 4204] New: Update template when changing account in compose window Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4204 Bug ID: 4204 Summary: Update template when changing account in compose window Classification: Unclassified Product: Claws Mail Version: 3.17.3 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P3 Component: UI/Compose Window Assignee: users at lists.claws-mail.org Reporter: psychonaut at nothingisreal.com In the compose window, changing the account automatically changes the signature in the message body to that of the corresponding account. It would be nice if the corresponding account's compose/reply/forward template were also automatically applied. (Of course, this should be done only if the message body hasn't yet been edited.) -- You are receiving this mail because: You are the assignee for the bug. From dave at howorth.org.uk Mon Apr 29 17:04:30 2019 From: dave at howorth.org.uk (Dave Howorth) Date: Mon, 29 Apr 2019 16:04:30 +0100 Subject: [Users] claws mail network log and SMTP timing Message-ID: <20190429160430.731ac501@acer-suse.lan> I've been experiencing an issue with sending messages, examples of which can be seen in the two log extracts below: 20:35:18] SMTP< 250 Accepted [20:35:18] SMTP> DATA [20:35:18] SMTP< 354 Enter message, ending with "." on a line by itself [20:35:18] SMTP> . (EOM) [20:35:39] SMTP< 250 OK id=1hKT6U-0003bn-Qy * Mail sent successfully. [20:35:39] SMTP> QUIT [09:39:04] SMTP< 354 Enter message, ending with "." on a line by itself [09:39:04] SMTP> . (EOM) [09:39:42] SMTP< 250 OK id=1hL1oW-0008IA-Mu * Mail sent successfully. [09:39:42] SMTP> QUIT [09:39:42] SMTP< 221 smarthost01d.mail.zen.net.uk closing connection The issue is the delay of 21 seconds and 38 second respectively shown in those extracts. Whilst that delay is occurring, the claws user interface is locked out, which is a bit frustrating on occasion. I've asked my ISP what the cause of the delay is but haven't yet got a satisfactory explanation, but in the meantime I have some questions about claws aspects this has made me aware of. Firstly, is there any way to stop the UI blocking in these circumstances, so I can carry on working? Secondly, is the log format documented anywhere and is it customisable? My searches haven't turned up anything. I've been guessing that the '>' means it is a message sent by claws to the SMTP server, and the '<' means a message received from the SMTP server but it would be good to confirm that. Also, to know why the timestamp shows the clock time but not the date and change it so it does show the date if possible. And does 'SMTP> . (EOM)' mean that is the timestamp at which the end of the message was sent? So the delay is definitely claws waiting for the SMTP server to respond, not the SMTP server waiting for claws to send something? From subscript at free.fr Mon Apr 29 17:20:54 2019 From: subscript at free.fr (wwp) Date: Mon, 29 Apr 2019 17:20:54 +0200 Subject: [Users] claws mail network log and SMTP timing In-Reply-To: <20190429160430.731ac501@acer-suse.lan> References: <20190429160430.731ac501@acer-suse.lan> Message-ID: <20190429172054.6cc8fbfc@ladybug> Hello Dave, On Mon, 29 Apr 2019 16:04:30 +0100 Dave Howorth wrote: > I've been experiencing an issue with sending messages, examples of which > can be seen in the two log extracts below: > > 20:35:18] SMTP< 250 Accepted > [20:35:18] SMTP> DATA > [20:35:18] SMTP< 354 Enter message, ending with "." on a line by itself > [20:35:18] SMTP> . (EOM) > [20:35:39] SMTP< 250 OK id=1hKT6U-0003bn-Qy > * Mail sent successfully. > [20:35:39] SMTP> QUIT > > > [09:39:04] SMTP< 354 Enter message, ending with "." on a line by itself > [09:39:04] SMTP> . (EOM) > [09:39:42] SMTP< 250 OK id=1hL1oW-0008IA-Mu > * Mail sent successfully. > [09:39:42] SMTP> QUIT > [09:39:42] SMTP< 221 smarthost01d.mail.zen.net.uk closing connection > > > The issue is the delay of 21 seconds and 38 second respectively shown > in those extracts. Whilst that delay is occurring, the claws user > interface is locked out, which is a bit frustrating on occasion. > > I've asked my ISP what the cause of the delay is but haven't yet got a > satisfactory explanation, but in the meantime I have some questions > about claws aspects this has made me aware of. > > Firstly, is there any way to stop the UI blocking in these > circumstances, so I can carry on working? Sure. Disable the sending dialog in the preferences (Mail Handling/Sending/Interface/Show send dialog), or if it's only one shot, click the Hide button. > Secondly, is the log format documented anywhere and is it customisable? > My searches haven't turned up anything. No customizable, what would like to do there? > I've been guessing that the '>' means it is a message sent by claws to > the SMTP server, and the '<' means a message received from the SMTP > server but it would be good to confirm that. I can confirm, > is "we send", < is "we receive". > Also, to know why the > timestamp shows the clock time but not the date and change it so it > does show the date if possible. Yeah, I tend to agree there, we should add the date (or make it customizable). But it matters when reading looong logs only. > And does 'SMTP> . (EOM)' mean that is > the timestamp at which the end of the message was sent? Sending . means sending end of message. This is SMTP-protocol-dependent. > So the delay is > definitely claws waiting for the SMTP server to respond, not the SMTP > server waiting for claws to send something? I think so, even if I've never such delay. Are you sending huge emails w/ tons of recipiends and attachments? They parse the email, potentially "long" studies (and usually, recipients are validated before that step, which can take a looong time too, could take 1-3 sec per recipient as I could see here). Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From ricardo at mones.org Mon Apr 29 18:01:21 2019 From: ricardo at mones.org (Ricardo Mones) Date: Mon, 29 Apr 2019 18:01:21 +0200 Subject: [Users] claws mail network log and SMTP timing In-Reply-To: <20190429172054.6cc8fbfc@ladybug> References: <20190429160430.731ac501@acer-suse.lan> <20190429172054.6cc8fbfc@ladybug> Message-ID: <20190429160121.pmf6qaqfdppbomdb@curuxu> On Mon, Apr 29, 2019 at 05:20:54PM +0200, wwp wrote: > Hello Dave, > > > On Mon, 29 Apr 2019 16:04:30 +0100 Dave Howorth wrote: […] > > The issue is the delay of 21 seconds and 38 second respectively shown > > in those extracts. Whilst that delay is occurring, the claws user > > interface is locked out, which is a bit frustrating on occasion. > > > > I've asked my ISP what the cause of the delay is but haven't yet got a > > satisfactory explanation, but in the meantime I have some questions […] > > So the delay is > > definitely claws waiting for the SMTP server to respond, not the SMTP > > server waiting for claws to send something? > > I think so, even if I've never such delay. Are you sending huge emails > w/ tons of recipiends and attachments? They parse the email, > potentially "long" studies (and usually, recipients are validated > before that step, which can take a looong time too, could take 1-3 sec > per recipient as I could see here). Could also be the ISP is applying some throttling mechanism to discourage potential internal spammers. regards, -- Ricardo Mones ~ The three principal virtues of a programmer are Laziness, Impatience, and Hubris. man perl From noreply at thewildbeast.co.uk Mon Apr 29 18:14:26 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Mon, 29 Apr 2019 16:14:26 +0000 Subject: [Users] [Bug 4205] New: log the date in the network log Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4205 Bug ID: 4205 Summary: log the date in the network log Classification: Unclassified Product: Claws Mail Version: other Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Other Assignee: users at lists.claws-mail.org Reporter: claws-bugzilla at howorth.org.uk At present the network log entries show the time but not the date. It is sometimes useful to be able to refer quickly to the date. e.g. instead of [09:39:42] SMTP> QUIT I would prefer [2019-04-29 09:39:42] SMTP> QUIT -- You are receiving this mail because: You are the assignee for the bug. From dave at howorth.org.uk Mon Apr 29 18:33:12 2019 From: dave at howorth.org.uk (Dave Howorth) Date: Mon, 29 Apr 2019 17:33:12 +0100 Subject: [Users] claws mail network log and SMTP timing In-Reply-To: <20190429172054.6cc8fbfc@ladybug> References: <20190429160430.731ac501@acer-suse.lan> <20190429172054.6cc8fbfc@ladybug> Message-ID: <20190429173312.62cbce8e@acer-suse.lan> On Mon, 29 Apr 2019 17:20:54 +0200 wwp wrote: > Hello Dave, > > On Mon, 29 Apr 2019 16:04:30 +0100 Dave Howorth > wrote: > > > I've been experiencing an issue with sending messages, examples of > > which can be seen in the two log extracts below: > > > > 20:35:18] SMTP< 250 Accepted > > [20:35:18] SMTP> DATA > > [20:35:18] SMTP< 354 Enter message, ending with "." on a line by > > itself [20:35:18] SMTP> . (EOM) > > [20:35:39] SMTP< 250 OK id=1hKT6U-0003bn-Qy > > * Mail sent successfully. > > [20:35:39] SMTP> QUIT > > > > [09:39:04] SMTP< 354 Enter message, ending with "." on a line by > > itself [09:39:04] SMTP> . (EOM) > > [09:39:42] SMTP< 250 OK id=1hL1oW-0008IA-Mu > > * Mail sent successfully. > > [09:39:42] SMTP> QUIT > > [09:39:42] SMTP< 221 smarthost01d.mail.zen.net.uk closing connection > > > > The issue is the delay of 21 seconds and 38 second respectively > > shown in those extracts. Whilst that delay is occurring, the claws > > user interface is locked out, which is a bit frustrating on > > occasion. > > > > I've asked my ISP what the cause of the delay is but haven't yet > > got a satisfactory explanation, but in the meantime I have some > > questions about claws aspects this has made me aware of. > > > > Firstly, is there any way to stop the UI blocking in these > > circumstances, so I can carry on working? > > Sure. Disable the sending dialog in the preferences > (Mail Handling/Sending/Interface/Show send dialog), or if it's only > one shot, click the Hide button. OK, I'll try those. > > Secondly, is the log format documented anywhere and is it > > customisable? My searches haven't turned up anything. > > No customizable, what would like to do there? > > > I've been guessing that the '>' means it is a message sent by claws > > to the SMTP server, and the '<' means a message received from the > > SMTP server but it would be good to confirm that. > > I can confirm, > is "we send", < is "we receive". Thanks. > > Also, to know why the > > timestamp shows the clock time but not the date and change it so it > > does show the date if possible. > > Yeah, I tend to agree there, we should add the date (or make it > customizable). But it matters when reading looong logs only. I'll submit an enhancement request :) #4205 > > And does 'SMTP> . (EOM)' mean that is > > the timestamp at which the end of the message was sent? > > Sending . means sending end of message. This is > SMTP-protocol-dependent. I don't understand what you mean here. Has the last byte of the message been sent at this time or not, is the question I'd like to answer. > > So the delay is > > definitely claws waiting for the SMTP server to respond, not the > > SMTP server waiting for claws to send something? > > I think so, even if I've never such delay. Are you sending huge emails > w/ tons of recipiends and attachments? They parse the email, > potentially "long" studies (and usually, recipients are validated > before that step, which can take a looong time too, could take 1-3 sec > per recipient as I could see here). My ignorance is confusing me. I thought SMTP servers received messages, queued them and then forwarded them. So I'd expect them to close the incoming connection when they have queued the message, which could be seconds, minutes or indeed hours before they processed the mail such as validating recipients. Is that not correct? From dave at howorth.org.uk Mon Apr 29 18:40:10 2019 From: dave at howorth.org.uk (Dave Howorth) Date: Mon, 29 Apr 2019 17:40:10 +0100 Subject: [Users] claws mail network log and SMTP timing In-Reply-To: <20190429160121.pmf6qaqfdppbomdb@curuxu> References: <20190429160430.731ac501@acer-suse.lan> <20190429172054.6cc8fbfc@ladybug> <20190429160121.pmf6qaqfdppbomdb@curuxu> Message-ID: <20190429174010.35e9759c@acer-suse.lan> On Mon, 29 Apr 2019 18:01:21 +0200 Ricardo Mones wrote: > Could also be the ISP is applying some throttling mechanism to > discourage potential internal spammers. True but I would expect my ISP to fess up to such behaviour when I asked them what the delay was. They're generally responsible and responsive (Zen) From subscript at free.fr Mon Apr 29 19:52:28 2019 From: subscript at free.fr (wwp) Date: Mon, 29 Apr 2019 19:52:28 +0200 Subject: [Users] claws mail network log and SMTP timing In-Reply-To: <20190429173312.62cbce8e@acer-suse.lan> References: <20190429160430.731ac501@acer-suse.lan> <20190429172054.6cc8fbfc@ladybug> <20190429173312.62cbce8e@acer-suse.lan> Message-ID: <20190429195228.33942ad6@ladybug> Hello Dave, On Mon, 29 Apr 2019 17:33:12 +0100 Dave Howorth wrote: > > > And does 'SMTP> . (EOM)' mean that is > > > the timestamp at which the end of the message was sent? > > > > Sending . means sending end of message. This is > > SMTP-protocol-dependent. > > I don't understand what you mean here. Has the last byte of the message > been sent at this time or not, is the question I'd like to answer. The answer to your former question is "yes", provided that I understand your question, which is not 100% sure. Is it grammatically correct? If so, please forgive my Engrish! > > > So the delay is > > > definitely claws waiting for the SMTP server to respond, not the > > > SMTP server waiting for claws to send something? > > > > I think so, even if I've never such delay. Are you sending huge emails > > w/ tons of recipiends and attachments? They parse the email, > > potentially "long" studies (and usually, recipients are validated > > before that step, which can take a looong time too, could take 1-3 sec > > per recipient as I could see here). > > My ignorance is confusing me. I thought SMTP servers received messages, > queued them and then forwarded them. So I'd expect them to close the > incoming connection when they have queued the message, which could be > seconds, minutes or indeed hours before they processed the mail such as > validating recipients. Is that not correct? I do not know what your ISP's SMTP server does at this last step (when it appears to stick for a while). The log is not showing more since the SMTP server doesn't say what is done, and IIRC, at this step in the SMTP protocol, nothing more informative is expected. What is certain is that the delay is on SMTP-server side. Regards, -- wwp -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From psychonaut at nothingisreal.com Tue Apr 30 13:36:13 2019 From: psychonaut at nothingisreal.com (Tristan Miller) Date: Tue, 30 Apr 2019 13:36:13 +0200 Subject: [Users] Unwanted signature padding In-Reply-To: <20161010093308.529d7089@kujata> References: <20161009164154.3f3463a9.psychonaut@nothingisreal.com> <20161010093308.529d7089@kujata> Message-ID: <20190430133613.70c83e48.psychonaut@nothingisreal.com> Greetings. On Mon, 10 Oct 2016 09:33:08 +0100, Paul wrote: > On Sun, 9 Oct 2016 16:41:54 +0200 > Tristan Miller wrote: > > > One of these annoyances is the placement of signatures. > > You will find that you have greater flexibility if you set a Reply > Template in your Account Preferences instead. Actually, one of the reasons I am (ab)using the signature function like this in the first place is because templates are not automatically (re)applied when I change identities (i.e., accounts) in the compose window, whereas signatures are. I meant to open an issue about this back when I first started this thread, but seem to have forgotten about it until now: Regards, Tristan -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tristan Miller Free Software developer, ferret herder, logologist https://logological.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From noreply at thewildbeast.co.uk Tue Apr 30 14:44:22 2019 From: noreply at thewildbeast.co.uk (noreply at thewildbeast.co.uk) Date: Tue, 30 Apr 2019 12:44:22 +0000 Subject: [Users] [Bug 4203] claws locks up In-Reply-To: References: Message-ID: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 --- Comment #7 from djh --- Created attachment 1977 --> https://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1977&action=edit log of lock up followed by termination I finally experienced another lock-up and this time whilst running under gdb. The output is attached. -- You are receiving this mail because: You are the assignee for the bug. From mail at leeunderwood.org Tue Apr 30 19:27:00 2019 From: mail at leeunderwood.org (Lee Underwood) Date: Tue, 30 Apr 2019 13:27:00 -0400 Subject: [Users] Update on HTML plugin? In-Reply-To: <20190429093357.6a86b696@utnubu> References: <20190421135550.350d1c7d@lee-desktop2> <20190421201627.1210f4aa@localhost> <20190428160941.31bfc428@lee-desktop2> <20190429093357.6a86b696@utnubu> Message-ID: <20190430132700.1fb2e14a@lee-desktop2> Thanks, Ralf. That helps greatly. It seems I will have to use another mail client while using 18.04. It's too bad as I have use CM for 10+ years now. 'Maybe' something will change. Thanks to all for the help. (I will stay on the list, though.) Lee On Mon, Apr 29, 2019, Ralf Mardorf wrote: > On Sun, 21 Apr 2019 13:55:50 -0400, Lee Underwood wrote: > >I was wondering if anyone had any update regarding the HTML plugin for > >Claws Mail v.3.16, in Ubuntu 18.04? > > On Sun, 28 Apr 2019 16:09:41 -0400, Lee Underwood wrote: > >How do I go about contacting Ubuntu about it? > > > Hi, > > "Point of contact for Ubuntu users to reach Ubuntu developers" - > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > Since Claws packages are "universe" packages, they aren't maintained by > Canonical, they're maintained by the community. > > Neither Fancy nor Dillo is available for 18.04. > > Take a look at the top right, only xenial is mentioned: > > https://packages.ubuntu.com/xenial/mail/claws-mail-fancy-plugin > > Here only cosmic, disco and eoan are provided: > > https://packages.ubuntu.com/cosmic/claws-mail-dillo-viewer > > Debian "upstream" for Ubuntu (take a look at the right of the link's > page) already dropped fancy (take a look at the left of the link's > page): > > https://tracker.debian.org/pkg/claws-mail > > You are hopefully aware about the Ubuntu release model poklicy. If not, > learn a little bit about your distro of choice. The executive summary: > Don't expect that a plugin for 18.04 ever will be provided. > > Perhaps a PPA or a Snap provides Claws with the desired plugin, > consider to send a request to: > > "This list is for Ubuntu user technical support." - > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users > > Regards, > Ralf > > _______________________________________________ > Users mailing list > Users at lists.claws-mail.org > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users From ethy.brito at inexo.com.br Tue Apr 30 21:19:35 2019 From: ethy.brito at inexo.com.br (Ethy H. Brito) Date: Tue, 30 Apr 2019 16:19:35 -0300 Subject: [Users] Update on HTML plugin? In-Reply-To: <20190430132700.1fb2e14a@lee-desktop2> References: <20190421135550.350d1c7d@lee-desktop2> <20190421201627.1210f4aa@localhost> <20190428160941.31bfc428@lee-desktop2> <20190429093357.6a86b696@utnubu> <20190430132700.1fb2e14a@lee-desktop2> Message-ID: <20190430161935.7b0a218c@pulsar.inexo.com.br> On Tue, 30 Apr 2019 13:27:00 -0400 Lee Underwood wrote: > Thanks, Ralf. That helps greatly. It seems I will have to use another mail > client while using 18.04. It's too bad as I have use CM for 10+ years now. > 'Maybe' something will change. > > Thanks to all for the help. (I will stay on the list, though.) > > Lee Hi You don't have to leave claws-mail. (big fat warning: this is a hideous/disgusting hack!! do it at your own risk) Install dillo browser package from Software updates (sudo apt install dillo). Download claws-mail-dillo-viewer for Ubuntu 18.10 (yes! eighteen-ten) (https://packages.ubuntu.com/cosmic/mail/claws-mail-dillo-viewer) and tweak control file to make dillo-viewer think it depends on claws-mail 3.16.0 Change (in control): Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.24.0), claws-mail (= 3.17.1-1), dillo (>= 3) to Depends: libc6 (>= 2.3.4), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.24.0), claws-mail (= 3.16.0-1), dillo (>= 3) Use something like (edit to fulfill your needs): fakeroot sh -c ' mkdir tmp dpkg-deb -R claws-mail-dillo-viewer_3.17.1-1_amd64.deb tmp cd tmp vi DEBIAN/control dpkg-deb -b tmp claws-mail-dillo-viewer_3.17.1-1~leeunderwood_amd64.deb ' Install with "dpkg -i ./claws-mail-dillo-viewer_3.17.1-1~leeunderwood_amd64" I did that a few weeks ago and it is running smooth so far. I do not remember exactly the commands I run, but you got the idea. Hope this helps. Cheers Ethy > > > On Mon, Apr 29, 2019, Ralf Mardorf wrote: > > > On Sun, 21 Apr 2019 13:55:50 -0400, Lee Underwood wrote: > > >I was wondering if anyone had any update regarding the HTML plugin for > > >Claws Mail v.3.16, in Ubuntu 18.04? > > > > On Sun, 28 Apr 2019 16:09:41 -0400, Lee Underwood wrote: > > >How do I go about contacting Ubuntu about it? > > > > > > Hi, > > > > "Point of contact for Ubuntu users to reach Ubuntu developers" - > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss > > > > Since Claws packages are "universe" packages, they aren't maintained by > > Canonical, they're maintained by the community. > > > > Neither Fancy nor Dillo is available for 18.04. > > > > Take a look at the top right, only xenial is mentioned: > > > > https://packages.ubuntu.com/xenial/mail/claws-mail-fancy-plugin > > > > Here only cosmic, disco and eoan are provided: > > > > https://packages.ubuntu.com/cosmic/claws-mail-dillo-viewer > > > > Debian "upstream" for Ubuntu (take a look at the right of the link's > > page) already dropped fancy (take a look at the left of the link's > > page): > > > > https://tracker.debian.org/pkg/claws-mail > > > > You are hopefully aware about the Ubuntu release model poklicy. If not, > > learn a little bit about your distro of choice. The executive summary: > > Don't expect that a plugin for 18.04 ever will be provided. > > > > Perhaps a PPA or a Snap provides Claws with the desired plugin, > > consider to send a request to: > > > > "This list is for Ubuntu user technical support." - > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-users > > > > Regards, > > Ralf > > > > _______________________________________________ > > Users mailing list > > Users at lists.claws-mail.org > > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > Users at lists.claws-mail.org > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users -- Ethy H. Brito /"\ InterNexo Ltda. \ / CAMPANHA DA FITA ASCII - CONTRA MAIL HTML +55 (12) 3797-6860 X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL S.J.Campos - Brasil / \ PGP key: http://www.inexo.com.br/~ethy/0xC3F222A0.asc