Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello, people! :) > > Probably I've missed something, but there is any means to integrate > qmail, spamdyke and chkuser (mine was with quotacheck)? I don't want > to reinstall/replace qmail (well, 215 domains are hosted at this > server). Right now all messages that have passed spamdyke are trying > to be delivered, even to non-existant users/domains. It's very > annoying (queue is loaded with junk for 1500-1600 messages > permanently). I've searched in mailing list, but didn't found anything > :( > I think that checking for the existence of users is a future feature of spamdyke, and is presently handled by the delivery end of things, after the message has been accepted from the sending server. Your undeliverable messages should expire from the local delivery queue after they've reached the age specified in your queuelifetime file. You might want to shorten the time (# of seconds) specified there. If you're using vpopmail, qmailadmin allows you to set your catchall action on the email accounts page. Without qmailadmin, you'll need to edit the .qmail-default file for each domain manually. You can either delete or bounce as a catchall action. Deleting is preferred, as bouncing contribute to backscatter spam. HTH -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
chkuser is just another filter that intercepts the data before qmail sees it, so I don't see any reason it won't work with spamdyke. IIRC, QmailToaster uses both chkuser and spamdyke. When chkuser rejects a recipient, spamdyke should log it with "DENIED_OTHER". -- Sam Clippinger Youri V. Kravatsky wrote: > Hello, people! :) > > Probably I've missed something, but there is any means to integrate > qmail, spamdyke and chkuser (mine was with quotacheck)? I don't want > to reinstall/replace qmail (well, 215 domains are hosted at this > server). Right now all messages that have passed spamdyke are trying > to be delivered, even to non-existant users/domains. It's very > annoying (queue is loaded with junk for 1500-1600 messages > permanently). I've searched in mailing list, but didn't found anything > :( > > ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
That's indeed the behavior I see with qmail-toaster. Spamdyke is still an add-on at this point, but will be included with the 'stock' system in the next major release. Sam Clippinger wrote: > chkuser is just another filter that intercepts the data before qmail > sees it, so I don't see any reason it won't work with spamdyke. IIRC, > QmailToaster uses both chkuser and spamdyke. When chkuser rejects a > recipient, spamdyke should log it with "DENIED_OTHER". > > -- Sam Clippinger > > Youri V. Kravatsky wrote: >> Hello, people! :) >> >> Probably I've missed something, but there is any means to integrate >> qmail, spamdyke and chkuser (mine was with quotacheck)? I don't want >> to reinstall/replace qmail (well, 215 domains are hosted at this >> server). Right now all messages that have passed spamdyke are trying >> to be delivered, even to non-existant users/domains. It's very >> annoying (queue is loaded with junk for 1500-1600 messages >> permanently). I've searched in mailing list, but didn't found anything >> :( >> >> -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello Sam, Wednesday, September 2, 2009, 12:05:59 AM, you wrote: > chkuser is just another filter that intercepts the data before qmail > sees it, so I don't see any reason it won't work with spamdyke. IIRC, > QmailToaster uses both chkuser and spamdyke. When chkuser rejects a > recipient, spamdyke should log it with "DENIED_OTHER". How should I activate chkuser with spamdyke? Add chkuser before/after spamdyke in the shell script that starts qmail? Or spamdyke has means to call to additional filters from its config? -- Best regards, Yourimailto:loka...@gmail.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Sam, > > Wednesday, September 2, 2009, 12:05:59 AM, you wrote: > >> chkuser is just another filter that intercepts the data before qmail >> sees it, so I don't see any reason it won't work with spamdyke. IIRC, >> QmailToaster uses both chkuser and spamdyke. When chkuser rejects a >> recipient, spamdyke should log it with "DENIED_OTHER". > How should I activate chkuser with spamdyke? Add chkuser before/after > spamdyke in the shell script that starts qmail? Or spamdyke has means to > call to additional filters from its config? > chkuser is implemented via a patch to qmail. -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello Eric, > chkuser is implemented via a patch to qmail. Well, BEFORE spamdyke adding, my chkuser was working perfectly (rejecting mails to non-existant and overquoting users). Now, as far as I understand, spamdyke injects received mails directly to qmail queue, or send them through local smtp, so they are always accepted, so queue of my server is full of autoresponses. Sam said, that there is no problem in using spamdyke and chkuser - and I again asking - how can I do it? I didn't found any traces about it in docs/faqs. -- Best regards, Yourimailto:loka...@gmail.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Eric, > >> chkuser is implemented via a patch to qmail. > Well, BEFORE spamdyke adding, my chkuser was working perfectly (rejecting > mails to non-existant and overquoting users). Now, as far as I understand, > spamdyke injects received mails directly to qmail queue, or send them > through local smtp, so they are always accepted, so queue of my server is > full of autoresponses. This is not quite right. Spamdyke passes them on to qmail-smtpd according to how you've configured your smtp/run file. An example is: #!/bin/sh QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` SPAMDYKE="/usr/local/bin/spamdyke" SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf" SMTPD="/var/qmail/bin/qmail-smtpd" TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb" HOSTNAME=`hostname` VCHKPW="/home/vpopmail/bin/vchkpw" REQUIRE_AUTH=0 exec /usr/bin/softlimit -m 2000 \ /usr/bin/tcpserver -v -R -H -l $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \ $SPAMDYKE --config-file $SPAMDYKE_CONF \ $SMTPD $VCHKPW /bin/true 2>&1 > Sam said, that there is no problem in using spamdyke > and chkuser - and I again asking - how can I do it? I didn't found any > traces about it in docs/faqs. > -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Sam, > > Wednesday, September 2, 2009, 12:05:59 AM, you wrote: > >> chkuser is just another filter that intercepts the data before qmail >> sees it, so I don't see any reason it won't work with spamdyke. IIRC, >> QmailToaster uses both chkuser and spamdyke. When chkuser rejects a >> recipient, spamdyke should log it with "DENIED_OTHER". > How should I activate chkuser with spamdyke? Add chkuser before/after > spamdyke in the shell script that starts qmail? Or spamdyke has means to > call to additional filters from its config? chkuser works together with spamdyke without any modifications. They are completely independent and do not interfere in any way. -- Teodor Milkov ICDSoft Ltd. System Administrator http://www.icdsoft.com/ signature.asc Description: OpenPGP digital signature ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
spamdyke does not change the way incoming emails are received or processed on a qmail server. Without spamdyke, an incoming connection is accepted by a daemon called "tcpserver", which starts a program called "qmail-smtpd" and exits. qmail-smtpd communicates with the remote server and accepts or rejects the message. With spamdyke, incoming connections are still accepted by tcpserver, but it starts a copy of "spamdyke" instead of qmail-smtpd. spamdyke then starts a copy of qmail-smtpd. When the remote server sends any data, spamdyke passes it to qmail-smtpd. When qmail-smtpd produces any output, spamdyke passes it to the remote server. That's why spamdyke is often described as a "filter" or a "pipe" -- it just passes the data back and forth between qmail-smtpd and the remote server. If none of spamdyke's filters are triggered, neither qmail-smtpd nor the remote server can tell spamdyke was even running. When spamdyke wants to block a message, it disconnects qmail-smtpd and terminates the process, so qmail-smtpd believes the remote server just disconnected without sending a complete message. At the same time, spamdyke continues responding to the remote server, imitating qmail-smtpd but sending errors and rejection codes instead of accepting the message. So, chkuser should install and function the same way whether spamdyke is present or not. If it does not, you may have found a bug in spamdyke -- please send more details about your setup and the errors so I can get it fixed. -- Sam Clippinger Youri V. Kravatsky wrote: > Hello Eric, > > >> chkuser is implemented via a patch to qmail. >> > Well, BEFORE spamdyke adding, my chkuser was working perfectly (rejecting > mails to non-existant and overquoting users). Now, as far as I understand, > spamdyke injects received mails directly to qmail queue, or send them > through local smtp, so they are always accepted, so queue of my server is > full of autoresponses. Sam said, that there is no problem in using spamdyke > and chkuser - and I again asking - how can I do it? I didn't found any > traces about it in docs/faqs. > > ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello, Sam! I'm again here with this f^&*^&*^king problem with chkuser. I have 2.09 patch. On Thu, Sep 3, 2009 at 11:40 PM, Sam Clippinger wrote: > So, chkuser should install and function the same way whether spamdyke is > present or not. If it does not, you may have found a bug in spamdyke -- > please send more details about your setup and the errors so I can get it > fixed. Well, let's try. There is big chance that I'm simply playing fool :o) Frankly speaking, that's not so hard with qmail and his changes-made-by-patches. 09/04/2009 13:47:21 STARTED: VERSION = 4.0.10+TLS+CONFIGTEST+DEBUG, PID = 51150 09/04/2009 13:47:21 CURRENT ENVIRONMENT MACHTYPE=i386 USER=root MAIL=/var/mail/root SHLVL=3 VENDOR=intel HOME=/root PAGER=more GROUP=wheel LOGNAME=root CHKUSER_RCPTLIMIT=20 TERM=linux BLOCKSIZE=K CHKUSER_WRONGRCPTLIMIT=10 HOST=host.dsite.ru SHELL=/bin/csh OSTYPE=FreeBSD PWD=/root FTP_PASSIVE_MODE=YES HOSTTYPE=FreeBSD EDITOR=vi PROTO=TCP TCPLOCALIP=89.108.80.21 TCPLOCALPORT=25 TCPLOCALHOST=localhost TCPREMOTEIP=88.238.84.247 TCPREMOTEPORT=8958 09/04/2009 13:47:21 CURRENT CONFIG access-file=/var/qmail/control/tcp.smtp config-file=/etc/spamdyke.conf dns-blacklist-entry=dnsbl.sorbs.net dns-blacklist-entry=zen.spamhaus.org dns-blacklist-entry=bl.spamcop.net dns-blacklist-entry=list.dsbl.org full-log-dir=/var/log/spamdyke graylist-dir=/home/vpopmail/greylist graylist-level=always-create-dir graylist-max-secs=864000 graylist-min-secs=180 greeting-delay-secs=2 idle-timeout-secs=45 local-domains-file=/var/qmail/control/rcpthosts local-domains-file=/var/qmail/control/morercpthosts max-recipients=5 recipient-blacklist-file=/var/qmail/control/blacklist.local recipient-whitelist-file=/var/qmail/control/whitelist.local reject-empty-rdns=1 reject-ip-in-cc-rdns=1 reject-missing-sender-mx=1 reject-unresolvable-rdns=1 relay-level=normal sender-blacklist-file=/var/qmail/control/blacklist.address sender-whitelist-file=/var/qmail/control/whitelist.remote smtp-auth-command=/home/vpopmail/bin/vchkpw /usr/bin/true smtp-auth-level=always 09/04/2009 13:47:21 - Remote IP = 88.238.84.247 09/04/2009 13:47:21 CURRENT CONFIG access-file=/var/qmail/control/tcp.smtp config-file=/etc/spamdyke.conf dns-blacklist-entry=dnsbl.sorbs.net dns-blacklist-entry=zen.spamhaus.org dns-blacklist-entry=bl.spamcop.net dns-blacklist-entry=list.dsbl.org dns-server-ip=89.108.87.199 dns-server-ip=195.161.118.36 dns-server-ip=81.176.64.2 dns-server-ip-primary=89.108.80.21 full-log-dir=/var/log/spamdyke graylist-dir=/home/vpopmail/greylist graylist-level=always-create-dir graylist-max-secs=864000 graylist-min-secs=180 greeting-delay-secs=2 idle-timeout-secs=45 local-domains-file=/var/qmail/control/rcpthosts local-domains-file=/var/qmail/control/morercpthosts max-recipients=5 recipient-blacklist-file=/var/qmail/control/blacklist.local recipient-whitelist-file=/var/qmail/control/whitelist.local reject-empty-rdns=1 reject-ip-in-cc-rdns=1 reject-missing-sender-mx=1 reject-unresolvable-rdns=1 relay-level=normal sender-blacklist-file=/var/qmail/control/blacklist.address sender-whitelist-file=/var/qmail/control/whitelist.remote smtp-auth-command=/home/vpopmail/bin/vchkpw /usr/bin/true smtp-auth-level=always 09/04/2009 13:47:21 - Remote rDNS = dsl88.238-21751.ttnet.net.tr 09/04/2009 13:47:21 LOG OUTPUT DEBUG(filter_rdns_missing()@filter.c:848): checking for missing rDNS; rdns: dsl88.238-21751.ttnet. DEBUG(filter_ip_in_rdns_cc()@filter.c:879): checking for IP in rDNS +country code; rdns: dsl88.238 FILTER_IP_IN_CC_RDNS ip: 88.238.84.247 rdns: dsl88.238-21751.ttnet.net.tr 09/04/2009 13:47:21 FROM CHILD TO REMOTE: 20 bytes 220 dsite.ru ESMTP 09/04/2009 13:47:26 FROM REMOTE TO CHILD: 32 bytes EHLO 88.238-21751.ttnet.net.tr 09/04/2009 13:47:26 FROM CHILD TO REMOTE: 14 bytes 250-dsite.ru 09/04/2009 13:47:26 FROM CHILD, FILTERED: 31 bytes 250-AUTH LOGIN CRAM-MD5 PLAIN 09/04/2009 13:47:26 FROM SPAMDYKE TO REMOTE: 3 bytes 250 09/04/2009 13:47:26 FROM SPAMDYKE TO REMOTE: 1 bytes - 09/04/2009 13:47:26 FROM SPAMDYKE TO REMOTE: 18 bytes AUTH LOGIN PLAIN 09/04/2009 13:47:26 FROM CHILD, FILTERED: 31 bytes 250-AUTH=LOGIN CRAM-MD5 PLAIN 09/04/2009 13:47:26 FROM CHILD TO REMOTE: 16 bytes 250-PIPELINING 09/04/2009 13:47:26 FROM CHILD TO REMOTE: 14 bytes 250 8BITMIME 09/04/2009 13:47:27 FROM REMOTE TO CHILD: 32 bytes MAIL FROM: 09/04/2009 13:47:28 LOG OUTPUT DEBUG(filter_sender_whitelist()@filter.c:1747): searching sender whitelist(s); sender: tefiqih...@li.org 09/04/2009 13:47:28 FROM CHILD TO REMOTE: 8 bytes 250 ok 09/04/2009 13:47:28 FROM REMOTE TO CHILD: 39 bytes RCPT TO: 09/04/2009 13:47:28 LOG OUTPUT DEBUG(filter_recipient_whitelist()@filter.c:2113): searching recipient whitelist(s); recipient: kalugin...@www.ja-maica.ru FILTER_RECIPIENT_WHITELIST recipient: kalugin...@www.ja-maica.ru file: /var/qmail/control/whitelist.local(84) DEBUG(filter_recipient_relay()@filter.c:2183): checking relaying; relay-level: 3 recipient: kalugin...@www.ja-maica.ru ip
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri Kravatsky wrote: > Hello, Sam! > > > I'm again here with this f^&*^&*^king problem with chkuser. I > have 2.09 patch. > > On Thu, Sep 3, 2009 at 11:40 PM, Sam Clippinger wrote: >> So, chkuser should install and function the same way whether spamdyke is >> present or not. If it does not, you may have found a bug in spamdyke -- >> please send more details about your setup and the errors so I can get it >> fixed. > Well, let's try. There is big chance that I'm simply playing fool :o) > Frankly speaking, > that's not so hard with qmail and his changes-made-by-patches. > > 09/04/2009 13:47:21 STARTED: VERSION = 4.0.10+TLS+CONFIGTEST+DEBUG, > PID = 51150 > > 09/04/2009 13:47:21 CURRENT ENVIRONMENT > MACHTYPE=i386 > USER=root > MAIL=/var/mail/root > SHLVL=3 > VENDOR=intel > HOME=/root > PAGER=more > GROUP=wheel > LOGNAME=root > CHKUSER_RCPTLIMIT=20 > TERM=linux > BLOCKSIZE=K > CHKUSER_WRONGRCPTLIMIT=10 > HOST=host.dsite.ru > SHELL=/bin/csh > OSTYPE=FreeBSD > PWD=/root > FTP_PASSIVE_MODE=YES > HOSTTYPE=FreeBSD > EDITOR=vi > PROTO=TCP > TCPLOCALIP=89.108.80.21 > TCPLOCALPORT=25 > TCPLOCALHOST=localhost > TCPREMOTEIP=88.238.84.247 > TCPREMOTEPORT=8958 > > 09/04/2009 13:47:21 CURRENT CONFIG > access-file=/var/qmail/control/tcp.smtp > config-file=/etc/spamdyke.conf > dns-blacklist-entry=dnsbl.sorbs.net > dns-blacklist-entry=zen.spamhaus.org > dns-blacklist-entry=bl.spamcop.net > dns-blacklist-entry=list.dsbl.org > full-log-dir=/var/log/spamdyke > graylist-dir=/home/vpopmail/greylist > graylist-level=always-create-dir > graylist-max-secs=864000 > graylist-min-secs=180 > greeting-delay-secs=2 > idle-timeout-secs=45 > local-domains-file=/var/qmail/control/rcpthosts > local-domains-file=/var/qmail/control/morercpthosts > max-recipients=5 > recipient-blacklist-file=/var/qmail/control/blacklist.local > recipient-whitelist-file=/var/qmail/control/whitelist.local > reject-empty-rdns=1 > reject-ip-in-cc-rdns=1 > reject-missing-sender-mx=1 > reject-unresolvable-rdns=1 > relay-level=normal > sender-blacklist-file=/var/qmail/control/blacklist.address > sender-whitelist-file=/var/qmail/control/whitelist.remote > smtp-auth-command=/home/vpopmail/bin/vchkpw /usr/bin/true > smtp-auth-level=always > > 09/04/2009 13:47:21 - Remote IP = 88.238.84.247 > > 09/04/2009 13:47:21 CURRENT CONFIG > access-file=/var/qmail/control/tcp.smtp > config-file=/etc/spamdyke.conf > dns-blacklist-entry=dnsbl.sorbs.net > dns-blacklist-entry=zen.spamhaus.org > dns-blacklist-entry=bl.spamcop.net > dns-blacklist-entry=list.dsbl.org > dns-server-ip=89.108.87.199 > dns-server-ip=195.161.118.36 > dns-server-ip=81.176.64.2 > dns-server-ip-primary=89.108.80.21 > full-log-dir=/var/log/spamdyke > graylist-dir=/home/vpopmail/greylist > graylist-level=always-create-dir > graylist-max-secs=864000 > graylist-min-secs=180 > greeting-delay-secs=2 > idle-timeout-secs=45 > local-domains-file=/var/qmail/control/rcpthosts > local-domains-file=/var/qmail/control/morercpthosts > max-recipients=5 > recipient-blacklist-file=/var/qmail/control/blacklist.local > recipient-whitelist-file=/var/qmail/control/whitelist.local > reject-empty-rdns=1 > reject-ip-in-cc-rdns=1 > reject-missing-sender-mx=1 > reject-unresolvable-rdns=1 > relay-level=normal > sender-blacklist-file=/var/qmail/control/blacklist.address > sender-whitelist-file=/var/qmail/control/whitelist.remote > smtp-auth-command=/home/vpopmail/bin/vchkpw /usr/bin/true > smtp-auth-level=always > > 09/04/2009 13:47:21 - Remote rDNS = dsl88.238-21751.ttnet.net.tr > > 09/04/2009 13:47:21 LOG OUTPUT > DEBUG(filter_rdns_missing()@filter.c:848): checking for missing rDNS; > rdns: dsl88.238-21751.ttnet. > DEBUG(filter_ip_in_rdns_cc()@filter.c:879): checking for IP in rDNS > +country code; rdns: dsl88.238 > FILTER_IP_IN_CC_RDNS ip: 88.238.84.247 rdns: > dsl88.238-21751.ttnet.net.tr > > 09/04/2009 13:47:21 FROM CHILD TO REMOTE: 20 bytes > 220 dsite.ru ESMTP > > 09/04/2009 13:47:26 FROM REMOTE TO CHILD: 32 bytes > EHLO 88.238-21751.ttnet.net.tr > > 09/04/2009 13:47:26 FROM CHILD TO REMOTE: 14 bytes > 250-dsite.ru > > 09/04/2009 13:47:26 FROM CHILD, FILTERED: 31 bytes > 250-AUTH LOGIN CRAM-MD5 PLAIN > > 09/04/2009 13:47:26 FROM SPAMDYKE TO REMOTE: 3 bytes > 250 > 09/04/2009 13:47:26 FROM SPAMDYKE TO REMOTE: 1 bytes > - > 09/04/2009 13:47:26 FROM SPAMDYKE TO REMOTE: 18 bytes > AUTH LOGIN PLAIN > > 09/04/2009 13:47:26 FROM CHILD, FILTERED: 31 bytes > 250-AUTH=LOGIN CRAM-MD5 PLAIN > > 09/04/2009 13:47:26 FROM CHILD TO REMOTE: 16 bytes > 250-PIPELINING > > 09/04/2009 13:47:26 FROM CHILD TO REMOTE: 14 bytes > 250 8BITMIME > > 09/04/2009 13:47:27 FROM REMOTE TO CHILD: 32 bytes > MAIL FROM: > > 09/04/2009 13:47:28 LOG OUTPUT > DEBUG(filter_sender_whitelist()@filter.c:1747): searching sender > whitelist(s); sender: tefiqih...@li.org > > 09/04/2009 13:47:28 FROM CHILD TO REMOTE: 8 bytes > 250 ok > > 09/04/2009 13:47:28 FROM REMOTE TO CHILD: 39 bytes > RCPT TO: > > 09/04/2009 13:47:28 LOG OUTPUT > DEBUG(fil
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello, Eric and all people! First of all, thanks to your efforts to rectify my problem :) > Please post your chkuser version, and chkuser_settings.h file. We need > to see how your chkuser is configured. /* 'chkuser_settings.h' v.2.0.9 * for qmail/netqmail > 1.0.3 and vpopmail > 5.3.x */ #define CHKUSER_ALWAYS_ON #define CHKUSER_VPOPMAIL #define CHKUSER_DOMAIN_WANTED #define CHKUSER_ENABLE_USERS #define CHKUSER_ENABLE_ALIAS #define CHKUSER_EZMLM_DASH '-' #define CHKUSER_BOUNCE_STRING "bounce-no-mailbox" #define CHKUSER_ENABLE_LOGGING #define CHKUSER_LOG_VALID_RCPT #define CHKUSER_MIN_DOMAIN_LEN 4 #define CHKUSER_LOG_VALID_SENDER #define CHKUSER_RCPT_LIMIT_VARIABLE "CHKUSER_RCPTLIMIT" #define CHKUSER_WRONGRCPT_LIMIT_VARIABLE "CHKUSER_WRONGRCPTLIMIT" #define CHKUSER_MBXQUOTA_VARIABLE "CHKUSER_MBXQUOTA" #define CHKUSER_ERROR_DELAY 1000 #define CHKUSER_RCPT_DELAY_ANYERROR #define CHKUSER_SENDER_DELAY_ANYERROR #define CHKUSER_ENABLE_EZMLM_LISTS #define CHKUSER_IDENTIFY_REMOTE_VARIABLE "CHKUSER_IDENTIFY" #define CHKUSER_USERS_DASH '-' #define CHKUSER_MAILMAN_STRING "mailman" #define CHKUSER_DB_CLEANUP #define CHKUSER_RCPT_MX <<< here is the solution of my problem? #define CHKUSER_ERROR_DELAY_INCREASE 300 #define CHKUSER_ENABLE_DOUBLEBOUNCE_VARIABLE "CHKUSER_DOUBLEBOUNCE" > Also, do you have a .qmail-default file? If so, what does it contain? cat /home/vpopmail/domains/ja-maica.ru/.qmail-default | /home/vpopmail/bin/vdelivermail '' delete cat /var/qmail/control/rcpthosts|grep ja-maica.ru ja-maica.ru I investigated this problem more thoroughly and what can I say - qmail really REJECTS letters to non-existent users of ja-maica.ru (e.g. s...@ja-maica.ru), but ACCEPTS mails for users like (s...@www.ja-maica.ru) - it tries to work as MX server for all hosts at the networks. Probably, it's not the problem of chkuser/spamdyke, but the qmail itself? Can it be fixed to changing rcpthosts strings to something like @ja-maica.ru? -- Sincerely yours, Youri -- WWW: http://www.lebedev.ru/jiri email: loka...@gmail.com FAX: +7-095-135-1405 ICQ: 1870550 ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri Kravatsky wrote: >Hello, Eric and all people! > > First of all, thanks to your efforts to rectify my problem :) > >> Please post your chkuser version, and chkuser_settings.h file. We need >> to see how your chkuser is configured. > > /* 'chkuser_settings.h' v.2.0.9 > * for qmail/netqmail > 1.0.3 and vpopmail > 5.3.x > */ > > #define CHKUSER_ALWAYS_ON > #define CHKUSER_VPOPMAIL > #define CHKUSER_DOMAIN_WANTED > #define CHKUSER_ENABLE_USERS > #define CHKUSER_ENABLE_ALIAS > #define CHKUSER_EZMLM_DASH '-' > #define CHKUSER_BOUNCE_STRING "bounce-no-mailbox" > #define CHKUSER_ENABLE_LOGGING > #define CHKUSER_LOG_VALID_RCPT > #define CHKUSER_MIN_DOMAIN_LEN 4 > #define CHKUSER_LOG_VALID_SENDER > #define CHKUSER_RCPT_LIMIT_VARIABLE "CHKUSER_RCPTLIMIT" > #define CHKUSER_WRONGRCPT_LIMIT_VARIABLE "CHKUSER_WRONGRCPTLIMIT" > #define CHKUSER_MBXQUOTA_VARIABLE "CHKUSER_MBXQUOTA" > #define CHKUSER_ERROR_DELAY 1000 > #define CHKUSER_RCPT_DELAY_ANYERROR > #define CHKUSER_SENDER_DELAY_ANYERROR > #define CHKUSER_ENABLE_EZMLM_LISTS > #define CHKUSER_IDENTIFY_REMOTE_VARIABLE "CHKUSER_IDENTIFY" > #define CHKUSER_USERS_DASH '-' > #define CHKUSER_MAILMAN_STRING "mailman" > #define CHKUSER_DB_CLEANUP > #define CHKUSER_RCPT_MX <<< here is the solution of my problem? > #define CHKUSER_ERROR_DELAY_INCREASE 300 > #define CHKUSER_ENABLE_DOUBLEBOUNCE_VARIABLE "CHKUSER_DOUBLEBOUNCE" > >> Also, do you have a .qmail-default file? If so, what does it contain? > cat /home/vpopmail/domains/ja-maica.ru/.qmail-default > | /home/vpopmail/bin/vdelivermail '' delete > > cat /var/qmail/control/rcpthosts|grep ja-maica.ru > ja-maica.ru > > I investigated this problem more thoroughly and what can I say - qmail > really REJECTS letters to non-existent users of ja-maica.ru (e.g. > s...@ja-maica.ru), but ACCEPTS mails for users like > (s...@www.ja-maica.ru) - it tries to work as MX server for all hosts at > the networks. Probably, it's not the problem of chkuser/spamdyke, but > the qmail itself? Can it be fixed to changing rcpthosts strings to > something like @ja-maica.ru? > Is your objective to accept or reject messages to the sub-domain(s)? What subdomains are you seeing besides @www. ? -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello, Eric! >> I investigated this problem more thoroughly and what can I say - qmail >> really REJECTS letters to non-existent users of ja-maica.ru (e.g. >> s...@ja-maica.ru), but ACCEPTS mails for users like >> (s...@www.ja-maica.ru) - it tries to work as MX server for all hosts at >> the networks. Probably, it's not the problem of chkuser/spamdyke, but >> the qmail itself? Can it be fixed to changing rcpthosts strings to >> something like @ja-maica.ru? > Is your objective to accept or reject messages to the sub-domain(s)? Of course, to reject. Or, well, do not accept emails to hosts that are not included directly in rcpthosts file. At least to reject to all subdomains of our domains. > What subdomains are you seeing besides @www. ? Subdomains of our domains. Mail that goes to domains that are not included to rcpthosts file is rejected. But mail to www.mydomain.com or mail.mydomain.com are accepted to deliver (to no avail, of course). -- Sincerely yours, Youri -- WWW: http://www.lebedev.ru/jiri email: loka...@gmail.com FAX: +7-095-135-1405 ICQ: 1870550 ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Can't Spamdyke block mail using wildcards? Something like *.mydomain.com..??? I think in the recipients blacklist area... Not sure..Haven't played with that much. If it's only the one domain (or a list of known domains), then I'd look into that. Michael J. Colvin NorCal Internet Services www.norcalisp.com > -Original Message- > From: spamdyke-users-boun...@spamdyke.org [mailto:spamdyke-users- > boun...@spamdyke.org] On Behalf Of Youri Kravatsky > Sent: Friday, September 04, 2009 2:01 PM > To: spamdyke users > Subject: Re: [spamdyke-users] Qmail + spamdyke + chkuser > >Hello, Eric! > > >> I investigated this problem more thoroughly and what can I say - qmail > >> really REJECTS letters to non-existent users of ja-maica.ru (e.g. > >> s...@ja-maica.ru), but ACCEPTS mails for users like > >> (s...@www.ja-maica.ru) - it tries to work as MX server for all hosts at > >> the networks. Probably, it's not the problem of chkuser/spamdyke, but > >> the qmail itself? Can it be fixed to changing rcpthosts strings to > >> something like @ja-maica.ru? > > > Is your objective to accept or reject messages to the sub-domain(s)? > Of course, to reject. Or, well, do not accept emails to hosts > that are not included directly in rcpthosts file. At least to reject > to all subdomains of our domains. > > > What subdomains are you seeing besides @www. ? > Subdomains of our domains. Mail that goes to domains that are not > included to > rcpthosts file is rejected. But mail to www.mydomain.com or > mail.mydomain.com are accepted to deliver (to no avail, of course). > > -- >Sincerely yours, Youri > -- > WWW: http://www.lebedev.ru/jiri email: loka...@gmail.com > FAX: +7-095-135-1405 ICQ: 1870550 > ___ > 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] Qmail + spamdyke + chkuser
Youri Kravatsky wrote: >Hello, Eric! > >>> I investigated this problem more thoroughly and what can I say - qmail >>> really REJECTS letters to non-existent users of ja-maica.ru (e.g. >>> s...@ja-maica.ru), but ACCEPTS mails for users like >>> (s...@www.ja-maica.ru) - it tries to work as MX server for all hosts at >>> the networks. Probably, it's not the problem of chkuser/spamdyke, but >>> the qmail itself? Can it be fixed to changing rcpthosts strings to >>> something like @ja-maica.ru? > >> Is your objective to accept or reject messages to the sub-domain(s)? > Of course, to reject. Or, well, do not accept emails to hosts > that are not included directly in rcpthosts file. At least to reject > to all subdomains of our domains. > >> What subdomains are you seeing besides @www. ? > Subdomains of our domains. Mail that goes to domains that are not > included to > rcpthosts file is rejected. But mail to www.mydomain.com or > mail.mydomain.com are accepted to deliver (to no avail, of course). > Does your rcpthosts contain ja-maica.ru or .ja-maica.ru ? (or both?) -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri Kravatsky wrote: >Hello, Eric! > >>> I investigated this problem more thoroughly and what can I say - qmail >>> really REJECTS letters to non-existent users of ja-maica.ru (e.g. >>> s...@ja-maica.ru), but ACCEPTS mails for users like >>> (s...@www.ja-maica.ru) - it tries to work as MX server for all hosts at >>> the networks. Probably, it's not the problem of chkuser/spamdyke, but >>> the qmail itself? Can it be fixed to changing rcpthosts strings to >>> something like @ja-maica.ru? > >> Is your objective to accept or reject messages to the sub-domain(s)? > Of course, to reject. Or, well, do not accept emails to hosts > that are not included directly in rcpthosts file. At least to reject > to all subdomains of our domains. > >> What subdomains are you seeing besides @www. ? > Subdomains of our domains. Mail that goes to domains that are not > included to > rcpthosts file is rejected. But mail to www.mydomain.com or > mail.mydomain.com are accepted to deliver (to no avail, of course). > Hey Youri, I think this is part of your problem: shu...@edwin:~$ host xyz.ja-maica.ru xyz.ja-maica.ru is an alias for www.ja-maica.ru. www.ja-maica.ru is an alias for www.dsite.ru. www.dsite.ru is an alias for dsite.ru. dsite.ru has address 89.108.80.21 dsite.ru mail is handled by 10 dsite.ru. shu...@edwin:~$ Any subdomain will find its way to your server. Is there any reason for the wildcard DNS record(s)? -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Michael Colvin wrote: > Can't Spamdyke block mail using wildcards? Something like > *.mydomain.com..??? I think in the recipients blacklist area... Not > sure..Haven't played with that much. > > If it's only the one domain (or a list of known domains), then I'd look into > that. > > > Michael J. Colvin > NorCal Internet Services > www.norcalisp.com This does bring up a neat little trick that can be used with spamdyke to block sender addresses that are spoofed with your domain. As long as all of your domain's mail is submitted with authentication (it should be if it isn't), you can add your domain(s) to the blacklist_senders file, like: @mydomain.com This will block anyone pretending to send from your domain who is not authenticated. -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello Eric, Saturday, September 5, 2009, 2:39:30 AM, you wrote: >>> What subdomains are you seeing besides @www. ? >> Subdomains of our domains. Mail that goes to domains that are not >> included to rcpthosts file is rejected. But mail to www.mydomain.com or >> mail.mydomain.com are accepted to deliver (to no avail, of course). > I think this is part of your problem: > shu...@edwin:~$ host xyz.ja-maica.ru > xyz.ja-maica.ru is an alias for www.ja-maica.ru. > www.ja-maica.ru is an alias for www.dsite.ru. > www.dsite.ru is an alias for dsite.ru. > dsite.ru has address 89.108.80.21 > dsite.ru mail is handled by 10 dsite.ru. > Any subdomain will find its way to your server. > Is there any reason for the wildcard DNS record(s)? Yes, it seems quite reasonable for www-hoster (I know, I know, it's not good practice to have www-carrier/database provider and mail server at one hardware, but we not always can change reality as we want). So in the case of any mistype/error users will access through HTTP any domain that is hosted succesfully. Really, the question is - why chkuser/qmail/spamdyke is accepting mail for subdomains, if they are not listed directly in rcpthosts? And how to stop it? Right now in rcpthosts is the string ja-maica.ru without "." and/or "@". Probably, I'll play with it at night, when the risk to lose some mail is minimal... -- Best regards, Yourimailto:loka...@gmail.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Eric, > > Saturday, September 5, 2009, 2:39:30 AM, you wrote: > What subdomains are you seeing besides @www. ? >>> Subdomains of our domains. Mail that goes to domains that are not >>> included to rcpthosts file is rejected. But mail to www.mydomain.com or >>> mail.mydomain.com are accepted to deliver (to no avail, of course). > >> I think this is part of your problem: >> shu...@edwin:~$ host xyz.ja-maica.ru >> xyz.ja-maica.ru is an alias for www.ja-maica.ru. >> www.ja-maica.ru is an alias for www.dsite.ru. >> www.dsite.ru is an alias for dsite.ru. >> dsite.ru has address 89.108.80.21 >> dsite.ru mail is handled by 10 dsite.ru. > >> Any subdomain will find its way to your server. >> Is there any reason for the wildcard DNS record(s)? > Yes, it seems quite reasonable for www-hoster (I know, I know, it's not > good practice to have www-carrier/database provider and mail server at one > hardware, but we not always can change reality as we want). So in the case > of any mistype/error users will access through HTTP any domain that is > hosted succesfully. > Really, the question is - why chkuser/qmail/spamdyke is accepting mail > for subdomains, if they are not listed directly in rcpthosts? And how to > stop it? > Right now in rcpthosts is the string > > ja-maica.ru > > without "." and/or "@". Probably, I'll play with it at night, when the risk > to lose some mail is minimal... > Hey Youri, I gotta admit that I don't know off hand how subdomains are supposed to be handled by qmail. So I did some testing. The first test I sent to mys...@sub.mydomain.com. Interestingly enough, it was rejected because I have @mydomain.com in my blacklist_senders file. This is to prevent spamd where the sender address is spoofed with my domain. It works because all email for my domain is sent with authentication (a good practice), and authenticated users circumvent all spamdyke rules. I was curious about what happens without spamdyke doing this, so I did another test w/out having the blacklist entry. In the smtp log I got: 09-05 07:45:04 CHKUSER rejected relaying:... client not allowed to relay 09-05 07:45:05 DENIED_OTHER from: The message bounced back to the sender with: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.5.3 - chkuser) So chkuser recognized that subdom.mydomain.com was not a domain that my server is configured to receive mail for. This seems right to me. My chkuser version is 2.0.8, but that's the only difference I see. Your system should recognize that the subdomain isn't in your rcpthosts file. Are you certain that you don't have .ja-maica.com (with leading .) in your rcpthosts or morercpthosts files? If not, then I'd look closer into your chkuser implementation. Are you seeing any chkuser messages in your smtp log? -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
I can see why spamdyke is accepting messages to your subdomains -- you've whitelisted the recipients. In the full log you sent, I see this line: FILTER_RECIPIENT_WHITELIST recipient: kalugin...@www.ja-maica.ru file: /var/qmail/control/whitelist.local(84) If you're just trying to stop deliveries to your subdomains, removing the whitelist entry will accomplish that goal. If you also want to fix chkuser, there's more work to be done. I don't use chkuser myself, so I'm not familiar with how to configure it. I've glanced at the patch file (version 2.0.9) and your configuration file; nothing jumps out as obviously incorrect. My first idea is the RELAYCLIENT environment variable may the problem. spamdyke sets that variable so that it may control relaying instead of letting qmail-smtpd handle it. I suspected this may prevent chkuser from working, but your configuration seems to eliminate that possibility. Were I you, I think my next step would be to remove spamdyke from the "run" file and see if chkuser starts working again. If it does, we can keep trying to figure out why spamdyke is interfering with it. -- Sam Clippinger Youri V. Kravatsky wrote: > Hello Eric, > > Saturday, September 5, 2009, 2:39:30 AM, you wrote: > > What subdomains are you seeing besides @www. ? >>> Subdomains of our domains. Mail that goes to domains that are not >>> included to rcpthosts file is rejected. But mail to www.mydomain.com or >>> mail.mydomain.com are accepted to deliver (to no avail, of course). >>> > > >> I think this is part of your problem: >> shu...@edwin:~$ host xyz.ja-maica.ru >> xyz.ja-maica.ru is an alias for www.ja-maica.ru. >> www.ja-maica.ru is an alias for www.dsite.ru. >> www.dsite.ru is an alias for dsite.ru. >> dsite.ru has address 89.108.80.21 >> dsite.ru mail is handled by 10 dsite.ru. >> > > >> Any subdomain will find its way to your server. >> Is there any reason for the wildcard DNS record(s)? >> > Yes, it seems quite reasonable for www-hoster (I know, I know, it's not > good practice to have www-carrier/database provider and mail server at one > hardware, but we not always can change reality as we want). So in the case > of any mistype/error users will access through HTTP any domain that is > hosted succesfully. > Really, the question is - why chkuser/qmail/spamdyke is accepting mail > for subdomains, if they are not listed directly in rcpthosts? And how to > stop it? > Right now in rcpthosts is the string > > ja-maica.ru > > without "." and/or "@". Probably, I'll play with it at night, when the risk > to lose some mail is minimal... > > ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello Sam, Saturday, September 5, 2009, 10:11:03 PM, you wrote: > I can see why spamdyke is accepting messages to your subdomains -- > you've whitelisted the recipients. In the full log you sent, I see this line: > FILTER_RECIPIENT_WHITELIST recipient: kalugin...@www.ja-maica.ru > file: /var/qmail/control/whitelist.local(84) > If you're just trying to stop deliveries to your subdomains, removing > the whitelist entry will accomplish that goal. If you also want to fix Well, how could I whitelist only ja-maica.ru without any subdomains? Right now whitelist.local has the following string @ja-maica.ru It seemed to me, that it makes only mail to u...@ja-maica.ru whitelisted? -- Best regards, Yourimailto:loka...@gmail.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Sam, > > Saturday, September 5, 2009, 10:11:03 PM, you wrote: > >> I can see why spamdyke is accepting messages to your subdomains -- >> you've whitelisted the recipients. In the full log you sent, I see this >> line: >> FILTER_RECIPIENT_WHITELIST recipient: kalugin...@www.ja-maica.ru >> file: /var/qmail/control/whitelist.local(84) >> If you're just trying to stop deliveries to your subdomains, removing >> the whitelist entry will accomplish that goal. If you also want to fix > Well, how could I whitelist only ja-maica.ru without any subdomains? > Right now whitelist.local has the following string > @ja-maica.ru > It seemed to me, that it makes only mail to u...@ja-maica.ru whitelisted? > You shouldn't need to whitelist ja-maica.ru, provided that it's in your rcpthosts file. -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hi, Eric! >>Well, how could I whitelist only ja-maica.ru without any subdomains? >> Right now whitelist.local has the following string >> @ja-maica.ru >> It seemed to me, that it makes only mail > You shouldn't need to whitelist ja-maica.ru, provided that it's in your > rcpthosts file. Well, I should. Not all hosted domains want to be greylisted. Still they/we don't want to overload server TOO heavy. Sincerely yours, Youri ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
No, an entry like "@example.com" will whitelist addresses in "example.com" and all of its subdomains. This is because the whitelist filter uses the same code as the blacklist filter, where this behavior is expected. Are you whitelisting your hosted domains just to turn off graylisting? You might consider using a configuration directory, which will let you enable/disable specific filters for specific domains (or recipients). -- Sam Clippinger Youri V. Kravatsky wrote: > Hello Sam, > > Saturday, September 5, 2009, 10:11:03 PM, you wrote: > > >> I can see why spamdyke is accepting messages to your subdomains -- >> you've whitelisted the recipients. In the full log you sent, I see this >> line: >> FILTER_RECIPIENT_WHITELIST recipient: kalugin...@www.ja-maica.ru >> file: /var/qmail/control/whitelist.local(84) >> If you're just trying to stop deliveries to your subdomains, removing >> the whitelist entry will accomplish that goal. If you also want to fix >> > Well, how could I whitelist only ja-maica.ru without any subdomains? > Right now whitelist.local has the following string > @ja-maica.ru > It seemed to me, that it makes only mail to u...@ja-maica.ru whitelisted? > > ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello Eric, Saturday, September 5, 2009, 7:43:00 PM, you wrote: > The first test I sent to mys...@sub.mydomain.com. Interestingly enough, > it was rejected because I have @mydomain.com in my blacklist_senders > file. This is to prevent spamd where the sender address is spoofed with > my domain. It works because all email for my domain is sent with > authentication (a good practice), and authenticated users circumvent all > spamdyke rules. Well, let's imagine, that you will send mail to thyself (or even more important, to the OTHER domain at your hosting), not through YOUR server, but through authenticated SMTP e.g. gmail.com, or through SMTP of his local internet provider (you know, cable providers blocks external SMTP servers access very freguently, and it is very reasonably, 'course). Then this mail will be definitely rejected, not being spam, but being inter-user communication. -- Best regards, Yourimailto:loka...@gmail.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Eric, > > Saturday, September 5, 2009, 7:43:00 PM, you wrote: > >> The first test I sent to mys...@sub.mydomain.com. Interestingly enough, >> it was rejected because I have @mydomain.com in my blacklist_senders >> file. This is to prevent spamd where the sender address is spoofed with >> my domain. It works because all email for my domain is sent with >> authentication (a good practice), and authenticated users circumvent all >> spamdyke rules. > Well, let's imagine, that you will send mail to thyself (or even more > important, to the OTHER domain at your hosting), not through YOUR server, > but through authenticated SMTP e.g. gmail.com, or through SMTP of his local > internet provider (you know, cable providers blocks external SMTP servers > access very freguently, and it is very reasonably, 'course). Then this mail > will be definitely rejected, not being spam, but being inter-user > communication. > Right, as it should be. All email from my domain *is* (at least should be) sent through my server, where it is delivered locally. I can't imagine why I would want to send email from my domain and to my domain via any external server. -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Hello Eric, Monday, September 7, 2009, 11:19:47 AM, you wrote: > Right, as it should be. All email from my domain *is* (at least should > be) sent through my server, where it is delivered locally. I can't > imagine why I would want to send email from my domain and to my domain > via any external server. Trust me, A LOT of providers block access to 25 port on the external networks INDEED. I do it myself in two organizations that I help to manage, 'cause I don't want to deal with permanent complains about spam that goes from infected computers. So, user with notebook has only one option - use local SMTP server in such kind of networks to deliver mail. -- Best regards, Yourimailto:loka...@gmail.com ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Youri V. Kravatsky wrote: > Hello Eric, > > Monday, September 7, 2009, 11:19:47 AM, you wrote: > >> Right, as it should be. All email from my domain *is* (at least should >> be) sent through my server, where it is delivered locally. I can't >> imagine why I would want to send email from my domain and to my domain >> via any external server. > Trust me, A LOT of providers block access to 25 port on the external > networks INDEED. I do it myself in two organizations that I help to manage, > 'cause I don't want to deal with permanent complains about spam that goes > from infected computers. So, user with notebook has only one option - use > local SMTP server in such kind of networks to deliver mail. > Only one option that you can see. I have a VPN that road warriors use. ;) -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Re: [spamdyke-users] Qmail + spamdyke + chkuser
Eric Shubert wrote: > Youri V. Kravatsky wrote: >> Hello Eric, >> >> Monday, September 7, 2009, 11:19:47 AM, you wrote: >> >>> Right, as it should be. All email from my domain *is* (at least should >>> be) sent through my server, where it is delivered locally. I can't >>> imagine why I would want to send email from my domain and to my domain >>> via any external server. >> Trust me, A LOT of providers block access to 25 port on the external >> networks INDEED. I do it myself in two organizations that I help to manage, >> 'cause I don't want to deal with permanent complains about spam that goes >> from infected computers. So, user with notebook has only one option - use >> local SMTP server in such kind of networks to deliver mail. >> > > Only one option that you can see. I have a VPN that road warriors use. ;) > Or if you have no VPN, port 587 would suit the purpose. I haven't heard of an ISP blocking port 587, but it wouldn't surprise me if there are a few. -- -Eric 'shubes' ___ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
