Blaise Hurtlin wrote:
> May I should explain a bit more what i want to do..
>
> I'm migrating my mail system from an old, buggy, Groupwise system to
> Postfix. The migration will take several month as I can't migrate all
> users at the same time.
> I want the following behaviour: all migrated users use the Postfix to
> send mails. On Postfix, if the user does not exist (ie, the mailbox is
> still on the Groupwise system), so i want to configure Postif to send
> the mail to Groupwise if he does not know the user.
>
> Blaise

Please do not top post.

Postfix cannot handle a "split" domain without using virutal_alias_maps
to an internal subdomain for DEFINED addresses or to use DEFINED
per-address transport_maps.
You CAN use the catch all method to rewrite/transport using the above
maps with local users DEFINED.  This creates (Out|Back)scatter without
some method of rejecting at the front edge. (See my previous comments.)

What happens if the user does not exist on "Groupwise"? 
You will be blindly accepting all messages for a domain and can easily
be used to attack another system (google "Joe Job").

Brian


>
> Brian Evans - Postfix List wrote:
>> Blaise Hurtlin wrote:
>>> Hi,
>>>
>>> I'm trying to configure my new Postfix system. I have all my users in
>>> a LDAP and use virtual mailbox.
>>>
>>> I need the following behaviour:
>>>  - Existing users in LDAP => delivered locally (this part works fine)
>>>  - Non-existing users => relay to another SMTP
>>>
>>> Any idea how to do that ? thanks..
>>>
>>> Blaise
>>
>> Don't blindly accept mail that can be rejected in a relay.  This causes
>> Backscatter and is frowned upon.
>>
>> You need to know at the Gateway which addresses are valid.
>> Techniques to do this include relay_recipient_maps and
>> 'check_recipient_access hash:/path/to/rcpt_map'
>> The first is used if you KNOW who is valid.  The second is used if you
>> don't with the following contents: 'subdomain.example.com
>> reject_unverified_sender'
>>
>> All of this is speculation without 'postconf -n'.
>>
>> Brian

Reply via email to