search for: tobster

...plugin is added to the mail_plugins for imap. Thanks for the hint with mail_debug. After enabling it I can see that the program seems to be called, so filter should not be the problem. But the result is that the message appears unencrypted in my sent folder > Apr 6 08:20:26 mbox2 dovecot: imap(tobster at brain-force.ch): Debug: imapsieve: mailbox Sent: APPEND event > Apr 6 08:20:26 mbox2 dovecot: imap(tobster at brain-force.ch): Debug: sieve: Pigeonhole version 0.4.16 (fed8554) initializing > Apr 6 08:20:26 mbox2 dovecot: imap(tobster at brain-force.ch): Debug: sieve: include: sieve_glob...

...installed dovecot-mysql.x86_64 1:2.2.26.0-2.el7.centos installed dovecot-pigeonhole.x86_64 1:2.2.26.0-2.el7.centos installed all over sudden both dovecot "think" that the mailbox filesystem is read only and fill the logs with Oct 28 11:39:50 mbox1 dovecot: lmtp(tobster at brain-force.ch): Error: ssY/MGZQ9FnoLgAAC4IaJw:2: sieve: failed to open logfile (LOGGING TO STDERR): open(/home/vmail/brain-force.ch/tobster/.dovecot.sieve.log) failed: Read-only file system But a test at cli shows that I can write to the location $ echo "test" >/home/vmail/brain-...

