On Wednesday 01 July 2020, ellie timoney wrote:
> Yes, please. If you don't, I will, but then you won't get
> automatic notifications of updates.
https://github.com/cyrusimap/cyrus-imapd/issues/3090
> Are they appearing in a log somewhere, or is this output
> from an analysis tool you're runni
Hi Sergey,
Quoting out of order, because it's a bit easier to explain that way:
> And there is another problem that is not obvious. -lpcreposix is needed
> in perl/imap/Makefile.PL and in perl/sieve/managesieve/Makefile.PL I seems.
This bit sounds a lot like https://github.com/cyrusimap/cyrus-im
On Tue, Jun 30, 2020, at 10:10 PM, Sergey wrote:
> On Monday 22 June 2020, ellie timoney wrote:
>
> > The Cyrus team is proud to announce the immediate availability
> > of a new version of Cyrus IMAP: 3.2.2
>
> There was a problem with AC_SYS_LARGEFILE. Most likely it was
> there before, but I
On Monday 22 June 2020, ellie timoney wrote:
> The Cyrus team is proud to announce the immediate availability
> of a new version of Cyrus IMAP: 3.2.2
There was a problem with AC_SYS_LARGEFILE. Most likely it was
there before, but I was no need to use AC_SYS_LARGEFILE.
Programs for x32 cannot wo
On Tuesday 30 June 2020, ellie timoney wrote:
> > > The Cyrus team is proud to announce the immediate availability of
> > > a new version of Cyrus IMAP: 3.2.2
> >
> > Tests have issued a new warning compared to 3.0.x (building in Linux):
> > verify-elf: WARNING: ./usr/lib64/libcyrus.so.0.0.0:
I have no idea what this refers to or where it comes from. Any further
information you could provide would be greatly appreciated!
Thanks
On Tue, Jun 30, 2020, at 5:14 AM, Sergey wrote:
> On Monday 22 June 2020, ellie timoney wrote:
>
> > The Cyrus team is proud to announce the immediate avail
On Friday 16 October 2015, Sergey wrote:
> I wanted to build Cyrus-IMAP with libpcre but it did not success.
> System libpcre-devel package install headers to /usr/include/pcre.
I returned to this question. 3.2.2 still does not find /usr/include/pcre/pcre.h
$ pkg-config --cflags libpcre
-I/usr/
On Monday 22 June 2020, ellie timoney wrote:
> The Cyrus team is proud to announce the immediate availability of a new
> version of Cyrus IMAP: 3.2.2
Tests have issued a new warning compared to 3.0.x (building in Linux):
verify-elf: WARNING: ./usr/lib64/libcyrus.so.0.0.0: found executable STACK
On Monday 29 June 2020, ellie timoney wrote:
> If you _want_ to use the hardware CRC32c algorithm
No. I want for Cyrus-IMAP works on systems without SSE4 when it built
on system with SSE4.
> > Can Cyrus-IMAP be running on systems without SSE4 at this case?
>
> Yep, it'll work just fine. The ha
Ellie,
I also had the doubt about this feature, though I'd already seen a mention that
the result of the hw implementation is incompatible (and before your last mail
completely forgot about it).
Maybe it makes sense to remove its mention (and detection) from configure
altogether, until it beco
Hi Sergey,
> Hardware support:
>SSE4.2: yes
This is detected for a hardware implementation of the CRC32c algorithm. Cyrus
doesn't actually use it though, because it's not compatible with the existing
CRC32 algorithm: i.e. for the same input, it produces a different checksum,
w
2020. 06. 21, vasárnap keltezéssel 10.53-kor Simon Matter ezt írta:
> 2020. 06. 20, szombat keltezéssel 21.31-kor Simon Matter ezt írta:
>
> The deliver.db still about 48MB.
>
I just deleted deliver.db and restart cyrus.
Restarting was pretty quick, takes only some seconds.
New deliver.db crea
2020. 06. 21, vasárnap keltezéssel 10.53-kor Simon Matter ezt írta:
> 2020. 06. 20, szombat keltezéssel 21.31-kor Simon Matter ezt írta:
> Please make sure the options here are also valid for your cyrus version.
> However, I also guess your deliver.db is corrupted somehow. From my own
> experie
> 2020. 06. 20, szombat keltezéssel 21.31-kor Simon Matter ezt írta:
>> Hi,
>>
>> The question is why is the deliver db > 2GB in skiplist format? Is it
>> normal or do you have a corrupt BDB db or does your db pruning not work
>> for deliverdb. I think that should be something like 'delprune
>> cm
2020. 06. 20, szombat keltezéssel 21.31-kor Simon Matter ezt írta:
> Hi,
>
> The question is why is the deliver db > 2GB in skiplist format? Is it
> normal or do you have a corrupt BDB db or does your db pruning not work
> for deliverdb. I think that should be something like 'delprune
> cmd=
2020. 06. 20, szombat keltezéssel 21.31-kor Simon Matter ezt írta:
>
> Hi,
>
> The question is why is the deliver db > 2GB in skiplist format? Is it
> normal or do you have a corrupt BDB db or does your db pruning not work
> for deliverdb. I think that should be something like 'delprune
> c
> Hi,
>
> I run into a problem on an old clearos server, where the cyrus shutdown
> always failed at step exporting databases.
> As I checked the situation using ps ax on an other console, I found
> that, it was exporting deliver.db.skiplist file, which failed after a
> lng time (some minutes).
On 10/06/2020 20:47, Miguel Mucio Santos Moreira wrote:
> Wolfgang,
>
> If you don't mind, I'd like to know if when you upgraded backend servers
> from 2.4 version to 2.5 version you have an increase, in metadata size.Here
> we had 30% around of increase
Yes, cyrus.* are larger. Not sure about .ca
Miguel,
That's perfectly normal, and I think it's even covered in the release
notes... Nope, I'm wrong, the release notes mention the larger Memory
footprint, due to more data and metadata being cached in memory. But
the on-disk size increases, too, as there is more information being held
in
Wolfgang,
If you don't mind, I'd like to know if when you upgraded backend servers from
2.4 version to 2.5 version you have an increase, in metadata size.Here we had
30% around of increase
Thanks one more time
Greetings
--
Miguel Moreira
DTE/SRE/GRE - Gerência de Redes
+55(31)3339-1401
PRODE
Wolfgang,
I'm sure your help and experience with Cyrus Murder upgrading will save a lot
of time and reduce the possibility of an eventual problem during the upgrade.
Thankful
--
Miguel Moreira
DTE/SRE/GRE - Gerência de Redes
+55(31)3339-1401
PRODEMGE - Companhia de Tecnologia da Informação do
Hi!
On 09/06/2020 14:56, Miguel Mucio Santos Moreira wrote:
> Dear Wolfgang,
>
> Firstly thanks for your answer, secondly I have one more doubt, during this
> time where the new Mupdate Master is receiving mailboxes information from
> backend servers, is necessary stopping comunications between fr
Dear Wolfgang,
Firstly thanks for your answer, secondly I have one more doubt, during this
time where the new Mupdate Master is receiving mailboxes information from
backend servers, is necessary stopping comunications between frontend servers
and mupdate master or none action is necessary besi
On 08/06/2020 17:37, Miguel Mucio Santos Moreira wrote:
> Now we're in doubt about how is the best solution to replace the mupdate
> master server for a new one.
> Nowadays we have around 16K mailboxes.
IIRC we simply replaced the mupdate server and did a "ctl_mboxlist -m" on
all backends to fill
Hi Marco,
On Thu, Jun 4, 2020, at 11:04 PM, Marco wrote:
> On 29/05/2020 06:20, ellie timoney has written:
> > The Cyrus team is proud to announce the immediate availability of a new
> > version of Cyrus IMAP: 3.2.1
>
> Hello,
>
> in Redhat EL8 I still fail these tests:
>
> ERRORS:
> Rename.
On 29/05/2020 06:20, ellie timoney has written:
The Cyrus team is proud to announce the immediate availability of a new version
of Cyrus IMAP: 3.2.1
Hello,
in Redhat EL8 I still fail these tests:
ERRORS:
Rename.rename_inbox
Perl exception: Errors found in syslog
at Cassandane/Instance.pm
Hello, David.
The code is in imap/lmtp_err..et, according to this bug report:
https://github.com/cyrusimap/cyrus-imapd/issues/3035
Good luck!
Javier.-
El 28/5/20 a las 13:20, David Faller escribió:
>
> Thanks for your solution, could you provide detailed which line did
> you change?
>
> under
Finally, I downloaded source from
https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.0/cyrus-imapd-3.2.0.tar.gz
untar into /usr/src
installed dependencies (pkg-config, libsasl2-dev, libicu-dev,
libjansson-dev, libssl-dev, bison, flex...)
edit /usr/src/cyrus-imapd-3.2.
On Mon, May 18, 2020, at 4:17 PM, Marco wrote:
> Ouch... I will try
>
> Thank you for the hint
> Marco
I think I might have figured out a way to work around (not fix) the problem (by
detecting when the LD_PRELOAD hasn't worked, and ignoring the syslog bits), and
written it down here so I don't
Il 15/05/2020 02:03, ellie timoney ha scritto:
The discussion on github about the lmtpd crash on RHEL7 makes me wonder if
FORTIFY_SOURCE, or something adjacent to it, is the cause of your Cassandane
LD_PRELOAD problem as well?
Ouch... I will try
Thank you for the hint
Marco
Cyrus Home P
The discussion on github about the lmtpd crash on RHEL7 makes me wonder if
FORTIFY_SOURCE, or something adjacent to it, is the cause of your Cassandane
LD_PRELOAD problem as well?
I don't know much about it -- it's not default on my system, and even though
github reminds me that I've looked at
Hello Michael,
On 11/05/2020 10:45, Michael Menge has written:
RedHat systems use SELinux by default and SELinux has the habit to
block access to files, sockets, ... Especial if software from
non-Redhat repos is used.
thank you for the hint, I think that this is not my issue.
I disabled SELIN
Quoting ellie timoney :
Hi Marco,
But it really seems that the LD_PRELOAD or the syslog.so doesn't
work for me.
Thanks for including that detail. Hopefully someone familiar with
RedHat can chime in with some insight into the LD_PRELOAD issue! At
a guess, "preventing library injection
Hi Ellie,
thank you for these feedback.
On 11/05/2020 03:03, ellie timoney has written:
# This fail on 3.2.0
# https://github.com/cyrusimap/cyrus-imapd/issues/2332
Caldav.supports_event
This one should be passing on 3.2.0, the issue above has been closed
Ouch. It still f
Hi Marco,
> But it really seems that the LD_PRELOAD or the syslog.so doesn't
> work for me.
Thanks for including that detail. Hopefully someone familiar with RedHat can
chime in with some insight into the LD_PRELOAD issue! At a guess, "preventing
library injection from intercepting syslog ca
Hi Ellie,
On 08/05/2020 03:29, ellie timoney ha scritto:
Hi Marco,
[...]
Thugh... if it's failing on missing syslog errors, that means it
found "utils/syslog.so" (otherwise it would be ignoring syslog
problems), so you probably did already run "make". But if it still
didn't find the sys
Hi Marco,
On Thu, May 7, 2020, at 7:51 PM, Marco wrote:
> The Instance.pm of Cassandane looks for a log in
>
> {basedir}/conf/log/syslog
>
> but the Cyrus IMAP log to system MAIL syslog, in redhat by default is
> /var/log/maillog.
Did you run "make" in the cassandane directory, like the instru
Il 07/05/2020 12:15, Robert Stepanek ha scritto:
2) The SearchFuzzy.striphtml_alternative fails for the following reason:
3) The SearchFuzzy.striphtml_rfc822 fails for the following reason:
These fail because they test a feature on the development branch. I have
fixed that on the cassandane m
On Thu, May 7, 2020, at 11:51 AM, Marco wrote:
> 1) The Rename.rename_inbox fails for this syslog error:
Probably ellie knows more for this one?
> 2) The SearchFuzzy.striphtml_alternative fails for the following reason:
> 3) The SearchFuzzy.striphtml_rfc822 fails for the following reason:
These
On 06/05/2020 19:59, Jason Tibbitts has written:
"M" == Marco writes:
M> thank you for the info. I trusted an old commit which I found on a
M> SPEC file for Fedora Cyrus IMAP 3.0.x. I'm trying to build an RPM
M> file.
Yes, you shouldn't trust that as I froze the Cassandane version in
Fedora
> "M" == Marco writes:
M> thank you for the info. I trusted an old commit which I found on a
M> SPEC file for Fedora Cyrus IMAP 3.0.x. I'm trying to build an RPM
M> file.
Yes, you shouldn't trust that as I froze the Cassandane version in
Fedora's packaging at an appropriate checkout back w
Hello,
On 06/05/2020 02:15, ellie timoney has written:
Cassandane is designed to be run from a git clone, and if you're using it, you
should generally keep it up to date. It is kept generally backwards
compatible, because I use it for testing new releases from old branches. You
don't need di
Hi Marco,
> I work with
> https://github.com/cyrusimap/cassandane/archive/00bfe0109f80437ed09154aca9fbd53eef8f1b09.tar.gz
> This cassandane release works pretty with 3.0.12. I didn't find build
> changes in Release notes for 3.2.0...
We don't do releases of Cassandane. That thing is just a sna
Il 04/05/2020 08:18, ellie timoney ha scritto:
The Cyrus team is proud to announce the first stable release from the new Cyrus
IMAP 3.2 series: 3.2.0
The main https://www.cyrusimap.org/ website now shows content for the 3.2
series.
Hello,
I'm trying to build this release, but I see many er
Correction:
https://www.cyrusimap.org/3.2/imap/download/release-notes/3.2/x/3.2.0-beta4.html
https://www.cyrusimap.org/3.2/imap/download/upgrade.html
On Mon, Mar 30, 2020, at 3:13 PM, ellie timoney wrote:
> The Cyrus team is proud to announce the fourth beta release from the
> new Cyrus
Thanks for the help, I'll give it another try in a couple of days, and if it
didn't workout, I might go for the same solution or try nginx.
Regards.
KMK
On Tuesday, February 18, 2020, 6:09:28 PM GMT+5, Jean-Christophe Delaye
wrote:
On 2020-02-17 12:17, Khalid Mehmood Khan via Info-c
On 2020-02-17 12:17, Khalid Mehmood Khan via Info-cyrus wrote:
> Hi!
>
> Does http proxy work in a cyrus murder environment? I keep getting ""PUT
> /dav/addressbooks/user/testuser/6ecc0a66-74a1412-1581679269354-210887/ef37977290d43113e709f68848aa9a8a5ff8a24f.vcf
> HTTP/1.1" (if-none-match=*) =>
On 2020-01-14 16:51, Savvas Karagiannidis wrote:
> Hi,
> according to the documentation for cyr_expire
> (https://www.cyrusimap.org/imap/reference/manpages/systemcommands/cyr_expire.html)
> you also have to add -X parameter in order to completely delete messages
> from mailboxes and -D parameter in
Hi,
according to the documentation for cyr_expire (
https://www.cyrusimap.org/imap/reference/manpages/systemcommands/cyr_expire.html)
you also have to add -X parameter in order to completely delete messages
from mailboxes and -D parameter in order to remove deleted mailboxes from
the server. -E is
Hi Anatoli;
Thanks for your reply; I’ll be focusing on the MKCOL for now:
I don’t know about permission to overwrite quite yet, but from looking at the
source it seems the break (at
https://github.com/cyrusimap/cyrus-imapd/blob/master/imap/http_dav.c#L5590) is
what causes HTTP_FORBIDDEN to be
Hi Johan,
In RFC 7231 (HTTP 1.1) section 3.1.1.5
(https://tools.ietf.org/html/rfc7231#section-3.1.1.5) it says that CT
header SHOULD be present, otherwise the recipient may interpret it the
way it wants, so IMO no problem on the Cyrus side here. For
application/json for example it MUST be present,
Sorry for the multiples emails...
The option "provide_uuid=1" I found in my last message seems to be
unrecognized by cyrus now (It's probably on by default). It's probably only
useful for new messages anyway.
So I'm back to square one and my google-fu failed me. If someone know how
to solve that p
But without rolling replication, or with mailboxes that were already DELETED.*
before the backup service was configured, I'm not sure what to expect. I'm not
sure if this is a case that I considered and did something for, but have since
forgotten about, or if it's a case that I hadn't consid
By shuffling the keywords on my google searches I was able to find this:
https://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-March/021405.html
Apparently there is a few settings to set to avoid copying the same message
multiple times. This would be a nice addition to the cyrus docs on
replicati
On Fri, Nov 15, 2019, at 5:12 PM, Deborah Pickett wrote:
> Semi-related questions about how Cyrus backup servers deal with deleted
> stuff.
>
> I have the following settings on the main mail server:
>
> deletedprefix: DELETED
> delete_mode: delayed
> expunge_mode: delayed
>
> My first question
Answering my own question:
... or do I need to establish my own SSH tunnel from master to backup
server?
I do have to supply my own tunnel. The Cyrus backup daemon currently
(3.1.7) doesn't support the STARTTLS command.
if (!strcmp(cmd.s, "Starttls") && tls_enabled()) {
Thanks Patrick. I wonder if I inadvertently compiled out support for TLS when I
built my binaries. I’ll try it again with the stock binaries rather than my
patched ones.
> On 8 Nov 2019, at 22:42, Patrick Boutilier wrote:
>
> Odd, works here.
>
>
> telnet localhost 2005
> Trying ::1...
> C
Just noticed that I am running an older version of Cyrus though.
On 11/8/19 7:35 AM, Patrick Boutilier wrote:
Odd, works here.
telnet localhost 2005
Trying ::1...
Connected to localhost.
Escape character is '^]'.
* SASL PLAIN
* STARTTLS
* COMPRESS DEFLATE
* OK domain Cyrus sync server v2.4.20
Odd, works here.
telnet localhost 2005
Trying ::1...
Connected to localhost.
Escape character is '^]'.
* SASL PLAIN
* STARTTLS
* COMPRESS DEFLATE
* OK domain Cyrus sync server v2.4.20
STARTTLS
OK Begin TLS negotiation now
On 11/8/19 2:12 AM, Deborah Pickett wrote:
... or do I need to establi
onicle.com/>
*Music: *http://www.gabrielebulfon.com <http://www.gabrielebulfon.com/>
*Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon
*Da:* Eugene V. Boontseff
*A:* Gabriele Bulfon
*Data:* 3 agosto 2019
om/cd/gabrielebulfon
Da:
Eugene V. Boontseff
A:
Gabriele Bulfon
Data:
3 agosto 2019 17.54.36 CEST
Oggetto:
Re: Cyrus 2.5.11 default domain on auth
On 31.07.2019 11:42, Gabriele Bulfon wrote:
If I try adding defaultdomain, what happens is that authentication works both
with and without specifying domain, but
Yep, that's the correct link, we're waiting on the CVE folks to update the
listing out of reserved status
On Mon, May 27, 2019, at 11:10 PM, Savvas Karagiannidis wrote:
> Hi Ellie,
> is there any link for details about CVE-2019-11356?
> Tried googling it but couldn't find anything related or in c
Hi Ellie,
is there any link for details about CVE-2019-11356?
Tried googling it but couldn't find anything related or in cyrus mailing
lists or in reported issues, other than this:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11356
Regards,
Savvas Karagiannidis
On Mon, May 27, 2019 at
On 4/2/19 7:15 PM, Ken Murchison wrote:
>
> On 4/2/19 1:02 PM, Jean-Christophe Delaye wrote:
>> Hello,
>>
>> We're testing Cyrus3.0.9 in a murder configuration.
>> It works fine for imap/imaps services. I can access mailboxes from
>> differents frontend, and move mailboxes from on backend to anoth
On 4/2/19 1:02 PM, Jean-Christophe Delaye wrote:
Hello,
We're testing Cyrus3.0.9 in a murder configuration.
It works fine for imap/imaps services. I can access mailboxes from
differents frontend, and move mailboxes from on backend to another !
I'm now blocked with the calendar features in this
Thanks, Ellie -- that was helpful. A couple of follow up comments, though.
On 3/18/19 7:55 PM, ellie timoney wrote:
This page is in the developer section, so its context is for people who are
Cyrus developers (especially for new contributors needing to get rolling
quickly).
Unfortunately no
Ken, Ellie,
Thanks for the information.
Ellie, I see that #2100 has everything to be merged, hasn't it? What's
blocking it?
Regards,
Anatoli
*From:* Ellie Timoney
*Sent:* Tuesday, March 19, 2019 03:29
*To:* Info-cyrus
*Subject:* Re: cyrus-imapd build dependencies
On Tue, Mar 19
:55
*To:* Info-cyrus
*Subject:* Re: cyrus-imapd build dependencies
Hi Patrick,
On Mon, Mar 18, 2019, at 11:33 PM, Patrick Goetz wrote:
This page on compiling cyrus-imapd:
https://www.cyrusimap.org/imap/developer/compiling.html
This page is in the developer section, so its context is for
On Tue, Mar 19, 2019, at 3:39 PM, Anatoli via Info-cyrus wrote:
> > The Cyrus httpd provides DAV services (which use the HTTP protocol). If
> you want the Cyrus httpd to support HTTP/2, you will need libnghttp2.
> Otherwise it will only support HTTP/1.
>
> Always wanted to ask what the nghttp2
m/cyrusimap/cyrus-imapd/issues/1765>? (It
needs to be moved out to implement efficient chroot)
Regards,
Anatoli
*From:* Ellie Timoney
*Sent:* Monday, March 18, 2019 21:55
*To:* Info-cyrus
*Subject:* Re: cyrus-imapd build dependencies
Hi Patrick,
On Mon, Mar 18, 2019, at 11:33 PM, Patri
Hi Patrick,
On Mon, Mar 18, 2019, at 11:33 PM, Patrick Goetz wrote:
> This page on compiling cyrus-imapd:
>
>https://www.cyrusimap.org/imap/developer/compiling.html
This page is in the developer section, so its context is for people who are
Cyrus developers (especially for new contributors
Hi Daniel,
Sorry for my late response. I was very busy and did not check the
mailinglist.
Op 12-02-19 om 14:29 schreef Daniel Bareiro:
>
> On 8/2/19 16:46, Paul van der Vlis wrote:
>
>>> After quite some time, today I decided to update the mail server from
>>> Debian Jessie (cyrus-imapd 2.4.17)
Heiler Bemerguy via Info-cyrus wrote on 07/03/2019 16:30:
> My "man imapd.conf" doesn't list this option at all. I think my Cyrus
> 2.5.10 is older than it..
Yes. It appeared in 2.5.11 according to my build environment.
But there already was the option
timeout: 30
before. So every connecti
My "man imapd.conf" doesn't list this option at all. I think my Cyrus
2.5.10 is older than it..
But I've added it to the .conf anyway. Won't hurt if it doesn't exist
yet, right? lol
Atenciosamente,
Heiler Bemerguy - CINBESA
Analista de Redes, Wi-Fi,
Virtualização e Serviços Internet
(55) 9
Thank you very much, it worked perfectly.
Best Regards,
Heiler Bemerguy - CINBESA
Analista de Redes, Wi-Fi,
Virtualização e Serviços Internet
(55) 91 98151-4894
Em 07/03/2019 11:55, Ivan Kuznetsov escreveu:
Hello
iptables -A INPUT -p tcp --syn --dport 143 -m connlimit
--connlimit-above 8 -j
Heiler Bemerguy via Info-cyrus wrote on 07/03/2019 15:39:
> Yes I've read imapd.conf and cyrus.conf and found no options to limit
> connections per source IP or "idleness"..
>
> It means anyone can open a lot of connections to any port (143, 25, 110 etc)
> and render the server unusable??
You can
Hello
iptables -A INPUT -p tcp --syn --dport 143 -m connlimit
--connlimit-above 8 -j REJECT
This will limit established imap connections to 8 per ip
07.03.2019 17:39, Heiler Bemerguy via Info-cyrus пишет:
Yes I've read imapd.conf and cyrus.conf and found no options to limit
connections per
Dear Cyrus friends and Heiler Bensimon Bemerguy,
Don’t forget to report your solution.
It might certainly help other Cyrus users as well, though it is not directly
related to Cyrus.
Wiel Offermans
wil...@offermans.rompen.nl
> On 7 Mar 2019, at 15:39, Heiler Bemerguy via Info-cyrus
> wro
Yes I've read imapd.conf and cyrus.conf and found no options to
limit connections per source IP or "idleness"..
It means anyone can open a lot of connections to any port (143,
25, 110 etc) and render the server unusable??
I'm using Debian, so I'll try to figure
Dear Cyrus friends and Heiler Bensimon Bemerguy,
You could use your firewall to achieve this.
For ipfw:
${fwcmd} add pass tcp from any to ${ip_me} imap setup limit src-addr 10
You have to lookup the right syntax for your firewall.
Dit you check man imapd or man cyrus, maybe there is also an op
On Fri, 22 Feb 2019, Stéphane Branchoux wrote:
> From: Stéphane Branchoux
> To: info-cyrus@lists.andrew.cmu.edu
> Date: Fri, 22 Feb 2019 19:41:15 +0100
> Subject: Cyrus imap and identity theft
>
> Each week , few users respond to phishing mails. I use rules on
> firewalls, DNS filters, training
fail2ban can do anything you want - including what you describe - you just have
tell it what to look for in the logs!
--
Merlin Hartley
Computer Officer
MRC Mitochondrial Biology Unit
University of Cambridge
Cambridge, CB2 0XY
United Kingdom
> On 26 Feb 2019, at 14:20, Stephane Branchoux
> wr
Hello,
Thanks for the link to ipset-balcklist, i will try it.
fail2ban is not interesting for me because with phishing, connexions are
succeded !
I would like to detect and block succeed connections when a user
connects from multiple
countries the same day.
Thanks
Le 26/02/2019 à 12:00,
On 22/02/2019 08:41 PM, Stéphane Branchoux wrote:
Each week , few users respond to phishing mails.
I use rules on firewalls, DNS filters, training program for users ,
anti spam products , anti virus ….
I am looking for a way or tools to reduce identity theft on my Cyrus
imap server.
For ex
> Hi Ellie
>
> Thanks a lot, I will try to build and test 2.4.20
Maybe try this:
http://www.invoca.ch/pub/packages/cyrus-imapd/RPMS/ils-7/SRPMS/cyrus-imapd-2.4.20-2.el7.src.rpm
Regards,
Simon
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/piperma
Hi Ellie
Thanks a lot, I will try to build and test 2.4.20
22.02.2019 04:20, ellie timoney пишет:
Hi Ivan,
#7 0x56193ed6382e in idle_update ()
with cyrus-imapd 2.4.17 (cyrus-imapd-2.4.17-13.el7.x86_64 rpm)
It looks like this version is old enough to still be using signal handlers in
Hi Ivan,
> #7 0x56193ed6382e in idle_update ()
> with cyrus-imapd 2.4.17 (cyrus-imapd-2.4.17-13.el7.x86_64 rpm)
It looks like this version is old enough to still be using signal handlers in
its IMAP IDLE implementation. This is known to be a problem, and IDLE was
rewritten to not use sig
Hello
I have gdb'ed the locked process, backtrace is below. It seems that
problem occurs when imapd process catch a signal when is inside malloc()
call. The signal handler has a malloc() call too, so finally there is
interlock between two mallocs
I have only a few time to investigate because
Hi mates!
I don't really know where the difference is, but in the dev environment,
searches are hugely faster. I know, in dev is not the same as production
in terms of muas traffic and so... but... we are talking in differences
like from 5 seconds to perhaps 40-50 seconds and obviously when sayin
thanks a lot mate!
I'm doing checks... for comparing the previous testing env and live
production :)
Cheers!
---
EGOITZ AURREKOETXEA
Departamento de sistemas
944 209 470
Parque Tecnológico. Edificio 103
48170 Zamudio (Bizkaia)
ego...@sarenet.es
www.sarenet.es [1]
Antes de imprimir este c
On Wed, Feb 13, 2019, at 2:24 PM, Egoitz Aurrekoetxea wrote:
> Or.. if using in imapd.conf "search_fuzzy_always: 1" isn't it?.
Yes, that will instruct imapd to always use FUZZY search for IMAP SEARCH
commands [1]. If you use JMAP, it always use fuzzy search (and hence the
Xapian backend).
[1]htt
Or.. if using in imapd.conf "search_fuzzy_always: 1" isn't it?.
If a search returns results... I assume is going through it... isn't
it?. else.. I assume nothing would be found... I really attached too the
configs (in url format of pastebin), https://pastebin.com/CtCEedty just
for... the cause y
Hi Egoitz,
On Wed, Feb 13, 2019, at 1:10 PM, Egoitz Aurrekoetxea wrote:
> Xapian version is xapian-core-1.4.9_1 (FreeBSD port). Could I see by
> some debbuging log Xapian is working in the searchs in order to know,
> that can't be faster and that all is ok?. At the moment I have tree
> tiers. But
On 8/2/19 16:46, Paul van der Vlis wrote:
>> After quite some time, today I decided to update the mail server from
>> Debian Jessie (cyrus-imapd 2.4.17) to Debian Stretch (cyrus-imapd 2.5.10-3).
> Hello Daniel,
Hello, Paul.
> I use cyrus-imapd 2.5.10-3 from Debian stable on serveral machines a
Hi!
As far as I remember You should rebuild 2.5.20-3 package with at least those
patches
https://github.com/cyrusimap/cyrus-imapd/commit/1e7cf05a6bcba8c639fe8222c28851b1a9802e63
https://github.com/cyrusimap/cyrus-imapd/commit/575b6b4503a5566115a6259f98c812b2b465f8b6
8 февраля 2019 г. 22:46:00 G
Op 11-02-19 om 10:45 schreef Lars Schimmer:
> On 2/8/19 6:39 PM, Paul van der Vlis wrote:
>> In some time it will be in Debian unstable and a few days later in
>> testing. https://packages.debian.org/search?keywords=cyrus-imapd
>
> Hip Hip Hooray!
> Thanks to all involved.
> Will test as soon as
On 2/8/19 6:39 PM, Paul van der Vlis wrote:
> Op 08-02-19 om 11:48 schreef Paul van der Vlis:
>> Hello,
>>
>> The freeze for the next version of Debian is in the next week.
>>
>> Somebody has packaged Cyrus version 3.08, but there are problems with
>> some of the Cassandane tests.
>>
>> When my inf
Op 08-02-19 om 22:49 schreef Jason L Tibbitts III:
>> "PV" == Paul van der Vlis writes:
>
> PV> Somebody has packaged Cyrus version 3.08, but there are problems
> PV> with some of the Cassandane tests.
>
> It may be useful to see how Fedora handles Cassandane as part of its
> build process.
> "PV" == Paul van der Vlis writes:
PV> Somebody has packaged Cyrus version 3.08, but there are problems
PV> with some of the Cassandane tests.
It may be useful to see how Fedora handles Cassandane as part of its
build process. I did a lot of work to get things functioning and get
patches p
Op 15-01-19 om 17:33 schreef Daniel Bareiro:
> Hi all!
>
> After quite some time, today I decided to update the mail server from
> Debian Jessie (cyrus-imapd 2.4.17) to Debian Stretch (cyrus-imapd 2.5.10-3).
Hello Daniel,
I use cyrus-imapd 2.5.10-3 from Debian stable on serveral machines and I
ca
1 - 100 of 4440 matches
Mail list logo
