Milter-greylist

Hi,

I don't think that's even the issue. As far as I can tell, 
Milter-Greylist is working correctly at my end. I assume the problem is 
that Comcast is trying to send the message, getting a tempfail, and 
treating it as a permanent failure and returning the message to the 
sender as undeliverable. I just want to know if I'm doing anything 
wrong, or if anyone else has had, or knows of anyone who has had, 
similar experiences with Comcast clearly violating Email standards by 
treating temporary failures as permanent errors.
Jayson

On 2/13/2019 4:46 PM, John Damm S�rensen john@... 
[milter-greylist] wrote:
>
> Comcast is probably using many different mail servers to resend 
> messages so my question is have you configured subnetmatch?
>
> From man page:
>
> /subnetmatch/
>     This is equivalent to the *-L* command line option. It takes a
>     slash followed by a CIDR mask as argument, and it commands the
>     subnet matching feature. Example, for a class C wide matching:
> subnetmatch /24
> /subnetmatch6/
>     This is equivalent to the *-M* command line option. It takes a
>     slash followed by a prefixlen as argument, and it commands the
>     subnet matching feature. Example, for a subnet wide matching:
> subnetmatch6 /64
>
> Best
>
> John
>
> Den 13-02-2019 kl. 21:46 skrev Jayson Smith jaybird@... 
> [milter-greylist]:
>>
>> Hi,
>>
>> I'm using Milter-Greylist mainly to filter spam received by the
>> submissions Email address for an online magazine, which by definition
>> must be public. This magazine is for writers with disabilities including
>> blindness, so tricks like putting the address in a picture won't work.
>> Anyway, I awoke this morning to the disturbing news that a regular
>> contributor was getting bounces when she tried to submit. I asked her to
>> forward a bounce, and it looks like Comcast, her ISP, is treating my
>> tempfail as a permfail and bouncing the message when it should be
>> retrying. My question is, am I doing something wrong or is Comcast
>> broken? Should my racl greylist line be a dacl instead? Below is the
>> greylist line in question, followed by the delivery status report.
>>
>> Thanks for any help,
>>
>> Jayson
>>
>> --------------------
>>
>> racl greylist list "grey users" delay 30m autowhite 3d msg "All mail to
>> this address is greylisted for spam prevention. Please try again later."
>>
>> Reporting-MTA: dns; resqmta-ch2-03v.sys.comcast.net [69.252.207.35]
>> Received-From-MTA: dns; resomta-ch2-08v.sys.comcast.net [69.252.207.104]
>> Arrival-Date: Wed, 13 Feb 2019 20:08:17 +0000
>>
>> Final-recipient: rfc822; submissions@...
>> Diagnostic-Code: smtp; 451 4.7.1 All mail to this address is greylisted
>> for spam prevention. Please try again later.
>>
>> Last-attempt-Date: Wed, 13 Feb 2019 20:08:18 +0000
>>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virusfri. www.avast.com 
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>