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

Reply via email to