On Sat, 2021-07-03 at 00:30 -0600, @lbutlr wrote:
>
> MX backups are a legacy of 30-40 years ago when it was very common to
> have machines that only periodically connected to the Internet. There
> are many reasons they are a bad idea in a modern context, and having a
> third party be a alternate
On 01 Jul 2021, at 23:54, Maurizio Caloro wrote:
>
> Searching any Service that offer free any possible MX Backup?
MX backups are a legacy of 30-40 years ago when it was very common to have
machines that only periodically connected to the Internet. There are many
reasons they are a ba
On 2021-07-02 07:54, Maurizio Caloro wrote:
Searching any Service that offer free any possible MX Backup?
Found kisolabs "dot" com but it seems this service are down
perfekt for testing backup mx :=)
Thanks for possible update or help
you could do self service with another post
On 2/07/2021 3:54 pm, Maurizio Caloro wrote:
Hello
Searching any Service that offer free any possible MX Backup?
Why do you need a backup MX? Usually MSAs will queue for a while (4 days
seems a common default due to language in the smtp RFCs) or the senders
will get a bounce notice. If you
Hello
Searching any Service that offer free any possible MX Backup?
Found kisolabs "dot" com but it seems this service are down
Thanks for possible update or help
Regards
Mauri
On Sun, Mar 31, 2019 at 06:59:40AM +, Dominic Raferd wrote:
> On Sun, 31 Mar 2019 at 07:40, Jon LaBadie wrote:
>
> > When I try to block spam from repeaters, via access.db,
> > firewall, ... the first thing that happens is the blocked
> > mail gets delivered via
On 31 Mar 2019, at 2:38, Jon LaBadie wrote:
When I try to block spam from repeaters, via access.db,
firewall, ... the first thing that happens is the blocked
mail gets delivered via my MX backup host. Mail received
by this route does not seem to be checked against the
access database
On Sun, 31 Mar 2019 at 07:40, Jon LaBadie wrote:
> When I try to block spam from repeaters, via access.db,
> firewall, ... the first thing that happens is the blocked
> mail gets delivered via my MX backup host. Mail received
> by this route does not seem to be checked against
When I try to block spam from repeaters, via access.db,
firewall, ... the first thing that happens is the blocked
mail gets delivered via my MX backup host. Mail received
by this route does not seem to be checked against the
access database.
Is there something I'm not turning on to enable checks
Il 2017-09-01 22:57 Noel Jones ha scritto:
[..]
On the backup MX:
[..]
Well, finally we did it!
Basically I think we can say that the backup server does not have to
recognize as local, domains and addresses.
This is what I did:
"server1.org" the.backed-up.domain.tld (primary domain)
On 9/3/2017 6:28 AM, Davide Marchi wrote:
> Il 2017-09-01 22:57 Noel Jones ha scritto:
> [..]
>>
>> On the backup MX:
>>
>>
>> DO NOT list the domain in mydestination, virtual_alias_domains, or
>> mailbox_domains parameters. These list domains for local delivery.
>
>
> You mean: do not list the
://www.postfix.org/ADDRESS_CLASS_README.html
ok!
On the other hand, most folks these days think a backup MX is more
trouble than it's worth due to the way they are abused by spammers.
I think it's very important to manage the MX backup server autonomously
and that is most important too, be careful
> My point is to understand why Postfix (on MX backup) store email
> into mailbox and does not queue them.
On the backup MX:
DO NOT list the domain in mydestination, virtual_alias_domains, or
mailbox_domains parameters. These list domains for local delivery.
DO list the
MX)
My point is to understand why Postfix (on MX backup) store email into
mailbox and does not queue them.
It seems to me that the essential parameter is:
/relay_domains = . . . the.backed-up.domain.tld >
(server1)/
and then:
mydestination = server2, localhost.server2, localho
Davide Marchi:
If I shut down the primary server, the MX backup receive the mail
correctly and mail goes into mailbox 'INBOX'.
Il 2017-08-27 14:49 wie...@porcupine.org ha scritto:
Well that is the mistake. This server should not deliver to mailbox.
On 27.08.17 22:35, Davide Marchi wrote
On Sun, Aug 27, 2017 at 01:01:58PM +0200, Davide Marchi wrote:
> If I shut down the primary server, the MX backup receive the mail correctly
> and mail goes into mailbox 'INBOX'.
> The problem is that if I try to look into the postfix queue this is empty:
Do not list the mx-back
Il 2017-08-27 14:49 wie...@porcupine.org ha scritto:
Davide Marchi:
If I shut down the primary server, the MX backup receive the mail
correctly and mail goes into mailbox 'INBOX'.
Well that is the mistake. This server should not deliver to mailbox.
Good, this is interesting, but a little
Davide Marchi:
> If I shut down the primary server, the MX backup receive the mail
> correctly and mail goes into mailbox 'INBOX'.
Well that is the mistake. This server should not deliver to mailbox.
Have a look at Postfix documentation:
"Configuring Postfix as primary or bac
Hi friends,
I'm wondering about an Postfix MX backup server correct configuration.
I'm working on Debian Jessie and Postfix 2.11.x.
If I shut down the primary server, the MX backup receive the mail
correctly and mail goes into mailbox 'INBOX'.
The problem is that if I try to look
Hi friends,
I would like to know how automate the users and domains list between primary
and backup MX server, where the primary (and secondary) mail server use
mysql for each user and domain list (and create so an MX backup server that
it does not become a "backscatter mail"!)
Hi all, I need an advice about my mx-backup server
main mail server has many antispam system (amavis, spamassassin, etc.),
when an email bounced by these antispam, the email goes to mx-backup
server. mx-backup server keep email inside own queue.
So, do I need install amavis and other antispam
Am 13.03.2014 14:42, schrieb Pol Hallen:
Hi all, I need an advice about my mx-backup server
main mail server has many antispam system (amavis, spamassassin, etc.),
when an email bounced by these antispam, the email goes to mx-backup
server. mx-backup server keep email inside own queue
Am 13.03.2014 14:46, schrieb li...@rhsoft.net:
Am 13.03.2014 14:42, schrieb Pol Hallen:
Hi all, I need an advice about my mx-backup server
main mail server has many antispam system (amavis, spamassassin, etc.),
when an email bounced by these antispam, the email goes to mx-backup
server. mx
On 3/13/2014 8:42 AM, Pol Hallen wrote:
Hi all, I need an advice about my mx-backup server
main mail server has many antispam system (amavis, spamassassin, etc.),
when an email bounced by these antispam, the email goes to mx-backup
server. mx-backup server keep email inside own queue.
So
the
primary fails.
hi, thanks for your reply. I need an mx-backup because my first server
could goes down. So, I follow your advices installing antispam on
mx-backup.
Pol
but with port 25 firewalled off until the
primary fails.
hi, thanks for your reply
I need an mx-backup
says who?
because my first server could goes down
* a server does not go down regulary
* short network outages are meaningsless for a MX
* if the server crashs monitoring / auto-restart / HA
but with port 25 firewalled off until the
primary fails.
hi, thanks for your reply. I need an mx-backup because my first server
could goes down. So, I follow your advices installing antispam on
mx-backup.
Pol
Note that a proper backup MX must not accept mail the primary would
reject
Hi All,
I am tringsetup one MX backup server! And I need help!
For sample,I have 2 MX:
10 mail.mydomain.net
20 mail.backup.mydomain.net
In my mainserver (10) I have this on main.cf
myhostname = mail.mydomain.net
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc
On Mon, Apr 29, 2013 at 12:16:56AM +, ren...@dokfile.com wrote:
I am trying to setup a MX backup server. And I need help.
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#backup
--
Viktor.
* Bissio2000 bissio2...@yahoo.it:
According to the standard configuration explained at
http://www.postfix.org/STANDARD_CONFIGURATION_README.html about setting up a
primary and secondary mx, I don't understand how the mx backup returns back
all messages when the primary server come up from
On 07/12/2010 10:25, Bissio2000 wrote:
Thanks... it works fine without any field into trasnport map (even if every
tutorial on line says to use transport map:)
So I'm wondering if I could use all domain name listed into
postfix_virtual_domains instead into relay_domains because so i could use
On 07/12/2010 10:25, Bissio2000 wrote:
Thanks... it works fine without any field into trasnport map (even if every
tutorial on line says to use transport map:)
So I'm wondering if I could use all domain name listed into
postfix_virtual_domains instead into relay_domains because so i could
Hi all,
i'm setting postfix server as primary and mx backup as well and i'm not
using relay_domains directive.
this is my configuration:
DNS
domain.com IN MX 10 primary.server.com
domain.com IN MX 20 secondary.server.com
POSTFIX
transport_maps = mysql:/etc/postfix/mysql_transport.cf
Bissio2000:
Hi all,
i'm setting postfix server as primary and mx backup as well and i'm not
using relay_domains directive.
this is my configuration:
DNS
domain.com IN MX 10 primary.server.com
domain.com IN MX 20 secondary.server.com
POSTFIX
transport_maps = mysql:/etc/postfix
Bissio2000:
Hi all,
i'm setting postfix server as primary and mx backup as well and i'm not
using relay_domains directive.
this is my configuration:
DNS
domain.com IN MX 10 primary.server.com
domain.com IN MX 20 secondary.server.com
POSTFIX
transport_maps = mysql:/etc/postfix
* Bissio2000 bissio2...@yahoo.it:
According to the standard configuration explained at
http://www.postfix.org/STANDARD_CONFIGURATION_README.html about setting up a
primary and secondary mx, I don't understand how the mx backup returns back
all messages when the primary server come up from
36 matches
Mail list logo
