On 11/09/11 20:39, Frank Bulk wrote:
> While working through this today we realized that because our email filtering gateways hold our domain's MX record, SurgeMail only sees the email filtering gateway IPs for any messages sent to us from customers with their own email servers.  I assume the "g_spam_allow" doesn't do any deep header inspection?
>
> For now we've added the IP addresses of our email filtering gateways to "g_spam_allow", but there's the risk that we'll get a spam blast targeted to 300 recipients that doesn't get filtered out and SurgeMail will happily deliver it.
>
> Frank
>
> -----Original Message-----
> From: SurgeMail Support [mailto:surgemailHIDDEN@t@netwinsite.com]
> Sent: Tuesday, November 08, 2011 9:38 PM
> To: surgemailHIDDEN@etwinsite.com
> Subject: Re: [SurgeMail List] Bulk emailing
>
> I suggest you set
> 	g_rcpt_max "1000"
> 	g_rcpt_max_in "100"
> 	g_spam_allow "ip.address.of.church,chruch2,church3"
> You could use wild cards for ip addresses in your local area, e.g.
> 	g_spam_allow "123.23.*"
> to fairly quickly cover any local places that would be likely to send to
> your users in bulk like this.
>
>
>
>
> On 9/11/2011 11:06 a.m., Frank Bulk wrote:
>> We have customers (churches and schools, primarily), that have their own email server and want to send one email to hundreds of our customers.  They keep hitting up against the "Limit for recipients of untrusted channels, default g_rcpt_max", which we've set to 100.
>>
>> How do we overcome that in way that minimizes abuse by spammers?
>>
>> Frank
>>

The only place we add our filtering gateway to is g_gateway_allow.  But 
then none of our customers use the filtering gateway for relaying.  All 
outbound relaying by our customers is done via Surgemail here.

Lyle Giese
LCR Computer Services, Inc.