Erik Weber wrote:
> Stephan Wentz wrote:
>> Erik Weber schrieb:
>>
>>> Stephan Wentz wrote:
>>>
>>>> Erik Weber schrieb:
>>>>
>>>>
>>>>> Pete Barnwell wrote:
>>>>>
>>>>>> There are ways around that:
>>>>>>
>>>>>> a) If it's Exchange 2K3 then it can
be configured not to blindly
>>>>>> accept
>>>>>> mail for <anything> domain.
>>>> So the only thing I need now is to suppress
the undeliverable-mails,
>>>> any
>>>> hints on that one?
>>>>
>>> Then you should really make sure that exchange
doesn't accept mail for
>>> non-existing users as Pete suggested. If you
tell us what version of
>>> exchange your customer is using it'll be easier
to provide an exact
>>> method.
>>>
>>
>>
>> Hmm I think we are talking past each other
>>
>> I don't know the exchange version, but I don't
think that this matters
>> here. The maia-host is located at a remote hoster,
the exchange server
>> is located in the intranet of the customer.
>>
>> What I want to achive/what I did already:
>>
>> - give the maia host a list of all valid recipients
(through
>> relay_recipient_maps, this works fine)
>> - relay all of these addresses to exchange (works
fine)
>> - discard all mails that are NOT in the
relay_recipient_maps, and
>> supress all bounce-messages.
>>
>
> I was assuming you were to use verify_maps, but
apparently you're not
>
> If you can get your customer to provide you with a list
of
> email-addresses (by running a script regularly or
something. Even
> better, a script that uploads it to your server, then
you can import it
> with anohter scheduled/cron job) that would be fine and
I think you're set.
What's the difference between relay_recipient_maps and
verify_maps? And
why is the second better?
Bye, Stephan
_______________________________________________
Maia-users mailing list
Maia-users renaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
|