Hello,
I've got a problem fetching my emails using getmail. First question is, of
course, what's causing the problems. I'm going to think that getmail get's an
error code from dovecot when trying to connect and just signals the most common
error, so it seems to be a problem with dovecot.
Sorry
Good Morning,
I tried using gdb, but that doesn't work for me:
$ ulimit -c unlimited
$ sudo systemctl restart dovecot
$ sudo -E getmail
getmail version 5.13
Copyright (C) 1998-2019 Charles Cazabon. Licensed under the GNU GPL
version 2.
SimpleIMAPSSLRetriever:peter.nabbef...@gmx.de@imap.gmx.ne
Hello,
I've never used gdb, so I don't know why I'm running into problems using
"gdb bt".
Usually, I'm fetching my mail using "sudo -E getmail", but this doesn't
seem to work with backtrace. :-/
Output from "dovecot -n" attached.
Kind regards,
Peter
# 2.3.6 (7eab80676): /etc/dovecot/dovec
Peter
Am 27. Mai 2019 19:24:44 MESZ schrieb Aki Tuomi via dovecot
:
>
>> On 27 May 2019 20:20 Peter Nabbefeld via dovecot
> wrote:
>>
>>
>> Hello,
>>
>> I still cannot fetch my mails, relying on my smartphone (which makes
>it
>> a burden to re
Hello,
I still cannot fetch my mails, relying on my smartphone (which makes it
a burden to read my mails ...) - could probably somebody help me?
Kind regards,
Peter
Hello,
I'm running dovecot with getmail for several months already, but today
it's always crashing: "getmailrc: operation error (child pid 2995 killed
by signal 6)".
The deliver process aborts due to an unknown reason.
> tail /var/log/dovecot-info.log
May 24 12:10:28 imap-login: Info: Login:
Am 18.02.19 um 11:34 schrieb Sami Ketola:
On 18 Feb 2019, at 12.15, Peter Nabbefeld wrote:
Am 17.02.19 um 18:27 schrieb Sami Ketola:
Easy way is to use just one config file. That is what I have done for years.
Sami
I'd preferred that, too, but it seems the 'modern' way - and I don't
Am 17.02.19 um 14:45 schrieb Aki Tuomi:
On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot
wrote:
Hello,
I've got a very strange problem:
When I try to configure the stats-writer socket, I'm told the
configuration is a duplicate, though none exists in the configuration
Am 17.02.19 um 18:27 schrieb Sami Ketola:
On 17 Feb 2019, at 11.47, Peter Nabbefeld via dovecot
wrote:
Is there any tool displaying an "effective" config tree (i.e., a tool
displaying the resulting configuration from every file, displaying
the original file and line number)
Hello,
I've got a very strange problem:
When I try to configure the stats-writer socket, I'm told the
configuration is a duplicate, though none exists in the configuration
files. So I'd guess the configuration is set either built-in or implicitly.
I've put the following into conf.d/10-maste
10 matches
Mail list logo