myrdhin bzh put forth on 3/7/2011 1:53 AM:
No, it's not SPAM.
Ok, agreed, not spam.
In fact, zeDomain.tld is a french know domain : wanadoo.fr (and orange.fr).
:(
The same 10 servers handle mail for both wanadoo.fr and orange.fr. All
Postfix controls relevant to your issue available in
On 3/7/2011 7:21 AM, Stan Hoeppner wrote:
myrdhin bzh put forth on 3/7/2011 1:53 AM:
No, it's not SPAM.
Ok, agreed, not spam.
In fact, zeDomain.tld is a french know domain : wanadoo.fr (and orange.fr). :(
The same 10 servers handle mail for both wanadoo.fr and orange.fr. All
Postfix
Noel Jones put forth on 3/7/2011 7:37 AM:
On 3/7/2011 7:21 AM, Stan Hoeppner wrote:
I would suggest you grep your mail log for all outbound smtp connections
to these 10 IP addresses, and document all the recipient domains. Then
add all these domains to your slow transport map. If you still
On Mon, Mar 07, 2011 at 11:55:34AM -0600, Stan Hoeppner wrote:
Unfortunately, the newer postfix rate delay controls are still based on
the recipient domain, not the MX destination.
Yeah. He can absolutely fix his current problem with it. But if he has
to configure huge delays to
myrdhin bzh put forth on 3/6/2011 5:33 PM:
Really, thank you for your patience :) I have difficulty understanding
perfectly
English...
No, the *process* limit of 3 is implemented in master(8), which spawns
processes on demand, up to the process limit. The concurrency limit
Hello,
From: Stan Hoeppner
My spammer RADAR is beeping...
:)
No, it's not SPAM.
My client have a domain (for example clientDomain.tld) and a SMTP server. This
server rewrite all email addresses from firstname.surn...@clientdomain.tld to
firstname.surname-clientdomaine@zedomain.tld
