Re: Config

Stephan Wentz wrote:
> 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?
>   

IIRC address_verify_map tries to deliver the mail to the
destination 
server (which would be a bad thing with the default exchange
setup), 
whereas relay_recipient_maps is something you supply as
static (or a 
table lookup).
I never said it was better, it can be easier to setup (if
you manage to 
get the destination to reject non-existing users) since you
don't have 
to fuddle with exporting and importing of lists 

By the looks of the discussion so far you should probably
force your 
customer to supply you with a list and use
relay_recipient_maps (or 
transport_maps).


-- 
Erik Weber
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users

Erik Weber wrote:
> Stephan Wentz wrote:
>> 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?
>>   
> 
> IIRC address_verify_map tries to deliver the mail to
the destination
> server (which would be a bad thing with the default
exchange setup),
> whereas relay_recipient_maps is something you supply as
static (or a
> table lookup).
> I never said it was better, it can be easier to setup
(if you manage to
> get the destination to reject non-existing users) since
you don't have
> to fuddle with exporting and importing of lists 
> 
> By the looks of the discussion so far you should
probably force your
> customer to supply you with a list and use
relay_recipient_maps (or
> transport_maps).

Yea, that's my setup right now, and it seems to work fine.
Only the
inital setup will be done by me, all later changes are
handled by the
customer, and he is happy with this solution. Case closed


Thanks for all your help!

Stephan
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users