On 8/3/2011 11:05 AM, Jirka Bourek wrote:
> Noel Jones wrote:
>>
>> Seems to me if you're getting a "relay access denied" then the
>> @testing.domain is working, and you have some other rule that's
>> rejecting the mail. Or maybe you somehow removed "testing.domain"
>> from relay_domains.
>>
>> Sor
Noel Jones wrote:
Seems to me if you're getting a "relay access denied" then the
@testing.domain is working, and you have some other rule that's
rejecting the mail. Or maybe you somehow removed "testing.domain"
from relay_domains.
Sorry, I don't debug SQL. I suggest you get it working with fla
On 8/3/2011 6:59 AM, Jirka Bourek wrote:
>
> and I get "Recipient address rejected: User unknown in relay
> recipient table". Adding "@testing.domain" into table domains leads
> to "Relay access denied"
Seems to me if you're getting a "relay access denied" then the
@testing.domain is working, and
Noel Jones wrote:
On 8/2/2011 9:31 AM, Jason Gauthier wrote:
Greetings,
Due to a new business requirement, I need to make a change with postfix that I
am not certain how to handle.
First, I use postfix as a relay only system. It does not do local delivery.
Once it does it's tasks it passes
On 8/2/2011 5:15 PM, Wietse Venema wrote:
> Jason Gauthier:
Good to know. Definitely meant REJECT, versus bounce.I used the
phrase bouncer as a metaphor to the large bodyguards that
stereotypically guard a club from unwanted guests. ;)
>>
>>> Do you know what 'xyz.com' wil
Jason Gauthier:
> >>
> >> Good to know. Definitely meant REJECT, versus bounce.I used the
> >> phrase bouncer as a metaphor to the large bodyguards that
> >> stereotypically guard a club from unwanted guests. ;)
>
> >Do you know what 'xyz.com' will be doing with mail you send to them where
>>
>> Good to know. Definitely meant REJECT, versus bounce.I used the
>> phrase bouncer as a metaphor to the large bodyguards that
>> stereotypically guard a club from unwanted guests. ;)
>Do you know what 'xyz.com' will be doing with mail you send to them where the
>address isn't valid on
On Tuesday, August 2, 2011, 15:44:30, Jason Gauthier wrote:
>>> Now, my requirements have changes. I have acquired a domain, we'll
>>> call it xyz.com. I don't host it, and never have. Therefore, I do
>>> not know what email addresses are valid. I would like to capture
>>> *any* email address sent
>> Now, my requirements have changes. I have acquired a domain, we'll call it
>> xyz.com. I don't host it, and never have. Therefore, I do not know what
>> email addresses are valid. I would like to capture *any* email address sent
>> to xyz.com and accept it, and deliver it somehow.
>> I'm
On 8/2/2011 9:31 AM, Jason Gauthier wrote:
> Greetings,
>
> Due to a new business requirement, I need to make a change with postfix that
> I am not certain how to handle.
> First, I use postfix as a relay only system. It does not do local delivery.
> Once it does it's tasks it passes the email
I'd suggest configuring as secondary, setting the MX record for this box as a
primary, and use transport maps as suggested.
-Dennis Carr
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity and top
posting.
Jason Gauthier wrote:
Greetings,
Due to a new business require
On Aug 2, 2011, at 10:31 AM, Jason Gauthier wrote:
> Greetings,
>
> Due to a new business requirement, I need to make a change with postfix that
> I am not certain how to handle.
> First, I use postfix as a relay only system. It does not do local delivery.
> Once it does it's tasks it passes
On Tuesday, August 2, 2011, 10:31:44, Jason Gauthier wrote:
> Due to a new business requirement, I need to make a change with
> postfix that I am not certain how to handle.
> First, I use postfix as a relay only system. It does not do local
> delivery. Once it does it's tasks it passes the email
13 matches
Mail list logo
