Wesley via Postfix-users:
> Hello
>
> I have a question about forwarding email to Gmail. Gmail requires the
> sender to provide identity authentication, including SPF or DKIM. Some
> of our old customers do not have dkim configured in their email system,
> bu
Hello
I have a question about forwarding email to Gmail. Gmail requires the
sender to provide identity authentication, including SPF or DKIM. Some
of our old customers do not have dkim configured in their email system,
but they do have spf. There is no problem sending messages directly
On 28/07/24 17:58, Walt E via Postfix-users wrote:
Is there any standard that, postmaster@domain is a required account for this
domain?
I asked this is b/c one of our domains has millions of users, and a people
registered the postmaster account (surely it's due to our mistake in work) with
On Sun, Jul 28, 2024 at 10:03:05AM +0200, Ralph Seichter via Postfix-users
wrote:
* Walt E. via Postfix-users:
Is there any standard that, postmaster@domain is a required account
for this domain?
Yes. The requirement has been specified as early as 1981 in RFC 822, and
in its successors up to
* A. Schulze via Postfix-users:
> https://datatracker.ietf.org/doc/html/rfc5321#section-4.5.1
>
> 5321 btw...
Indeed, that was an unfortunate typo on my end. Thanks, Andreas.
-Ralph
___
Postfix-users mailing list -- postfix-users@postfix.org
To
On Sun, Jul 28, 2024 at 10:03:05AM +0200, Ralph Seichter via Postfix-users
wrote:
> * Walt E. via Postfix-users:
>
> > Is there any standard that, postmaster@domain is a required account
> > for this domain?
>
> Yes. The requirement has been specified as early as 1981 in RFC 822, and
> in its
Am 28.07.24 um 10:03 schrieb Ralph Seichter via Postfix-users:
Yes. The requirement has been specified as early as 1981 in RFC 822, and
in its successors up to and including RFC 5322.
https://datatracker.ietf.org/doc/html/rfc5321#section-4.5.1
5321 btw...
Andreas
* Walt E. via Postfix-users:
> Is there any standard that, postmaster@domain is a required account
> for this domain?
Yes. The requirement has been specified as early as 1981 in RFC 822, and
in its successors up to and including RFC 5322.
-Ralph
___
Is there any standard that, postmaster@domain is a required account for this
domain?
I asked this is b/c one of our domains has millions of users, and a people
registered the postmaster account (surely it's due to our mistake in work) with
that domain as his personal email.
Our lawyer
On 2024-07-25 11:15, Corey H via Postfix-users wrote:
So, relayhost = mail.example.net without '[]' will lookup MX records
for mail.example.net?
On 25.07.24 15:40, Corey H via Postfix-users wrote:
OK I got the idea.
when sending email to u...@foo.com, and relayhost = [mail.example.net],
this
On 2024-07-25 11:15, Corey H via Postfix-users wrote:
So, relayhost = mail.example.net without '[]' will lookup MX records
for mail.example.net?
Thanks.
OK I got the idea.
when sending email to u...@foo.com, and relayhost = [mail.example.net],
this postfix won't lookup MX records for
So, relayhost = mail.example.net without '[]' will lookup MX records for
mail.example.net?
Thanks.
On 2024-07-25 11:12, Serhii via Postfix-users wrote:
From postfix docs: "The form [hostname] turns off MX or SRV lookups."
https://www.postfix.org/postconf.5.html#relayhost
On 7/25/24 09:09,
* Corey H via Postfix-users [25/07/2024 11:09] :
>
> relayhost = [mail.example.net]:587
> but what does this mean with '[]' and hostname in it?
>From the documentation[1]:
"The form [hostname] turns off MX or SRV lookups."
Emmanuel
1: https://www.postfix.org/postconf.5.html#relayhost
From postfix docs: "The form [hostname] turns off MX or SRV lookups."
https://www.postfix.org/postconf.5.html#relayhost
On 7/25/24 09:09, Corey H via Postfix-users wrote:
Hi list,
I saw this configuration in my company's postfix.
relayhost = [mail.example.net]:587
Generally I would write it
Hi list,
I saw this configuration in my company's postfix.
relayhost = [mail.example.net]:587
Generally I would write it as:
relayhost = 1.2.3.4
but what does this mean with '[]' and hostname in it?
Thanks.
___
Postfix-users mailing list --
One of my customers in HK want to send bulk messages to local users
> > > (about 500/day).
> > > I plan to setup a separated sending out server in HongKong for him.
> > > my question is how to route messages for a specific account to a
> > > specific postf
On 10/07/2024 10:33, Phil Biggs via Postfix-users wrote:
Wednesday, July 10, 2024, 8:59:57 AM, Jeff Pang via Postfix-users wrote:
Hello experts,
One of my customers in HK want to send bulk messages to local users
(about 500/day).
I plan to setup a separated sending out server in HongKong
Wednesday, July 10, 2024, 8:59:57 AM, Jeff Pang via Postfix-users wrote:
> Hello experts,
> One of my customers in HK want to send bulk messages to local users
> (about 500/day).
> I plan to setup a separated sending out server in HongKong for him.
> my question is how to
Hello experts,
One of my customers in HK want to send bulk messages to local users
(about 500/day).
I plan to setup a separated sending out server in HongKong for him.
my question is how to route messages for a specific account to a
specific postfix server to send out?
Thanks in advance
I will order one as well.
Here's a link to the web site where you can order it:
https://www.tiltedwindmillpress.com/product/ryoms-preorder/
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to
Wednesday, July 3, 2024, 8:03:38 AM, Jean-François Bachelet via Postfix-users
wrote:
> Hello folks ^^)
> There was a new Postfix book in the writing announced on the list, is it
> finished and where to find/buy it ?
> Thanks by advance :)
> Cheers,
> Jeff
>
Hello folks ^^)
There was a new Postfix book in the writing announced on the list, is it
finished and where to find/buy it ?
Thanks by advance :)
Cheers,
Jeff
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email
On 2024-05-30 at 02:23:45 UTC-0400 (Thu, 30 May 2024 08:23:45 +0200)
Matus UHLAR - fantomas via Postfix-users
is rumored to have said:
AFAIK mailman2 does this as hardcoded behaviour, if the sender's
domain has DMARC policy different than "none".
No, it is configurable. Mailman v2 predates
Hello the list,
I saw some open source providers who have these dmarc settings:
_dmarc.disroot.org. 3495 IN TXT "v=DMARC1; p=reject; adkim=s; aspf=s;
rua=mailto:ab...@disroot.org; ruf=mailto:ab...@disroot.org;;
_dmarc.autistici.org. 3504 IN TXT "v=DMARC1; p=reject; adkim=s; aspf=s;
Wietse Venema via Postfix-users wrote in
<4vvgyx1yynzj...@spike.porcupine.org>:
|Wietse Venema via Postfix-users:
|> Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests
|> thts from Postfix. Just need to figure out how to enable/disable
|> this particular command based on the
Wietse Venema via Postfix-users:
> Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests
> thts from Postfix. Just need to figure out how to enable/disable
> this particular command based on the Postfix and Milter protocol
> versions. There is already some 'set' intersection code
On Fri, 8 Mar 2024 at 05:52, Stephen Satchell via Postfix-users
wrote:
>
> Assuming that one's configuration has open relay, what does a log entry
> for relayed mail look like?
I think you really need to look at multiple log entries to discover that, e.g.
Mar 13 16:21:06 mail-4
On Sat, Mar 09, 2024 at 12:58:38PM -0500, Wietse Venema via Postfix-users wrote:
> Viktor Dukhovni via Postfix-users:
> > On Sat, Mar 09, 2024 at 12:49:42PM +0100, Matus UHLAR - fantomas via
> > Postfix-users wrote:
> >
> > > In case of domains in relay_domains, the command could be even
> > >
Viktor Dukhovni via Postfix-users:
> On Sat, Mar 09, 2024 at 12:49:42PM +0100, Matus UHLAR - fantomas via
> Postfix-users wrote:
>
> > In case of domains in relay_domains, the command could be even
> > postfix/relay, so one needs to exclude that one as well.
>
> Actually, no, the "relay"
On Sat, Mar 09, 2024 at 12:49:42PM +0100, Matus UHLAR - fantomas via
Postfix-users wrote:
> In case of domains in relay_domains, the command could be even
> postfix/relay, so one needs to exclude that one as well.
Actually, no, the "relay" transport is implemented by the smtp(8)
delivery agent,
Stephen Satchell via Postfix-users skrev den 2024-03-08 06:52:
grep relay= mail.log | grep -v relay=local
I can then use the message ID to get all the log information for
each questioned transaction.
Am I on the right road? Please disabuse me of any incorrect notions.
On 08.03.24 12:47,
Stephen Satchell via Postfix-users:
> Assuming that one's configuration has open relay, what does a log entry
> for relayed mail look like?
>
> I don't think I've any open relay, but I want to look and make sure.
>
> I've searched for half an hour, and no answer came up. But, I did find
>
Stephen Satchell via Postfix-users skrev den 2024-03-08 06:52:
grep relay= mail.log | grep -v relay=local
I can then use the message ID to get all the log information for each
questioned transaction.
Am I on the right road? Please disabuse me of any incorrect notions.
is it not grep -i
On 07.03.24 21:52, Stephen Satchell via Postfix-users wrote:
Assuming that one's configuration has open relay, what does a log
entry for relayed mail look like?
It looks like any other mail, just it was received without authentication,
from unstrusted clients and sent to remote (not in
Assuming that one's configuration has open relay, what does a log entry
for relayed mail look like?
I don't think I've any open relay, but I want to look and make sure.
I've searched for half an hour, and no answer came up. But, I did find
some hints. Specifically, I use this command to
Wietse Venema via Postfix-users:
> John Levine via Postfix-users:
> > I am trying to tidy up a complicated and messy postfix config that has
> > all the issues you'd expect in one that has been twiddled by many
> > people over a decade to handle multiple sort of related mail streams.
>
> Auch.
>
John Levine via Postfix-users:
> I am trying to tidy up a complicated and messy postfix config that has
> all the issues you'd expect in one that has been twiddled by many
> people over a decade to handle multiple sort of related mail streams.
Auch.
> Today's issue is ensuring that we only do
I am trying to tidy up a complicated and messy postfix config that has
all the issues you'd expect in one that has been twiddled by many
people over a decade to handle multiple sort of related mail streams.
Today's issue is ensuring that we only do submission rewrites on
outgoing mail, not
Wietse Venema via Postfix-users wrote in
<4tqkyr4p2zzj...@spike.porcupine.org>:
|Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests
|thts from Postfix. Just need to figure out how to enable/disable
|this particular command based on the Postfix and Milter protocol
|versions.
FYI: the libmilter interface is an internal communication protocol.
It is NOT publically documented on purpose (hence complaining about
missing documentation is somehow annoying).
--
Please don't Cc: me, use only the list for replies.
___
Postfix-users
Looks like there is sufficient basis to make SMTPD_QUIT_NC rerquests
thts from Postfix. Just need to figure out how to enable/disable
this particular command based on the Postfix and Milter protocol
versions. There is already some 'set' intersection code for doing
such things on the Postfix side.
ntly
informative for reverse engineering. :-)
But it really is sad. 20+ years ago there were really good HOWTOs
in the Linux world, not to talk about all those papers/ and the
historical BSD PSD and USD documentation series. And their manual
pages. (Today the Linux ones are pretty good, though.) And
Steffen Nurpmeso via Postfix-users:
> Wietse Venema via Postfix-users wrote in
> <4tqc213rcwzj...@spike.porcupine.org>:
> |So you're suggesting that as long as an MTA-to Milter connection
> |is not in an error state, sending
> |
> |SMFIC_QUIT_NC
> |
> |and later sending
> |
> |
Steffen Nurpmeso wrote in
<20240131203248.XtHi_6Do@steffen%sdaoden.eu>:
|Wietse Venema via Postfix-users wrote in
| <4tqc213rcwzj...@spike.porcupine.org>:
||So you're suggesting that as long as an MTA-to Milter connection
||is not in an error state, sending
||
||SMFIC_QUIT_NC
||
Wietse Venema via Postfix-users wrote in
<4tqc213rcwzj...@spike.porcupine.org>:
|So you're suggesting that as long as an MTA-to Milter connection
|is not in an error state, sending
|
|SMFIC_QUIT_NC
|
|and later sending
|
|SMTIC_CONNECT
|
|are sufficient to make a Milter fully
So you're suggesting that as long as an MTA-to Milter connection
is not in an error state, sending
SMFIC_QUIT_NC
and later sending
SMTIC_CONNECT
are sufficient to make a Milter fully forget a past SMTP session and
to make it ready to handle events from a new SMTP session?
I'd like
Wietse Venema via Postfix-users wrote in
<4tq7t76ypkzj...@spike.porcupine.org>:
|Claus Assmann via Postfix-users:
|>> SMFIP_NOQUIT would
|>> be a good protocol extension in general
|>
|> "Use the source, Luke."
|>
|> You mean something like
|> SMFIC_QUIT_NC
|> ?
|
|And... Postfix
postfix-users@postfix.org wrote in
<20240131155624.ga51...@veps.esmtp.org>:
|> SMFIP_NOQUIT would
|> be a good protocol extension in general
|
|"Use the source, Luke."
|
|You mean something like
|SMFIC_QUIT_NC
|?
I did, i have that symbol (like MDS256..), yes. So maybe, yes.
This is
On Wed, Jan 31, 2024 at 12:13:51PM -0500, Wietse Venema via Postfix-users wrote:
> - The MTA then needs to keep the Milter connection open while watting
> for new work. Once there is work, the MTA sends SMFIC_CONNECT and
> so on.
>
> - This sounds like the MTA needs a Milter connection cache
Claus Assmann via Postfix-users:
> > SMFIP_NOQUIT would
> > be a good protocol extension in general
>
> "Use the source, Luke."
>
> You mean something like
> SMFIC_QUIT_NC
> ?
And... Postfix 'knows' that constant since postfix-2.5.0, but there
is no code to negotiate or send it.
What would
> SMFIP_NOQUIT would
> be a good protocol extension in general
"Use the source, Luke."
You mean something like
SMFIC_QUIT_NC
?
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
Wietse Venema via Postfix-users wrote in
<4tpmnz1dqyzj...@spike.porcupine.org>:
|Postfix has to be compatible with libmilter, the reference
|implementation from Sendmail. It absolutely makes no sends for me
|to unilaterally add features. If you wish to propose libmilter API
|changes, such as
Postfix has to be compatible with libmilter, the reference
implementation from Sendmail. It absolutely makes no sends for me
to unilaterally add features. If you wish to propose libmilter API
changes, such as claimng a code, then this mailing list is not the
place to do that.
Claus Assmann is on
f
successive emails. And i do see (at least the macros of, mind
you) SMFIC_CONNECT etc, do i.
And then, you know, i am so happy about your spawn(8), it drives
my s-postgray for two years without just any problems, and given
how long the specific postfix-daemon/spawn/s-postgray program
tuple lives
As you have apparently now learned, there is a big difference between the
sendmail package and the postfix sendmail command (which exists for
compatibility reasons and is part of Postfix so no need to try to install it
independently).
--
Larry Stone
lston...@stonejongleux.com
> On Jan
(Sorry if this doesn't show up in the right thread, but these
problems actually caused me to lose the mail sent to me last
night, so I'm responding to what I see in the mailing list
archive.)
All of my problems seem to have come from this original sin:
yum install ... postfix sendmail ...
Don Cohen via Postfix-users:
> I see in maillog something like this:
>
> Jan 17 22:22:50 isis-20240117-1030 sendmail[120557]: 40HMMokm120557: to=don,
> ctladdr=opc (1000/1000), delay=00:00:00, xdelay=00:00:00, mailer=relay,
> pri=30107, relay=[127.0.0.1] [127.0.0.1], dsn=5.0.0, reply=554- ,
>
127.0.0.1], dsn=5.0.0, reply=554- ,
> stat=Service unavailable
The above,
> vs the old:
>
> Jan 19 00:20:10 losangelesyouthorchestra postfix/pickup[18701]: 988894075B:
> uid=0 from=
Plus this above line
>
> Also, can someone tell me that the (8.16.1/8.16.1/Submit) is all
18 Jan 2024 16:38:51 + (UTC)
This gives me the impression that the new path is really two hops while
the old path was only one.
Also, can someone tell me that the (8.16.1/8.16.1/Submit) is all about?
Thanks, and sorry for so many questions.
___
Pos
On 2023-11-02 at 04:49:37 UTC-0400 (Thu, 02 Nov 2023 10:49:37 +0200)
Ivan Ionut via Postfix-users
is rumored to have said:
Hi, it's possible that postscreen does not block the email when
postscreen_dnsbl_threshold is reached but to pass that email to
spamassassin(with a score and a tag).
* Matus UHLAR - fantomas via Postfix-users :
> > And thus the solution is: Don't use the dnsbl in postscreen, but ONLY
> > in spamassassin/rspamd instead.
>
> No problem, you can safely use postscreen with multiple DNSBLs and DNSWLs.
> - just don't rely on single hit, unless it's your own DNSBL.
On 02.11.23 10:49, Ivan Ionut via Postfix-users wrote:
> Hi, it's possible that postscreen does not block the email when
> postscreen_dnsbl_threshold is reached but to pass that email to
> spamassassin(with a score and a tag).
* Matus UHLAR - fantomas via Postfix-users :
Postscreen does not
* Matus UHLAR - fantomas via Postfix-users :
> On 02.11.23 10:49, Ivan Ionut via Postfix-users wrote:
> > Hi, it's possible that postscreen does not block the email when
> > postscreen_dnsbl_threshold is reached but to pass that email to
> > spamassassin(with a score and a tag).
>
> Postscreen
On 02.11.23 10:49, Ivan Ionut via Postfix-users wrote:
Hi, it's possible that postscreen does not block the email when
postscreen_dnsbl_threshold is reached but to pass that email to
spamassassin(with a score and a tag).
Postscreen does not tag. It passes or blocks the mail.
--
Matus UHLAR
Hi, it's possible that postscreen does not block the email when
postscreen_dnsbl_threshold is reached but to pass that email to
spamassassin(with a score and a tag).
--
Ivan Ionuț
Str. Mircea cel Bătrân nr 1, Galati 800023
Tel/Fax: +40236 493277
Email: ivan.io...@tehnopol-gl.ro
_The
Ivan Ionut:
> Thx, but I noticed that there is only for cidr...and i want for
> hosts/domains too.
If you want client name/domain based policies, don't use postscreen,
use smtpd_mumble_restrictions instead.
An smtpd process can do complex things such as verifying fully-confirmed
Ivan Ionut via Postfix-users:
>
> Hi, I'm using postscreen_dnsbl_sites to block some spam and I want some
> domain/hosts/ip to bypass this option, like an whitelist.
>
> Does postscreen/postfix has this option?
>
Yes. Near the top of https://www.postfix.org/POSTSCREEN_README.html#quick
Quick
Hi, I'm using postscreen_dnsbl_sites to block some spam and I want some
domain/hosts/ip to bypass this option, like an whitelist.
Does postscreen/postfix has this option?
p.s. my postfix version: 3.6.4
--
Ivan Ionuț
Str. Mircea cel Bătrân nr 1, Galati 800023
Tel/Fax: +40236 493277
Hi,
I use OpenDMARC and I have it sending failure reports
with "FailureReports true". Unfortunately, one organisation
that sends me emails has a bug in their SPF record, and they
no longer have the postmaster@ email address needed to receive
DMARC reports, and I'm not sure that they know how to
Hello
Just FYI,
After simple putting this line into postfix's main.cf:
recipient_delimiter = +
And reload postfix, the plus alias address should work.
I am using dovecot LMTP as delivery agent. Nothing changes to dovecot
configuration.
Here are the versions:
Postfix 3.6.4
Dovecot 2.3.16
On 20 Apr 2023 10:03, Matus UHLAR - fantomas via Postfix-users wrote:
On 20.04.23 09:25, Silamael Darkomen via Postfix-users wrote:
I have a question about the automatic adding of missing headers.
Did an experiment with always_add_missing_headers = no.
I sent a mail via telnet manually
On 20.04.23 09:25, Silamael Darkomen via Postfix-users wrote:
I have a question about the automatic adding of missing headers.
Did an experiment with always_add_missing_headers = no.
I sent a mail via telnet manually to postfix and checked, what it's
forwarding to the next mail server
Hello,
I have a question about the automatic adding of missing headers.
Did an experiment with always_add_missing_headers = no.
I sent a mail via telnet manually to postfix and checked, what it's
forwarding to the next mail server.
According to the tcpdump output, a missing Date header seems
gt; entirely of 7-bit octets (i.e. still 8-bit octets, but in the range
> > 0–127). Similarly, the "8bit" transfer encoding is also an "identity"
> > encoding, which makes no promise about the high bit of the content.
>
> (1) With testing (sent from roundcube, read f
And there is a discussion on stackoverflow:
https://stackoverflow.com/questions/25710599/content-transfer-encoding-7bit-or-8-bit
regards.
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to
ng is also an "identity"
encoding, which makes no promise about the high bit of the content.
(1) With testing (sent from roundcube, read from gmail) I found that:
X-Sender: t...@myposts.ovh
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
两鬓可怜青，只为
transfer encoding is also an "identity"
encoding, which makes no promise about the high bit of the content.
--
Viktor.
P.S. I used in a "ndash" in the above, so the content is not all ASCII.
___
Postfix-users mailing list --
tom--- via Postfix-users skrev den 2023-04-08 14:57:
If message has image included, or has UTF8 chars, is base64 encoding
must be used? Thank you again.
utf-8 is 7bit, so no
The same is true for HTML entries, many news mails have utf8 and
qoutedprintble, and always its HTML, hmm:)
there is
If message has image included, or has UTF8 chars, is base64 encoding
must be used? Thank you again.
On 2023-04-08 19:58, Wietse Venema via Postfix-users wrote:
tom--- via Postfix-users:
Hello,
1. use MIME encoding for 8bit chars
I suppose you mean that you encode message header or boody
tom--- via Postfix-users:
> Hello,
>
> 1. use MIME encoding for 8bit chars
I suppose you mean that you encode message header or boody content
using Base64 or Quoted-Printable.
> 2. Content-Transfer-Encoding: 7bit
Both base64 and quoted-printable are 7-bit transfer encodings.
> Do they mean
Hello,
1. use MIME encoding for 8bit chars
2. Content-Transfer-Encoding: 7bit
Do they mean the same stuff?
Should I use 8bit encoding, or 7bit? If I am composing the Chinese
message.
Thank you.
Tom Reed
___
Postfix-users mailing list --
On 10.03.23 19:25, pyh--- via Postfix-users wrote:
I am running a postfix server for email forwarding.
Should I enable openSRS for this forwarding service?
if you want to forward mail and also allow users to do that, you apparently
should do SRS. Otherwise forwarding destination can reject
* { font-size: 13px; font-family: 'MS Pゴシック', sans-serif;}p, ul, ol, blockquote
{ margin: 0;}a { color: #0064c8; text-decoration: none;}a:hover { color:
#0057af; text-decoration: underline;}a:active { color: #004c98;}
Hello,
I am running a postfix server for email forwarding.
Should I
On 2023-02-28 at 05:13:04 UTC-0500 (Tue, 28 Feb 2023 11:13:04 +0100)
natan
is rumored to have said:
Hi
Is there any rfc about having to use or regarding the need to use
"sender login mismatch";
No. It is very rare for any RFC to make authorization policy
recommendations.
--
B
On 28.02.23 11:13, natan wrote:
Is there any rfc about having to use or regarding the need to use
"sender login mismatch";
I don't know of such RFC.
It's mail server policy question - whatever policy you set up and enforce.
Many senders require everyone only to send mail from thei
Hi
Is there any rfc about having to use or regarding the need to use
"sender login mismatch";
This is just a loose question
I know that everything depends on the administrator and you don't have
to impose anything
--
winnie hw skrev den 2023-02-25 00:44:
> Thanks. I have setup these two options in main.cf
>
> maximal_queue_lifetime = 1d
> bounce_queue_lifetime = 1d
On Sat, Feb 25, 2023 at 7:40 PM Benny Pedersen wrote:
and now logs that shows the problem ?
postfix have over 900 lines of default well
winnie hw skrev den 2023-02-26 02:15:
I am trying to resolve the problem when an undelivered message stays
in queue too long, then the sender can't know this so they ask me why
the sent message can't be gotten by others. any better solution?
if postfix dont know local recipients then it will
I am trying to resolve the problem when an undelivered message stays in
queue too long, then the sender can't know this so they ask me why the sent
message can't be gotten by others. any better solution?
Thanks.
On Sat, Feb 25, 2023 at 7:40 PM Benny Pedersen wrote:
> winnie hw skrev den
Matus UHLAR - fantomas skrev den 2023-02-25 11:45:
On 25.02.23 07:44, winnie hw wrote:
Thanks. I have setup these two options in main.cf,
maximal_queue_lifetime = 1d
bounce_queue_lifetime = 1d
delay_warning_time is NOT bounce_queue_lifetime
+1, now 3 lines of non default settings without
winnie hw skrev den 2023-02-25 00:44:
Thanks. I have setup these two options in main.cf
maximal_queue_lifetime = 1d
bounce_queue_lifetime = 1d
and now logs that shows the problem ?
postfix have over 900 lines of default well choiced default settings,
you choiced to change 2 of them without
On 25.02.23 07:44, winnie hw wrote:
Thanks. I have setup these two options in main.cf,
maximal_queue_lifetime = 1d
bounce_queue_lifetime = 1d
delay_warning_time is NOT bounce_queue_lifetime
On Fri, Feb 24, 2023 at 9:28 PM Matus UHLAR - fantomas
wrote:
On 24.02.23 20:45, winnie hw wrote:
Thanks. I have setup these two options in main.cf,
maximal_queue_lifetime = 1d
bounce_queue_lifetime = 1d
On Fri, Feb 24, 2023 at 9:28 PM Matus UHLAR - fantomas
wrote:
> On 24.02.23 20:45, winnie hw wrote:
> >When the peer MTA can't accept messages, my local postfix will retry
> >delivery
On 24.02.23 20:45, winnie hw wrote:
When the peer MTA can't accept messages, my local postfix will retry
delivery for a few days.
My question is,
1) how can I shorten the retry time?
http://www.postfix.org/postconf.5.html#maximal_queue_lifetime
2) when the first delivery fails, I want to
Hello list,
When the peer MTA can't accept messages, my local postfix will retry
delivery for a few days.
My question is,
1) how can I shorten the retry time?
2) when the first delivery fails, I want to notify the sender user, how to
do it?
Thanks.
To forward mail from a primary DNS MX host to a system that is not
a DNS MX host,
https://www.postfix.org/STANDARD_CONFIGURATION_README.html#backup
Wietse
Thanks so very much; this is great.
~c
--
Charlie Derr Director of Instructional Technology
Bard College at Simon's Rock
charlie derr:
> Pretty sure this is a transport map invocation which is needed.
>
> Our situation is that we have a server a.example.com which is receiving
> email for the entire example.com domain. What we wish to do is to have
> any email that is directed to an example.com email address *not*
Pretty sure this is a transport map invocation which is needed.
Our situation is that we have a server a.example.com which is receiving
email for the entire example.com domain. What we wish to do is to have
any email that is directed to an example.com email address *not* be sent
to the IP
After some delay, I have verified that postscreen_dnsbl_sites works
as promised: it adds up the scores from all matching patterns.
This verification required some infrastructure to test postscreen's
scoring code outside of postscreen. I have written a half-dozen
tests to ensure that future
On 30.05.22 14:02, Peter wrote:
Next question: What happens if zen returns multiple responses:
127.0.0.10
127.0.0.3
postscreen_dnsbl_sites = zen.spamhaus.org=127.0.0.[1..2]*3
zen.spamhaus.org=127.0.0.3*2
zen.spamhaus.org=127.0.0.[4..255]*3
On 30.05.22 10:06, Matus UHLAR - fantomas wrote:
1 - 100 of 1366 matches
Mail list logo
