Nikolaos Milas:
>to force relaying to*both* those servers (mail AND mail2) at the
>same time? According to the documentation, I don't see that's
>possible (it seems only one transport:nexthop definition is
>acceptable), but can we achieve this somehow (except using
>always_bcc on mail.example.com)
On Thu, Aug 09, 2012 at 12:15:45PM +0300, Nikolaos Milas wrote:
> >>>/etc/postfix/transportmap
> >>>example.com relay:[mail.example.com], relay:[mail2.example.com]
> >No. As documented.
> >
> >>>to force relaying to*both* those servers (mail AND mail2) at the
> >>>same time? According to the docu
On 8/8/2012 1:32 πμ, Viktor Dukhovni wrote:
On Wed, Aug 08, 2012 at 12:58:41AM +0300, Nikolaos Milas wrote:
>A question: Could we use the format:
>
>/etc/postfix/transportmap
>example.com relay:[mail.example.com], relay:[mail2.example.com]
No. As documented.
>to force relaying to*both* tho
On 8/8/2012 4:24 AM, Nikolaos Milas wrote:
> On 8/8/2012 3:41 πμ, Stan Hoeppner wrote:
>
>> Yes, this is not a Postfix issue but a mail store issue. Nikolaos, what
>> mail server are you using? Cyrus, Dovecot, other?
>>
>> As Viktor points out, building an HA mail server is not trivial. But we
On 8/8/2012 12:24 μμ, Nikolaos Milas wrote:
It's Dovecot 2.0.
Addendum: We use Maildir and the load is low (aside spam). Only about
250 users/mailboxes (4G each). All servers are CentOS 5.8 (planning move
to 6.3).
Currently we have only one internal mail server (Postfix/Dovecot),
receivin
On 8/8/2012 3:41 πμ, Stan Hoeppner wrote:
Yes, this is not a Postfix issue but a mail store issue. Nikolaos, what
mail server are you using? Cyrus, Dovecot, other?
As Viktor points out, building an HA mail server is not trivial. But we
can probably point you to HA docs, and mailing lists, re
On 8/7/2012 5:32 PM, Viktor Dukhovni wrote:
> On Wed, Aug 08, 2012 at 12:58:41AM +0300, Nikolaos Milas wrote:
...
>> A second question: Is anyone aware of any (Linux) "smart" script
>> automating (at least to some extent) reliably enough detection of a
>> mail server failure (to avoid re-inventing
On Wed, Aug 08, 2012 at 12:58:41AM +0300, Nikolaos Milas wrote:
> A question: Could we use the format:
>
> /etc/postfix/transportmap
> example.com relay:[mail.example.com], relay:[mail2.example.com]
No. As documented.
> to force relaying to *both* those servers (mail AND mail2) at the
> same ti
On 7/8/2012 3:48 μμ, Viktor Dukhovni wrote:
This is difficult to automate reliably...
Thank you Victor for all the valuable info. I see.
A question: Could we use the format:
/etc/postfix/transportmap
example.com relay:[mail.example.com], relay:[mail2.example.com]
to force relaying to *both*
On Tue, Aug 07, 2012 at 03:24:37PM +0300, Nikolaos Milas wrote:
> I was wondering whether we could set up this server in a way so it
> can forward (relay) all mail to mail.example.com AND, if (and only
> if) this is temporarily down, then:
>
> 1. Keep incoming mail in queue until it can contact ma
Hello,
We are setting up a gateway server (mx.example.com) to serve as primary
MX (for domain example.com).
It will receive mail from the Internet and forward (relay) it using:
transport_maps = hash:/etc/postfix/transportmap
where: /etc/postfix/transportmap
example.com relay:[ma
11 matches
Mail list logo
