On Saturday 31 January 2009 10:29:35 Wietse Venema wrote:
> Well, that is just too bad. Postfix does not have to solve every
> problem that happens in a down-stream MTA. We live in a free world,
> and the market is always right.
Agreed. Which is why I informed if it's possible using standard conf
Melvyn Sopacua:
> On Saturday 31 January 2009 09:45:16 Wietse Venema wrote:
> > Melvyn Sopacua:
> > > On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
> > > > Melvyn Sopacua:
> > > > > The problem is that postfix will see "success" initially:
> > > > >
> > > > > - client sends
> > > > > -
On Saturday 31 January 2009 09:22:28 Terry Carmen wrote:
> Melvyn Sopacua wrote:
> > On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
> >> Melvyn Sopacua:
> >>> The problem is that postfix will see "success" initially:
> >>>
> >>> - client sends
> >>> - postfix receives
> >>> - postfix rel
On Saturday 31 January 2009 09:45:16 Wietse Venema wrote:
> Melvyn Sopacua:
> > On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
> > > Melvyn Sopacua:
> > > > The problem is that postfix will see "success" initially:
> > > >
> > > > - client sends
> > > > - postfix receives
> > > > - postf
Melvyn Sopacua:
> On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
> > Melvyn Sopacua:
> > > The problem is that postfix will see "success" initially:
> > >
> > > - client sends
> > > - postfix receives
> > > - postfix relays, gets OK
> > > > postfix deletes queued message
> > > - exch
Melvyn Sopacua wrote:
On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
Melvyn Sopacua:
The problem is that postfix will see "success" initially:
- client sends
- postfix receives
- postfix relays, gets OK
> postfix deletes queued message
- exchange checks quota, decides
On Saturday 31 January 2009 08:03:17 Wietse Venema wrote:
> Melvyn Sopacua:
> > The problem is that postfix will see "success" initially:
> >
> > - client sends
> > - postfix receives
> > - postfix relays, gets OK
> > > postfix deletes queued message
> > - exchange checks quota, decides mailbox
On Saturday 31 January 2009 08:21:56 Sahil Tandon wrote:
> On Sat, 31 Jan 2009, Melvyn Sopacua wrote:
> > @example.comlocalmailbox, |logthis, relay:[mx2.example.com]
>
> Hm, and where is this access map syntax documented?
No where, it's pseudo code to explain what my 'backup' service woul
On Sat, 31 Jan 2009, Melvyn Sopacua wrote:
> On Friday 30 January 2009 21:12:30 Victor Duchovni wrote:
> > On Fri, Jan 30, 2009 at 08:42:22PM -0900, Melvyn Sopacua wrote:
> > > 1) Accept mail for example.com as primary MX (yes, possible)
> > > 2) Relay to mx2.example.com (yes, possible)
> > > 3) I
Melvyn Sopacua:
> The problem is that postfix will see "success" initially:
>
> - client sends
> - postfix receives
> - postfix relays, gets OK
> > postfix deletes queued message
> - exchange checks quota, decides mailbox is full
> - exchange sends DSN to client
Use reject_unverified_recipien
On Saturday 31 January 2009 06:49:28 Terry Carmen wrote:
> Melvyn Sopacua wrote:
> > The reason is that a client has unsolved ongoing configuration issues
> > with their Exchange server and can no longer afford to loose mail because
> > of it. The Exchange server is not my problem(tm).
> >
> > . .
Hi Victor,
On Friday 30 January 2009 21:12:30 Victor Duchovni wrote:
> On Fri, Jan 30, 2009 at 08:42:22PM -0900, Melvyn Sopacua wrote:
> > 1) Accept mail for example.com as primary MX (yes, possible)
> > 2) Relay to mx2.example.com (yes, possible)
> > 3) If mx2.example.com gives fatal error, reduc
Melvyn Sopacua wrote:
The reason is that a client has unsolved ongoing configuration issues with
their Exchange server and can no longer afford to loose mail because of it.
The Exchange server is not my problem(tm).
. . .
4) Magically catch the accepted mail that bounces after completed tra
On Fri, Jan 30, 2009 at 08:42:22PM -0900, Melvyn Sopacua wrote:
> 1) Accept mail for example.com as primary MX (yes, possible)
> 2) Relay to mx2.example.com (yes, possible)
> 3) If mx2.example.com gives fatal error, reduce to transient and try again
> later (not sure if relay -o soft_bounce=yes w
Hello,
I'd like to know if I can provide the following solution using postfix:
1) Accept mail for example.com as primary MX (yes, possible)
2) Relay to mx2.example.com (yes, possible)
3) If mx2.example.com gives fatal error, reduce to transient and try again
later (not sure if relay -o soft_boun
15 matches
Mail list logo
