<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[Forums - All Forums]]></title>
		<link>http://www.greylisting.org/forums/</link>
		<description><![CDATA[Forums - http://www.greylisting.org/forums]]></description>
		<pubDate>Fri, 16 May 2008 09:28:51 -0400</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[How can I verify  it is working? postgrey]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=34</link>
			<pubDate>Fri, 09 May 2008 21:33:36 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=34</guid>
			<description><![CDATA[Hi all<br />
<br />
Have installed "postgrey"  but trying to prove whether it is working.<br />
Installed RHEL5 box and with  " yum install   postgrey  "       ... details below.<br />
<br />
Have run the command below but it just hangs<br />
<br />
# /usr/sbin/postgreyreport --show_tries --dbdir=/var/spool/postfix/postgrey<br />
<br />
<br />
How can I verify  it is working?<br />
<br />
<br />
################################################################################ ########################<br />
mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge<br />
################################################################################ ########################<br />
# yum info postgrey<br />
...<br />
...<br />
Installed  Packages<br />
Name   : postgrey<br />
Arch   : noarch<br />
Version: 1.31<br />
Release: 1.el5.rf<br />
Size   : 99 k<br />
Repo   : installed<br />
Summary: Postfix Greylisting Policy Server<br />
<br />
Description:<br />
Postgrey is a Postfix policy server implementing greylisting.  When a request<br />
for delivery of a mail is received by Postfix via SMTP, the triplet CLIENT_IP /<br />
SENDER / RECIPIENT is built.  If it is the first time that this triplet is<br />
seen, or if the triplet was first seen less than 5 minutes, then the mail gets<br />
rejected with a temporary error. Hopefully spammers or viruses will not try<br />
again later, as it is however required per RFC.<br />
################################################################################ ########################]]></description>
			<content:encoded><![CDATA[Hi all<br />
<br />
Have installed "postgrey"  but trying to prove whether it is working.<br />
Installed RHEL5 box and with  " yum install   postgrey  "       ... details below.<br />
<br />
Have run the command below but it just hangs<br />
<br />
# /usr/sbin/postgreyreport --show_tries --dbdir=/var/spool/postfix/postgrey<br />
<br />
<br />
How can I verify  it is working?<br />
<br />
<br />
################################################################################ ########################<br />
mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge<br />
################################################################################ ########################<br />
# yum info postgrey<br />
...<br />
...<br />
Installed  Packages<br />
Name   : postgrey<br />
Arch   : noarch<br />
Version: 1.31<br />
Release: 1.el5.rf<br />
Size   : 99 k<br />
Repo   : installed<br />
Summary: Postfix Greylisting Policy Server<br />
<br />
Description:<br />
Postgrey is a Postfix policy server implementing greylisting.  When a request<br />
for delivery of a mail is received by Postfix via SMTP, the triplet CLIENT_IP /<br />
SENDER / RECIPIENT is built.  If it is the first time that this triplet is<br />
seen, or if the triplet was first seen less than 5 minutes, then the mail gets<br />
rejected with a temporary error. Hopefully spammers or viruses will not try<br />
again later, as it is however required per RFC.<br />
################################################################################ ########################]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[I never signed up for this]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=33</link>
			<pubDate>Mon, 21 Apr 2008 18:25:30 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=33</guid>
			<description><![CDATA[Since saturday, all of my corporate emails are going through this filter.  I never signed up for greylisting.  How do I stop this from effecting my emails?<br />
<br />
thanks]]></description>
			<content:encoded><![CDATA[Since saturday, all of my corporate emails are going through this filter.  I never signed up for greylisting.  How do I stop this from effecting my emails?<br />
<br />
thanks]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[whitelisted objects are temporary rejected]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=31</link>
			<pubDate>Wed, 02 Apr 2008 08:41:01 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=31</guid>
			<description><![CDATA[Hello,<br />
<br />
in my whitelist-file at "/etc/greylistd/whistlist-hosts" I entered *sender.de and reload greylist configuration with "greylist reload".<br />
when the senders E-Mail comes in, the E-Mail "name@sender.de" was still temporary rejected and listed in greylist under "greylist -list --grey".<br />
<br />
The problem is, the sender sent the mails from differend IP adresses.<br />
<br />
my system: debian woody, exim4, spamassassin, clamav, greylistd, couriermail, vexim.<br />
<br />
thanks for any help.]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
in my whitelist-file at "/etc/greylistd/whistlist-hosts" I entered *sender.de and reload greylist configuration with "greylist reload".<br />
when the senders E-Mail comes in, the E-Mail "name@sender.de" was still temporary rejected and listed in greylist under "greylist -list --grey".<br />
<br />
The problem is, the sender sent the mails from differend IP adresses.<br />
<br />
my system: debian woody, exim4, spamassassin, clamav, greylistd, couriermail, vexim.<br />
<br />
thanks for any help.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Internet unexpectedly disconnected after implement greylist with windows 2003 SMTP.]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=30</link>
			<pubDate>Thu, 13 Mar 2008 23:42:51 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=30</guid>
			<description><![CDATA[Am using, windows 2003 SMTP and POP3 as my email server. I am using free version of greylists, I have tested Greylist and JEP(S) GreyList for my spam email blocker. Well it is working fine as a filter. <br />
<br />
After implement whitelist, Windows 2003 SMTP outbound delivery intervals and SMTP Relay properties. <br />
<br />
Problems, which I am facing and solved<br />
<br />
1.Badmail overflow can be get read by writing a batch file to delete with periodic interval (Recommend by Microsoft)<br />
<br />
2.Queue folder overflow can be rectified by setting Relay Restrictions under the SMTP virtual sever properties. Follow this url to understand better about queue folder overflow. http://searchexchange.techtarget.com/tip...64,00.html<br />
<br />
Problems that I am facing and cannot be solved.<br />
<br />
1.Internet disconnected every half an hour once. When it disconnect queue folder under mailroot contains not queue problem bad mail folder I only maintain it to be 1mb max, that also no prob. I really cant able to find what is the reall cause the internet connection to be down with periodic interval.<br />
<br />
Conclusion:<br />
	After uninstall Greylist or JEP(S) GreyList Application from that server, the internet connection never drop down or disconnected. Why it happen like that, please help me to overcome this issue, everything works find except the inter connection instability. <br />
<br />
My Greylist properties<br />
<br />
Sink Timeout: 30000<br />
Database: MS Sql server<br />
Whitelist only: yahoo, hotmail, gmail, mycompany<br />
Remainging values all I use the default properties of greylist]]></description>
			<content:encoded><![CDATA[Am using, windows 2003 SMTP and POP3 as my email server. I am using free version of greylists, I have tested Greylist and JEP(S) GreyList for my spam email blocker. Well it is working fine as a filter. <br />
<br />
After implement whitelist, Windows 2003 SMTP outbound delivery intervals and SMTP Relay properties. <br />
<br />
Problems, which I am facing and solved<br />
<br />
1.Badmail overflow can be get read by writing a batch file to delete with periodic interval (Recommend by Microsoft)<br />
<br />
2.Queue folder overflow can be rectified by setting Relay Restrictions under the SMTP virtual sever properties. Follow this url to understand better about queue folder overflow. http://searchexchange.techtarget.com/tip...64,00.html<br />
<br />
Problems that I am facing and cannot be solved.<br />
<br />
1.Internet disconnected every half an hour once. When it disconnect queue folder under mailroot contains not queue problem bad mail folder I only maintain it to be 1mb max, that also no prob. I really cant able to find what is the reall cause the internet connection to be down with periodic interval.<br />
<br />
Conclusion:<br />
	After uninstall Greylist or JEP(S) GreyList Application from that server, the internet connection never drop down or disconnected. Why it happen like that, please help me to overcome this issue, everything works find except the inter connection instability. <br />
<br />
My Greylist properties<br />
<br />
Sink Timeout: 30000<br />
Database: MS Sql server<br />
Whitelist only: yahoo, hotmail, gmail, mycompany<br />
Remainging values all I use the default properties of greylist]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Internet unexpectedly disconnected after implement greylist with windows 2003 SMTP.]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=29</link>
			<pubDate>Thu, 13 Mar 2008 23:36:19 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=29</guid>
			<description><![CDATA[Internet unexpectedly disconnected after implement greylist with windows 2003 SMTP.<br />
<br />
Am using, windows 2003 SMTP and POP3 as my email server. I am using free version of greylists, I have tested Greylist and JEP(S) GreyList for my spam email blocker. Well it is working fine as a filter. <br />
<br />
After implement whitelist, Windows 2003 SMTP outbound delivery intervals and SMTP Relay properties. <br />
<br />
Problems, which I am facing and solved<br />
<br />
1.Badmail overflow can be get read by writing a batch file to delete with periodic interval (Recommend by Microsoft)<br />
<br />
2.Queue folder overflow can be rectified by setting Relay Restrictions under the SMTP virtual sever properties. Follow this url to understand better about queue folder overflow. http://searchexchange.techtarget.com/tip...64,00.html<br />
<br />
Problems that I am facing and cannot be solved.<br />
<br />
1.Internet disconnect every half an hour once. When it disconnect queue folder under mailroot contains not queue problem bad mail folder I only maintain it to be 1mb max, that also no prob. I really cant able to find what is the reall cause the internet connection to be down with periodic interval.<br />
<br />
Conclusion:<br />
	After uninstall Greylist or JEP(S) GreyList Application from that server, the internet connection never drop down or disconnected. Why it happen like that, please help me to overcome this issue, everything works find except the inter connection instability. <br />
<br />
My Greylist properties<br />
<br />
Sink Timeout: 30000<br />
Database: MS Sql server<br />
Whitelist only: yahoo, hotmail, gmail, mycompany<br />
Remainging values all I use the default properties of greylist]]></description>
			<content:encoded><![CDATA[Internet unexpectedly disconnected after implement greylist with windows 2003 SMTP.<br />
<br />
Am using, windows 2003 SMTP and POP3 as my email server. I am using free version of greylists, I have tested Greylist and JEP(S) GreyList for my spam email blocker. Well it is working fine as a filter. <br />
<br />
After implement whitelist, Windows 2003 SMTP outbound delivery intervals and SMTP Relay properties. <br />
<br />
Problems, which I am facing and solved<br />
<br />
1.Badmail overflow can be get read by writing a batch file to delete with periodic interval (Recommend by Microsoft)<br />
<br />
2.Queue folder overflow can be rectified by setting Relay Restrictions under the SMTP virtual sever properties. Follow this url to understand better about queue folder overflow. http://searchexchange.techtarget.com/tip...64,00.html<br />
<br />
Problems that I am facing and cannot be solved.<br />
<br />
1.Internet disconnect every half an hour once. When it disconnect queue folder under mailroot contains not queue problem bad mail folder I only maintain it to be 1mb max, that also no prob. I really cant able to find what is the reall cause the internet connection to be down with periodic interval.<br />
<br />
Conclusion:<br />
	After uninstall Greylist or JEP(S) GreyList Application from that server, the internet connection never drop down or disconnected. Why it happen like that, please help me to overcome this issue, everything works find except the inter connection instability. <br />
<br />
My Greylist properties<br />
<br />
Sink Timeout: 30000<br />
Database: MS Sql server<br />
Whitelist only: yahoo, hotmail, gmail, mycompany<br />
Remainging values all I use the default properties of greylist]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Composite resin fillings are now much sought after for esthetic reasons]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=28</link>
			<pubDate>Tue, 04 Mar 2008 00:26:12 -0500</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=28</guid>
			<description><![CDATA[One way to treat a cavity in the teeth is to remove the decayed portion of the tooth and then "fill" the area on the tooth where the decayed material once lived. Fillings are used to “fill” the area that was once occupied by decay.<br />
<br />
Fillings are also used to repair cracked or broken teeth and teeth that have worn out. The procedure of using a filling is relatively easy. The dentist will numb the area around the decayed tooth with a local anesthetic. Next, a drill is used to remove the decayed area. <br />
<br />
Next, the dentist will probe the area of decay and decide if the entire decay can been removed. Once the decay has been removed, your dentist will prepare the space for the filling by cleaning the cavity of bacteria and debris. He will slightly etch the surface of the tooth to roughen it. The filling is then placed on the area. Generally, after the filling is in, your dentist will finish and polish it.<br />
<br />
The procedure of laying a Composite resin filling is called bonding. Bonding is a form of restorative cosmetic dentistry procedure that is performed to repair a damaged tooth that is worn, chipped, decayed or discolored. It is called so because we "bond" or attach a tooth colored material called composite resin onto the tooth. Bonding is also an effective way to close a small space or gaps between two teeth. <br />
<br />
Composite resin fillings have many advantages. Since the Composite resin filling bonds to the tooth, composite fillings restore most of the original strength of the tooth. In addition, they restore the natural appearance of the tooth. Teeth restored with white fillings are less sensitive to hot and cold. Most importantly, composite fillings are mercury-free and require less removal of tooth structure to place them.]]></description>
			<content:encoded><![CDATA[One way to treat a cavity in the teeth is to remove the decayed portion of the tooth and then "fill" the area on the tooth where the decayed material once lived. Fillings are used to “fill” the area that was once occupied by decay.<br />
<br />
Fillings are also used to repair cracked or broken teeth and teeth that have worn out. The procedure of using a filling is relatively easy. The dentist will numb the area around the decayed tooth with a local anesthetic. Next, a drill is used to remove the decayed area. <br />
<br />
Next, the dentist will probe the area of decay and decide if the entire decay can been removed. Once the decay has been removed, your dentist will prepare the space for the filling by cleaning the cavity of bacteria and debris. He will slightly etch the surface of the tooth to roughen it. The filling is then placed on the area. Generally, after the filling is in, your dentist will finish and polish it.<br />
<br />
The procedure of laying a Composite resin filling is called bonding. Bonding is a form of restorative cosmetic dentistry procedure that is performed to repair a damaged tooth that is worn, chipped, decayed or discolored. It is called so because we "bond" or attach a tooth colored material called composite resin onto the tooth. Bonding is also an effective way to close a small space or gaps between two teeth. <br />
<br />
Composite resin fillings have many advantages. Since the Composite resin filling bonds to the tooth, composite fillings restore most of the original strength of the tooth. In addition, they restore the natural appearance of the tooth. Teeth restored with white fillings are less sensitive to hot and cold. Most importantly, composite fillings are mercury-free and require less removal of tooth structure to place them.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[What the Hell...]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=25</link>
			<pubDate>Sat, 22 Dec 2007 17:38:34 -0500</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=25</guid>
			<description><![CDATA[... just a snap out of my MX - Logfile:<br />
<br />
<br />
Code:<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d1b-000001af, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d13-000000d4, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d1c-000001d6, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org)<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d15-0000011e, Recipient: &lt;***@arcormail.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcormail.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d13-000000d5, Recipient: &lt;***@nexgo.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@nexgo.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d19-0000018b, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
<br />
and so on ...<br />
<br />
What the hell is a so named spamblocker/filter/whatever that blocks or delayed mails from a server that proveable never send out spam, act as spamrelay or anything else that can maybe explain that?<br />
<br />
Ok, in some brains a good idea to block all mails, spam or not...<br />
<br />
That won't work folkz!<br />
<br />
I will inform the touched users on an other way and let them know what's going on. My last Q about that is unanswered from you since 3 month...<br />
<br />
<br />
Without greetings...<br />
Micha[/code]]]></description>
			<content:encoded><![CDATA[... just a snap out of my MX - Logfile:<br />
<br />
<br />
Code:<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d1b-000001af, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d13-000000d4, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d1c-000001d6, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org)<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d15-0000011e, Recipient: &lt;***@arcormail.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcormail.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d13-000000d5, Recipient: &lt;***@nexgo.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@nexgo.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
[22/Dec/2007 23:18:13] Sent: Queue-ID: 476d8d19-0000018b, Recipient: &lt;***@arcor.de&gt;, Result: delayed, Status: 4.1.1 450 4.7.1 &lt;***@arcor.de&gt;: Recipient address rejected: Policy Rejection- Greylisted, please try later (see http://www.greylisting.org).<br />
<br />
and so on ...<br />
<br />
What the hell is a so named spamblocker/filter/whatever that blocks or delayed mails from a server that proveable never send out spam, act as spamrelay or anything else that can maybe explain that?<br />
<br />
Ok, in some brains a good idea to block all mails, spam or not...<br />
<br />
That won't work folkz!<br />
<br />
I will inform the touched users on an other way and let them know what's going on. My last Q about that is unanswered from you since 3 month...<br />
<br />
<br />
Without greetings...<br />
Micha[/code]]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[SMTP Mail Issues]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=24</link>
			<pubDate>Sat, 22 Dec 2007 09:12:48 -0500</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=24</guid>
			<description><![CDATA[since we installed greylist we have issues in our SMTP blcoking by the server often and then reviving the SMTP connection after few hours<br />
<br />
What settings can be changed so this is not effected<br />
Thanks<br />
Admin<br />
http://www.netgains.org]]></description>
			<content:encoded><![CDATA[since we installed greylist we have issues in our SMTP blcoking by the server often and then reviving the SMTP connection after few hours<br />
<br />
What settings can be changed so this is not effected<br />
Thanks<br />
Admin<br />
http://www.netgains.org]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[We are a UK web host - our results are excellent!]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=23</link>
			<pubDate>Thu, 08 Nov 2007 04:00:08 -0500</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=23</guid>
			<description><![CDATA[Greylisting is reaching parts that other developers just can't reach (namely Microsoft and Yahoo, even with their bloated budgets).<br />
<br />
Greylisting was applied to all our web hosting accounts late October 2007 and has proved a great success dramatically reducing the amount of spam on all hosted accounts.<br />
<br />
Here is some of the feedback from our very happy clients:<br />
<br />
"I like this Greylisting - my inbox has never been so clear of trash.  THANK YOU!"<br />
"Would just like to say how brilliant the new spam greylisting is, haven't received a bad email since it was launched, thank you very much, it is a big improvement to all our inboxes in the office."<br />
"Since you added greylisting to our account it has almost eliminated spam emails for us.  Great work."<br />
"When you put that greylisting on it was as if someone had turned the spam-tap to off.  Worked straight away for us, many thanks."<br />
<br />
<br />
And finally from us to you:  A BIG Thanks.  Brilliant. <br />
<br />
If any host is contemplating trying it then waste no more time - apply Greylisting today and give your clients a smile on their face!<br />
<br />
I hope you manage to keep ahead of the spammers and we all continue to benefit from Greylisting.<br />
<br />
Best regards<br />
<br />
David G Walker - Managing Director Seiretto Ltd.<br />
http://www.Seiretto.com]]></description>
			<content:encoded><![CDATA[Greylisting is reaching parts that other developers just can't reach (namely Microsoft and Yahoo, even with their bloated budgets).<br />
<br />
Greylisting was applied to all our web hosting accounts late October 2007 and has proved a great success dramatically reducing the amount of spam on all hosted accounts.<br />
<br />
Here is some of the feedback from our very happy clients:<br />
<br />
"I like this Greylisting - my inbox has never been so clear of trash.  THANK YOU!"<br />
"Would just like to say how brilliant the new spam greylisting is, haven't received a bad email since it was launched, thank you very much, it is a big improvement to all our inboxes in the office."<br />
"Since you added greylisting to our account it has almost eliminated spam emails for us.  Great work."<br />
"When you put that greylisting on it was as if someone had turned the spam-tap to off.  Worked straight away for us, many thanks."<br />
<br />
<br />
And finally from us to you:  A BIG Thanks.  Brilliant. <br />
<br />
If any host is contemplating trying it then waste no more time - apply Greylisting today and give your clients a smile on their face!<br />
<br />
I hope you manage to keep ahead of the spammers and we all continue to benefit from Greylisting.<br />
<br />
Best regards<br />
<br />
David G Walker - Managing Director Seiretto Ltd.<br />
http://www.Seiretto.com]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Greylist in Outlook]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=22</link>
			<pubDate>Tue, 06 Nov 2007 09:21:56 -0500</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=22</guid>
			<description><![CDATA[I used to work without any problem with Outlook 2000 on my old notebook.<br />
<br />
Since I have the new one, equiped with Outlook 2003, I have a serious problem:<br />
<br />
When I send a mail, I receive the following message:<br />
<br />
 451 Greylisting enabled, try again in 1 minutes<br />
<br />
If I try to send again  the same mail, it is OK, sometimes at second try, sometimes at third....<br />
<br />
It happens to ANY destination (even when sending to mailbox which I'm sure  don't have antispam activated)<br />
<br />
It is very sad, because I'm obliged to go to my "sent item" box, forward the mail.......<br />
<br />
Note that this problem happens when I'm at home (in France, my Internet supplier is Free), but not when I'm connected to my company's network!!!<br />
<br />
I have Avast Antivirus, Windows Firewall, Freebox (modem) router mode enabled<br />
<br />
My questions are:<br />
- What can cause this "greylist" <br />
- How is it possible to cure that (perhaps does an option exist in Outlook, allowing an automatic re-send....)<br />
<br />
Thanks for your help]]></description>
			<content:encoded><![CDATA[I used to work without any problem with Outlook 2000 on my old notebook.<br />
<br />
Since I have the new one, equiped with Outlook 2003, I have a serious problem:<br />
<br />
When I send a mail, I receive the following message:<br />
<br />
 451 Greylisting enabled, try again in 1 minutes<br />
<br />
If I try to send again  the same mail, it is OK, sometimes at second try, sometimes at third....<br />
<br />
It happens to ANY destination (even when sending to mailbox which I'm sure  don't have antispam activated)<br />
<br />
It is very sad, because I'm obliged to go to my "sent item" box, forward the mail.......<br />
<br />
Note that this problem happens when I'm at home (in France, my Internet supplier is Free), but not when I'm connected to my company's network!!!<br />
<br />
I have Avast Antivirus, Windows Firewall, Freebox (modem) router mode enabled<br />
<br />
My questions are:<br />
- What can cause this "greylist" <br />
- How is it possible to cure that (perhaps does an option exist in Outlook, allowing an automatic re-send....)<br />
<br />
Thanks for your help]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Pb with whitelisting]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=21</link>
			<pubDate>Sat, 29 Sep 2007 12:09:41 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=21</guid>
			<description><![CDATA[pb with whitelist<br />
Really sorry, i've just seen that I did post on the wrong list (greylisting problems) instead of whitelisting. I repost it here.<br />
<br />
Hello,<br />
if I understand well how whitelist in greylist works, inserting an adress in /etc/postgrey/whitelist_clients would avoid any client to be temporarly rejected.<br />
I'm using it with postfix but while /etc/postgrey/whitelist_clients contens the line :<br />
<br />
orange-ftgroup.com<br />
<br />
I can see in my postfix logs the following :<br />
In: MAIL FROM: SIZE=5987<br />
Out: 250 Ok<br />
In: RCPT TO:<br />
Out: 450 : Recipient address rejected:<br />
Greylisted for 58 seconds (see http://isg.ee.ethz.ch/tools/postgrey/hel...dress.html)<br />
<br />
I probably misconfigured something but I don't know what.<br />
Somebody could show me the way ???<br />
<br />
Thank you in advance.<br />
PhL]]></description>
			<content:encoded><![CDATA[pb with whitelist<br />
Really sorry, i've just seen that I did post on the wrong list (greylisting problems) instead of whitelisting. I repost it here.<br />
<br />
Hello,<br />
if I understand well how whitelist in greylist works, inserting an adress in /etc/postgrey/whitelist_clients would avoid any client to be temporarly rejected.<br />
I'm using it with postfix but while /etc/postgrey/whitelist_clients contens the line :<br />
<br />
orange-ftgroup.com<br />
<br />
I can see in my postfix logs the following :<br />
In: MAIL FROM: SIZE=5987<br />
Out: 250 Ok<br />
In: RCPT TO:<br />
Out: 450 : Recipient address rejected:<br />
Greylisted for 58 seconds (see http://isg.ee.ethz.ch/tools/postgrey/hel...dress.html)<br />
<br />
I probably misconfigured something but I don't know what.<br />
Somebody could show me the way ???<br />
<br />
Thank you in advance.<br />
PhL]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[MS Exchange 2003 SP2 bug related to greylisting]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=18</link>
			<pubDate>Sat, 16 Jun 2007 06:46:24 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=18</guid>
			<description><![CDATA[HI.<br />
<br />
There is a serios bug in MS Exchange 2003 SP2 - when sending to hosts that implement greylisting, sometimes the Exchange server fails to requeue the message and doesn't retry it.<br />
Such messages are lost until the Exchange server administrator restarts the server or related services, then suddenly the sender users get an NDR for old emails that might have been sent several weeks ago, and/or the recipient gets an old email that was sent long ago.<br />
You will find more technical details in the links below.<br />
<br />
This bug was reported to MS more then a year ago, but they still haven't figured it out, and even didn't acknowledge it publicly.<br />
This means that there are many Exchange servers out-there having this bug, and in many cases especialy small businesses, the Exchange admin isn't aware of it at all.<br />
<br />
This is definitely a bug at the MS Exchange server side which fails to retry - it is not a bug in the greylisting receiving implementation, but as we all know any problem with email delivery affects the users at both ends, therefor it is important for you to be aware of the problem even if the problem is not at your side.<br />
So if your users or someone at the sending side tells you about similar problems, you will have a better answer. Knowledge is power!<br />
<br />
If you have already noticed this problem, please reply to this post, and also ask the Exchange admin at the sender side to read this post, and to read the other links below.<br />
<br />
Please read the following links to better understand this problem:<br />
<br />
http://groups.google.com/groups?um=1&tab...reylisting<br />
<br />
Subject: Exchange 2003 SP2 Greylisting bug - survey<br />
http://www.microsoft.com/technet/communi...sloc=en-us<br />
<br />
Subject: Exchange --&gt; Greylisting<br />
http://www.microsoft.com/communities/new...88c4e1198f<br />
<br />
Greylisting Problem - microsoft.public.exchange.admin | Google Groups: <br />
http://groups.google.com/group/microsoft...ac14b116db<br />
<br />
Any comments are welcome.<br />
<br />
Yizhar Hurwitz<br />
http://yizhar.mvps.org]]></description>
			<content:encoded><![CDATA[HI.<br />
<br />
There is a serios bug in MS Exchange 2003 SP2 - when sending to hosts that implement greylisting, sometimes the Exchange server fails to requeue the message and doesn't retry it.<br />
Such messages are lost until the Exchange server administrator restarts the server or related services, then suddenly the sender users get an NDR for old emails that might have been sent several weeks ago, and/or the recipient gets an old email that was sent long ago.<br />
You will find more technical details in the links below.<br />
<br />
This bug was reported to MS more then a year ago, but they still haven't figured it out, and even didn't acknowledge it publicly.<br />
This means that there are many Exchange servers out-there having this bug, and in many cases especialy small businesses, the Exchange admin isn't aware of it at all.<br />
<br />
This is definitely a bug at the MS Exchange server side which fails to retry - it is not a bug in the greylisting receiving implementation, but as we all know any problem with email delivery affects the users at both ends, therefor it is important for you to be aware of the problem even if the problem is not at your side.<br />
So if your users or someone at the sending side tells you about similar problems, you will have a better answer. Knowledge is power!<br />
<br />
If you have already noticed this problem, please reply to this post, and also ask the Exchange admin at the sender side to read this post, and to read the other links below.<br />
<br />
Please read the following links to better understand this problem:<br />
<br />
http://groups.google.com/groups?um=1&tab...reylisting<br />
<br />
Subject: Exchange 2003 SP2 Greylisting bug - survey<br />
http://www.microsoft.com/technet/communi...sloc=en-us<br />
<br />
Subject: Exchange --&gt; Greylisting<br />
http://www.microsoft.com/communities/new...88c4e1198f<br />
<br />
Greylisting Problem - microsoft.public.exchange.admin | Google Groups: <br />
http://groups.google.com/group/microsoft...ac14b116db<br />
<br />
Any comments are welcome.<br />
<br />
Yizhar Hurwitz<br />
http://yizhar.mvps.org]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Incorrectly Configured Servers]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=17</link>
			<pubDate>Wed, 06 Jun 2007 05:19:16 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=17</guid>
			<description><![CDATA[My host is looking at implementing greylisting and having read the details of this site I have a concern that maybe someone could help with.<br />
<br />
Imagine a new customer sends you an email. Your greylisting bounces it back. No problem so far, as the sender's server will just resend it. But, the sender's server is not configured correctly, doesn't resend and eventually the new customer gets a bounced back message.<br />
<br />
Luckily your new customer also has your phone number, so they ring you and say I tried to email you but it got bounced back. Ah yes say you, that's because we have greylisting and your mail server is configured incorrectly. OK says your new customer, I'll check with our server admin.<br />
<br />
5 minutes later the customer calls back. I've checked with our server admin and they say there's no problem with our servers, it's a problem your end. <br />
<br />
Do you then argue with them explaining that there server admins are rubbish and should be sacked immediately???<br />
<br />
OK, I've been a bit tongue in cheek, but the point I'm trying to make is you have two people speaking to each other, both of which have limited/non-existent technical knowledge. All they want to do is email each other. I don't think you can't expect end users to argue with new customers over a mail server configuration problem.<br />
<br />
What would you suggest to be the course of action in this case?<br />
<br />
Thanks]]></description>
			<content:encoded><![CDATA[My host is looking at implementing greylisting and having read the details of this site I have a concern that maybe someone could help with.<br />
<br />
Imagine a new customer sends you an email. Your greylisting bounces it back. No problem so far, as the sender's server will just resend it. But, the sender's server is not configured correctly, doesn't resend and eventually the new customer gets a bounced back message.<br />
<br />
Luckily your new customer also has your phone number, so they ring you and say I tried to email you but it got bounced back. Ah yes say you, that's because we have greylisting and your mail server is configured incorrectly. OK says your new customer, I'll check with our server admin.<br />
<br />
5 minutes later the customer calls back. I've checked with our server admin and they say there's no problem with our servers, it's a problem your end. <br />
<br />
Do you then argue with them explaining that there server admins are rubbish and should be sacked immediately???<br />
<br />
OK, I've been a bit tongue in cheek, but the point I'm trying to make is you have two people speaking to each other, both of which have limited/non-existent technical knowledge. All they want to do is email each other. I don't think you can't expect end users to argue with new customers over a mail server configuration problem.<br />
<br />
What would you suggest to be the course of action in this case?<br />
<br />
Thanks]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Finding out the blocked user in the database]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=16</link>
			<pubDate>Wed, 23 May 2007 17:19:43 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=16</guid>
			<description><![CDATA[Is there a way to get a list of IP's that are getting blocked in the access database. Right now when i go to the database under Internal it just lists the number of blocked IPs but dosent show individual IP's. I know you can go to the Log and see the response of the servers in order to evaluate if the email was blocked or not. But is that the one and only way to identify a blocked email source?<br />
Please advise.]]></description>
			<content:encoded><![CDATA[Is there a way to get a list of IP's that are getting blocked in the access database. Right now when i go to the database under Internal it just lists the number of blocked IPs but dosent show individual IP's. I know you can go to the Log and see the response of the servers in order to evaluate if the email was blocked or not. But is that the one and only way to identify a blocked email source?<br />
Please advise.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Greylisting with Forwarded Email]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=15</link>
			<pubDate>Wed, 23 May 2007 17:17:15 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=15</guid>
			<description><![CDATA[Hey, <br />
I setup a test exchange box in a new domain. I set forwarding from my gmail account to my newdomain email account on exchange. What i found out was when i check the access database any email that is being forwarded from my gmail will be listed as <br />
gmailusername+caf_=testdomainusername=testdomain.com@gmail.com<br />
<br />
Problem is, in this way i am not able to identify the original user who is sending email to my gmail account. For example if Sue at sue@hotmail.com sends an email to my gmail account and it gets forwarded to my test domain account it will have the same format in the database as i mentioned earlier. Since from the database i would never know that email came from Sue, what would be the way to identify the original user of the email?<br />
My guess was that since my gmail account is already been whitelisted, when Sue sends me an email it really dosent matter if i whitelist her email separately because my gmail account is already in the whitelist.<br />
<br />
I apologize if my language here is a bit confusing. Any help on this would be appreciated. I would love to implement this in my real environment.]]></description>
			<content:encoded><![CDATA[Hey, <br />
I setup a test exchange box in a new domain. I set forwarding from my gmail account to my newdomain email account on exchange. What i found out was when i check the access database any email that is being forwarded from my gmail will be listed as <br />
gmailusername+caf_=testdomainusername=testdomain.com@gmail.com<br />
<br />
Problem is, in this way i am not able to identify the original user who is sending email to my gmail account. For example if Sue at sue@hotmail.com sends an email to my gmail account and it gets forwarded to my test domain account it will have the same format in the database as i mentioned earlier. Since from the database i would never know that email came from Sue, what would be the way to identify the original user of the email?<br />
My guess was that since my gmail account is already been whitelisted, when Sue sends me an email it really dosent matter if i whitelist her email separately because my gmail account is already in the whitelist.<br />
<br />
I apologize if my language here is a bit confusing. Any help on this would be appreciated. I would love to implement this in my real environment.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Greylisting with Forwarded Email]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=14</link>
			<pubDate>Wed, 23 May 2007 17:15:49 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=14</guid>
			<description><![CDATA[Hey, <br />
I setup a test exchange box in a new domain. I set forwarding from my gmail account to my newdomain email account on exchange. What i found out was when i check the access database any email that is being forwarded from my gmail will be listed as <br />
gmailusername+caf_=testdomainusername=testdomain.com@gmail.com<br />
<br />
Problem is, in this way i am not able to identify the original user who is sending email to my gmail account. For example if Sue at sue@hotmail.com sends an email to my gmail account and it gets forwarded to my test domain account it will have the same format in the database as i mentioned earlier. Since from the database i would never know that email came from Sue, what would be the way to identify the original user of the email?<br />
My guess was that since my gmail account is already been whitelisted, when Sue sends me an email it really dosent matter if i whitelist her email separately because my gmail account is already in the whitelist.<br />
<br />
I apologize if my language here is a bit confusing. Any help on this would be appreciated. I would love to implement this in my real environment.]]></description>
			<content:encoded><![CDATA[Hey, <br />
I setup a test exchange box in a new domain. I set forwarding from my gmail account to my newdomain email account on exchange. What i found out was when i check the access database any email that is being forwarded from my gmail will be listed as <br />
gmailusername+caf_=testdomainusername=testdomain.com@gmail.com<br />
<br />
Problem is, in this way i am not able to identify the original user who is sending email to my gmail account. For example if Sue at sue@hotmail.com sends an email to my gmail account and it gets forwarded to my test domain account it will have the same format in the database as i mentioned earlier. Since from the database i would never know that email came from Sue, what would be the way to identify the original user of the email?<br />
My guess was that since my gmail account is already been whitelisted, when Sue sends me an email it really dosent matter if i whitelist her email separately because my gmail account is already in the whitelist.<br />
<br />
I apologize if my language here is a bit confusing. Any help on this would be appreciated. I would love to implement this in my real environment.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[sqlgrey]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=13</link>
			<pubDate>Wed, 25 Apr 2007 02:18:52 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=13</guid>
			<description><![CDATA[http://sqlgrey.sourceforge.net/<br />
<br />
This is an excellent greylisting implementation that works very well for several sites I manage, including one that processes over a million messages on the average day.<br />
<br />
sqlgrey is a fork of postgrey and has the following additional features:<br />
<br />
    * SQLgrey can withstand a database crash (grey-listing is automatically switched off)<br />
    * 3 grey-listing algorithms to choose from<br />
    * Support for file-based IP and FQDN whitelists<br />
    * Support for fetching up-to-date whitelists from a repository<br />
    * Can mail the admin when the database is unavailable<br />
    * Auto-whitelists now understand SRS (SPF-aware mail forwarding)<br />
    * IPv6 support<br />
    * OPTIN / OPTOUT support<br />
    * Fine log controls<br />
    * Activity reports<br />
<br />
<br />
well worth looking into if you want to have a hassle free experience with greylisting.]]></description>
			<content:encoded><![CDATA[http://sqlgrey.sourceforge.net/<br />
<br />
This is an excellent greylisting implementation that works very well for several sites I manage, including one that processes over a million messages on the average day.<br />
<br />
sqlgrey is a fork of postgrey and has the following additional features:<br />
<br />
    * SQLgrey can withstand a database crash (grey-listing is automatically switched off)<br />
    * 3 grey-listing algorithms to choose from<br />
    * Support for file-based IP and FQDN whitelists<br />
    * Support for fetching up-to-date whitelists from a repository<br />
    * Can mail the admin when the database is unavailable<br />
    * Auto-whitelists now understand SRS (SPF-aware mail forwarding)<br />
    * IPv6 support<br />
    * OPTIN / OPTOUT support<br />
    * Fine log controls<br />
    * Activity reports<br />
<br />
<br />
well worth looking into if you want to have a hassle free experience with greylisting.]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Why aren't accepted senders automatically white-listed?]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=12</link>
			<pubDate>Wed, 18 Apr 2007 01:02:22 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=12</guid>
			<description><![CDATA[Something that isin't mentioned at all (as far as I can tell) about greylisting is that people sending legit mail to a greylist receiver will get a message telling them that their message wasn't delivered and that the system will keep trying to deliver it (etc etc).  Messages like this usually cause consternation, worry and confusion on the part of most people, and every effort should be made to not force known-good sending MTA's through a greylist challenge.<br />
<br />
Hence my question, which is this:<br />
<br />
Once a sending MTA has passed a greylist challenge, why isin't it automatically white-listed (by it's IP address) so that in the future all mail from it will be accepted? <br />
<br />
Are there really instances where a sending MTA (located at a particular IP address) would pass a greylist challenge today, but fail it tommorrow, or next week?]]></description>
			<content:encoded><![CDATA[Something that isin't mentioned at all (as far as I can tell) about greylisting is that people sending legit mail to a greylist receiver will get a message telling them that their message wasn't delivered and that the system will keep trying to deliver it (etc etc).  Messages like this usually cause consternation, worry and confusion on the part of most people, and every effort should be made to not force known-good sending MTA's through a greylist challenge.<br />
<br />
Hence my question, which is this:<br />
<br />
Once a sending MTA has passed a greylist challenge, why isin't it automatically white-listed (by it's IP address) so that in the future all mail from it will be accepted? <br />
<br />
Are there really instances where a sending MTA (located at a particular IP address) would pass a greylist challenge today, but fail it tommorrow, or next week?]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[blacklisting]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=11</link>
			<pubDate>Thu, 15 Mar 2007 18:00:45 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=11</guid>
			<description><![CDATA[while I will say greylisting is the best means of cutting out spam that I've ever seen, it's not 100% I would like to also like to impliment a blacklisting feature, currently I do have exchanges filtering enabled but I'd like something that offers a little more than what exchange does I was thinking something like ORFilter I don't know I haven't read up on many yet, I would really like something that logs what it does.<br />
<br />
can you use any other third party applications like this with greylisting?<br />
and if so are there any that are recomended over the others as far as either functionality or compatibility goes?<br />
<br />
Thanks!<br />
Brady R. Cole]]></description>
			<content:encoded><![CDATA[while I will say greylisting is the best means of cutting out spam that I've ever seen, it's not 100% I would like to also like to impliment a blacklisting feature, currently I do have exchanges filtering enabled but I'd like something that offers a little more than what exchange does I was thinking something like ORFilter I don't know I haven't read up on many yet, I would really like something that logs what it does.<br />
<br />
can you use any other third party applications like this with greylisting?<br />
and if so are there any that are recomended over the others as far as either functionality or compatibility goes?<br />
<br />
Thanks!<br />
Brady R. Cole]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[greylisting with backup MX server]]></title>
			<link>http://www.greylisting.org/forums/showthread.php?tid=10</link>
			<pubDate>Mon, 12 Mar 2007 21:18:05 -0400</pubDate>
			<guid isPermaLink="false">http://www.greylisting.org/forums/showthread.php?tid=10</guid>
			<description><![CDATA[Hi.  I have a local SMTP receiver in Melbourne Australia and a backup MX server in Virginia USA.<br />
<br />
Is it a requirement that these servers share their greylisting databases?<br />
<br />
I am seeing some MTAs send email to one server and get a temporary rejection 451 then send to the other server and get temp rejection 451 there too. They do not try again.<br />
<br />
Most MTAs work fine.<br />
Any ideas?  Thanks.]]></description>
			<content:encoded><![CDATA[Hi.  I have a local SMTP receiver in Melbourne Australia and a backup MX server in Virginia USA.<br />
<br />
Is it a requirement that these servers share their greylisting databases?<br />
<br />
I am seeing some MTAs send email to one server and get a temporary rejection 451 then send to the other server and get temp rejection 451 there too. They do not try again.<br />
<br />
Most MTAs work fine.<br />
Any ideas?  Thanks.]]></content:encoded>
		</item>
	</channel>
</rss>