On 2023-04-18 12:49, Viktor Dukhovni via Postfix-users wrote:
On Tue, Apr 18, 2023 at 10:35:22AM +0800, tom--- via Postfix-users
wrote:
So my question is, smtp code 450 will cause the sender to retry
delivery
to secondary MX?
Yes, if the client is a legitimate MTA, less common with a junk
Note that reject_unknown_client_hostname is a very strict test that is
likely to reject legit mail. Consider using
reject_unknown_reverse_client_hostname instead.
Do you know where I can set the action code 550 for this directive?
Thanks.
___
On Tue, Apr 18, 2023 at 10:35:22AM +0800, tom--- via Postfix-users wrote:
> So my question is, smtp code 450 will cause the sender to retry delivery
> to secondary MX?
Yes, if the client is a legitimate MTA, less common with a junk-sending
botnet. Once you're confident your
, [194.33.39.17]; from= to=
proto=ESMTP helo=
I found this message was re-delivered by peer MTA to my secondary MX
quickly.
So my question is, smtp code 450 will cause the sender to retry
delivery to secondary MX?
After a 450 "defer" response, the sender is free to retry any time
message was re-delivered by peer MTA to my secondary MX
quickly.
So my question is, smtp code 450 will cause the sender to retry delivery
to secondary MX?
Thank you
Tom
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send
fh--- via Postfix-users:
>
> >
> > If I remember correctly, someone mentioned NoListing recently on that
> > list.
> > For this, you *need* a secondary MX, and it is actually your main mail
> > server - the primary MX never accepts mail...
>
> Hall
If I remember correctly, someone mentioned NoListing recently on that
list.
For this, you *need* a secondary MX, and it is actually your main mail
server - the primary MX never accepts mail...
Hallo,
1. what's the advantage of this architecture?
2. how to make primary MX not acce
considering. If you still want to
implement a secondary MX then it must have all of the same anti-spam
measures as the primary server, be just as well maintained, and
requires a lot of work to get right, all of this for a server which
will likely see little or no legitimate email traffic. My opinion
is
r served spending your time and efforts on the
> primary server.
If I remember correctly, someone mentioned NoListing recently on that list.
For this, you *need* a secondary MX, and it is actually your main mail
server - the primary MX never accepts mail...
--
Regards,
Jaroslaw Rafa
r..
Corey Hickman via Postfix-users writes:
> Hello,
>
> Since almost every sending MTA has the queues, do I need a secondary
> MX for my domain email?
>
> I am afraid the secondary MX was abused by spammers.
>
> Thanks.
I am now running secondary mx. It is valuable for me.
On 01/04/2023 08:04, Peter via Postfix-users wrote:
On 1/04/23 00:36, Corey Hickman via Postfix-users wrote:
Since almost every sending MTA has the queues, do I need a secondary
MX for my domain email?
Secondary, or backup MXes are almost never recommended in the modern
internet and tend to
On 1/04/23 00:36, Corey Hickman via Postfix-users wrote:
Since almost every sending MTA has the queues, do I need a secondary MX
for my domain email?
Secondary, or backup MXes are almost never recommended in the modern
internet and tend to be a relic of the 1990s dialup internet. What is
* Corey Hickman via Postfix-users :
> Since almost every sending MTA has the queues, do I need a secondary MX for
> my domain email?
I don't know if the RFC mandate it, but nowadays everbody knows
better, so WTF.
> I am afraid the secondary MX was abused by spammers.
Indeed.
Hello,
Since almost every sending MTA has the queues, do I need a secondary MX
for my domain email?
I am afraid the secondary MX was abused by spammers.
Thanks.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an
On Wed, 23 Nov 2022, raf wrote:
[...]
"v=spf1 mx -all" :)
[...]
I think it's more polite to use actual IP addresses so
as to eliminate a DNS lookup.
Given the flagrant abuse of includes and the like, I don't think
politeness is given much consideration; of course, that's my opinion.
--
Fre
How do I setup one secondary MX for two primary mail server? The two main ones
have different domains and settings. All three are postfix.
Thank you.
November 23, 2022, 10:07 AM, "raf" wrote:
>
> On Sun, Nov 20, 2022 at 12:04:34PM +0100, Benny Pedersen wrote:
>
> &
On Sun, Nov 20, 2022 at 12:04:34PM +0100, Benny Pedersen wrote:
> linux...@gmx.net skrev den 2022-11-20 09:49:
>
> > when secondary MX server forwards messages to primary MX, how can I
> > setup SPF policy to make them not breaking SPF?
>
> "v=spf1 mx -all"
linux...@gmx.net skrev den 2022-11-20 09:49:
when secondary MX server forwards messages to primary MX, how can I
setup SPF policy to make them not breaking SPF?
On 20.11.22 12:04, Benny Pedersen wrote:
"v=spf1 mx -all" :)
all other variants is just more verbose
Matus UHLAR
Matus UHLAR - fantomas skrev den 2022-11-20 15:31:
linux...@gmx.net skrev den 2022-11-20 09:49:
when secondary MX server forwards messages to primary MX, how can I
setup SPF policy to make them not breaking SPF?
On 20.11.22 12:04, Benny Pedersen wrote:
"v=spf1 mx -all" :)
all othe
linux...@gmx.net skrev den 2022-11-20 09:49:
when secondary MX server forwards messages to primary MX, how can I
setup SPF policy to make them not breaking SPF?
On 20.11.22 12:04, Benny Pedersen wrote:
"v=spf1 mx -all" :)
all other variants is just more verbose
By using this you
Jaroslaw Rafa skrev den 2022-11-20 11:29:
Dnia 20.11.2022 o godz. 09:49:35 linux...@gmx.net pisze:
when secondary MX server forwards messages to primary MX, how can I
setup
SPF policy to make them not breaking SPF?
Just except your secondary MX's sending IP address from SPF
linux...@gmx.net skrev den 2022-11-20 09:49:
when secondary MX server forwards messages to primary MX, how can I
setup SPF policy to make them not breaking SPF?
"v=spf1 mx -all" :)
all other variants is just more verbose
Dnia 20.11.2022 o godz. 09:49:35 linux...@gmx.net pisze:
>
> when secondary MX server forwards messages to primary MX, how can I setup
> SPF policy to make them not breaking SPF?
Just except your secondary MX's sending IP address from SPF check.
--
Regards,
Jaroslaw Rafa
r.
dear list,
when secondary MX server forwards messages to primary MX, how can I setup SPF
policy to make them not breaking SPF?
Thanks
This is a perfect example of why NOT to use Google for your first
resort
in asking questions! The linked howto is very bad, and it will make
your
new secondary MX host a spam magnet.
You are absolutely correct.
I wrongly assumed that antispam/antivirus measures was something that
everyone
On 9/15/2022 8:45 AM, I wrote:
The concept of "secondary MX" dates way back to pre-spam days. I think
it can safely be considered an outmoded idea at this point. But if you
insist on doing it, make sure that you use:
* Recipient validation
* Identical anti-spam controls on
On Wed, Sep 14 2022 at 07:10:57 PM +0800, Henrik Pang
wrote:
Hello,
Is there a guide for adding a secondary MX with postfix?
the secondary MX would forward messages to the main MX.
When the main MX was in failure, the secondary MX should hold messages
for some time.
On 9/14/2022 6:14 AM
accept mail if address
verification fails, which happens when primary MX is down, which is exactly
when we need backup MX.
On Wed, Sep 14 2022 at 07:10:57 PM +0800, Henrik Pang
wrote:
Is there a guide for adding a secondary MX with postfix?
the secondary MX would forward messages to the main MX
k Pang
wrote:
Hello,
Is there a guide for adding a secondary MX with postfix?
the secondary MX would forward messages to the main MX.
When the main MX was in failure, the secondary MX should hold
messages for some time.
Thank you.
Hello,
Is there a guide for adding a secondary MX with postfix?
the secondary MX would forward messages to the main MX.
When the main MX was in failure, the secondary MX should hold messages for
some time.
Thank you.
On Tue, Apr 26, 2022 at 08:47:22AM +0800, ミユナ (alice) wrote:
> given the case my primary MX is in USA. if I deploy a secondary MX in
> the EU, how can I setup EU MX to forward messages to the US one?
>
> using a internal MX record for destination? for instance,
> internal.domai
Hello
given the case my primary MX is in USA. if I deploy a secondary MX in
the EU, how can I setup EU MX to forward messages to the US one?
using a internal MX record for destination? for instance,
internal.domain.com points to my primary MX server, and use this MX for
routing by secondary
Hi,
If the primary send a 550, the reply is no.
Regards
> De: "Wyatt Chun"
> À: "Postfix users"
> Envoyé: Mardi 17 Mars 2020 07:37:30
> Objet: about secondary MX
> Hello
> If the primary MX server returns "mailbox full" error, will
Hello
If the primary MX server returns "mailbox full" error, will the delivery
agent try to send message to the secondary MX?
example.de.299 IN MX 10 secondary.mx.
example.de.299 IN MX 5 primary.mx.
Thank you.
G?nther J. Niederwimmer:
> The second MX shout have also dovecot and all the Mails that is clear?
No. Secondary MXes forward email to primary MXes.
If you want something else, don't call it secondary MX. That
term already has common usage.
RFC 5321
A relay SMTP server is usually th
> On Jun 6, 2019, at 6:48 AM, Günther J. Niederwimmer
> wrote:
>
> Now I like to create a secondary postfix for my system.
>
> What are the best to realize, have this two servers in sync?
>
> I have enable postscreen, all I found on Internet, is to have installed
> memcache is this correct?
>
>
Am Freitag, 7. Juni 2019, 05:10:09 CEST schrieb Durga Prasad Malyala:
> On Fri, Jun 7, 2019, 08:05 Viktor Dukhovni
>
> wrote:
> > > On Jun 6, 2019, at 6:48 AM, Günther J. Niederwimmer
> >
> > wrote:
> > > Now I like to create a secondary postfix for my system.
> > >
> > > What are the best to
Am Freitag, 7. Juni 2019, 04:21:49 CEST schrieb Viktor Dukhovni:
> > On Jun 6, 2019, at 6:48 AM, Günther J. Niederwimmer
> > wrote:
> >
> > Now I like to create a secondary postfix for my system.
> >
> > What are the best to realize, have this two servers in sync?
> >
> > I have enable postscre
On Fri, Jun 7, 2019, 08:05 Viktor Dukhovni
wrote:
>
> > On Jun 6, 2019, at 6:48 AM, Günther J. Niederwimmer
> wrote:
> >
> > Now I like to create a secondary postfix for my system.
> >
> > What are the best to realize, have this two servers in sync?
> >
> > I have enable postscreen, all I found
> On Jun 6, 2019, at 6:48 AM, Günther J. Niederwimmer wrote:
>
> Now I like to create a secondary postfix for my system.
>
> What are the best to realize, have this two servers in sync?
>
> I have enable postscreen, all I found on Internet, is to have installed
> memcache is this correct?
>
Hello,
postfix 3.4.5
i mean i have a correct running postfix server. ;-)
Now I like to create a secondary postfix for my system.
What are the best to realize, have this two servers in sync?
I have enable postscreen, all I found on Internet, is to have installed
memcache is this correct?
But
Wietse:
> Tricks with MX-priority spamtraps share the problem that they make
> assumptions about the behavior of all legitimate MTAs.
> For a related approach, see, for example, "nolisting".
Daniel Miller:
> Do I infer from that MX-priority spamtraps are a Bad Idea - at least in
> the real world?
On Wed, Sep 10, 2014 at 10:55:47AM -0700, Daniel Miller wrote:
> Temporarily at least I'll drop the secondaries from my DNS and see if it
> helps - but I still think there's something broken on their end. I just
> don't know how to express it properly beyond, "it's wrong, and it's on your
> end".
, which means I have
a pair of secondary MX records below my primary which accept anything
they get - and those get used to build DNS blacklists. Properly
configured hosts talk to my primary server without issue. The only
question here is - does anyone have an objection to what I'm doing with
t
On 9/10/2014 10:24 AM, Viktor Dukhovni wrote:
If your system ever responds with a 4XX, retries will hit the
secondaries. You need to at least exclude clients that first tried the
primary and tempfailed. However, transient connection or DNS problems
can also cause a legitimate client to skip the
Daniel Miller:
> This question is actually two questions - neither of which are
> Postfix-specific but email-generic - but this list is the best resource
> I have to ask such questions.
>
> First - I've been contributing to "Project Tarbaby", which means I have
&g
t;Project Tarbaby", which means I have a
> pair of secondary MX records below my primary which accept anything they get
> - and those get used to build DNS blacklists. Properly configured hosts talk
> to my primary server without issue. The only question here is - does anyone
> hav
This question is actually two questions - neither of which are
Postfix-specific but email-generic - but this list is the best resource
I have to ask such questions.
First - I've been contributing to "Project Tarbaby", which means I have
a pair of secondary MX records below m
s happen all the time in different
parts of the Internet.
As the result of outages in intermediate networks, the primary MX
server will be reachable for most clients but unreachable for others.
Therefore, the secondary MX server will see legitimate connections
while the primary MX server is up.
Se
ce on what to use or where to start
reading, I would appreciate it.
And yes, sorry for the subject line yet again... It seems that secondary
MX server might be a better description?
--
John Hinton
877-777-1407 ext 502
http://www.ew3d.com
Comprehensive Online Solutions
Den 2012-07-13 10:46, Ramesh skrev:
Is it possible configuring webmail access to secondary MX, so that
when primary is down, users can access webmail.
this is only possible with 2 master mta, not with an secondary mx,
webmail is not part of postfix problem
2 diff main mta can deliver to
Am 13.07.2012 10:46, schrieb Ramesh:
> Hi Robert,
>
> Is it possible configuring webmail access to secondary MX, so that when
> primary is down, users can access webmail.
> please let me any info need about our setup.
>
> -Ramesh
classic webmail has to look in a mailbox
Hi Robert,
Is it possible configuring webmail access to secondary MX, so that when primary
is down, users can access webmail.
please let me any info need about our setup.
-Ramesh
From: Robert Schetterer
To: postfix-users@postfix.org
Sent: Friday, 13 July
Am 13.07.2012 08:54, schrieb Ramesh:
>
> Hi All,
>
> We have primary and secondary MX configured, when primary is down all
> messages queued at secondary.
> Is there any method we can access messages from secondary MX queue,
> b'coz sometimes primary is down more th
Hi All,
We have primary and secondary MX configured, when primary is down all messages
queued at secondary.
Is there any method we can access messages from secondary MX queue, b'coz
sometimes primary is down more than down time, due to fiber issues at ISP end.
Please let me know h
Le Fri 2/12/2011, Ken D'Ambrosio disait
> Hey, all. I've got a primary -- my actual destination/IMAP server -- and, for
> various reasons, a secondary SMTP server. My primary only rejects mail to
> invalid recipients (spam is dealt with internally). I'd like my secondary to
> reject invalid rec
Am 02.12.2011 23:02, schrieb Ken D'Ambrosio:
> Hey, all. I've got a primary -- my actual destination/IMAP server -- and, for
> various reasons, a secondary SMTP server. My primary only rejects mail to
> invalid recipients (spam is dealt with internally). I'd like my secondary to
> reject invalid
Hey, all. I've got a primary -- my actual destination/IMAP server -- and, for
various reasons, a secondary SMTP server. My primary only rejects mail to
invalid recipients (spam is dealt with internally). I'd like my secondary to
reject invalid recipients, also. I can bring over /etc/aliases and
On Monday 21 September 2009 20:49:05 Justin C. Le Grice wrote:
> Here is my question, How can I modify my workarounds.org setup so
> I can verify and cache email addresses from the clients email
> server when visible? I want to cache them for the rare occasions
> when the clients email server is no
I've looked and I've googled but cannot find a straight answer or HowTo!
I can find plenty of options to create lists of known email addresses
locally but this is not exactly what I want.
I am looking to be a relay host or secondary MX for a couple of my clients.
I have my Postfix
and googling have not been very
>successful.
>
Not exactly the question you asked, but if you are using one of the policy
servers from http://www.openspf.org/Software , both provide their own mechanism
for bypassing SPF checks for specific relays (like secondary MX).
The Python implementation pr
d server as
>> the issuer.
>
> Add your secondary MX to mynetworks.
Generally, "mynetworks" also grants "relay" rights, which violates least
privilege. So I would use a separate "whitelist" that is invoked just
after "reject_unauth_destination" and befo
he mail is transfered from my backup MX
to my master server and my server is considering that second server as
the issuer.
Add your secondary MX to mynetworks.
You shouldn't ever reject mail already accepted by your
secondary. To facilitate that, your secondary must have as
strict or strict
Hello,
I am using two postfix server and quite often some misconfigured mail
server are sending mail to the backup MX instead of the primary.
Both server have postfix implemented using the 'classic' conf:
in main.cf
smtpd_recipient_restrictions =
permit_mynetworks,
per
ry-status;
> boundary="9B095B5ADSN=_01C9A571EDB220B262B8webmail.int.i"
> X-DSNContext: 335a7efd - 4523 - 0001 - 80040546
> Message-ID:
> Subject: Delivery Status Notification (Failure)
>
>
> Pretty much what I expect.
>
> But let's say I set up my postfix m
let's say I set up my postfix mail server with the changes discussed
above and telnet into it (don't feel like updating DNS for a secondary MX).
Mail sent to a valid address works just fine (yay!).
When I send mail to my domain with an invalid address, again, I get a
bounceback, but it
post...@corwyn.net wrote:
At 11:40 AM 5/19/2009, Noel Jones wrote:
Add an entry to /etc/postfix/relay_recipients:
@the.backed-up.domain.tld x
Technically correct, but unwise.
You must validate recipients for the backed-up domain.
why "must"?
Won't the mail just be forwarded to the primary m
On Tue, May 19, 2009 at 1:07 PM, wrote:
> At 11:40 AM 5/19/2009, Noel Jones wrote:
>>>
>>> Add an entry to /etc/postfix/relay_recipients:
>>> @the.backed-up.domain.tld x
>>
>> Technically correct, but unwise.
>> You must validate recipients for the backed-up domain.
>
> why "must"?
>
> Won't the
At 11:40 AM 5/19/2009, Noel Jones wrote:
Add an entry to /etc/postfix/relay_recipients:
@the.backed-up.domain.tld x
Technically correct, but unwise.
You must validate recipients for the backed-up domain.
why "must"?
Won't the mail just be forwarded to the primary mail server, who can
reject
post...@corwyn.net wrote:
I have a postfix mail server (postfix-2.3.3-2.1.centos.mysql_pgsql)
hosting 20-30 virtual domains on mysql.
Now I find myself with the need to make that server also the secondary
MX for another specific domain that I was for all users.
If I understand the steps
I have a postfix mail server (postfix-2.3.3-2.1.centos.mysql_pgsql)
hosting 20-30 virtual domains on mysql.
Now I find myself with the need to make that server also the
secondary MX for another specific domain that I was for all users.
If I understand the steps correctly (from
http
Santiago Romero wrote:
Now I have a nice hash file with all the valid accounts, but ...
How do I deal in a relay_recipient_maps file with qmail's mailing
list addresses?
How does qmail know that an address is valid or not? If a Postfix
maptype can be invented that reads that type of
Now I have a nice hash file with all the valid accounts, but ...
How do I deal in a relay_recipient_maps file with qmail's mailing list
addresses?
How does qmail know that an address is valid or not? If a Postfix
maptype can be invented that reads that type of file, then it could
be q
Santiago Romero:
> Now I have a nice hash file with all the valid accounts, but ...
>
> How do I deal in a relay_recipient_maps file with qmail's mailing list
> addresses?
How does qmail know that an address is valid or not? If a Postfix
maptype can be invented that reads that type of file, th
The list if valid recipients in those domains is specified in
relay_recipient_maps. Specify one or more map files listing the valid
recipients; all other recipients are rejected.
http://www.postfix.org/postconf.5.html#relay_recipient_maps
If this file is scp'ed as a plain text file, you wil
Santiago Romero wrote:
Postfix calls domains that it accepts mail for but delivers elsewhere
(such as MX backups) relay_domains. You can use a plain text file or
any supported postfix map type.
The list if valid recipients in those domains is specified in
relay_recipient_maps. Specify one
Postfix calls domains that it accepts mail for but delivers elsewhere
(such as MX backups) relay_domains. You can use a plain text file or
any supported postfix map type.
The list if valid recipients in those domains is specified in
relay_recipient_maps. Specify one or more map files listi
Santiago Romero wrote:
To summarize it, currently I have 2 files called:
valid_accounts.txt: a list of valid accounts in the primary MX.
domains_to_check_user.txt: Holds a list of domains. Server only checks
RCPT against valid_accounts.txt for the domains present in this file.
When a new emai
On Mon, Feb 23, 2009 at 05:01:09PM CET, Santiago Romero
said:
>
> Hi.
>
> I have a secondary MX server with qmail that I'm migrating to postfix.
> Currently, my qmail server checks RCPT TO addresses against a plain text
> file that contains all the valid email a
Hi.
I have a secondary MX server with qmail that I'm migrating to postfix.
Currently, my qmail server checks RCPT TO addresses against a plain text
file that contains all the valid email accounts for some of the domains
that is making MX-backup for. That "plain-text" file is
80 matches
Mail list logo
