[prev in list] [next in list] [prev in thread] [next in thread]
List: qmail-scanner-general
Subject: Re: [Qmail-scanner-general] User validation before
From: Tomas Charvat <tc () excello ! cz>
Date: 2007-10-20 22:37:13
Message-ID: 471A8319.9030601 () excello ! cz
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
[Attachment #4 (multipart/alternative)]
There are a lot of SPP plugins to verify existence of recipient. I would
suggest to use them.
SPP invoke before qmail-scanner. I would love to see SPP recipient
validation via SMTP delivery attempt or VRFY cmd for mail relays with
Mysql DB caching, like Postfix has.
It would trigger even before greylisting.
tomas
Jason Haar wrote:
> Lampa wrote:
>
>> Hello,
>>
>> use shupp toaster (www.shupp.org/toaster), implement patch chkuser
>> (http://www.interazioni.it/opensource/chkuser/) or there are other
>> mechanism (for example using badmailto or oposite - using only valid
>> emails - eg create list of all emails you have).
>>
>>
> i.e. this is such a fundamental problem that it must be dealt with at
> the Qmail level instead of within Qmail-Scanner. With the overhead of
> running perl, AVs and (especially) SpamAssassin, it just isn't
> appropriate to do this within Qmail-Scanner. Doing it within Qmail
> itself (i.e. a patch) will remove a huge amount of traffic from even
> getting to Qmail-Scanner.
>
> I'd also suggest looking at the RECIPIENTS extension on
> http://www.fehcom.de/qmail/qmail.html
>
>
[Attachment #7 (text/html)]
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
There are a lot of SPP plugins to verify existence of recipient. I
would suggest to use them.<br>
SPP invoke before qmail-scanner. I would love to see SPP recipient
validation via SMTP delivery attempt or VRFY cmd for mail relays with
Mysql DB caching, like Postfix has.<br>
It would trigger even before greylisting.<br>
<br>
tomas<br>
<br>
<br>
Jason Haar wrote:
<blockquote cite="mid471A4BD2.7090405@trimble.co.nz" type="cite">
<pre wrap="">Lampa wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
use shupp toaster (<a class="moz-txt-link-abbreviated" \
href="http://www.shupp.org/toaster">www.shupp.org/toaster</a>), implement patch \
chkuser (<a class="moz-txt-link-freetext" \
href="http://www.interazioni.it/opensource/chkuser/">http://www.interazioni.it/opensource/chkuser/</a>) \
or there are other mechanism (for example using badmailto or oposite - using only \
valid emails - eg create list of all emails you have).
</pre>
</blockquote>
<pre wrap=""><!---->i.e. this is such a fundamental problem that it must be dealt \
with at the Qmail level instead of within Qmail-Scanner. With the overhead of
running perl, AVs and (especially) SpamAssassin, it just isn't
appropriate to do this within Qmail-Scanner. Doing it within Qmail
itself (i.e. a patch) will remove a huge amount of traffic from even
getting to Qmail-Scanner.
I'd also suggest looking at the RECIPIENTS extension on
<a class="moz-txt-link-freetext" \
href="http://www.fehcom.de/qmail/qmail.html">http://www.fehcom.de/qmail/qmail.html</a>
</pre>
</blockquote>
</body>
</html>
["smime.p7s" (application/x-pkcs7-signature)]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Qmail-scanner-general mailing list
Qmail-scanner-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic