Thanks for the blindingly quick reply.
> * Bryan Harrison :
>> I've recently migrated services to a new mailserver, which has of course
>> promptly started kicking out dire errors that didn't show during testing.
>
> You are running gilded-bat.laughingboot.ne
I've recently migrated services to a new mailserver, which has of course
promptly started kicking out dire errors that didn't show during testing.
Here's an example transcript, postconf -n is below
Out: 220 gilded-bat.laughingboot.net ESMTP Postfix
In: EHLO [10.2.45.174]
Out: 250-gilded-bat.lau
;> On Tue, Nov 09, 2010 at 03:13:01PM -0800, Bryan Harrison wrote:
>>> Viktor:
>>>> Perhaps the original domain is incorrectly listed in
>>>> $mydestination
>>>
>>> I have no mydestination entry. Can I use one to force the correct
>
ry info for hundreds of email addresses.
Can you suggest any less labor-intensive way I might configure Postfix to force
the correct behavior?
Thanks again,
Bryan
___
On Nov 9, 2010, at 1:59 PM, Victor Duchovni wrote:
> On Tue, Nov 09, 2010 at 01:51:22PM -0800, Bryan Harr
> Please post a shorter problem description with relevant log entries, postconf
> -n output and all relevant table entries.
I accept full responsibility for the fact that my post was so wordy it was easy
to miss that it contains everything you've requested except the log entries.
;) Once more
I’ve moderate expertise with Postfix and sys admin in general, and after 10
days of beating my head against this particular brick wall am posting this
overly long, rather tedious question because I’ve exhausted my other resources
but am not quite ready to throw in the towel.
That said…
Here’
