On 2/3/19 2:09 PM, Hegedüs Ervin wrote:
Hi John,
On Sun, Feb 03, 2019 at 09:56:38AM +0100, John Fawcett wrote:
On 01/02/2019 13:39, Ervin Hegedüs wrote:
I'ld try to set up the managesieve (for RoundCube) - the sieve is
works as well with dovecot (I mean my filters works perfectly).
W
e a
replication process listening on the other master, or should both
servers be set up for replication in an almost identical way (with the 3
exceptions above)?
thanks for any insights.
John
pEpkey.asc
Description: application/pgp-keys
On 5/25/2010 11:07 AM, Brad Davidson wrote:
Timo,
-Original Message-
From: Timo Sirainen
Fixed: http://hg.dovecot.org/dovecot-1.2/rev/6f25b20b8367
(It was already fixed in v2.0.)
I know you were hoping to make 1.2.11 the last in that branch, but it seems
like we've seen a
On 6/10/2010 5:38 PM, fakessh wrote:
hi dovecot network
the principle of fail2ban is repeated for connections with the same login
fail2ban does not work if the attack changes to login every time
this type of attack is rather to find valid user accounts
I may be wrong, I hope I too am a victim
ns:
After my NEXT dovecot upgrade, I'm back in the quagmire, needing to know a) b)
and c) above.
I am confident that dovecot is not lacking in this department, I just can't
find what I'm looking for in the documentation.
Thanks in advance,
John
"return" keyword should be dropped from both
functions. Thoughts?
Thanks,
John
*John Woods | System Integration Administrator*
*Great Plains Manufacturing* | 1030 E North St | Salina, KS 67401
P: 785-823-3276 ext. 2663 | F: 785-822-5676 | E:
john.wo...@greatplainsmfg.com <ma
introduction of SMTPUTF8 and that has remained so. I
don't believe turning off SMTPUTF8 in Postfix will change the behaviour
in this case.
John
rding this violation to other systems, which is seldom acceptable
> either.
>
Would accepting UTF8 local part in the From header have any negative
consequences for Dovecot? If it does not I would accept it, based on the
fact that it maintains greater interoperability with other systems.
John
On 04/03/18 09:55, Stephan Bosch wrote:
> Op 3/4/2018 om 9:07 AM schreef John Fawcett:
>> On 03/03/18 22:10, Stephan Bosch wrote:
>>> Clearly, the relevant specifications don't allow UTF-8 in the local part
>>> without email address internationalization (EAI), wh
|
> MAIL_STORAGE_SERVICE_FLAG_TEMP_PRIV_DROP |
> MAIL_STORAGE_SERVICE_FLAG_NO_LOG_INIT |
> MAIL_STORAGE_SERVICE_FLAG_NO_IDLE_TIMEOUT)
> tmp_base_dir = 0x56239bd7a040 "tp data)"
> c =
> error = 0x0
>
>
The assert and consequent core dump i
dress... :)
>> This is about SMTPUTF8 (RFC6531). Looks like your only option is to disable
>> smtputf8_enable in Postfix config.
> It IS already disabled.
>
Ralph
if you compile and enable SMTPUTF8 in Postfix the mails should bounce
without getting to dovecot. That may or may not be what you want, but at
least they won't stick in the queue.
John
enssl itself.
Do you get any issue in certificate validation in the client?
John
On 10/03/18 14:06, Aki Tuomi wrote:
>
>> On 10 March 2018 at 14:49 John Fawcett < j...@voipsupport.it
>> <mailto:j...@voipsupport.it>> wrote:
>>
>>
>> On 08/03/18 18:43, Peter Linss wrote:
>>> I just added an ECDSA certificate to my mail
On 10/03/18 14:20, John Fawcett wrote:
> On 10/03/18 14:06, Aki Tuomi wrote:
>>
>>> On 10 March 2018 at 14:49 John Fawcett < j...@voipsupport.it
>>> <mailto:j...@voipsupport.it>> wrote:
>>>
>>>
>>> On 08/03/18 18:43, Peter Linss wro
I guess I've been lucky. My Red Hat server I built in 2003 finally gave up
the ghost yesterday. Fifteen years with almost zero problems running
7x24. Now I'm trying to build a basic server to host my e-mail using
CentOS 7, Sendmail and Dovecot. Server is running great as are Sendmail
and Dovec
I've been struggling trying to get Thunderbird to read e-mail off a
CentOS 7 server.
Sendmail writes mail in /var/spool/mail
I've configured dovecot to try to read from there using Thunderbird
(POP3/SMTP).
The firewall allows ports 25/110.
I verified I have mail in /var/spool/mail
but Thun
server build.
This time Dovecot was installed and active at boot but still can't find
my mail in /var/spool/mail.
On 7/13/2018 11:44 AM, Aki Tuomi wrote:
Should your INBOX path be /var/spool/mail/%u then?
---
Aki Tuomi
Dovecot oy
Original message
From: John Rowan
Dat
to specify
mail_location = maildir:~/Maildir
and everything's working.
Thanks for help.
On 7/13/2018 11:44 AM, Aki Tuomi wrote:
Should your INBOX path be /var/spool/mail/%u then?
---
Aki Tuomi
Dovecot oy
Original message ----
From: John Rowan
Date: 13/07/2018 17:44 (GMT+02
Can the groups send and receive from outside the domain ? If so, it's
going to be difficult to prevent groups from seeing each others emails
because an email that originated from group A could be sent to some
other domain (out on the internet), then get forwarded to a user in
group B. Just a thou
On Wed, 2019-01-02 at 00:59 -0800, M. Balridge wrote:
> > The main problem is : After some time of indexing from Dovecot, Dovecot
> > returns errors (invalid SID, etc...) and Solr return "out of range
> > indexes" errors
>
> I've been watching the progress of this thread with no small concern, mai
attached proposal. I tested
against 2.2.36 only. It applies correctly against 2.3.4 with a warning,.
John
--- dovecot-2.2.36/src/doveadm/doveadm-settings.c 2018-04-30
15:52:05.0 +0200
+++ dovecot-2.2.36-new/src/doveadm/doveadm-settings.c 2019-01-04
14:59:11.556270077 +0100
daemon already running).
The net_connect_unix() error with a zero length socket name is inexplicable to
me, unless it's got a non printing character in it or there is something
different happening on FreeBSD.
One suggestion is to run with the default setting, but look at resolving the
permission problem for the default socket creation at
/var/run/dovecot/stats-writer rather than working round it.
John
On 06/01/2019 02:26, John Fawcett wrote:
> On 05/01/2019 15:49, Mark Hills wrote:
>> I use IMAP preauth; I connect with Alpine over SSH which is very useful.
>>
>> The last few upgrades this has become more difficult to to. Last time
>> (moving 2.2 -> 2.3, I think
On 06/01/2019 11:37, Stephan Bosch wrote:
>
> Op 06/01/2019 om 03:35 schreef John Fawcett:
>> On 06/01/2019 02:26, John Fawcett wrote:
>>
>>> Can't see anything in the Dovecot 2.3.4 code that would give this
>>> problem, setting
>>>
>>> st
ves for my question about this
issue back in Oct 1, 2019. It's a client issue, and (imho) a mistake
in the IMAP specification. But I haven't spent any time reading the
spec closely to understand the reasoning.
John
Justin> Maybe I'm misunderstanding - all of our clients use pop3
Justin> (thunderbird and eudora). Do pop3 and imap overlap somehow, or
Justin> does the server use IMAP internally regardless of the client
Justin> protocol settings?
No, IMAP and POP are just the transport mechanisms. But POP is
e
original email any more.
Justin> On Thu, Jul 30, 2020 at 3:51 PM John Stoffel wrote:
Justin> Maybe I'm misunderstanding - all of our clients use pop3
Justin> (thunderbird and eudora). Do pop3 and imap overlap somehow, or
Justin> does the server use IMAP internally regardless o
esses up my main text based
mail reader doing IMAP.
Maybe I need to move to Mutt finally. Ugh... re-programming my
fingers for a new mail reader won't be fun at all.
John
Antonio> On Jul 30, 2020, at 5:48 AM, John Stoffel wrote:
Antonio> "Antonio"
Antonio> Agreed… Is Mailmate an option for you?
Never heard of it, will have to look into it. I'd be willing to
change the iPhone mail reader for sure, the Apple one kinda sucks
overall, especially for sorting and such. IMHO.
>> On Aug 10, 2020, at 7:51 PM, John
>>>>> "John" == John Stoffel writes:
Antonio> Agreed… Is Mailmate an option for you?
John> Never heard of it, will have to look into it. I'd be willing to
John> change the iPhone mail reader for sure, the Apple one kinda
John> sucks overall, especia
Recently I upgraded dovecot quite a few major versions. Since then some
mailboxes are experiencing deleted mail reappearing. It seems to be happening
roughly once a day, but not for every mail client or mailbox, I have at least
two clients with this issue: Thunderbird and Outlook.
Storage is lo
I upgraded from version 2.0.12.
Running a force-resync on affected mailboxes did resurrect some different and
very old mail, but this only happened on first run of force resync. The mail
that reappears every day is still happening.
> since you are running mdbox did you run purge before the upg
second intervals? That should help you narrow
down which (if any) disk is your hotspot.
It's not clear to me if you have one big btrfs filesystem, or a bunch
of smaller ones stiched together. In any case, it should be very easy
to get better performance here.
I think s
>>>>> "Miloslav" == Miloslav Hůla writes:
Miloslav> Hi, thank you for your reply. I'll continue inline...
Me too... please look for further comments. Esp about 'fio' and
Netapp useage.
Miloslav> Dne 09.09.2020 v 3:15 John Stoffel napsal(a):
M
>>>>> "Miloslav" == Miloslav Hůla writes:
Miloslav> Dne 09.09.2020 v 17:52 John Stoffel napsal(a):
Miloslav> There is a one PCIe RAID controller in a chasis. AVAGO
Miloslav> MegaRAID SAS 9361-8i. And 16x SAS 15k drives conneced to
Miloslav> it. Because
>>>>> "Miloslav" == Miloslav Hůla writes:
Miloslav> Dne 10.09.2020 v 17:40 John Stoffel napsal(a):
>>>> So why not run the backend storage on the Netapp, and just keep the
>>>> indexes and such local to the system? I've run Netapps for m
file in PEM format? Does it have a password?
You can use this command (without posting the output) to check an rsa kkey:
openssl rsa -in /etc/pki/tls/private/mail_acmewidgets_net.key -check
You should get somethings like:
RSA key ok
writing RSA key
-BEGIN RSA PRIVATE KEY-
-END RSA PRIVATE KEY-
John
I see the same content on both clients, and the storage
> directories become identical as well.
Are there any replication errors logged? Does
doveadm replicator status
or
doveadm replicator status
give any sign of errors?
Can you give some example or evidence of the disalignment that is happening?
John
up memberships?
>
> Regards,
> Graham
> —
>
Hi Graham
this may not solve the problem, but I thought I'd point out that the
error message relates to
/var/lib/dovecot/sieve/vacation.sieve
whereas your test using sudo related to a different file
/var/lib/dovecot/sieve/vacation.svbin
John
body tambien
I've noticed various errors when running some of the doveadm comamnds
and I've always put it down to not having run it under the right user or
in the right intial conditions or having a virtual setup rather than
system users. Not sure if that's the case with this error. I confirm I
get the same error as you.
John
On 18/10/2020 22:53, Piotr Auksztulewicz wrote:
> On Sat, Oct 17, 2020 at 11:17:34PM +0200, John Fawcett wrote:
>>> I have observed my mail storage directories on both instances and have
>>> noticed that they diverge a little over time - the instance B not having
>>>
gt; Except for this accented-character search mystery. I've got a _lot_
> of mail with various languages in bodies, so _do_ need to get this
> sorted.
>
>> On 10/18/20 2:58 PM, John Fawcett wrote:
> ...
>> silly question
> ...
>
> hardly!
>
>
> cre
On 19/10/2020 17:00, PGNet Dev wrote:
> On 10/19/20 1:18 AM, John Fawcett wrote:
>> I would recommend you to redo the tests after correcting the
>> configuration. To be doubly sure you can include accented and unique non
>> accented text in the same email and search for both
007facce1b8000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x7faccdeb1000)
libm.so.6 => /lib64/libm.so.6 (0x7faccdbaf000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7faccd999000)
libdl.so.2 => /lib64/libdl.so.2 (0x7faccd795000)
/lib64/ld-linux-x86-64.so.2 (0x7facd0ab6000)
John
On 19/10/2020 17:56, PGNet Dev wrote:
> On 10/19/20 8:24 AM, John Fawcett wrote:
>
>> Depending how solr has been setup you could see the logging in the web
>> server access log. My access log is where I configured it in
>> /var/log/httpd/servername.access_log, yours ma
On 19/10/2020 19:02, PGNet Dev wrote:
> On 10/19/20 9:48 AM, John Fawcett wrote:
>> --with-icu should be sufficient, actually on centos 7 I got libuci
>> compiled in without setting the explicit flag.
>
>> Here's my ldd, which is under /usr/local/lib/dovecot
>
On 21/10/2020 16:44, Patrik Peng wrote:
> On 16.10.20 18:34, Patrik Peng wrote:
>> On 16.10.20 18:00, Scott Q. wrote:
>>> This reminds me, the way I was able to reproduce this consistently
>>> was by having large headers ( 100+ lines ).
>>>
>>>
>>> On Friday, 16/10/2020 at 11:49 Patrik Peng wrote:
On 21/10/2020 19:00, John Fawcett wrote:
> On 21/10/2020 16:44, Patrik Peng wrote:
>> On 16.10.20 18:34, Patrik Peng wrote:
>>> On 16.10.20 18:00, Scott Q. wrote:
>>>> This reminds me, the way I was able to reproduce this consistently
>>>>
nf -n:
Hi
is there any error in the log?
Can you show some evidence or an example? ie some email delivery in the
master but not on the slave?
Can you be sure to check both new and cur subdirectories on master and
slave?
John
On 22/10/2020 10:23, John Fawcett wrote:
> On 21/10/2020 19:00, John Fawcett wrote:
>> On 21/10/2020 16:44, Patrik Peng wrote:
>>> On 16.10.20 18:34, Patrik Peng wrote:
>>>> On 16.10.20 18:00, Scott Q. wrote:
>>>>> This reminds me, the way I was abl
costs for my own domain.
Dovecot, postfix, spamassasin, etc. If you need more anti-spam, then
you'll need to spend $10/mon for a bigger memory VM in my expierence.
John
e 's|</head>|<style>* {color:white !important; background-color:
black !important; } |'
@lbutlr> exit 0
@lbutlr> The script is in both the /usr/local/virtual/user/ with the
.active_sieve and in /usr/lib/dovecot/sieve (unique files, not links,
but identical).
Can you get the script to work to just add a line or two at the end
instead as a simple test? Something like:
#!/bin/sh
sed -e 's||Hi there.|i'
exit 0
And of course make sure you're matching case-insensitively as well.
I kinda think the mimedefang milter might be better, but ... not
sure.
John
further panics /
segfaults and no noticed adverse effects. I'd recommend the dovecot team
to consider including the patch in the next update.
John
diff -ur dovecot-2.3.11.3-orig/src/lib-http/http-client-request.c
dovecot-2.3.11.3/src/lib-http/http-client-request.c
--- dovecot-2.3.11.3-ori
(It's a logical deduction from the fact we
didn't see the assert failures before and that part of the code has not
changed).
John
;
doveadm(doveadm_cmd_run_ver2+0x472) [0x55c0eaa6a372] ->
doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55c0eaa6a497] ->
doveadm(main+0x1d4) [0x55c0eaa47c54] ->
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7f35c3d34555] ->
doveadm(+0x1d0ef) [0x55c0eaa480ef]
Aborted
John
On 31/10/2020 22:01, PGNet Dev wrote:
> On 10/31/20 9:55 AM, John Fawcett wrote:
>> I can contribute a patch that solves the segfault. Unfortunately though
>> fts search may be more broken than this. It does not give me search
>> results, even though I see it querying
asically, you are just saying
to us: "Broke! Fix!" and we can't help much without details.
How is your "mail_location" defined in your configuration? And what
is your search term?
John
On 01/11/2020 15:20, PGNet Dev wrote:
> On 11/1/20 1:56 AM, John Fawcett wrote:
>> At the moment I don't see other corrections needed in dovecot apart from
>> command line doveadm fts which is not a show stopper. Via doveadm search
>> I confirm - on my simple config - t
>>>>> "Gionatan" == Gionatan Danti writes:
Gionatan> Il 2020-11-01 13:23 John Stoffel ha scritto:
>> How is your "mail_location" defined in your configuration? And what
>> is your search term?
Gionatan> Hi, I just discovered having such s
On 31/10/2020 17:55, John Fawcett wrote:
> On 31/10/2020 04:57, PGNet Dev wrote:
>> On 10/18/20 10:28 PM, Aki Tuomi wrote:
>>>> doveadm(myu...@example.com): Panic: file mail-storage.c: line
>>>> 2112 (mailbox_get_open_status): assertion failed: (box->opened
on local messages or local messages directly
at aliases?
John
>
> But it cannot do that, can it? Is there a work-around? I am still
> hoping that the mail server still works locally if the Internet
> connection fails. But I would need to learn some Postfix magic for
> that, would I?
>
> Thanks in advance,
> rdiez
locks
them completely for email delivery) at $5/month and install
postfix/dovecot together. Works great.
John
ing matching
*@example.com to dovecot-lda what would happen if the destination was an
alias and not a real user? Which real user should the email be delivered to?
John
e recommendation is to have specific users
always directed to the same server. If you implemented this
recommendation for the ActiveSync connections, would that solve the problem?
John
On 04/11/2020 18:33, Gustavo Ajeitos [Office365] wrote:
> Hi John,
>
> Thank you for your answer!
>
> I agree with you, I think you recommendation should solve the problem,
> it seems the only possible workaround.
> I have to investigate if it possible and how to accom
> "François" == François Poulain writes:
François> Le Sat, 31 Oct 2020 13:36:32 +0100,
François> François Poulain a écrit :
>> I am trying to import a mail IMAP account using doveadm.
François> Am I wrong trying to do so?
I think so. Have you tried 'imapsysnc' or other imap downloading t
ing
apache in front of solr? One obvious thing to check is the url= part of
your fts_solr setting including the credentials and the solr core name.
You may also want to test your solr installation from the command line.
For example this does a manual soft commit:
curl
https://user:passw...@solr.example.com:443/solr/dovecot/update?softCommit=true
<https://user:passw...@solr.example.com:443/solr/dovecot/update?softCommit=true>
If your solr server is correctly configured you should get back
something like this:
0
3
John
ovecot, just left the defaults.
For 401's returned from your solr server you'll need to look into how
you set up authentication.
John
On 13/11/2020 21:32, PGNet Dev wrote:
> On 11/13/20 11:37 AM, John Fawcett wrote:
>>> still dunno why the 401. :-/
>>
>> So I just did a quick check of running dovecot with a standalone
>> solr-8.7.0 instance and I'm not seeing any issues.
>
> +1
>
&g
On 13/11/2020 22:04, PGNet Dev wrote:
>> I guess you didn't need to enclose username and password in quotes, i.e.
>>
>> fts_solr =
>> url=https://myuser:my%40p...@solr.example.com:8984/solr/dovecot/
>> use_libfts soft_commit=yes batch_size=250
>
> On 11/1
On 13/11/2020 22:30, John Fawcett wrote:
> On 13/11/2020 22:04, PGNet Dev wrote:
>>> I guess you didn't need to enclose username and password in quotes, i.e.
>>>
>>> fts_solr =
>>> url=https://myuser:my%40p...@solr.example.com:8984/solr/dovecot/
>>
basic auth credentials for a tika server is not
currently supported by Dovecot.
The following patch allows to have user and password specified in the
fts_tika url in much the same way you can for fts_solr.
fts_tika = https://user:password@tika_host/tika
John
--- dovecot-2.3.11.3-orig/src/plugin
On 15/11/2020 15:49, PGNet Dev wrote:
> On 11/15/20 6:33 AM, John Fawcett wrote:
>> I've configured a tika server behind an apache proxy which enforces
>> basic auth, but sending basic auth credentials for a tika server is not
>> currently supported by Dovecot.
>
>
On 15/11/2020 18:10, John Fawcett wrote:
> On 15/11/2020 15:49, PGNet Dev wrote:
>> On 11/15/20 6:33 AM, John Fawcett wrote:
>>> I've configured a tika server behind an apache proxy which enforces
>>> basic auth, but sending basic auth credentials for a tika serve
On 15/11/2020 20:48, PGNet Dev wrote:
> On 11/15/20 11:13 AM, John Fawcett wrote:
>> Just a couple of updates about Tika and Solr together.
>>
>> 1. On mass reindexing I'm seeing panics - see below. These are present
>> with Dovecot 2.3.10 and 2.3.11.3. Seem t
On 15/11/2020 21:54, PGNet Dev wrote:
> On 11/15/20 12:21 PM, John Fawcett wrote:
>> I'm using tika-server.jar installed as a service
>
> yup. same here.
>
> atm, listening on localhost, with Dovecot -> Tika direct, no proxy.
>
> similarly fragile under load.
On 16/11/2020 01:14, PGNet Dev wrote:
> On 11/15/20 1:29 PM, John Fawcett wrote:
>>> atm, listening on localhost, with Dovecot -> Tika direct, no proxy.
>>>
>>> similarly fragile under load. throwing ~10 messages with .5-5MB
>>> attachments at
ields {
> userid = $userid
> rip = $rip
> protocol = $service
> session = $session
> }
> }
>
>
One solution is to use a primary key containing all the columns except
last_login. The side effect is that you can get more than one row per
userid, but if you order them by last_login you can get the last one.
John
nother question.
Before exploring the other segfaults it would be worthwhile getting that
fix. If other segfaults continue then I suggest posting the logging from
Dovecot
John
ttp_set.request_timeout_msecs = 60*1000;
http_set.ssl = &ssl_set;
http_set.debug = user->mail_debug;
- tika_http_client = http_client_init(&http_set);
+ tika_http_client = http_client_init_private(&http_set);
}
*http_url_r = tuser->http_url;
return 0;
John
that would be to use the policy_context
attribute available in Postfix 3.1 and later in order to differentiate
whether you are calling quota-status for inbound or outbound email, example:
policy_context=submission
http://www.postfix.org/SMTPD_POLICY_README.html
John
nk you have to do anything specific. I did a very standard
setup following the Dovecot documentation and I can search on any of
those fields. What issue are you seeing?
John
On 07/12/2020 02:32, michael1970 wrote:
> Hi John,
>
> I have the standard Dovecot Solr, like in documentation.
>
> When I query in solr backend
> http://127.0.0.1:8983/solr/dovecot/select?q=*%3A*
> I see as json:
>
> "uid":[1075],
>
the list traffic is of interest, you can easily
stop the messages from this list by using the unsubscribe link which you
can find in the header of all the list email or by using this link
https://dovecot.org/mailman/listinfo/dovecot
John
p patch for using basic
auth with the tika server and the previous posted patch (not mine) which
solves an assert when using solr and tika together.
John
diff -ur dovecot-2.3.11.3-orig/src/plugins/fts/fts-build-mail.c
dovecot-2.3.11.3/src/plugins/fts/fts-build-mail.c
--- dovecot-2.3.11.3-o
..@test.tennis24.ee
> anymore. If I send out it works fine but no mail arrives.
>
> --
>
> *peacecop kalmer:*
>
> *Instituudi tee 3-27 *
>
> *76902 * *Harku *
>
> *Harku*
>
> *Harjumaa*
> Estonia
>
> *+372 652 4228 *
>
> *+372 5620 4556 *
>
> *__ *
>
The following may help
https://sourceforge.net/p/postfixadmin/discussion/676076/thread/0a7aaf6305/
https://dovecot.org/pipermail/dovecot/2020-August/119642.html
John
usr/lib/dovecot/libdovecot.so.0
> No symbol table info available.
> #18 0x77dd3070 in io_loop_handler_run_internal () from
> /usr/lib/dovecot/libdovecot.so.0
> No symbol table info available.
> #19 0x77dd1b7c in io_loop_handler_run () from
> /usr/lib/dovecot/libdovecot.so.0
> No symbol table info available.
> #20 0x77dd1ce0 in io_loop_run () from
> /usr/lib/dovecot/libdovecot.so.0
> No symbol table info available.
> #21 0x77d520d3 in master_service_run () from
> /usr/lib/dovecot/libdovecot.so.0
> No symbol table info available.
> #22 0x55564bf5 in main ()
> No symbol table info available.
> (gdb)
>
>
> Thanks for any suggestion
> --Jiri Kacena
Looks like this (or something very similar) was already fixed
https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b024fb
John
Forwarding
However, unless I'm reading this wrongly, both methods are affected by
trusted_networks settings. I guess for people to help further, you'd
need to give more info your configuration settings.
John
On 07/12/2020 23:09, Adi Pircalabu wrote:
> On 08-12-2020 3:13, John Fawcett wrote:
>> On 07/12/2020 06:02, Adi Pircalabu wrote:
>>> Hi,
>>>
>>> I have a Dovecot proxy setup with several proxy machines (currently
>>> running 2.3.11.3) in front of the re
On 07/12/2020 23:22, John Fawcett wrote:
> On 07/12/2020 23:09, Adi Pircalabu wrote:
>> On 08-12-2020 3:13, John Fawcett wrote:
>>> On 07/12/2020 06:02, Adi Pircalabu wrote:
>>>> Hi,
>>>>
>>>> I have a Dovecot proxy setup with several proxy
On 08/12/2020 01:01, Adi Pircalabu wrote:
> On 08-12-2020 10:33, Adi Pircalabu wrote:
>> On 08-12-2020 9:41, John Fawcett wrote:
>>> On 07/12/2020 23:22, John Fawcett wrote:
>>>> On 07/12/2020 23:09, Adi Pircalabu wrote:
>>>>> On 08-12-2020 3:13, John F
f an email.
You might be able to debug it in dovecot with lmtp_rawlog_dir setting
which will show the input and output dialog of the lmtp session.
John
[40970]: lmtp(40988): Debug: SSL:
where=0x2002, ret=1: SSL negotiation finished successfully
John
On 13/12/2020 05:59, Mar Alegre wrote:
> Hello,
>
> I have encountered what I believe to be a bug, or at least inaccurate
> documentation. I am running version 2.3.4.1 of Dovecot (installed via
> the default repo for Debian 10), so my apologies if this has been
> fixed in a more recent version. I t
ommand" means full auth command started with "AUTH",
> not only authentication method. But I may be wrong in the
> interpretation of this part.
>
Your reading of the RFC looks correct. AUTH commands start with the
string "AUTH". This is no different after a negative res
the Solr logs, where *2276996170* is the
> value passed by Dovecot as rows number and it clearly don't fit with
> the rows data type.
>
> Have you had experienced the same behaviour? Is there a workaround?
> Thanks
> Antonino
>
Hi Antonio
out of curiosity, what does the dovecot log show for this issue?
John
str_printfa(str,
"wt=xml&fl=uid,score&rows=%u&sort=uid+asc&q=%%7b!lucene+q.op%%3dAND%%7d",
- status.uidnext);
+ I_MIN(status.uidnext,SOLR_MAX_MULTI_ROWS));
prefix_len = str_len(str);
if (solr_add_definite_query_args(str, args, and_args)) {
John
> "Harald" == Harald Leithner writes:
Harald> we have a problem upgrading Dovecot from 2.2 to 2.3.13 on one
Harald> server it seems one user triggers a segfault while trying to
Harald> authenticate.
Can you get the user to change their password to not have quite some
special characters maybe
gt;>> doveadm(u@d): Error: fts_solr: Indexing failed: Request timed out
>>>> (Request queued 134.122 secs ago, 1 send attempts in 134.098 secs,
>>>> 131.923 in http ioloop, 0.000 in other ioloops, connected 376.408
>>>> secs ago)
>>>> doveadm(u@d): Error: Mailbox Sent: Mail search failed: Internal
>>>> error occurred. Refer to server log for more information.
>>>> [*2021-01-14 17:09:40*]
>>>> doveadm(u@d): Error: Mailbox Sent: Transaction commit failed: FTS
>>>> transaction commit failed: backend deinit
>>>
>>> The last message about indexed block of ten messages (*2021-01-14
>>> 16:10:00.628 7453-7462)* arrives already after reindexing error on
>>> the other console occurs and doveadm exits. Interestingly, exactly
>>> at the time mentioned in the error message (*2021-01-14 17:09:40*,
>>> i.e. *16:06:40* - I don’t know why timezone differs) a message about
>>> indexing of a single message *7463* arrives (which is actually NEXT
>>> message to the block that gets indexed 20 seconds later).
>>>
>>> The whole mailbox consists of 8530 messages and doveadm/solr can’t
>>> finish indexing it at all starting over and over.
>>>
>>> Can you please help me understanding the reason of this behaviour?
>>>
>>> P.S. Is there any possibility to determine what message in vmail
>>> maildir corresponds to solr log, e.g. to
>>> 7463/78a0ec27b091da5e405413681708/u@d (1688879057103486976) ?
>>>
>>> Thanks, Programmierus
>>
>
I previously posted a patch (7 Dec 2020) you might find useful in this
circumstance which includes an additional setting, for example:
plugin {
...
fts_max_size = 2M
...
}
fts_max_size - do not parse message bodies if the message size exceeds
this value. A value of 0 indicates no limit. When the message body is not
parsed, attachments are also not parsed.
John
t; <https://filebin.ca/5oy6yqLSCr3H/rawlog.obfuscated.txt>
>
> (Both files were processed with perl doveadm-obfuscate.pl
> <https://www.dovecot.org/tools/doveadm-obfuscate.pl>; the script
> doesn’t replace non-latin characters so they were replaced with ‘R’
> manually)
>
> Wo
1 - 100 of 696 matches
Mail list logo
