OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: about special relay due to earthquake from Taiwan

From: mouss (usebsdfree.fr)
Date: Sat Dec 30 2006 - 13:24:16 CST


Dogz wrote:
> Hi, Mouss,
>
>
>
> 2006/12/30, mouss <usebsdfree.fr>:
>>
>> >>do not top post.
>
>
> I don't get it, I don't understand what you meant.

http://en.wikipedia.org/wiki/Top-posting
http://www.caliburn.nl/topposting.html
...

>
>> If you know what domains to route where it's easy with the transport
>> table.
>> cn dogz.cnexample.com
>> hk dogz.hkexample.com
>> known-chinese-domain.example.com
> <http://known-chinese-domain.example.com/>
> dogs.cnexample.com
>

I don't know what Magnus meant here.

> In this case, we found the one of ISP can help us to relay it to send out
> emails to China, Hong Kong and so on. He just give us one email
> account to
> relay. Therefore we need to forward some domains belonged to China
> NIC, Hong
> Kong NIc and so on to this ISP, so that we can send out the email to
> China,
> HK domains.
>

if this ISP supports extensions, you can forward to
dogs.cn+user=domainexample.com
so that a later server can get the original address from here. This
assumes you have some control at the other end.

if he doesn't support extensions (but you still have some control at the
other end), you can play with the "To" header (aka multi-drop
mailboxes). but this is uggly and fragile.

The best would be if he accepts relaying from your network to some
domains (whatever is the user part).

>>
>> >so you relay mail for test.com.anydomain.example ?
>
>
> NO, relay the relative mails to the specific email address.

I meant that /test\.com/ matches any address that contains "test.com".
Including contest.company.com.

better use hash maps since you don't need pcre here.

>
>> the .test.com entry is subject to parent_domain_matches_subdomain
>> setting.
>
> Yes, I know this. thank you for your reminding.
>
>>> # vi /etc/postfix/transport
>> >> /test\.com/ dogzgmail.com
>> >no. this is a (risky) virtual alias entry. (it's risky because it
>> breaks
>> recipient validation).
>> I know what you meant, but I just test by following what he said.
>>
>> >for transports, use something like (hash, not pcre here):
>> >test.example smtp:[earthquake.relay.example]:587
>> what is the different if I use relay_domains map ? and I don't need
>> to ask
>> them to open the port.
>>
>
>

relay_domains is just to declare which domains you accept to relay any
mail to.
if you don't need to open the port, just remove ":587" so that the
standard port is used.

but this assumes that the relay ISP accepts to relay any mail for you,
not just mail to "dogz".