public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jalus Bilieyich <countolaf17@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Setting up fetchmail to feed postfix
Date: Sun, 26 Nov 2017 09:58:29 -0600	[thread overview]
Message-ID: <fd4782d9-465b-0755-ce4f-2427ac419334@gmail.com> (raw)
In-Reply-To: <795e745e-05a6-c5de-6083-414bd7f11a99@gmail.com>

Yes, I have an IMAP account provided by GMail.

On 11/26/2017 12:58 AM, Alan McKinnon wrote:
> On 26/11/2017 04:30, Peter Humphrey wrote:
>> On Saturday, 25 November 2017 16:20:46 GMT Jalus Bilieyich wrote:
>>> As an everyday user of KMail, I am completely happy with using it. I
>>> don't see any flaws with it. Maybe it's just me or...? Is there a reason
>>> behind the hostile glare towards KMail?
>>
>> Do you have POP3 or IMAP-4 accounts?
>>
>> It used to be like that for me too, but not for a long time now. I get 
>> duplicate messages, which are a known problem and easily worked around, but 
>> the latest version of KMail whinges about more than one candidate for 
>> display and just gives up. Then I have to stop KMail, start akonadiconsole 
>> and use it to delete the akonadi cache of the affected folder, restart 
>> akonadi and (when the debug messages quieten down) restart KMail and click 
>> on the same folder. Then it rebuilds the threads and stores them neatly away 
>> in MySQL.
>>
>> This happens several times a day, sometimes even more than once in the same 
>> folder. I don't know why I should be affected more than anyone else, but I 
>> do seem to be. It reminds me of Dale and his struggles a few years ago with 
>> ... what was it again, Dale?
>>
> 
> it was the init thingy, and before that it was HAL
> 


  parent reply	other threads:[~2017-11-26 15:58 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-24 15:39 [gentoo-user] Setting up fetchmail to feed postfix Peter Humphrey
2017-11-24 16:08 ` Wols Lists
2017-11-24 16:34   ` Peter Humphrey
2017-11-24 18:10     ` Matthias Hanft
2017-11-27 13:44       ` Peter Humphrey
2017-11-30  0:39         ` Peter Humphrey
2017-11-30  6:46           ` J. Roeleveld
2017-11-30  8:13           ` Neil Bothwick
2017-11-24 16:16 ` Ralph Seichter
2017-11-24 16:40   ` Peter Humphrey
2017-11-24 17:29     ` Ralph Seichter
2017-11-24 17:30   ` Rich Freeman
2017-11-24 17:52     ` Ralph Seichter
2017-11-27 13:44       ` Peter Humphrey
2017-11-27 16:13         ` Ralph Seichter
2017-11-27 17:48           ` [gentoo-user] " Ian Zimmerman
2017-11-27 19:10             ` Ralph Seichter
2017-11-27 22:14             ` Neil Bothwick
2017-11-28  0:23               ` Peter Humphrey
2017-11-26 10:25     ` [gentoo-user] " J. Roeleveld
2017-11-24 22:24 ` Neil Bothwick
2017-11-25  8:43   ` Marc Joliet
2017-11-25  9:04     ` Neil Bothwick
2017-11-25  9:23       ` Marc Joliet
2017-11-25 16:20         ` Jalus Bilieyich
2017-11-26  2:30           ` Peter Humphrey
2017-11-26  6:58             ` Alan McKinnon
2017-11-26 10:45               ` Peter Humphrey
2017-11-26 15:58               ` Jalus Bilieyich [this message]
2017-11-26  8:52             ` Neil Bothwick
2017-11-26 10:00             ` Ralph Seichter
2017-11-26 11:00               ` Peter Humphrey
2017-11-26 17:46               ` [gentoo-user] " Ian Zimmerman
2017-11-26 18:46                 ` Ralph Seichter
2017-11-26 19:35                   ` Jack
2017-11-26 20:58                   ` Wols Lists
2017-11-26 21:46                     ` Rich Freeman
2017-11-26 23:05                       ` Ian Zimmerman
2017-11-26 23:18                         ` Rich Freeman
2017-11-26 10:22             ` [gentoo-user] " J. Roeleveld
2017-11-26 15:25               ` Mick
  -- strict thread matches above, loose matches on Subject: below --
2017-11-26  7:25 roger.cahn
2017-11-26  7:26 roger.cahn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fd4782d9-465b-0755-ce4f-2427ac419334@gmail.com \
    --to=countolaf17@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox