On Fri, Jun 21, 2024 at 16:22:24 -0400, Wietse Venema wrote:
> Locally-generated bounces are generated by the Postfix bounce
> daemon which talks to a cleanup service to queue a message.
> One could run bounce daemons with a cleanup_service override
> in master.cf:
Thanks Wietse, that makes
Geert Hendrickx via Postfix-users:
> Hi
>
> We have few different sets of Postfix mailservers with different roles;
> inbound servers, outbound servers that DKIM sign outgoing mail with a
> milter, and some other servers that just relay mail that is already signed
> elsewhere.
>
> The first and
relayhost (one that DKIM signs outbound e-mail), without impacting regular
mail routing? Similar to non_smtpd_milters for locally generated mail?
(a sender_dependent_relayhost_maps override for empty senders won't do,
as such mail could come in via smtpd as well, and shouldn't be signed
gt;
> My new main.cf :
>
> relayhost = [smtp.gmx.com]:465
That's much better, thanks. Given comments below, secure connections to
this server under the name "mail.gmx.com" (that's the only DNS SAN in
the certificate) pass certificate verification at the "secure" leve
3 à 13:33, Peter via Postfix-users a écrit :
The cert is signed for mail.gmx.com, either change the relayhost setting
to reflect this or create a new cert that also includes smtp.gmx.com.
On 11.09.23 14:23, François Patte via Postfix-users wrote:
Changing the relayhost does not change the behavi
led for
smtp.gmx.com[212.227.17.174]:465: num=62:hostname mismatch
On 11.09.23 23:33, Peter via Postfix-users wrote:
The cert is signed for mail.gmx.com, either change the relayhost
setting to reflect this or create a new cert that also includes
smtp.gmx.com.
since I assume you con't control t
227.17.174]:465: num=62:hostname mismatch
The cert is signed for mail.gmx.com, either change the relayhost setting
to reflect this or create a new cert that also includes smtp.gmx.com.
Changing the relayhost does not change the behavior: turning security
level to "secure" complain
.23 23:33, Peter via Postfix-users wrote:
The cert is signed for mail.gmx.com, either change the relayhost
setting to reflect this or create a new cert that also includes
smtp.gmx.com.
since I assume you con't control that server, you need to change relayhost
to [mail.gmx.com]:465
and then change
ned for mail.gmx.com, either change the relayhost setting
to reflect this or create a new cert that also includes smtp.gmx.com.
Peter
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
all
mail_owner = postfix
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
meta_directory = /etc/postfix
mydestination =
myhostname = pingala.fqdn
newaliases_path = /usr/bin/newaliases.postfix
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix/README_F
u probably don't want this.
> >
> > > smtpd_tls_security_level = encrypt
> >
> > Nor this, except on the submission services in master.cf.
And turned off SASL AUTH on your inbound port 25.
> > You're obfuscating the essential hostnames, making help nee
On 10.09.23 10:38, François Patte via Postfix-users wrote:
relayhost = [smtp.myfai.fqdn]:465
smtp_sasl_auth_enable = yes
smtp_sasl_mechanism_filter = login
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
what is on your /etc/postfix/sasl_passwd ? It should be
[smtp.myfai.fqdn]:465
://www.postfix.org/DEBUG_README.html#mail
It looks like you "tampered" with the logs. They don't match your
reported configuration below.
postconf -n
relayhost = [myfai.fqdn]:465
This is not equal to "my-fai-smtp".
smtp_tls_wrappermode = yes
Good, needed for trans
reply to
> > > MAIL FROM command))
> >
> > https://www.postfix.org/DEBUG_README.html#mail
It looks like you "tampered" with the logs. They don't match your
reported configuration below.
> postconf -n
> relayhost = [myfai.fqdn]:465
This is not equal to
tory = /usr/share/man
meta_directory = /etc/postfix
mydestination =
myhostname = myhost.fqdn
newaliases_path = /usr/bin/newaliases.postfix
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix/README_FILES
relayhost = [myfai.fqdn]:465
sample_directory = /usr/share/doc/pos
On Sat, Sep 09, 2023 at 06:55:03PM +0200, François Patte via Postfix-users
wrote:
> I would like to use my fai smtp server to send mails using postfix.
>
> As my postfix install is configured, I get only (in mail-log):
>
> Sep 9 16:50:49 myserver postfix/qmgr[205575]: 92BEFB4BEA:
> from=,
Bonjour,
I would like to use my fai smtp server to send mails using postfix.
As my postfix install is configured, I get only (in mail-log):
Sep 9 16:50:49 myserver postfix/qmgr[205575]: 92BEFB4BEA:
from=, size=484, nrcpt=1 (queue active)
Sep 9 16:50:49 myserver postfix/smtp[205832]:
Am 06.07.23 um 21:39 schrieb Viktor Dukhovni via Postfix-users:
So the service provider advertises, but fails to implement "PLAIN", that
sounds like a bad idea. Open a bug report. They should not do that.
I did have one open. More for cram-md5 than plain, of course. The issue
is: For
On Thu, Jul 06, 2023 at 06:38:34PM +0200, Ede Wolf via Postfix-users wrote:
> Jep, I just retested. Changed to plain, restarted postfix and mail gets
> deferred:
>
> relay=smtp.worldserver.net[217.13.200.36]:587, delay=1,
> delays=0.07/0.01/0.95/0, dsn=4.7.0, status=deferred (SASL
Am 06.07.23 um 14:51 schrieb Viktor Dukhovni via Postfix-users:
I am surprised to hear that "login" works and "plain" does not, are you
sure about that?
Jep, I just retested. Changed to plain, restarted postfix and mail gets
deferred:
relay=smtp.worldserver.net[217.13.200.36]:587,
On Thu, Jul 06, 2023 at 08:10:39AM +0200, Ede Wolf via Postfix-users wrote:
> > BINGO! The server is advertising CRAM-MD5, and unless you filter it out
> > SASL will attempt to use that instead of plain. Therefore, in the
> > proposed "master.cf" entry you also need:
> >
> > -o {
Hello Viktor,
again, thanks very much for your help
See below, with the critical additional detail you present now (and
sadly did not know to present before), there's more to be done.
The problem here is, that the annoucement of CRAM-MD5 is false. While it
still does work for older
a Postfix-users wrote:
> >
> >> I am having a weired issue. My provider for the relayhost switched to
> >> SSL - which is fine by itself - but that also changed the authentication
> >> scheme.
> >
> > What SASL mechanism was used before that?
Hello Viktor,
thanks very much for your reply. I still may have some understanding issues:
Am 05.07.23 um 16:22 schrieb Viktor Dukhovni via Postfix-users:
On Wed, Jul 05, 2023 at 02:42:54PM +0200, Ede Wolf via Postfix-users wrote:
I am having a weired issue. My provider for the relayhost
On Wed, Jul 05, 2023 at 02:42:54PM +0200, Ede Wolf via Postfix-users wrote:
> I am having a weired issue. My provider for the relayhost switched to
> SSL - which is fine by itself - but that also changed the authentication
> scheme.
What SASL mechanism was used before that? You'r
Hello,
I am having a weired issue. My provider for the relayhost switched to
SSL - which is fine by itself - but that also changed the authentication
scheme.
So SASL, what worked for over a decade, does not work any more, instead
I need to send plain text username/pw. Confirmed
> On 21.05.23 15:53, Tom Reed via Postfix-users wrote:
>>My postfix has setup another MTA for relay host,
>>
>>relayhost = [relay_ip]
>>
>>If I setup this postfix as backup mx for a domain, such as foo.com.
>>will messages for foo.com relay from relay_ip
On 21.05.23 15:53, Tom Reed via Postfix-users wrote:
My postfix has setup another MTA for relay host,
relayhost = [relay_ip]
If I setup this postfix as backup mx for a domain, such as foo.com.
will messages for foo.com relay from relay_ip too, or go directly to the
primary MX?
On 21.05.23 11
On 21.05.23 15:53, Tom Reed via Postfix-users wrote:
My postfix has setup another MTA for relay host,
relayhost = [relay_ip]
If I setup this postfix as backup mx for a domain, such as foo.com.
will messages for foo.com relay from relay_ip too, or go directly to the
primary MX?
messages
Hello list,
My postfix has setup another MTA for relay host,
relayhost = [relay_ip]
If I setup this postfix as backup mx for a domain, such as foo.com.
will messages for foo.com relay from relay_ip too, or go directly to the
primary MX?
Thanks in advance.
--
sent from https://dkinbox.com
: (240) 513-5290
From: on behalf of Wietse Venema
Reply-To: Postfix users
Date: Wednesday, October 26, 2022 at 15:38
To: Postfix users
Subject: Re: [EXTERNAL] Re: MX records and relayhost: Am I going this correctly
?
White, Daniel E. (GSFC-770.0)[AEGIS]:
Many thanks for the sanity check, Mr. P
Wietse
> Again, many thanks for the quick response
>
> From: on behalf of Wietse Venema
>
> Reply-To: Postfix users
> Date: Wednesday, October 26, 2022 at 14:09
> To: Postfix users
> Subject: [EXTERNAL] Re: MX records and relayhost: Am I going this correctly ?
>
>
thanks for the quick response
From: on behalf of Wietse Venema
Reply-To: Postfix users
Date: Wednesday, October 26, 2022 at 14:09
To: Postfix users
Subject: [EXTERNAL] Re: MX records and relayhost: Am I going this correctly ?
White, Daniel E. (GSFC-770.0)[AEGIS]:
MX Records
gt; Then in /etc/postfix/main.cf, I have
>
>relayhost = mydomain.tld
>
> I have seen this work with relay-1 unavailable.
This is the obvious (to me) approach when the domain has multiple
MX hosts. It is also similar to the first relayhost example in the
stock main
MX Records:
mydomain.tld. 33 IN MX 10 relay-1.mydomain.tld.
mydomain.tld. 33 IN MX 20 relay-2.mydomain.tld.
with relay-1 and relay-2 having appropriate A and PTR records.
Then in /etc/postfix/main.cf, I have
relayhost = mydomain.tld
I
Danil Smirnov:
> On Thu, Sep 1, 2022 at 1:27 PM Wietse Venema wrote:
>
> > There is a missing colon: the syntax is randmap:{list...}
>
> Great! It works now. :) Thank you, Wietse.
>
> Is it possible to confirm that the approach is working in the postfix logs?
Look at the time stamps.
On Thu, Sep 1, 2022 at 1:27 PM Wietse Venema wrote:
> There is a missing colon: the syntax is randmap:{list...}
>
Great! It works now. :) Thank you, Wietse.
Is it possible to confirm that the approach is working in the postfix logs?
They look just the same way as without
Danil Smirnov:
> Hi!
>
> On Wed, Feb 23, 2022 at 7:01 PM Wietse Venema wrote:
>
> > Short answer:
> >
> > Use randmap to select from 10 delivery agents.
> >
> > sender_dependent_default_transport_maps = randmap{smtp1:, smtp2:, ...}
There is a missing colon: the syntax is randmap:{list...}
Hi!
On Wed, Feb 23, 2022 at 7:01 PM Wietse Venema wrote:
> Short answer:
>
> Use randmap to select from 10 delivery agents.
>
> sender_dependent_default_transport_maps = randmap{smtp1:, smtp2:, ...}
>
> Use rate delays of 1s.
>
> smtp1_transport_rate_delay = 1s
>
On 20.08.22 03:43, Wietse Venema wrote:
Maybe you have chroot turned on in master.cf?
You're right, that was the issue. Thanks for the hint!
That is NOT POSTFIX.
And neither did I claim it was - I was just showing that it could be an
issue of my postfix configuration because it worked with
witcher:
> Aug 19 23:02:43 portable-navi postfix/smtp[385223]: 2190C1428ED:
> to=, relay=none, delay=585, delays=585/0.11/0/0,
> dsn=4.4.3, status=deferred (Host or domain name not found. Name service
> error for name=smtp.example.com type=MX: Host not found, try again)
That is Postfix. Maybe you
On 19.08.22 09:48, Matus UHLAR - fantomas wrote:
sender_dependent_default_transport_maps allows specifying transport,
with some limits
I see! It *seems* to use the correct transport for the server now, but
now I'm getting another error:
```
Aug 19 23:02:43 portable-navi postfix/smtp[385223]:
onf.5.html#sender_dependent_relayhost_maps
looks like sender_dependent_relayhost_maps requires just relayhost, not
transport.
It is also overridden with other settings, see the page above.
sender_dependent_default_transport_maps allows specifying transport, with
some limits:
http://www.p
On 19.08.22 02:12, Matus UHLAR - fantomas wrote:
you can define multiple transports in master.cf and use them if you
need different client settings.
That's interesting, thank you for the tip and example configuration!
so you can use transport like "smtpssl:" in your *relayhost_maps:
smtpssl
On 19.08.22 13:27, witcher wrote:
I've set up Postfix for use as a relayhost, using multiple SMTP servers
via `sender_dependent_relayhost_maps`.
The issue I have is that one needs to use the settings
`smtp_tls_security_level = encrypt` and `smtp_tls_wrappermode = yes`,
while another one needs
Hello,
I've set up Postfix for use as a relayhost, using multiple SMTP servers
via `sender_dependent_relayhost_maps`.
The issue I have is that one needs to use the settings
`smtp_tls_security_level = encrypt` and `smtp_tls_wrappermode = yes`,
while another one needs `smtp_tls_security_level
Am 08.07.2022 um 21:35 schrieb Viktor Dukhovni:
On Fri, Jul 08, 2022 at 09:08:28PM +0200, Postfix-jtroendle wrote:
submission/inet/rewrite_service_name = submission-rewrite
Your mistake is believing that the trivial rewrite service setting in
smtpd(8) can determine message routing. This is
On Fri, Jul 08, 2022 at 09:08:28PM +0200, Postfix-jtroendle wrote:
> submission/inet/rewrite_service_name = submission-rewrite
Your mistake is believing that the trivial rewrite service setting in
smtpd(8) can determine message routing. This is not the case. This
only determines the address
accidentally a REDIRECT or FILTER.
postconf -n
compatibility_level = 3.6
inet_protocols = ipv4
mydomain = mydomain.com
myhostname = smarthost.mydomain.com
mynetworks = 127.0.0.0/8
relayhost = [4.4.4.1]
smtp_tls_note_starttls_offer = yes
smtpd_tls_cert_file = /etc/ssl/certs/smarthost_mydomain_com
The Postfix SMTP client is not as smart as you appear to believe.
It receives the nexthop from the queue manager.
- If the nexthop from the queue manager is an [ipaddress] then the
SMTP client uses that address.
- If the nexthop from the queue manager is a domain name, then the
SMTP client
and
sender_dependent_relayhost_maps to correctly identify 1.1.1.1 as next
hop. But then, managed by qmgr, smtp takes over and chooses either
4.4.4.1 (relayhost in main.cf) or resolves the next hop via DNS (if no
relayhost in main.cf):
Jul 8 10:29:19 localhost
postfix/submission-rewrite/trivial-rewrite[103626]: maps_find
Russell Jones:
> > perhaps changing the delay to 0... why did you change it at all?
>
> Is setting it to 0 not allowing it to send out as quickly as possible with
> no delay at all?
>
> I set it to 1s because I was attempting to configure 10 messages per second
>
messages
> per second.
>
>
> >> Le mer. 23 févr. 2022 à 17:08, Russell Jones a
> >> écrit :
> >>> I am struggling to understand why my postfix configuration is not
> >>> allowing me to send 10 messages per second through my c
nd why my postfix configuration is not
allowing me to send 10 messages per second through my configured relayhost.
When watching the logs, it is sending 1 message per second.
initial_destination_concurrency = 10
default_destination_concurrency_limit = 10
default_destination_rate_delay = 1s
smtp
ds,
> YM
>
> Le mer. 23 févr. 2022 à 17:08, Russell Jones a
> écrit :
>
>> Hi all,
>>
>> I am struggling to understand why my postfix configuration is not
>> allowing me to send 10 messages per second through my configured relayhost.
>> When watching t
every second.
Regards,
YM
Le mer. 23 févr. 2022 à 17:08, Russell Jones a écrit :
> Hi all,
>
> I am struggling to understand why my postfix configuration is not allowing
> me to send 10 messages per second through my configured relayhost. When
> watching the logs, it is sendin
Hi all,
I am struggling to understand why my postfix configuration is not allowing
me to send 10 messages per second through my configured relayhost. When
watching the logs, it is sending 1 message per second.
initial_destination_concurrency = 10
default_destination_concurrency_limit = 10
aviour?
compatibility_level = 2
header_checks = pcre:/etc/postfix/header_checks
Any FILTER directives in header_checks?
relayhost = [smtp-relay.site.com]:25
This applies to all remote destinations where the transport table does
not set an explicit nexthop.
smtp_connection_reuse_count_lim
=sites,dc=com
site.ldap:domain=site.com
I would appreciate any other insights; I've been over this many times today and
have not found any reason that relayhost is being bypassed.
RobertC
From: owner-postfix-us...@postfix.org on
behalf of Viktor Dukhovni
Sent
On Tue, Oct 26, 2021 at 04:22:53PM +, Cooper, Robert A wrote:
> Howdy! We have noticed that certain email going through our outbound
> relay are ignoring the "relayhost = [smtp-relay.site.com]:25".
Sorry, that's not possible. The delivery of messages for *all*
recipien
Howdy! We have noticed that certain email going through our outbound relay are
ignoring the "relayhost = [smtp-relay.site.com]:25". The condition seems to be
when a message has an envelope rewrite based on LDAP lookup (specifically, from
site.com to email.site.com, which goe
st create something for yourself.
Builtin solutions exist for typical cases. Usually people who use relayhost
do know which domains are their local domains (so they should not be handled
via relayhost), and have control over this. On the other hand, if you are
serving multiple domains that users
On 2021-05-06 15:56, Jaroslaw Rafa wrote:
Dnia 6.05.2021 o godz. 14:07:55 Vytenis Adm pisze:
Yes, we did look into it, and it's not an option. "transport_maps"
looks into a DB, and we can't rely on it. Clients can point MX to
their own servers, and "transport_maps" will route to our MX
Thanks Matus for taking time to respond. Appreciated.
On 2021-05-06 14:34, Matus UHLAR - fantomas wrote:
On 06.05.21 10:37, Vytenis Adm wrote:
We have a postfix server, which forwards all customer's outbound
emails to a "relayhost". Our "relayhost" is somewhat
> On May 6, 2021, at 8:56 AM, Jaroslaw Rafa wrote:
>
> "transport_maps" looks into a *map*, and a map in Postfix is more than just
> DB. For example it can be a *TCP table*, which means Postfix is asking some
> program that listens on a specific port for the key, and gets a value in
> return. It
Dnia 6.05.2021 o godz. 14:07:55 Vytenis Adm pisze:
>
> Yes, we did look into it, and it's not an option. "transport_maps"
> looks into a DB, and we can't rely on it. Clients can point MX to
> their own servers, and "transport_maps" will route to our MX
> regardless of what is set in customer's
On 06.05.21 10:37, Vytenis Adm wrote:
We have a postfix server, which forwards all customer's outbound
emails to a "relayhost". Our "relayhost" is somewhat costly, so
our goal is to minimize it's usage. MX is served by separate
Postfix instance.
Our goal is to deliver lo
On 2021-05-06 12:42, Matus UHLAR - fantomas wrote:
On 06.05.21 10:37, Vytenis Adm wrote:
We have a postfix server, which forwards all customer's outbound
emails to a "relayhost". Our "relayhost" is somewhat costly, so our
goal is to minimize it's usage. MX is served
On 06.05.21 10:37, Vytenis Adm wrote:
We have a postfix server, which forwards all customer's outbound
emails to a "relayhost". Our "relayhost" is somewhat costly, so our
goal is to minimize it's usage. MX is served by separate Postfix
instance.
Our goal is to deliver lo
Hi list,
We have a postfix server, which forwards all customer's outbound emails
to a "relayhost". Our "relayhost" is somewhat costly, so our goal is to
minimize it's usage. MX is served by separate Postfix instance.
Our goal is to deliver local emails to our MX
IL Ka:
> >
> > Yes, "relayhost" also affects the routing of mail to "relay_domains".
> >
> > Thank you, Viktor.
>
> I see: "relay_domains" -> "relay_transport".
> "relayhost" affects both: default_transport
>
> Yes, "relayhost" also affects the routing of mail to "relay_domains".
>
> Thank you, Viktor.
I see: "relay_domains" -> "relay_transport".
"relayhost" affects both: default_transport and relay_transport
On Wed, May 05, 2021 at 02:20:30AM +0300, IL Ka wrote:
> Does there any difference between setting "relayhost" and
> default_transport smtp with explicit next hop?
Yes, "relayhost" also affects the routing of mail to "relay_domains".
--
Viktor.
Hello,
Does there any difference between setting "relayhost" and default_transport
smtp with
explicit next hop?
Ilya.
On Mon, Mar 01, 2021 at 11:14:57AM +0100, Jaap Gordijn wrote:
> relayhost = aaa.bbb.ccc:25
> virtual_mailbox_domains = xxx.yyy.zzz
> virtual_transport = lmtp:unix:private/dovecot-lmtp
>
> I would like to achieve the following
> - mail of all subnets in my LAN is relaye
On 1 Mar 2021, at 5:14, Jaap Gordijn wrote:
For my local mailserver with postfix/dovecot and virtual domains set
up as
follows:
relayhost = aaa.bbb.ccc:25
virtual_mailbox_domains = xxx.yyy.zzz
virtual_transport = lmtp:unix:private/dovecot-lmtp
I would like to achieve the following
- mail
For my local mailserver with postfix/dovecot and virtual domains set up as
follows:
relayhost = aaa.bbb.ccc:25
virtual_mailbox_domains = xxx.yyy.zzz
virtual_transport = lmtp:unix:private/dovecot-lmtp
I would like to achieve the following
- mail of all subnets in my LAN is relayed if nesessary
Demi M. Obenour:
> >> I am not sure whether adding such a feature motivated by just the
> >> presented use-case is warranted.
> >
> > My take: not if it only solves only one problem.
>
> I agree. In particular, we should avoid a pile of features with very
> narrow use-cases.
I think that this
On 1/16/21 5:12 PM, Wietse Venema wrote:
> Viktor Dukhovni:
>> On Sat, Jan 16, 2021 at 04:48:22AM -0500, Viktor Dukhovni wrote:
>>
>>> On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
>>>
>>>> My goal is to conditionally select the relayhost
On 16 Jan 2021, at 02:48, Viktor Dukhovni wrote:
> Since the queue manager has no mechanism for size-dependent selection of
> a default transport
Postfix does, however, know the size of the message based if it is over or
under the message_size_limit, and it must know that before the message
Viktor Dukhovni:
> On Sat, Jan 16, 2021 at 04:48:22AM -0500, Viktor Dukhovni wrote:
>
> > On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
> >
> > > My goal is to conditionally select the relayhost based on the total size
> > > of the outgoing mess
On Sat, Jan 16, 2021 at 04:48:22AM -0500, Viktor Dukhovni wrote:
> On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
>
> > My goal is to conditionally select the relayhost based on the total size
> > of the outgoing message. The rationale is that I'm us
On Sat, Jan 16, 2021 at 08:14:34AM +, Alexander wrote:
> My goal is to conditionally select the relayhost based on the total size
> of the outgoing message. The rationale is that I'm using Amazon AWS SES
> for the most part. Alas, SES only accepts messages up to 10 M
Hello,
My goal is to conditionally select the relayhost based on the total size
of the outgoing message. The rationale is that I'm using Amazon AWS SES
for the most part. Alas, SES only accepts messages up to 10 MB in size
(this includes images and attachments that are part of the message
On Thu, Dec 10, 2020 at 02:56:17PM -0500, Viktor Dukhovni wrote:
> On Thu, Dec 10, 2020 at 05:33:46AM -0800, Jon Leech wrote:
>
> > The only meaningful messages in the mail logs were
> >
> > Dec 10 00:01:58 celly postfix/smtp[21050]: warning: relayhost configuration
&
On Thu, Dec 10, 2020 at 05:33:46AM -0800, Jon Leech wrote:
> The only meaningful messages in the mail logs were
>
> Dec 10 00:01:58 celly postfix/smtp[21050]: warning: relayhost configuration
> problem
> Dec 10 00:01:58 celly postfix/smtp[21050]: send attr reason = unable to
DNS lookups are done by SYSTEM LIBRARY functions, and these log
nothing no matter how you twiddle Postfix options. Postfix is the
messenger of bad news; don't blame the messenger.
Consider using strace (see http://www.postfix.org/DEBUG_README.html)
and find out what if you have a 'missing file'
I'm using postfix 3.4.14-0+deb10u1 as the MTA on my Debian machine,
with
disable_dns_lookups = yes
relayhost [mail.sonic.net]:587
This has worked fine for many years until on 12/3, without any
changes in my local OS / postfix configuration, it started failing to
deliver mail
Matthew Patton wrote:
> > Why send mail as user@myhostname, when the named host will never
> > ever receive email?
>
> Because I need to retain FROM what host it originated. If I see an
> email from root@domain I have no idea which host it came from.
In my mailer I would immediately look at the
Patton, Matthew [Contractor]:
> > Why send mail as user@myhostname, when the named host will never
> > ever receive email?
>
> Because I need to retain FROM what host it originated. If I see
> an email from root@domain I have no idea which host it came from.
> The emails are cron scripts and the
On Sun, Aug 16, 2020 at 01:58:16AM +, Patton, Matthew [Contractor] wrote:
> > Why send mail as user@myhostname, when the named host will never
> > ever receive email?
>
> Because I need to retain FROM what host it originated. If I see an email from
> root@domain I have no idea which host
> Why send mail as user@myhostname, when the named host will never
> ever receive email?
Because I need to retain FROM what host it originated. If I see an email from
root@domain I have no idea which host it came from. The emails are cron scripts
and the like, not user-generated email.
If
ser@myhostname, when the named host will never
> ever receive email? You can avoid a lot of complication by using a
> myorigin setting that specifies a domain name, and MX records for
> that domain that point to a suitable mailhub.
>
> myorigin = example.com
>
> And perhaps e
l never
ever receive email? You can avoid a lot of complication by using a
myorigin setting that specifies a domain name, and MX records for
that domain that point to a suitable mailhub.
myorigin = example.com
And perhaps even
relayhost = example.com
Wietse
On a regular sending host I have set 'myhostname' (because logical hostname
differs from the system-level nee AWS autogenerated hostname),
'myorigin=$myhostname' (Postfix default) and 'relayhost=[1.2.3.4]' but
'mydestination' does NOT include $myhostname. I want the relayhost to be the
sole
pending on whether the messages to delivered via LMTP are just the
> inbound traffic, or truly "all mail", even bounces to the original
> sender, ...
>
> > On Jul 25, 2019, at 4:32 PM, Wietse Venema wrote:
> >
> > default_transport = lmtp
> > relayhost = [mail.example.com]
>
> --
> Viktor.
>
>
Jul 25, 2019, at 4:32 PM, Wietse Venema wrote:
>
> default_transport = lmtp
> relayhost = [mail.example.com]
--
Viktor.
Matthias Schneider:
> Hi,
>
> is it possible to configure a LMTP only server as relayhost= in postfix?
>
> I'd like to relay all mails to my local lmtp server
Yes.
default_transport = lmtp
relayhost = [mail.example.com]
Wietse
Hi,
is it possible to configure a LMTP only server as relayhost= in postfix?
I'd like to relay all mails to my local lmtp server
Best Regards,
MS
I?ve also tried sender_dependent_relayhost_maps, it didn?t work.
Bounces have the EMPTY envelope sender address, not MAILER-DAEMON.
Instead you need to match on <>:
empty_address_relayhost_maps_lookup_key (default: <>)
The sender_dependent_relayhost_maps search string that will be
1 - 100 of 500 matches
Mail list logo
