https://rimuhosting.com/knowledgebase/linux/mail/greylisting%20with%20postgr... I have followed the instructions at the above URL to configure greylisting for non-list mail to the LUV server (that is for the direct address of the president etc). That should cut down on spam without inconvenience. I might implement it for the committee list too as that is AFAIK the only list that accepts posts from non-members. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On 19/04/16 12:13, Russell Coker via luv-main wrote:
https://rimuhosting.com/knowledgebase/linux/mail/greylisting%20with%20postgr...
I have followed the instructions at the above URL to configure greylisting for non-list mail to the LUV server (that is for the direct address of the president etc). That should cut down on spam without inconvenience. I might implement it for the committee list too as that is AFAIK the only list that accepts posts from non-members.
Good idea! I use greylisting on my own email server, too. Thanks, Andrew
Russell Coker via luv-main <luv-main@luv.asn.au> writes:
https://rimuhosting.com/knowledgebase/linux/mail/greylisting%20with%20postgr...
Are you already using postscreen? 15:05 <knoba> SMTP triage server available in Postfix 2.8, see http://www.postfix.org/POSTSCREEN_README.html and http://www.postfix.org/postscreen.8.html Last time greylisting came up (many years ago), the folks on Freenode's #postfix (who are generally very sensible) basically said Don't bother doing greylisting, postscreen is better in every way. I'm using postgrey still because my postfix is f'ing ancient. According to my postgrey config, ca. 2011, @bigpond.com & @optusnet.com.au need to bypass postgrey due to brain damage in their MTA pools (they retry from different server IPs).
On 19/04/2016 3:09 PM, Trent W. Buck via luv-main wrote:
According to my postgrey config, ca. 2011, @bigpond.com & @optusnet.com.au need to bypass postgrey due to brain damage in their MTA pools (they retry from different server IPs).
There are loads of "brain damaged services" doing just that, which makes greylisting much more painful than it should be. Cheers AndrewM
On Tuesday, 19 April 2016 3:09:22 PM AEST Trent W. Buck via luv-main wrote:
I'm using postgrey still because my postfix is f'ing ancient.
I started off using postgrey but switched to sqlgrey as it is (or at least was then) pretty clever in learning about systems that retry correctly. http://sqlgrey.sourceforge.net/ # The main drawback of grey-listing as it was done in early implementations # was the delaying of legit emails. # # This is nearly solved by the auto-white-listing mechanisms built # into SQLgrey: # # When a sender has been seen coming from a given IP address, it # is automatically accepted when coming again from the same IP address. # # When several senders from the same domain have been seen coming # from the same IP address, senders from the same domain are accepted # when coming from the same IP address. # # The delay shouldn't really be a drawback anymore: users will only # experience delays (mostly in the 6 to 30 minutes range) when receiving # the first email from a given sender. And on a large scale, new senders # from a given domain are automatically accepted from the IPs previously # used for this domain email traffic. -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
On Tue, 19 Apr 2016 03:09:22 PM Trent W. Buck via luv-main wrote:
<luv-main@luv.asn.au> writes:
https://rimuhosting.com/knowledgebase/linux/mail/greylisting%20with%20pos tgrey
Are you already using postscreen?
15:05 <knoba> SMTP triage server available in Postfix 2.8, see http://www.postfix.org/POSTSCREEN_README.html and http://www.postfix.org/postscreen.8.html
Last time greylisting came up (many years ago), the folks on Freenode's #postfix (who are generally very sensible) basically said
Don't bother doing greylisting, postscreen is better in every way.
Thanks for the suggestion, I'll check that out. But I'll try it on other mail servers first. While spam on the LUV server is a problem for the president it isn't a problem for regular members who would have a problem if I broke email... On Tue, 19 Apr 2016 04:27:10 PM Andrew McGlashan via luv-main wrote:
On 19/04/2016 3:09 PM, Trent W. Buck via luv-main wrote:
According to my postgrey config, ca. 2011, @bigpond.com & @optusnet.com.au need to bypass postgrey due to brain damage in their MTA pools (they retry from different server IPs).
There are loads of "brain damaged services" doing just that, which makes greylisting much more painful than it should be.
There are lots of significant mail receivers such as Yahoo and Verizon that rapidly block IP addresses due to accusations of spamming. While it's annoying that some big senders use lots of addresses it does mitigate those problems. On Tue, 19 Apr 2016 08:53:43 PM Chris Samuel via luv-main wrote:
I started off using postgrey but switched to sqlgrey as it is (or at least was then) pretty clever in learning about systems that retry correctly.
Thanks for the suggestion, I might install that on my own mail server. I don't know whether the benefit would be worth it for the LUV server. I might get Andrew Pam to help with anti-spam measures. I think he gets more spam through the LUV server than anyone else. ;) -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
On 19/04/16 21:26, Andrew Pam via luv-main wrote:
On 19/04/16 21:23, Russell Coker via luv-main wrote:
I might get Andrew Pam to help with anti-spam measures. I think he gets more spam through the LUV server than anyone else. ;)
I certainly hope nobody else is getting as much! :)
How many in number/day on average? LUV is certainly my main source of spam by far, but to be honest it does not bother enough to complain. btw: I still receive luv-vice-president email. Daniel.
Cheers, Andrew _______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
On Tue, 19 Apr 2016 09:54:43 PM Daniel Jitnah wrote:
btw: I still receive luv-vice-president email.
Fixed. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
Russell Coker via luv-main <luv-main@luv.asn.au> writes:
On Tue, 19 Apr 2016 04:27:10 PM Andrew McGlashan via luv-main wrote:
On 19/04/2016 3:09 PM, Trent W. Buck via luv-main wrote:
According to my postgrey config, ca. 2011, @bigpond.com & @optusnet.com.au need to bypass postgrey due to brain damage in their MTA pools (they retry from different server IPs).
There are loads of "brain damaged services" doing just that, which makes greylisting much more painful than it should be.
There are lots of significant mail receivers such as Yahoo and Verizon that rapidly block IP addresses due to accusations of spamming. While it's annoying that some big senders use lots of addresses it does mitigate those problems.
Sorry, I was unclear. What I meant was: Turning on postgrey may prevent bigpond/optus accounts from posting to LUV. [Last checked in 2011] Although by this point, it's probably moot -- someone would've complained.
On Wed, 20 Apr 2016 07:56:01 PM Trent W. Buck via luv-main wrote:
Sorry, I was unclear. What I meant was:
Turning on postgrey may prevent bigpond/optus accounts from posting to LUV. [Last checked in 2011]
No. The LUV lists don't have greylisting applied. It might have prevented some people from sending mail to the president, but I think that the default configuration of Postgrey covers this. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/
participants (6)
-
Andrew McGlashan -
Andrew Pam -
Chris Samuel -
Daniel Jitnah -
Russell Coker -
trentbuck＠gmail.com