On 2/24/2013 6:39 AM, Robert Schetterer wrote:
Am 24.02.2013 12:28, schrieb Deeztek.com Support:On 2/22/2013 4:13 PM, Wietse Venema wrote:Deeztek.com Support:On February 22, 2013 3:40:22 PM Viktor Dukhovni <[email protected]> wrote:On Fri, Feb 22, 2013 at 03:13:27PM -0500, Deeztek.com Support wrote:[email protected] smtp:[1.1.1.1] [email protected] smtp:[2.2.2.2] example.com smtp:somewhere.elseSorry about the top-posting. Okay this is a little bit closer. So, I'm assuming if I use the domain in conjuction with recipients for the same domain the transport line for the domain has to point somewhere completely different than the recipient lines? In other words I can't have the following? [email protected] smtp:[1.1.1.1] [email protected] smtp:[2.2.2.2] example.com smtp:[1.1.1.1]You can, but the bob entry is redundant. I don't recommend per-mailbox transport entries at all, it is best to stick to per-domain transport entries only, and handle per-user routing via virtual(5) alias rewriting.Typically this would be done with virtual aliases that send [email protected] to [email protected] WietseI cannot seem to find any reference to the format you have suggested above for the aliases file.[email protected] smtp:[1.1.1.1] should be in transport , not aliases I tried it as[email protected] to [email protected] with no luck. Any suggestions? ThanksBest Regards MfG Robert Schetterer
I realize that and it works when I put: [email protected] smtp:[1.1.1.1]in transport. However, according to Victor "...it is best to stick to per-domain transport entries only, and handle per-user routing via virtual(5) alias rewriting." Then Wietse said I should enter something like
[email protected] to [email protected]in the aliases but I can't seem to get that to work neither do I find a reference for such an entry in docs or google.
smime.p7s
Description: S/MIME Cryptographic Signature
