On 8/23/2009 7:01 PM, MySQL Student wrote:
Hi,
I'm also pretty sure it's not a network issue. After passing
billions of packets there isn't a single error. I'm also pretty sure
DNS is configured properly.
Have you checked the connection between postfix and the exchange
machines? After some ye
Hi,
>> I'm also pretty sure it's not a network issue. After passing
>> billions of packets there isn't a single error. I'm also pretty sure
>> DNS is configured properly.
>
> Have you checked the connection between postfix and the exchange
> machines? After some years, a cable can get bad, lousy,
Hi,
> problem today. Mail was queuing up on one of our servers with exactly
> the same messages as what you had. In our case a perl script on the
> postfix server had gone crazy and started consuming all the memory and
> swap space on the machine. Once that was fixed, the errors cleared up
> and t
Sorry in advance for the top posting or whatever gmail does on mobile
phones - i have no control over that. I bumped into a very similar
problem today. Mail was queuing up on one of our servers with exactly
the same messages as what you had. In our case a perl script on the
postfix server had gone
Hi,
This is just a wild guess...
> I'm also pretty sure it's not a network issue. After passing
> billions of packets there isn't a single error. I'm also pretty sure
> DNS is configured properly.
Have you checked the connection between postfix and the exchange
machines? After some years, a cabl
Hi,
I have been using an older version of postfix on a relay server for
quite a few years now, without any real incident. It accepts mail from
one or two other servers and forwards it on to an internal Exchange
server on the same network. It handles about 250k messages per day.
It's configured wit
