Re: qmail-remote crashed.
Erwin Hoffmann <[email protected]> Mon, 18 Feb 2019 20:19:48 +0100
| Newsgroups | gmane.mail.qmail.general |
|---|---|
| Message-ID | <[email protected]> |
Hi, > Am 18.02.2019 um 18:26 schrieb Rejaine Silveira Monteiro = <[email protected]>: >=20 > Helo Erwin >=20 > I'm not using TLS and using qmail-1.03-jms1-7.10.patch (FORCE_TLS=3D0 > and DENY_TLS=3D1) > anyway, I created the tlsdestinations file as you indicated, but it > did not work. Sorry, caught the mail on the wrong mailing list ... I though you are = referring to my s/qmail. >=20 > the only problem is with clients using mail.protection.outlook.com >=20 > in the link below you can read that there may be problems with new > ips, due to some "policy reputation" stuff (our mta ip was changed > last nigth) and maybe that is why we can not send it there .. >=20 > = https://docs.microsoft.com/pt-br/office365/securitycompliance/removing-a-u= ser-domain-or-ip-address-from-a-block-list-after-sending-spam-email >=20 > I publish SPF, but not DMARC or DKIM ... so I guess I'll have to wait > a little longer .. There is however little, I can do in this case. Sorry.=20 Regards. --eh.=20 >=20 > Em seg, 18 de fev de 2019 =C3=A0s 13:35, Erwin Hoffmann = <[email protected]> escreveu: >>=20 >> Hi, >>=20 >>=20 >>> Am 18.02.2019 um 16:30 schrieb Rejaine Silveira Monteiro = <[email protected]>: >>>=20 >>> Hi all >>>=20 >>> I made this weekend the migration of my qmail to a virtual machine >>> with opensuse 42.2 leap, (4vcpu and 4G RAM and a faster internet = link, >>> better than the previous server). >>>=20 >>> everything is working fine and several emails are already being = sent >>> and received. >>>=20 >>> however I am having many segfault problems with qmail-remote. >>>=20 >>> the qmail settings as well as the defined limits are identical to = the >>> previous server. >>>=20 >>> kernel 4.4.62-18.6-default 64 bits >>> qmail-smtpd-softlimit =3D 66000000 >>=20 >> Remember: Softlimit only is in place for qmail-smtpd (receiving = emails); not sending emails. >>=20 >>=20 >>>=20 >>> it *seems* that errors occur when qmail tries to deliver mail to >>> *.mail.protection.outlook.com domains (at least it seems) , but I = can >>> access the mta's on port 25 using telnet. >>>=20 >>> here is a part of strace for qmail-rspawn >>>=20 >>> select(84, [0 3 5 7 9 11 13 15 17 19 21 25 27 29 31 33 35 37 39 41 = 43 >>> 45 47 49 51 53 55 57 59 61 63 65 67 69 71 75 77 79 81 83], NULL, = NULL, >>> NULL) =3D 1 (in [0]) >>> rt_sigprocmask(SIG_BLOCK, [CHLD], NULL, 8) =3D 0 >>> read(0, "\n\00017/1048242\[email protected]"..., 1024) =3D 65 >>> open("17/1048242", O_RDONLY|O_NONBLOCK) =3D 2 >>> fstat(2, {st_mode=3DS_IFREG|0644, st_size=3D11841, ...}) =3D 0 >>> pipe([23, 24]) =3D 0 >>> fcntl(23, F_SETFD, FD_CLOEXEC) =3D 0 >>> vfork() =3D 21071 >>> close(2) =3D 0 >>> fcntl(24, F_SETFD, FD_CLOEXEC) =3D 0 >>> rt_sigprocmask(SIG_UNBLOCK, [CHLD], NULL, 8) =3D 0 >>> select(84, [0 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 = 41 >>> 43 45 47 49 51 53 55 57 59 61 63 65 67 69 71 75 77 79 81 83], NULL, >>> NULL, NULL) =3D ? ERESTARTNOHAND (To be >>> restarted if no handler) >>> --- SIGCHLD {si_signo=3DSIGCHLD, si_code=3DCLD_KILLED, si_pid=3D20994,= >>> si_uid=3D361, si_status=3DSIGSEGV, si_utime=3D7, si_stime=3D0} --- >>> wait4(-1, [{WIFSIGNALED(s) && WTERMSIG(s) =3D=3D SIGSEGV}], WNOHANG, = NULL) =3D 20994 >>> close(32) =3D 0 >>> wait4(-1, 0x7ffd77421f1c, WNOHANG, NULL) =3D 0 >>> rt_sigreturn({mask=3D[]}) =3D -1 EINTR (Interrupted = system call) >>> rt_sigprocmask(SIG_BLOCK, [CHLD], NULL, 8) =3D 0 >>> rt_sigprocmask(SIG_UNBLOCK, [CHLD], NULL, 8) =3D 0 >>> select(84, [0 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 = 41 >>> 43 45 47 49 51 53 55 57 59 61 63 65 67 69 71 75 77 79 81 83], NULL, >>> NULL, NULL) =3D 1 (in [31]) >>> rt_sigprocmask(SIG_BLOCK, [CHLD], NULL, 8) =3D 0 >>> read(31, "", 128) =3D 0 >>> write(1, "\16\0Zqmail-remote crashed.\n\0", 26) =3D 26 >>> close(31) =3D 0 >>> rt_sigprocmask(SIG_UNBLOCK, [CHLD], NULL, 8) =3D 0 >>>=20 >>> any ideas? >>=20 >> Not currently. But you can give me some more informations: >>=20 >> a) What is the version of ucspi-ssl you have used (check the = symlinked ucspi.h). >> b) What is the OpenSSL/LibreSSL Version you are using? >>=20 >> In oder to diagnose TSL problems, disable TLS delivery to that = address: >>=20 >> tlsdestinations: >> !.outlook.com: >>=20 >> and see, what is happening. >>=20 >> Use >>=20 >> mconnect 104.47.9.33 >>=20 >> to check the settings after responding with 'ehlo you'. >>=20 >> Best regards. >> --eh. >>=20 >>=20 >>>=20 >>> -- >>> *Esta mensagem pode conter informa=C3=A7=C3=B5es confidenciais ou = privilegiadas, >>> sendo seu sigilo protegido por lei. Se voc=C3=AA n=C3=A3o for o = destinat=C3=A1rio ou a >>> pessoa autorizada a receber esta mensagem, n=C3=A3o pode usar, = copiar ou >>> divulgar as informa=C3=A7=C3=B5es nela contidas ou tomar qualquer = a=C3=A7=C3=A3o baseada nessas >>> informa=C3=A7=C3=B5es. Se voc=C3=AA recebeu esta mensagem por = engano, por favor avise >>> imediatamente ao remetente, respondendo o e-mail e em seguida = apague-o. >>> Agradecemos sua coopera=C3=A7=C3=A3o.* >>>=20 >>=20 >> Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id = 7E4034BE >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >=20 > --=20 > *Esta mensagem pode conter informa=C3=A7=C3=B5es confidenciais ou = privilegiadas,=20 > sendo seu sigilo protegido por lei. Se voc=C3=AA n=C3=A3o for o = destinat=C3=A1rio ou a=20 > pessoa autorizada a receber esta mensagem, n=C3=A3o pode usar, copiar = ou=20 > divulgar as informa=C3=A7=C3=B5es nela contidas ou tomar qualquer = a=C3=A7=C3=A3o baseada nessas=20 > informa=C3=A7=C3=B5es. Se voc=C3=AA recebeu esta mensagem por engano, = por favor avise=20 > imediatamente ao remetente, respondendo o e-mail e em seguida = apague-o.=20 > Agradecemos sua coopera=C3=A7=C3=A3o.* >=20 Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de | PGP Key-Id 7E4034BE