|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Duplicating Mails (going OT)
From: Admin Mailing Lists (mlist
intergrafix.net)Date: Fri Apr 14 2000 - 10:12:07 CDT
- Next message: Bennett Todd: "Re: Duplicating Mails (going OT)"
- Previous message: Rask Ingemann Lambertsen: "Re: Linux Memory Overcommits"
- In reply to: Wietse Venema: "Re: Duplicating Mails"
- Next in thread: Bennett Todd: "Re: Duplicating Mails (going OT)"
- Reply: Admin Mailing Lists: "Re: Duplicating Mails (going OT)"
- Reply: Bennett Todd: "Re: Duplicating Mails (going OT)"
- Reply: Wietse Venema: "Re: Duplicating Mails (going OT)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
While we're on the general topic, is there a way to send all OUTGOING
email from a domain/server to a file?
i.e. sorta something like what sendmail's -X switch did
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
admin
intergrafix.net Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://cygnus.ncohafmuta.com http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
On Fri, 14 Apr 2000, Wietse Venema wrote:
> Robert Kiessling:
> > Hi,
> >
> > what is the best way to duplicate emails using postfix?
>
> In the future, you would specify a routing map thusly:
>
> domain.name smtp:mailin01.provider.de, smtp:mailin02.provider.de
>
> which would leave the envelope recipient alone.
>
> Currently, the Postfix transport map lets you specify only one
> single destination, and there is no clean way to duplicate mail
> in Postfix that I am aware of.
>
> Wietse
>
> > I want emails to user
domain to be delivered to two mailservers,
> > mailin01.provider.de and mailin02.provider.de for backup purposes.
> >
> > One attempt was to use PCRE and a virtual map:
> >
> > /^([^%]+)
(.+)$/ ${1}%${2}
mailin01.provider.de,${1}%${2}
mailin02.provider.de
> >
> > But this requires mailin01 and mailin02 to understand the %
> > syntax. Also, it leads to possibly confusing mail header entries like
> >
> > | Received: from mailin00.provider.de (mailin00.provider.de [194.24.209.85])
> > | by mailin01.provider.de (8.9.3/8.9.3) with ESMTP id PAA00812
> > | for <user%domain.de
mailin01.provider.de>; Fri, 14 Apr 2000 15:35:23 +0200 (MET DST)
> >
> > Ideally, I would like to be able to specify
> >
> > default_transport = smtp:[mailin01.provider.de],smtp:[mailin02.provider.de]
> >
> > but the second entry seems to be just ignored.
> >
> > Are there other solutions?
> >
> > Robert
> >
> >
> >
> >
>
>
>
- Next message: Bennett Todd: "Re: Duplicating Mails (going OT)"
- Previous message: Rask Ingemann Lambertsen: "Re: Linux Memory Overcommits"
- In reply to: Wietse Venema: "Re: Duplicating Mails"
- Next in thread: Bennett Todd: "Re: Duplicating Mails (going OT)"
- Reply: Admin Mailing Lists: "Re: Duplicating Mails (going OT)"
- Reply: Bennett Todd: "Re: Duplicating Mails (going OT)"
- Reply: Wietse Venema: "Re: Duplicating Mails (going OT)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]