similar to: sieve match ANY header

On 8 Apr 2019, at 16:35, Shawn Heisey via dovecot <dovecot at dovecot.org> wrote: > I would like to create a sieve rule where I do a regex match on ALL headers, not a specific header. This is a really bad idea. Headers can be quite long, contain data that you do not have control over, and checking all headers will be very expensive and may leave you open to various regex attacks.

On 4/8/2019 4:55 PM, @lbutlr via dovecot wrote: > On 8 Apr 2019, at 16:35, Shawn Heisey via dovecot <dovecot at dovecot.org> wrote: >> I would like to create a sieve rule where I do a regex match on ALL headers, not a specific header. > > This is a really bad idea. Headers can be quite long, contain data that you do not have control over, and checking all headers will be very

I just installed glusterfs-swift 3.3.1 on a couple of Fedora 18 servers. This is based on swift 1.7.4 and has keystone in the config. I had experimented with the one based on swift 1.4.8 and tempauth and had some problems with it. The HOWTO I can find is still for the old one. Is there an updated one? I would also need to find some instructions on setting up keystone from scratch for

Hello Everyone, I am using Zabbix to monitor my Dovecot server, and my logs are filled with lines like this: > Oct 21 15:04:46 osaka dovecot[1256]: pop3-login: Aborted login (no auth > attempts in 0 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, secured, > session=<bWd0nr14SuF/AAAB> > Oct 21 15:05:29 osaka dovecot[1256]: imap-login: Aborted login (no auth > attempts

On 5/9/2018 10:15 PM, Shawn Heisey wrote: > It's been about three weeks since I asked this question.? All the > information I have available says that all users have no limits on > virtual memory, so it must be dovecot itself that sets the limit.? Can > that be changed in the 1.2 version?? I can't upgrade to 2.x yet. > > Here's an actual syslog entry, redacted to

I have an idea I'd like to run past everyone. Every gluster peer would have two NICs - one "public" and the other "private" with different IP subnets. The idea that I am proposing would be to have every gluster peer have all private peer addresses in /etc/hosts, but the public addresses would be in DNS. Clients would use DNS. The goal is to have all peer-to-peer

I have a machine with my mail service on it running Debian Squeeze. The version of dovecot on that server is 1.2.15. I'm building a new server with Ubuntu 18.04 (started with 16.04, upgraded in place), where the dovecot version is 2.2.33. I plan to migrate all my services to this new machine. The virtual mailboxes are on disk in maildir format, with accounts in a mysql database managed by

i use solr fts indexing. It worls very well but it have one database per system, not per user. Lets suppose i delete one or more e-mail users in system. How to remove them in solr database to reclaim space?

I was running the previous version of UFO, the 3.3 one that was based on Swift 1.4.8. Now there is a 3.3.1 based on Swift 1.7.4. The config that I used last time to enable S3 isn't working with the new one, just updated yesterday using yum. I was using tempauth in the old version and I'm still using tempauth. I have a CentOS 6 system and a Fedora 18 system with UFO on them. The

On 8 Apr 2019, at 17:16, Shawn Heisey via dovecot <dovecot at dovecot.org> wrote: > On 4/8/2019 4:55 PM, @lbutlr via dovecot wrote: >> On 8 Apr 2019, at 16:35, Shawn Heisey via dovecot <dovecot at dovecot.org> wrote: >>> I would like to create a sieve rule where I do a regex match on ALL headers, not a specific header. >> This is a really bad idea. Headers can

I'm configuring some Sieve scripts for virtual users. I'd like to keep the Sieve scripts somewhere "sensible". Currently, all the mail goes into /var/mail/vhosts/<domain>/<mailbox> So I thought a good place for the sieve script might be in there as well, for example: /var/mail/vhosts/example.com/username/sieve Is there any reason *not* to store the sieve scripts

__ Francis Augusto Medeiros-Logeay francis at francisaugusto.com Mobile: +47 45 17 14 91 Oslo, Norway Sent from a mobile device / Enviado a partir de dispositivo m?vel > On 24 Jul 2020, at 19:34, Shawn Heisey <elyograg at elyograg.org> wrote: > > ?On 7/22/2020 11:13 AM, Francis Augusto Medeiros-Logeay wrote: >> On Solr I get this error: >>

I'm getting mmap failed messages in syslog on version 1.2.15 for dovecot.index.cache files.? This old dovecot version is installed with debian packages.? The OS and all software is 64-bit. I've found info on this log message, with a suggested fix of raising vsz_limit ... but this seems to be a config option for dovecot 2.x, not 1.x. The file it complains about being unable to mmap is

Package: logcheck-database Version: 1.2.54 Severity: normal Tags: patch When views are used in bind, the logcheck filters don't catch the common informational log messages. Added regex bits to the filter definitions. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel:

https://bugzilla.samba.org/show_bug.cgi?id=10636 Summary: Feature request: Show current source path on receipt of Posix signal Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at

Dovecot package version is 1:1.2.15-7+deb6u1. It is in Debian 6.0.10, using the Debian package. The server is in my basement at home, and is exposed to the Internet so I can fully access my mail from anywhere. I use IMAP for reading mail. I have a number of folders in my mailbox that have thousands of messages in them, from mailing lists. When I'm at home, I have a LAN connection to the

I'm running, dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 uname -rm 5.8.13-200.fc32.x86_64 x86_64 grep _NAME /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" CPE_NAME="cpe:/o:fedoraproject:fedora:32" Solr FTS plugin is enabled/configured, mail_plugins = virtual acl fts fts_solr plugin { fts = solr fts_autoindex = yes

Hi, I am finally trying to use an fts engine with dovecot. My version is 2.3.7.2 under Ubuntu 20.04. I installed solr 7.7.3 and then 8.6.0 to see if this was a version-related error. I copied the schema from 7.7.0 as many people said this was fine. I get the following error when trying to reindex a user's mailbox: doveadm(francis at francisaugusto.com): Error: fts_solr: Indexing failed:

Hello, running dovecot 2.3.2.1 on Arch Linux, and installed solr 7.4.0. According to the wiki, there should be doc/solr-schema.xml, but I cannot find it. Tried "whereis dovecot": dovecot: /usr/bin/dovecot /usr/lib/dovecot /etc/dovecot /usr/include/dovecot /usr/share/dovecot /usr/share/man/man1/dovecot.1.gz But I cannot find any xml files using find /usr/{lib,share}/dovecot -name

I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way. Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ... 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,