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 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/ [4]
_______________________________________________
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



Links:
------
[1] http://aliaseddomain.com
[2] http://originaldomain.com
[3] http://mail.domain.net
[4] http://www.spamdyke.org/
[5] http://test.spamdyke.org
[6] http://alias.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

Reply via email to