Hi,
you always can create a backup of your EC2 instance and do a rollback in case
of any trouble after or during upgrade.
WBR,
Andrey Tovstik
> On 8 Jul 2021, at 04:42, Shawn Heisey wrote:
>
> I have a mail server in AWS that is currently running Ubuntu 18. Every time
> I log in, I am
I've been a little bit terrified of doing an upgrade, because I do have a couple of people using my mail server for real work
email and I don't want to disrupt them.
Besides Postfix you could have a look at
https://doc.dovecot.org/installation_guide/upgrading/from-2.2-to-2.3/
On Wed, Jul 07, 2021 at 07:41:57PM -0600, Shawn Heisey wrote:
> On Ubuntu 20, postfix would be upgraded to 3.4.10-1ubuntu1. Many
> other packages, probably including the mysql server, would also be
> upgraded.
>
>
> I'm writing today to find out what are the likely pain points I might
>
I have a mail server in AWS that is currently running Ubuntu 18. Every
time I log in, I am reminded that I can upgrade to Ubuntu 20.
On Ubuntu 18, postfix is version 3.3.0-1ubuntu0.3. On Ubuntu 20,
postfix would be upgraded to 3.4.10-1ubuntu1. Many other packages,
probably including the
post...@ptld.com wrote:
> Please RTFM Postfix documentation. If it does not mention IP addresses
> then it does not use the IP addres,
I did read the manual which says:
"Reject the request when the HELO or EHLO hostname has no DNS A or MX
record."
Good. Does it mention IP addresses? No it
The principle is very simple: Postfix documentation describes what
Postfix does.
The documentation does not describe all the things that Postfix
does not do. That would make the documentation much larger, and
much harder to read.
Understood.
> Please RTFM Postfix documentation. If it does not mention IP addresses
> then it does not use the IP addres,
I did read the manual which says:
"Reject the request when the HELO or EHLO hostname has no DNS A or MX
record."
Good. Does it mention IP addresses? No it doesn't. Therefore
it
post...@ptld.com:
> > On 07-07-2021 5:31 pm, Richard wrote:
> >
> > If the "hostname has no DNS A ... record", i.e., the *hostname*
> > presented on the HELO/EHLO doesn't resolve, then no IPnumber will be
> > returned [to do anything with].
>
> Yes, if the hostname has no DNS records then
On 07-07-2021 5:31 pm, Richard wrote:
If the "hostname has no DNS A ... record", i.e., the *hostname*
presented on the HELO/EHLO doesn't resolve, then no IPnumber will be
returned [to do anything with].
Yes, if the hostname has no DNS records then ofcourse it has no IP. But
if the hostname
post...@ptld.com:
> > On 07-07-2021 4:39 pm, Wietse Venema wrote:
> > Please RTFM Postfix documentation. If it does not mention IP addresses
> > then it does not use the IP addres,
>
> I did read the manual which says:
> "Reject the request when the HELO or EHLO hostname has no DNS A or MX
>
On 07-07-2021 5:22 pm, Kevin N. wrote:
reject_invalid_helo_hostname
Would reject an invalid host name such as "ho+st", but a valid hostname
such as "host" would pass
reject_non_fqdn_helo_hostname
Would reject a non fully-qualified hostname such as "host", but a
fully-qualified one such as
> Date: Wednesday, July 07, 2021 16:54:42 -0400
> From: post...@ptld.com
>
> I did read the manual which says:
> "Reject the request when the HELO or EHLO hostname has no DNS A or
> MX record."
>
> Best to my knowledge "DNS A" means IP so the manual does mention IP
> addresses, but then it
reject_invalid_helo_hostname
Would reject an invalid host name such as "ho+st", but a valid hostname
such as "host" would pass
(https://datatracker.ietf.org/doc/html/rfc2821#section-2.3.5):
501 5.5.2 : Helo command rejected: Invalid name
reject_non_fqdn_helo_hostname
Would reject a
On 07-07-2021 4:39 pm, Wietse Venema wrote:
Please RTFM Postfix documentation. If it does not mention IP addresses
then it does not use the IP addres,
I did read the manual which says:
"Reject the request when the HELO or EHLO hostname has no DNS A or MX
record."
Best to my knowledge "DNS
post...@ptld.com:
> Under smtpd_helo_restrictions there is
> reject_invalid_helo_hostname
> reject_non_fqdn_helo_hostname
> reject_unknown_helo_hostname
>
>
> #1) What is the difference between invalid and non_fqdn? In plain speak
> they sound the same to me. If its not fqdn
Under smtpd_helo_restrictions there is
reject_invalid_helo_hostname
reject_non_fqdn_helo_hostname
reject_unknown_helo_hostname
#1) What is the difference between invalid and non_fqdn? In plain speak
they sound the same to me. If its not fqdn isn't that malformed?
#2) I assume to
Mike Hughes:
> And issued a 'postmap /etc/postfix/myrecipientmap' command to pick
> it up. Might have done postfix reload or systemctl restart postfix
> a couple times to try to resolve the following.
>
> Messages are now being sent correctly; however, I still have a
> handful of messages in the
Thanks for all the ideas! I wanted to address the 'root' of the problem (so
sorry!) so rather than adjusting the parameters of the mail senders, I ended up
creating a '/etc/postfix/myrecipientmap' file and populated it with the
following:
@subdomain.domain.com @domain.com
Then I added a
Hi Wieste,
> To cut through the noise:
>
> 1 - Configure a Postfix smtpd process on an additional IP addresss
> or TCP port ***THAT ONLY THIS CLIENT WILL CONNECT TO.
>
> 2 - Configure that smtpd process with an smtpd_command_filter that
> replaces "MAIL FROM:<>" with the preferred
On Wed, 7 Jul 2021, Mike Hughes wrote:
I just noticed that we have a bunch of undeliverable messages piling up in the
queue. I have root defined in aliases for another address, which works when
sending to r...@domain.com. However, since the FQDN in main.cf is defined as
On 2021-07-07 17:03, post...@ptld.com wrote:
On 07-07-2021 9:50 am, Mike Hughes wrote:
I just noticed that we have a bunch of undeliverable messages piling
up in the queue. I have root defined in aliases for another address,
which works when sending to r...@domain.com. However, since the
That did the trick! Many thanks. ;)
On 2021-07-07 10:21, Kevin N. wrote:
It seems that in the MAIL command the IP address is still not between
[].
should be
On a quick look, it seems that you could try setting
resolve_numeric_domain = yes in your Postfix configuration and see if
that
You can fix MAIL FROM and other commands with smtpd_command_filter. See
http://www.postfix.org/postconf.5.html#smtpd_command_filter
Wietse
Hi mike, tks for feedback.
which does how to article(doc) you use for that setup? I read many man
pages from community about that, but not read this issue, in Centos 8.
regards.
On Wed, Jul 7, 2021 at 12:04 PM wrote:
> > On 07-07-2021 9:50 am, Mike Hughes wrote:
> > Hi all,
> >
> > I just
Hans van Zijst:
> I'm trying to get Postfix to send its bounce notices to a different
> address than "postmaster", so I configured
>
> notify_classes = resource, software, bounce, 2bounce
> bounce_notice_recipient = bou...@example.com
> 2bounce_notice_recipient = bou...@example.com
>
To cut through the noise:
1 - Configure a Postfix smtpd process on an additional IP addresss
or TCP port ***THAT ONLY THIS CLIENT WILL CONNECT TO.
2 - Configure that smtpd process with an smtpd_command_filter that
replaces "MAIL FROM:<>" with the preferred address.
# Listen
It seems that in the MAIL command the IP address is still not between [].
should be
On a quick look, it seems that you could try setting
resolve_numeric_domain = yes in your Postfix configuration and see if
that changes anything.
From http://www.postfix.org/postconf.5.html
postfix-users@postfix.org
Dne 07.07.2021 v 17:03 post...@ptld.com napsal(a):
On 07-07-2021 9:50 am, Mike Hughes wrote:
Hi all,
I just noticed that we have a bunch of undeliverable messages piling
up in the queue. I have root defined in aliases for another address,
which works when sending to
I believe you are correct, but again I have no control over that part.
Also, I mistakenly attached the log attempt from the telnet session I
tried, the actual systems having issues have the from address within
brackets, here is the system in question:
Jul 6 15:18:42 localhost
On 07-07-2021 9:50 am, Mike Hughes wrote:
Hi all,
I just noticed that we have a bunch of undeliverable messages piling up
in the queue. I have root defined in aliases for another address, which
works when sending to r...@domain.com. However, since the FQDN in
main.cf is defined as
When using IP addresses in the email address, shouldn't the IP be
enclosed between []?
For example: noreply@[100.67.10.122] instead of noreply@100.67.10.122
Cheers,
K.
On 07/07/2021 17:49, j...@wrightthisway.com wrote:
Hello folks. I have set up a fresh instance of Postfix at my office to
On 2021-07-07 08:50, Mike Hughes wrote:
I just noticed that we have a bunch of undeliverable messages piling
up in the queue. I have root defined in aliases for another address,
which works when sending to r...@domain.com. However, since the FQDN
in main.cf is defined as
Hello folks. I have set up a fresh instance of Postfix at my office to
help do some troubleshooting on another issue. There is a relay
upstream that is having issues forwarding mail from some devices here,
and this seemed the easiest way to get some data to help them
troubleshoot. Install
Le 07/07/2021 à 15:41, Emmanuel Fusté a écrit :
Le 07/07/2021 à 15:36, Emmanuel Fusté a écrit :
Le 07/07/2021 à 15:26, Wietse Venema a écrit :
Emmanuel Fust?:
Le 07/07/2021 ? 15:06, Wietse Venema a ?crit?:
Viktor Dukhovni:
On Tue, Jul 06, 2021 at 12:56:50PM +0200, Xavier Beaudouin wrote:
Hi Mike, whats up?
What is your SO(version) in MTA server, what is your postfix server?
On Wed, Jul 7, 2021 at 10:51 AM Mike Hughes wrote:
> Hi all,
>
> I just noticed that we have a bunch of undeliverable messages piling up in
> the queue. I have root defined in aliases for another address,
Hi all,
I just noticed that we have a bunch of undeliverable messages piling up in the
queue. I have root defined in aliases for another address, which works when
sending to r...@domain.com. However, since the FQDN in main.cf is defined as
host.subdomain.domain.com it's appending the whole
I'm trying to get Postfix to send its bounce notices to a different
address than "postmaster", so I configured
notify_classes = resource, software, bounce, 2bounce
bounce_notice_recipient = bou...@example.com
2bounce_notice_recipient = bou...@example.com
error_notice_recipient =
> On 7 Jul 2021, at 9:43 am, Emmanuel Fusté
> wrote:
>
> arghh no, sorry, smtp client must be added in between.
> A little more complex
No, just a dedicated SMTP listener service that runs in parallel
with the existing SMTP server. Everything else is the same...
The SMTP server replaces
Le 07/07/2021 à 15:36, Emmanuel Fusté a écrit :
Le 07/07/2021 à 15:26, Wietse Venema a écrit :
Emmanuel Fust?:
Le 07/07/2021 ? 15:06, Wietse Venema a ?crit?:
Viktor Dukhovni:
On Tue, Jul 06, 2021 at 12:56:50PM +0200, Xavier Beaudouin wrote:
I currently have an appliance that misuse the
Le 07/07/2021 à 15:26, Wietse Venema a écrit :
Emmanuel Fust?:
Le 07/07/2021 ? 15:06, Wietse Venema a ?crit?:
Viktor Dukhovni:
On Tue, Jul 06, 2021 at 12:56:50PM +0200, Xavier Beaudouin wrote:
I currently have an appliance that misuse the null sender (mail
from:<>) to send mail.
Emmanuel Fust?:
> Le 07/07/2021 ? 15:06, Wietse Venema a ?crit?:
> > Viktor Dukhovni:
> >> On Tue, Jul 06, 2021 at 12:56:50PM +0200, Xavier Beaudouin wrote:
> >>
> >>> I currently have an appliance that misuse the null sender (mail
> >>> from:<>) to send mail.
> >>>
> >>> Unfortunatly, this
Le 07/07/2021 à 15:06, Wietse Venema a écrit :
Viktor Dukhovni:
On Tue, Jul 06, 2021 at 12:56:50PM +0200, Xavier Beaudouin wrote:
I currently have an appliance that misuse the null sender (mail
from:<>) to send mail.
Unfortunatly, this appliance is closed source
and we can only setup : fixed
Viktor Dukhovni:
> On Wed, Jul 07, 2021 at 03:07:21PM +0300, Meir Welcher wrote:
>
> > I got it sorted out.
> > I am running a second postfix instance on the server, and the path for the
> > "smtp_tls_session_cache_database" needed to be set differently for the
> > second instance.
>
> The two
Viktor Dukhovni:
> On Tue, Jul 06, 2021 at 12:56:50PM +0200, Xavier Beaudouin wrote:
>
> > I currently have an appliance that misuse the null sender (mail
> > from:<>) to send mail.
> >
> > Unfortunatly, this appliance is closed source
> > and we can only setup : fixed ip address and recipient
On Wed, Jul 07, 2021 at 03:07:21PM +0300, Meir Welcher wrote:
> I got it sorted out.
> I am running a second postfix instance on the server, and the path for the
> "smtp_tls_session_cache_database" needed to be set differently for the
> second instance.
The two Postfix instances MUST specify
I got it sorted out.
I am running a second postfix instance on the server, and the path for the
"smtp_tls_session_cache_database" needed to be set differently for the
second instance.
On Wed, Jul 7, 2021 at 2:29 PM Meir Welcher wrote:
> We have a busy outbound only mail gateway.
> The system
We have a busy outbound only mail gateway.
The system load is fine, but tlsmgr shows 99-100% cpu.
I am afraid the tlsmgr is slowing everything else down.
How can that be tuned?
Should I run a second postfix instance on the same server?
Thank you,
Meir
47 matches
Mail list logo
