This is probably problem on the other end.
Aki
On 20.11.2017 19:36, Dovecot list wrote:
> Hello. I try to migrate dovecot 1 to dovecot 2 with doveadm backup.
> But when i try to set doveadm backup i get :
>
> mx3:/root/dsync@[23:11] # doveadm -v -c ah.temp backup -R -u a...@test.pl
> imapc:
> d
I am testing Solr FTS on dovecot. Read online that some suggested to run
cronjob commit every minute, and optimize once a day.
I am using Solr 7.1.0 and I see some configurations:
In /etc/default/solr.in.sh:
#SOLR_OPTS="$SOLR_OPTS -Dsolr.autoSoftCommit.maxTime=3000"
#SOLR_OPTS="$SOLR_OPTS -Dsolr
Update:
I have modified mail_max_userip_connections to 400 which made no difference.
The end user customer actually had Apple remote into their device and
they were impressed that the end user knew their IMAP settings. They
tested it and during this connection time, it worked as expected with
Thanks a lot for the help.
You are right about the JSON as the default in solr v7.1.0. I now
switched it back to XML and now it works.
# doveadm -v index -u fail2...@mydomain.com Inbox
doveadm(fail2...@mydomain.com): Info: INBOX: Caching mails seq=1..388
388/388
Gao
On 2017-11-30 02:00 PM, C
Am 30. November 2017 22:14:59 MEZ schrieb Gao :
>I am testing the solr FTS following the guide here:
>http://things.m31.ch/?p=379
>
>Now I am having problem when I try to test:
>
># doveadm -v index -u fail2...@mydomain.com Inbox
>doveadm(fail2...@mydomain.com): Error: fts_solr: Invalid XML inpu
I am testing the solr FTS following the guide here:
http://things.m31.ch/?p=379
Now I am having problem when I try to test:
# doveadm -v index -u fail2...@mydomain.com Inbox
doveadm(fail2...@mydomain.com): Error: fts_solr: Invalid XML input at
1:0: not well-formed (invalid token) (near: {
"
Am 30. November 2017 18:20:58 MEZ schrieb Mark Foley :
>I'm wanting to experiment with sieve processing for the first time.
>Having some trouble getting
>started. I googled to page, https://wiki2.dovecot.org/Pigeonhole/Sieve,
>went to the "Download
>and Installation" link, then the "Pigeonhole do
I'm wanting to experiment with sieve processing for the first time. Having some
trouble getting
started. I googled to page, https://wiki2.dovecot.org/Pigeonhole/Sieve, went to
the "Download
and Installation" link, then the "Pigeonhole download page" link and downloaded
dovecot-2.2-pigeonhole-0.4.
Hello all,
finally I upgraded to dovecot 2.2.10 (that comes with CentOS 7.4).
But the problem is still there!
Why sieve can't move a message in a public namespace complaining about
"Mailbox does not exists"?
None of you ever try? Some of you have a working setup?
I attach "dovecot -n" output.
Hi,
On Wed, Nov 29, 2017 at 12:18 AM, Aki Tuomi wrote:
>
>> On November 29, 2017 at 5:58 AM Alex wrote:
>>
>>
>> Hi, I'm receiving the following messages in my mail logs that I
>> haven't seen before:
>>
>> Nov 28 22:45:31 bwipropemail dovecot: auth: login(?,179.210.41.21):
>> Username character
Op 16-11-2017 om 2:07 schreef MRob:
Hi, this is partly Postfix related, but I want to know if there could
be way to distinguish port of the SASL AUTH request to segregate user
services.
Currently I use unix listener for dovecot sasl auth, but could change
to inet_listener.
Only way I can
Thank you very much, the solution was so simple.
Am 30.11.2017 um 14:32 schrieb Felix Zielcke:
Am Donnerstag, den 30.11.2017, 13:47 +0100 schrieb Christopher
Satchell:
Hello,
when Dovecot launches (and pretty much at any action afterwards) it
always throws following error:
managesieve: Fatal
Op 25-11-2017 om 13:00 schreef Tomislav Perisic:
Does anyone have any idea regarding this?
On 17 Nov 2017 11:36, "Tomislav Perisic" wrote:
Hi,
We have 2 servers, server A and server B.
Server A has:
Postfix
dovecot-2.2.33.2-1.el6.x86_64
Server B has:
dovecot-2.2.33.2-1.el6.x86_64
doveco
Am Donnerstag, den 30.11.2017, 13:47 +0100 schrieb Christopher
Satchell:
> Hello,
>
> when Dovecot launches (and pretty much at any action afterwards) it
> always throws following error:
>
> > managesieve: Fatal: Plugin 'sieve_imapsieve' not found from
> > directory
>
> /usr/lib/dovecot/module
Op 29-11-2017 om 6:17 schreef Aki Tuomi:
On November 29, 2017 at 4:37 AM Mark Moseley wrote:
Just happened to be surfing the docs and saw this. This is beyond awesome:
https://wiki2.dovecot.org/AuthDatabase/Lua
Any words of wisdom on using it? I'd be putting a bunch of mysql logic in
it. A
Op 30-11-2017 om 13:47 schreef Christopher Satchell:
Hello,
when Dovecot launches (and pretty much at any action afterwards) it
always throws following error:
| managesieve: Fatal: Plugin 'sieve_imapsieve' not found from
directory /usr/lib/dovecot/modules/sieve
| config: Error: managesiev
Hello,
when Dovecot launches (and pretty much at any action afterwards) it
always throws following error:
| managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory
/usr/lib/dovecot/modules/sieve
| config: Error: managesieve-login: dump-capability process returned 89
dovecot-si
El 30 nov. 2017 4:02 a.m., "Steffen Kaiser"
escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 29 Nov 2017, Sergio Belkin wrote:
Now, I'd want to every mail was sent to support-...@example.com it triggers
> an autoreply vacation style.
>
> So, I've wrote and compiled a sieve filte
On 30.11.2017 12:33, Hajo Locke wrote:
> Hallo Liste,
>
> hat sich schon mal jemand mit 2 Faktor Auth für dovecot beschäftigt?
> Es geht dabei nicht nur um die Absicherung einer Weboberfläche sondern
> direkt die Absicherung der Standard pop/imap Verbindungen des Clients.
> Wir machen das auth bi
Hallo Liste,
hat sich schon mal jemand mit 2 Faktor Auth für dovecot beschäftigt? Es
geht dabei nicht nur um die Absicherung einer Weboberfläche sondern
direkt die Absicherung der Standard pop/imap Verbindungen des Clients.
Wir machen das auth bisher über MySQL. Rein technisch würde das gehen,
Stephan Bosch wrote:
Op 28-10-2017 om 17:18 schreef Stephan Bosch:
Op 10/26/2017 om 1:32 PM schreef Marc Weustink:
...
Will get back on this later.
This was actually a Dovecot problem. Merged yesterday:
https://github.com/dovecot/core/commit/451698c60d7b3a763742c8e99503ab30596036f0
htt
21 matches
Mail list logo
