Thanks. I was going to look into alternate transports.
For the test, discard may be what we're looking for.
For the invalid domains, 'error' is much more appropriate.
On Wed, Apr 4, 2012 at 1:08 PM, Noel Jones wrote:
> On 4/4/2012 2:48 PM, Edward Morbius wrote:
>>
Further research. This looks promising.
http://kudithipudi.org/2009/05/15/how-to-block-outbound-e-mails-in-postfix/
On Wed, Apr 4, 2012 at 11:37 AM, Edward Morbius wrote:
> I'd like to set up a delivery rule / method which simply rejects
> delivery for a specific domain (or set
I'd like to set up a delivery rule / method which simply rejects
delivery for a specific domain (or set of domains).
The immediate need is testing based on a domain we control. We've
also got an issue of stale contacts for expired domains which pile up
in our queues but I haven't addressed them.
no longer having that issue, and
based on Viktor's response, we're still well under postfix's default
timeouts for both values.
On Mon, Oct 17, 2011 at 11:42 PM, Ralf Hildebrandt <
ralf.hildebra...@charite.de> wrote:
> * Edward Morbius :
> > Several of our peer m
r).
The slow connections are mostly smaller clients with low delivery rates, and
we're suspecting under-provisioned MS Exchange servers and the like.
Thanks.
On Tue, Oct 18, 2011 at 8:25 AM, Viktor Dukhovni wrote:
> On Mon, Oct 17, 2011 at 07:17:18PM -0700, Edward Morbius wrote:
>
Several of our peer mail systems (outbound) seem to take a while responding
to initial SMTP connections.
Is there any particularly dread pitfall to watch out for in bumping these
values up? 20s for connection, 40s for HELO is where we're at presently.
My main fear would be resource exhaustion, t
List management at KPSU isn't what it could be.
We've got contacts for a few domains which haven't existed in human memory,
and whose messages gum up our works. While I work with client relations to
mop up the mess, would it be possible to define a delivery rule and assign
domains to it such that
