This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] "Dirty" recycled network assigned
- Previous message (by thread): [address-policy-wg] "Dirty" recycled network assigned
- Next message (by thread): [address-policy-wg] "Dirty" recycled network assigned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber, UniVie/ACOnet
Woeber at CC.UniVie.ac.at
Mon Jan 28 10:58:36 CET 2008
Florian Weimer wrote: > * Janos Zsako: > > >>>2. There is MORE than 1 IP address using for mail service. >> >>You can offer mail relay service through your mail server(s). >> >>The customer(s) should then configure their mail servers to forward >>mail to the "smart" host (your relay), rather than deliver it >>directly. > > > You also need to rewrite Received: lines, to remove records of the > supposedly infected address space. And you should do this on a separate > server on a dedicated prefix, so that misguided blacklist operators do > not retaliate against your main mail service for doing that. 8-( I really don't get that one :-) I suppose the NCC manufactures a completely fresh and shiny address space object when giving out "previously used" address space? Otherwise, messing around with changed lines *after* an allocation or assignment transaction is a BAD IDEA [TM] (as I found out ;-) ) Wilfried.
- Previous message (by thread): [address-policy-wg] "Dirty" recycled network assigned
- Next message (by thread): [address-policy-wg] "Dirty" recycled network assigned
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]