search for: envidence

My nightly logwatch report had a never before seen section last night, "barracuda spam firewall". I have not problem with the emails it noted as being rejected. But I've always thought of "barracuda" as a commercial product. I have neither configured nor enabled any barracuda software and "yum list '*barrac*'" comes up empty. What is this? Jon -- Jon

Hy everybody, first, excuse me for my english, I''m french (sorry for that :D). My actual problem is that I encountered a [b]NoMethodError[/b] when I tried to access to a session value that is not nil. I''m doing some ajax calls and I afffect the key/value and access to session variable in the same controler "injection_controller.rb". I also access to session in a view

Hello! I'm having crashes with LMTP delivery when user is over quota on the latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. I see the issue has been fixed on January 17, but it doesn't seem to have made it into 2.3.0.1 (I compared with the source from https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz).

Got a coredump: Mar 5 15:09:42 mail-cbf dovecot: lmtp(backup at backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master: service(lmtp): child 15425 killed with signal 6 (core dumped) #0 0x00007fea19977428 in __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 resultvar = 0 pid = 15425 selftid = 15425 #1 0x00007fea1997902a in

On 04.03.2018 16:25, Reio Remma wrote: > Hello! > > I'm having crashes with LMTP delivery when user is over quota on the > latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. > > I see the issue has been fixed on January 17, but it doesn't seem to > have made it into 2.3.0.1 (I compared with the source from >

Hi Stephan, Here it is: Program received signal SIGSEGV, Segmentation fault. p_strdup (pool=pool at entry=0x55555579bc20, str=0x6d65642e6c69616d <error: Cannot access memory at address 0x6d65642e6c69616d>) at strfuncs.c:51 51????? strfuncs.c: No such file or directory. (gdb) bt full #0? p_strdup (pool=pool at entry=0x55555579bc20, str=0x6d65642e6c69616d <error: Cannot access memory at

Op 3/5/2018 om 3:14 PM schreef Ralf Hildebrandt: > Got a coredump: > > Mar 5 15:09:42 mail-cbf dovecot: lmtp(backup at backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master: service(lmtp): child 15425 killed with signal 6 (core dumped) Hmm, yes, I think this an unnecessary RFC5322 -> RFC5321 address translation. Will look at making a fix tomorrow. Regards,

That's a good thought. I'm building from the alpine repo and I indeed see pigeonhole is 0.5.5 https://git.alpinelinux.org/aports/tree/main/dovecot/APKBUILD?h=3.8-stable Let me build it with 0.5.7.2 Regards, ? Laszlo On 2019. 10. 07. 10:45, Stephan Bosch via dovecot wrote: > > > On 07/10/2019 10:17, Demonhost via dovecot wrote: >> Hi Stephan, >> >> Here it

On 07/10/2019 10:17, Demonhost via dovecot wrote: > Hi Stephan, > > Here it is: > We still can't reproduce it here. First of all, did you update Pigeonhole along with Dovecot? This kind of weirdness can happen when Pigeonhole was compiled against a different version of Dovecot. You could compile Pigeonhole manually as well to make sure, which also gives you the opportunity to

I think alpine does not have that https://pkgs.alpinelinux.org/packages?name=dovecot*&branch=v3.8&repo=main&arch=x86_64 https://git.alpinelinux.org/aports/tree/main/dovecot/APKBUILD?h=3.8-stable What else would help? strace? On 2019. 10. 06. 23:05, Stephan Bosch via dovecot wrote: > > > On 06/10/2019 23:03, Demonhost wrote: >> Hi Stephan, >> >> I managed