Hello list I currently have an issue with an imapsieve script on my dovecot server CentOS Linux release 7.3.1611 (Core) Dovecot 2.2.26.0 (23d1de6) Pigeonhole 2.2.26.0 The goal is to "fire" an imapsieve script upon mailclient saves message to sent folder I setup the following in 90-plugin.conf: plugin { sieve_plugins = sieve_imapsieve sieve_extprograms sieve_extensions =

...1:2.2.26.0-2.el7.centos > installed > dovecot-pigeonhole.x86_64 1:2.2.26.0-2.el7.centos > installed > > all over sudden both dovecot "think" that the mailbox filesystem is read > only and fill the logs with > > Oct 28 11:39:50 mbox1 dovecot: lmtp(tobster at brain-force.ch): Error: > ssY/MGZQ9FnoLgAAC4IaJw:2: sieve: failed to open logfile (LOGGING TO > STDERR): open(/home/vmail/brain-force.ch/tobster/.dovecot.sieve.log) > failed: Read-only file system > > But a test at cli shows that I can write to the location > > $ echo &quo...

Hi list I just realized that that I don not receive all mails in my mailbox (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers (running postfix) the queue fills up with mails that cannot be delivered via lmtp to my backend servers. The error message on the frontend is "lost connection with backend while sending data" When I checked the logs on the backend server I found

...is built based on 0.4.14 Should I try with 0.4.16? I will build it again this afternoon with the version you suggested and report back with the results. Thanks for the help here tobi ----- Originale Nachricht ----- Von: Stephan Bosch <stephan at rename-it.nl> Gesendet: 08.01.17 - 11:00 An: tobster at brain-force.ch@pgp.brain-force.ch, Dovecot Mailing List <dovecot at dovecot.org> Betreff: Re: dovecot-pigeonhole running external script ends with signal 11 > Op 1/8/2017 om 10:00 AM schreef Tobi: >> Hi Stephan >> >> according to ps aux the process that segfaults is...

...at I don't want to provide backup user with unnecessary write permissions within maildirs and mail user within backup logs dir. I was talking about mail_user:mail_group 0750 on dirs and 0640 on files. (Or, possibly, mail_user:backup_group 2750 and 2640.) 26.12.2014, 11:19, "Tobi" <tobster at brain-force.ch>: > Whats the reason you do not want to use default dovecot user. Your idea would assume that at least the group must have write access. For me a no-go on mailboxes. > > Am 24. Dezember 2014 13:21:15 MEZ, schrieb Von Random <von at vdrandom.org>: >> Hello....

...ome non-compatible changes in 2.2.27 that makes older versions of pigeonhole incompatible, when external programs are used. We moved the program-client code from pigeonhole to dovecot core and made some changes to it to facilitate other uses for it. Aki > On January 8, 2017 at 3:33 PM Tobi <tobster at brain-force.ch> wrote: > > > Hi Stephan > > thanks for insisting on the pigeonhole version. That seems to be the reason. With 0.4.16 I built the rpms again and after yum install on my mailbox servers the script "terminated normally" > > Just one thing that d...

Op 25-4-2016 om 18:01 schreef Timo Sirainen: > On 25 Apr 2016, at 13:48, Tobi <tobster at brain-force.ch> wrote: >> Hi list >> >> I just realized that that I don not receive all mails in my mailbox >> (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers >> (running postfix) the queue fills up with mails that cannot be delivered >>...

> On October 28, 2017 at 1:41 PM Tobi <tobster at brain-force.ch> wrote: > > > Hello list > > I saw the response from Vlad in my queue (as dovecot was broken there > has been no delivery to mailbox) but after fix and queue flush Vlads > message does not show up in my mailbox. > > > Check the systemd unit for...

...not go in my brain so far: in 1 out of maybe 20 cases the script worked with 0.4.14 without an error. But thats not important as with 0.4.16 it works in 100% of processed mails so far. Again thanks a lot for the great help here and happy mailing tobi ----- Originale Nachricht ----- Von: Tobi <tobster at brain-force.ch> Gesendet: 08.01.17 - 12:22 An: Dovecot Mailing List <dovecot at dovecot.org> Betreff: Re: dovecot-pigeonhole running external script ends with signal 11 > Hi Stephan > > currently the rpm is built based on 0.4.14 > Should I try with 0.4.16? I will build it...

...filesystem access and mail_access_groups is also useless for some reason. It just does not change anything. Probably because I don't use mail_location and variables when I provide path for home. (It's stored as is in a database on mailbox creation.) 26.12.2014, 12:07, "Tobi" <tobster at brain-force.ch>: > Have you checked the dovecot wiki for 'filepermissions in shared mailboxes' ? > Explains how dovecot set ACL when creating mailboxes > > Am 26. Dezember 2014 09:37:37 MEZ, schrieb Von Random <von at vdrandom.org>: >> Err, my bad, of course 06...

Hi Aki yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole rpm is based on 0.4.14 Do you think that the error might come from self building the rpms? Regards tobi Am 04.01.2017 um 08:55 schrieb Aki Tuomi: > On 04.01.2017 09:49, Tobi wrote: >> Hi Stephan >> >> Am 03.01.2017 um 21:12 schrieb Stephan Bosch: >> >>> Since you're using

Hello, I'm using dovecot 2.2.13 on Debian stable. My users are authenticated through PAM, and stored in an LDAP backend I'm trying to set-up replication with ssl, following (mainly) this : http://wiki2.dovecot.org/Replication 1) I only diverted from the instructed setup by not setting "doveadm_port = 12345", as it would give me errors of the like: > Fatal:

Hello, Thunderbird has been bugging us with connection errors. Dovecot is installed on a local server that carries a local IP and a public IP. When Thunderbird on a local client connects successfully, Wireshark shows a SYN request from the client's IP on LAN to the public IP of the server, followed by the ACK from the same public IP. When Thunderbird on the same local client fails to connect,

I wonder if there is an easy way to provide dovecot a flat text file of ipv4 #'s which should be ignored or dropped? I have accumulated 45,000+ IPs which routinely try dictionary and 12345678 password attempts. The file is too big to create firewall drops, and I don't want to compile with wrappers *if* dovecot has an easy ability to do this. If dovecot could parse a flat text file of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 01.03.2015 um 08:53 schrieb Jim Pazarena: > I have accumulated 45,000+ IPs which routinely try dictionary and > 12345678 password attempts. The file is too big to create firewall > drops, Have you also checked ipset (http://ipset.netfilter.org/) Its extremely powerful even with huge block lists -----BEGIN PGP SIGNATURE----- Version:

I'm not sure that this is a dovecot issue. For me it sounds more that the router somehow learned dovecots LAN ip and then takes a shortcut by sending the packets directly to dovecot on routers LAN interface instead of going all the way to the WAN interface and then back to LAN. You could verify if that is the case by tcpdump on dovecot and see on what interface the request comes is. If that

Hello list we encounter a weird SSL issue with one of our dovecot (2.2.24 on Centos6) which we can only explain if our assumtion is correct :-) Symptoms are that imaps connections (on port 993) suddenly get veeeery slow. Up to 180s for one connection with openssl s_client The thing we do not understand is that in the same time imap connections with starttls are just 1s. We can see that entropy on

Hello, my first post in this list. Hope it's the right place.:-) I'm having a problem running getmail together with Dovecot LDA for virtual users. To achive this I let getmail run under the user that owns the virtual email accounts-root. The problem is that getmail is running under the user vmail and therefore the emails received will be put into vmail's mailbox. But the emails