Re: [spamdyke-users] New version: spamdyke 5.0.1
Hi Sam, I sent you my spamdyke-qrv excessive output personally. But while I was looking inside I noticed that valias and vuserinfo commands exits with code 255: QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:94): executing command as UID 89, GID 89: /var/vpopmail/bin/valias QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:205): command exited with code 255: /var/vpopmail/bin/valias QRV-EXCESSIVE(validate()@validate-qrv.c:286): current_step = 58, working_username = aliaseddomain.com-forwardtest, working_domain = aliaseddomain.com, tmp_name = , tmp_filename = .qmail-default, tmp_path = /var/vpopmail/domains/originaldomain.com/.qmail-default, qmail_dash = -, qmail_ext = QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:94): executing command as UID 89, GID 89: /var/vpopmail/bin/vuserinfo QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:135): child process output 34 bytes: no such user forwardt...@originaldomain.com QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:205): command exited with code 255: /var/vpopmail/bin/vuserinfo QRV-EXCESSIVE(validate()@validate-qrv.c:286): current_step = 59, working_username = aliaseddomain.com-forwardtest, working_domain = aliaseddomain.com, tmp_name = , tmp_filename = .qmail-default, tmp_path = /var/vpopmail/domains/originaldomain/.qmail-default, qmail_dash = -, qmail_ext = QRV-EXCESSIVE(validate()@validate-qrv.c:1520): INVALID RECIPIENT recipient: forwardt...@aliaseddomain.com resolved username: aliaseddomain.com-forwardtest On 2015-05-01 14:34, Sam Clippinger via spamdyke-users wrote: Drat! Just when I thought I'd found every possible corner case, another corner appears. That should be one of those Laws of Programming or something... Anyway, I'm pretty confused -- vpopmail doesn't do anything internally to handle alias domains, it just adds another line to /var/qmail/users/assign and lets qmail do the work (as opposed to the way it handles forward addresses, which is very different). I'm not able to reproduce this. I setup a virtual machine with only one domain on it, created through vpopmail: test.spamdyke.org [5] Then I created a single mailbox under that domain: s...@test.spamdyke.org Then I added an alias domain: /home/vpopmail/bin/vaddaliasdomain alias.spamdyke.org [6] test.spamdyke.org [5] When I test validation of s...@test2.spamdyke.org, it works: spamdyke-qrv -v alias.spamdyke.org [6] samc I also tried creating a forward address under the real domain and validating it through the forward domain: /home/vpopmail/bin/valias -i s...@silence.org forwarda...@test.spamdyke.org Then tried validating the forward through the alias domain: spamdyke-qrv -v alias.spamdyke.org [6] forwardaddr But that works too. Could you provide a little more detail about how your aliases and forwards are set up? Or better yet, could you try recompiling spamdyke-qrv with excessive output and validating the address from the command line? You shouldn't need to replace the running binary to do this, just running it from the source folder should work: cd /path/to/src/spamdyke-5.0.1/spamdyke-qrv VALIAS_PATH=/path/to/valias VUSERINFO_PATH=/path/to/vuserinfo ./configure --with-vpopmail-support --with-excessive-output make ./spamdyke-qrv -vv aliaseddomain.com [1] forwardtest That will produce a ton of output, but it'll show every step spamdyke-qrv is using to validate the address. -- Sam Clippinger On May 1, 2015, at 1:53 PM, Konstantin via spamdyke-users spamdyke-users@spamdyke.org wrote: Oh, I did a mistake testing it in a rush. Actually the same problem left in this version. spamdyke-qrv doesn't check vpopmail forwards for aliased vpopmail domains. As I described before when I have aliaseddomain.com [1] as an alias domain for originaldomain.com [2] apamdyke-qrv ignores forwards for aliaseddomain.com [1]. For example when I'm trying to send an email to a vpopmail forward address forwardt...@aliaseddomain.com spamdyke-qrv refuses to accept it: mail # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.domain.net [3] ESMTP HELO 250 mail.domain.net [3] mail from: sen...@somedomain.com 250 ok rcpt to: forwardt...@originaldomain.com 250 ok DATA 354 go ahead Subject: test asd . 250 ok 1430505246 qp 28925 mail from: sen...@somedomain.com 250 ok rcpt to: forwardt...@aliaseddomain.com 554 Refused. The recipient address does not exist. Sorry about confusing you in my previous message. -- BR, Konstantin On 2015-05-01 11:27, Konstantin via spamdyke-users wrote: Testing it now. It really seems like issue with forwards on vpopmail aliased domains is fixed. So I can remove my workaround forwards now. Thank you, Sam! On 2015-05-01 10:36, Sam Clippinger via spamdyke-users wrote: spamdyke lives! spamdyke version 5.0.1 is now available: http://www.spamdyke.org/ [4] [1] This version fixes a ton of bugs, including a number of access violations that can lead to crashes. Most importantly, the recipient validation feature now works correctly (and has
Re: [spamdyke-users] New version: spamdyke 5.0.1
Oh, I did a mistake testing it in a rush. Actually the same problem left in this version. spamdyke-qrv doesn't check vpopmail forwards for aliased vpopmail domains. As I described before when I have aliaseddomain.com as an alias domain for originaldomain.com apamdyke-qrv ignores forwards for aliaseddomain.com. For example when I'm trying to send an email to a vpopmail forward address forwardt...@aliaseddomain.com spamdyke-qrv refuses to accept it: mail # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.domain.net ESMTP HELO 250 mail.domain.net mail from: sen...@somedomain.com 250 ok rcpt to: forwardt...@originaldomain.com 250 ok DATA 354 go ahead Subject: test asd . 250 ok 1430505246 qp 28925 mail from: sen...@somedomain.com 250 ok rcpt to: forwardt...@aliaseddomain.com 554 Refused. The recipient address does not exist. Sorry about confusing you in my previous message. -- BR, Konstantin On 2015-05-01 11:27, Konstantin via spamdyke-users wrote: Testing it now. It really seems like issue with forwards on vpopmail aliased domains is fixed. So I can remove my workaround forwards now. Thank you, Sam! On 2015-05-01 10:36, Sam Clippinger via spamdyke-users wrote: spamdyke lives! spamdyke version 5.0.1 is now available: http://www.spamdyke.org/ [1] This version fixes a ton of bugs, including a number of access violations that can lead to crashes. Most importantly, the recipient validation feature now works correctly (and has been exhaustively tested). Version 5.0.1 is backwards-compatible with version 5.0.0; simply replacing the old binary with the new one should be safe. -- Sam Clippinger Links: -- [1] http://www.spamdyke.org/ ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] New version: spamdyke 5.0.1
Testing it now. It really seems like issue with forwards on vpopmail aliased domains is fixed. So I can remove my workaround forwards now. Thank you, Sam! On 2015-05-01 10:36, Sam Clippinger via spamdyke-users wrote: spamdyke lives! spamdyke version 5.0.1 is now available: http://www.spamdyke.org/ [1] This version fixes a ton of bugs, including a number of access violations that can lead to crashes. Most importantly, the recipient validation feature now works correctly (and has been exhaustively tested). Version 5.0.1 is backwards-compatible with version 5.0.0; simply replacing the old binary with the new one should be safe. -- Sam Clippinger Links: -- [1] http://www.spamdyke.org/ ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users -- BR, Konstantin ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):
Unfortunately after about four hours I'm seeing segfaults in my logs again. :( I found it strange that it didn't happened right away after installing a new spamdyke version. ... Apr 13 11:31:11 mail kernel: spamdyke[26755]: segfault at 11 ip 7fbe85b03828 sp 7fff69e76990 error 4 in libc-2.20.so[7fbe85ab9000+18f000] Apr 13 11:31:12 mail kernel: spamdyke[26757]: segfault at 11 ip 7f58fb0ad828 sp 7fffc4458310 error 4 in libc-2.20.so[7f58fb063000+18f000] Apr 13 11:31:14 mail kernel: spamdyke[26852]: segfault at 11 ip 7fccb8c5e828 sp 7fffc7f75680 error 4 in libc-2.20.so[7fccb8c14000+18f000] Apr 13 11:31:30 mail kernel: spamdyke[27029]: segfault at 11 ip 7fe3c1cf2828 sp 7fff02d8dbe0 error 4 in libc-2.20.so[7fe3c1ca8000+18f000] Apr 13 11:31:44 mail kernel: spamdyke[27195]: segfault at 11 ip 7fa9c03f7828 sp 7fff603a84a0 error 4 in libc-2.20.so[7fa9c03ad000+18f000] Apr 13 11:31:44 mail kernel: spamdyke[27194]: segfault at 11 ip 7f26ce2e3828 sp 7fffd0e82ad0 error 4 in libc-2.20.so[7f26ce299000+18f000] Apr 13 11:32:09 mail kernel: spamdyke[27473]: segfault at 11 ip 7f9cb6c8b828 sp 7fff98b69090 error 4 in libc-2.20.so[7f9cb6c41000+18f000] Apr 13 11:32:10 mail kernel: spamdyke[27512]: segfault at 11 ip 7f211777f828 sp 7fffb6cfaf00 error 4 in libc-2.20.so[7f2117735000+18f000] Apr 13 11:32:36 mail kernel: spamdyke[27704]: segfault at 11 ip 7f8565bf6828 sp 7fff13651420 error 4 in libc-2.20.so[7f8565bac000+18f000] Apr 13 11:32:43 mail kernel: spamdyke[27829]: segfault at 11 ip 7f8752792828 sp 7fff05047470 error 4 in libc-2.20.so[7f8752748000+18f000] ... Let me know if I can help you to debug this issue. BR, Konstantin On 2015-04-12 17:16, Konstantin via spamdyke-users wrote: LOL. I think it even has a graphic installer in our days. Which I never used actually. :) If you need a test environment I can always make one for you. Your patch is working, I think. I don't see kernel general protection errors in logs anymore. So I assume that problem in my case is fixed. The only one that bothers me now is that spamdyke-qrv fails to check valid recipients for aliased domain forwards. So to make that work now I have to create an additional duplicate forwards for these aliased domains as workaround. Everything else is just great. :) Thank you. BR, Konstantin On 2015-04-12 11:13, Sam Clippinger via spamdyke-users wrote: Wow Gentoo, really? Every time I consider Gentoo, I start getting flashbacks of installing Slackware 1.2 from floppy disks back in the elder days. Nevertheless, I tried installing Gentoo to try to duplicate your environment and gave up about halfway through the install guide... I can't remember how far I got, but it was one of the pages in the low 500's, I think. :) Anyway, I've spent the last couple days hunting bugs and I've found a few that might be responsible for these errors. Could you try applying this patch and see if it resolves the segfaults? It should apply cleanly to spamdyke 5.0.0: cd /path/to/src/spamdyke-5.0.0 patch -p1 spamdyke-5.0.0-segfault.patch make Then install the new binary over the old one. If this doesn't fix your crashes, at least it'll fix a lot of other potential ones! -- Sam Clippinger On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users spamdyke-users@spamdyke.org wrote: Hi Everyone! On a virtual gentoo server I currently have: ebuild: dev-libs/openssl-1.0.1l-r1 OpenSSL 1.0.1l 15 Jan 2015 ebuild: sys-devel/gcc-4.8.4 gcc (Gentoo 4.8.4 p1.4, pie-0.6.1) 4.8.4 ebuild: sys-libs/glibc-2.20-r2 glibc 2.20 ebuild: sys-kernel/gentoo-sources-3.17.7 custom build kernel 3.17.7-gentoo-domU Not sure about /etc/xinetd.d/smtps_psa since I don't have it but unning process looks like this: 10821 ? S 4:07 /usr/bin/tcpserver -p -v -R -x /etc/tcprules.d/tcp.qmail-smtp.cdb -c 40 -u 201 -g 200 0.0.0.0 smtp spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd /var/vpopmail/bin/vchkpw /bin/true Let me know if I can provide you something more relevant, Sam. -- BR, Konstantin On 2015-04-09 20:27, Sam Clippinger via spamdyke-users wrote: I've been looking through the many log files you sent, thank for being so thorough! From what I can see in the files you and Konstantin have sent, it looks like the problem lies somewhere in the TLS/SSL cleanup routine. In your log files, all of the crashes seem to happen just after a client fails to connect with SMTPS due to a cipher negotiation problem. There are only four different OpenSSL error codes being logged, which translate as: error:1406B0CB:SSL routines:GET_CLIENT_MASTER_KEY:peer error no cipher error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version Those appear to be the only connections that are crashing, other connections that successfully negotiate their TLS/SSL sessions
Re: [spamdyke-users] Segfault in spamdyke (libc-2.14.1.so) since use of version 5 | *** glibc detected *** /usr/local/bin/spamdyke: double free or corruption (fasttop):
LOL. I think it even has a graphic installer in our days. Which I never used actually. :) If you need a test environment I can always make one for you. Your patch is working, I think. I don't see kernel general protection errors in logs anymore. So I assume that problem in my case is fixed. The only one that bothers me now is that spamdyke-qrv fails to check valid recipients for aliased domain forwards. So to make that work now I have to create an additional duplicate forwards for these aliased domains as workaround. Everything else is just great. :) Thank you. BR, Konstantin On 2015-04-12 11:13, Sam Clippinger via spamdyke-users wrote: Wow Gentoo, really? Every time I consider Gentoo, I start getting flashbacks of installing Slackware 1.2 from floppy disks back in the elder days. Nevertheless, I tried installing Gentoo to try to duplicate your environment and gave up about halfway through the install guide... I can't remember how far I got, but it was one of the pages in the low 500's, I think. :) Anyway, I've spent the last couple days hunting bugs and I've found a few that might be responsible for these errors. Could you try applying this patch and see if it resolves the segfaults? It should apply cleanly to spamdyke 5.0.0: cd /path/to/src/spamdyke-5.0.0 patch -p1 spamdyke-5.0.0-segfault.patch make Then install the new binary over the old one. If this doesn't fix your crashes, at least it'll fix a lot of other potential ones! -- Sam Clippinger On Apr 9, 2015, at 11:05 PM, Konstantin via spamdyke-users spamdyke-users@spamdyke.org wrote: Hi Everyone! On a virtual gentoo server I currently have: ebuild: dev-libs/openssl-1.0.1l-r1 OpenSSL 1.0.1l 15 Jan 2015 ebuild: sys-devel/gcc-4.8.4 gcc (Gentoo 4.8.4 p1.4, pie-0.6.1) 4.8.4 ebuild: sys-libs/glibc-2.20-r2 glibc 2.20 ebuild: sys-kernel/gentoo-sources-3.17.7 custom build kernel 3.17.7-gentoo-domU Not sure about /etc/xinetd.d/smtps_psa since I don't have it but unning process looks like this: 10821 ? S 4:07 /usr/bin/tcpserver -p -v -R -x /etc/tcprules.d/tcp.qmail-smtp.cdb -c 40 -u 201 -g 200 0.0.0.0 smtp spamdyke -f /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd /var/vpopmail/bin/vchkpw /bin/true Let me know if I can provide you something more relevant, Sam. -- BR, Konstantin On 2015-04-09 20:27, Sam Clippinger via spamdyke-users wrote: I've been looking through the many log files you sent, thank for being so thorough! From what I can see in the files you and Konstantin have sent, it looks like the problem lies somewhere in the TLS/SSL cleanup routine. In your log files, all of the crashes seem to happen just after a client fails to connect with SMTPS due to a cipher negotiation problem. There are only four different OpenSSL error codes being logged, which translate as: error:1406B0CB:SSL routines:GET_CLIENT_MASTER_KEY:peer error no cipher error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number error:1409442E:SSL routines:SSL3_READ_BYTES:tlsv1 alert protocol version Those appear to be the only connections that are crashing, other connections that successfully negotiate their TLS/SSL sessions seem to be fine. I haven't had any success in reproducing this bug yet, but I'm still working on it. I'm curious about some of the versions on your server though -- could you send me the version numbers of OpenSSL, gcc and the kernel you're running? Could you also send me your /etc/xinetd.d/smtps_psa file (the one that starts spamdyke for SMTPS)? I'd like to see how it's being started so I can try to simulate it. Thanks! -- Sam Clippinger On Apr 7, 2015, at 5:44 PM, Dirk via spamdyke-users spamdyke-users@spamdyke.org wrote: Dear Sam, at first thank you for glorious work with spamdyke! I'm using it since several years and it's very helpful to me. At 30th march 2015 I've done an upgrade to version 5 (previous: last 4 version). Since then I often get a segfault in spamdyke: Tue Apr 7 12:05:19 2015] spamdyke[13607]: segfault at 14 ip 7f60ce1e3ba8 sp 7fff6bac3ce0 error 4 in libc-2.14.1.so[7f60ce19b000+187000] [Tue Apr 7 12:16:20 2015] spamdyke[13959]: segfault at 14 ip 7fe1145bdba8 sp 7fffa6426b90 error 4 in libc-2.14.1.so[7fe114575000+187000] [Tue Apr 7 12:47:31 2015] spamdyke[15309]: segfault at 14 ip 7f9971e49ba8 sp 7fffa03aad20 error 4 in libc-2.14.1.so[7f9971e01000+187000] [Tue Apr 7 15:30:51 2015] spamdyke[21795]: segfault at 14 ip 7fb0cac66ba8 sp 7fff209aa400 error 4 in libc-2.14.1.so[7fb0cac1e000+187000] [Tue Apr 7 16:13:02 2015] spamdyke[23130]: segfault at 14 ip 7f47bd14eba8 sp 7fff5b5fd1e0 error 4 in libc-2.14.1.so[7f47bd106000+187000] [Tue Apr 7 17:22:50 2015] spamdyke[26691]: segfault at 14 ip 7f24e499bba8 sp 7fff0cbd2060 error 4 in libc-2.14.1.so[7f24e4953000+187000] [Tue Apr 7 22:37:46 2015] spamdyke[6768]: segfault at 14 ip 7fcd7c1ffba8 sp 7fff0fd874f0 error 4 in libc-2.14.1.so[7fcd7c1b7000
[spamdyke-users] Vesrion 5.0.0 reject-sender=no-mx overriding based on source IP address
Hi Sam, Thank you very much for what you are doing. I'm testing spamdyke 5.0.0 now and I found spamdyke-qrv feature very useful. Sometimes it crashes, but still usable. :) I'm trying to make some exceptions for emails that comes from a certain IP subnets using config-dir=/etc/spamdyke/config.d mail spamdyke # cat /etc/spamdyke/config.d/_ip_/10/1 reject-empty-rdns=0 reject-sender=none And it doesn't seem working for me. Did I missed something? -- BR, Konstantin ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Problems Using spamdyke-qrv With Aliases In Alias Domain
Hi Martin, Thank you very much for you letter. On 2015-01-10 07:40, Martin H. Sluka wrote: Hi Konstantin, I have difficulties using spamdyke-qrv in combination with aliases on aliased domains with vpopmail. For example when I'm creating a new domain original-domain.com with alias domain alias-domain.com and then after creating forward al...@original-domain.com I expect to be receiving email on al...@alias-domain.com as well. But spamdyke-qrv filters it. :( maybe it's the bug explained here: http://comments.gmane.org/gmane.mail.spam.spamdyke.user/4055 At least, this one caused trouble at our site in connection with forwardings to remote addresses in .qmail files. It doesn't look like a problem with .qmail files to me, because I'm successfully using it with mailman installation which relies on these files. The following patch works for me as a workaround: --- spamdyke-5.0.0/spamdyke-qrv/validate-qrv.c 2014-01-27 23:28:00.0 +0100 +++ spamdyke-5.0.0/spamdyke-qrv/validate-qrv.c.patched 2014-12-30 That is, instead of trying to recursively resolve aliases, I just consider their status as unknown, which lets spamdyke accept messages by default. If that does not work for you, please send the output of spamdyke-qrv -vv alias-domain.com alias to the list (assuming that you have configured and compiled spamdyke-qrv --with-excessive-output). Thank you very much for you patch. I'll try to look through the spamdyke-qrv logic deeper now. Full excessive output is attached. But I think here is the problem with aliases on aliases domains starts: ... skipped... QRV-EXCESSIVE(validate()@validate-qrv.c:1060): found vpopmail command on line 0 QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:93): executing command as UID 89, GID 89: /var/vpopmail/bin/valias QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:192): command exited with code 255: /var/vpopmail/bin/valias QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:93): executing command as UID 89, GID 89: /var/vpopmail/bin/vuserinfo QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:134): child process output 39 bytes: no such user al...@original-domain.com QRV-EXCESSIVE(exec_command_argv()@exec-qrv.c:192): command exited with code 255: /var/vpopmail/bin/vuserinfo QRV-EXCESSIVE(validate@validate-qrv.c:1131): INVALID RECIPIENT recipient: al...@alias-domain.com resolved username: alias-domain.com-alias QRV-EXCESSIVE(validate()@validate-qrv.c:160): current_step = 37, tmp_username = alias-domain.com-alias, tmp_domain = alias-domain.com, tmp_name = , tmp_filename = .qmail-default, tmp_path = /var/vpopmail/domains/1/original-domain.com/.qmail-default, qmail_dash = -, qmail_ext = QRV-EXCESSIVE(read_file()@fs-qrv.c:370): opened file for reading: /var/vpopmail/domains/1/original-domain.com/.qmail-default valias can't find the required alias on aliased-domain probably because it exist only in mysql database of the original domain. When I'm using valias to show all aliases on alias-domain.com it gives empty result. mail ~ # valias -s original-domain.com al...@original-domain.com - postmas...@original-domain.com mail ~ # valias -s alias-domain.com mail ~ # But delivery without spamdyke's reject-recipient=invalid to postmas...@original-domain.com address using al...@alias-domain.com recipient in qmail works just fine. So I consider it as a spamdyke-qrv's easy reproducible bug. -- BR, KonstantinQRV-EXCESSIVE(process_command_line()@configuration-qrv.c:209): configured option VALIAS_PATH = /var/vpopmail/bin/valias QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:210): configured option VUSERINFO_PATH = /var/vpopmail/bin/vuserinfo QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:214): processed command line: qmail_percenthack_file = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:215): processed command line: qmail_locals_file = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:216): processed command line: qmail_virtualdomains_file = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:217): processed command line: qmail_assign_cdb = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:218): processed command line: qmail_defaultdelivery_file = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:219): processed command line: qmail_envnoathost_file = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:220): processed command line: qmail_me_file = (NULL) QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:221): processed command line: recipient_domain = alias-domain.com QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:222): processed command line: recipient_username = alias QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:256): final option value: qmail_percenthack_file = /var/qmail/control/percenthack QRV-EXCESSIVE(process_command_line()@configuration-qrv.c:257): final option value: qmail_locals_file =
[spamdyke-users] Problems Using spamdyke-qrv With Aliases In Alias Domain
Hi guys, I have difficulties using spamdyke-qrv in combination with aliases on aliased domains with vpopmail. For example when I'm creating a new domain original-domain.com with alias domain alias-domain.com and then after creating forward al...@original-domain.com I expect to be receiving email on al...@alias-domain.com as well. But spamdyke-qrv filters it. :( In example below you can see how spamdyke rejects email to al...@alias-domain.com, but not to al...@original-domain.com mail # vadddomain original-domain.com test mail # vaddaliasdomain original-domain.com alias-domain.com mail # valias -i postmas...@original-domain.com al...@original-domain.com mail # telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.some-domain.com ESMTP HELO mail 250 mail.some-domain.com mail from: tes...@another-domain.com 250 ok rcpt to: al...@alias-domain.com 554 Refused. The recipient address does not exist. rcpt to: al...@original-domain.com 250 ok quit 221 mail.some-domain.com Connection closed by foreign host. My current spamdyke version is 5.0.0+TLS+CONFIGTEST+DEBUG mail # cat /etc/spamdyke/spamdyke.conf log-level=verbose qmail-rcpthosts-file=/var/qmail/control/rcpthosts tls-certificate-file=/var/qmail/control/servercert.pem graylist-level=always-create-dir graylist-dir=/var/tmp/spamdyke/graylist graylist-exception-rdns-dir=/etc/spamdyke/never-graylist graylist-exception-ip-file=/etc/spamdyke/graylist-exception-ip-file graylist-exception-rdns-file=/etc/spamdyke/graylist-exception-rdns-file graylist-max-secs=3369600 graylist-min-secs=50 reject-empty-rdns reject-unresolvable-rdns reject-sender=no-mx rejection-text-recipient-same-as-sender rhs-blacklist-entry=sbl-xbl.spamhaus.org greeting-delay-secs=0 max-recipients=100 connection-timeout-secs=1800 idle-timeout-secs=120 config-dir=/etc/spamdyke/config.d rdns-blacklist-file=/etc/spamdyke/rdns-keyword-blacklist-file reject-recipient=invalid recipient-validation-command=/usr/local/bin/spamdyke-qrv spamdyke-qrv was configured using vpopmail: ./configure --with-vpopmail-support VALIAS_PATH=/path/to/valias VUSERINFO_PATH=/path/to/vuserinfo Any ideas how to fix it? -- BR, Konstantin ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
