On 10/08/17 16:51, Voytek wrote:
> I currently have Postfix 2.11 /MySQL on Centos 6, looking at migrating to
> current Postfix.
>
> current server:
> CentOS release 6.x
> mail_version = 2.11.0
This is not the stock postfix for CentOS 6, so if you want to upgrade it
on the same server you might wa
On 10.08.17 08:04, Mai Ling wrote:
My question is can postfix retry a failed delivery using another
smtp_bind_address than the first tried and failed one?
did you even read error messages you've got and searched the net for
answers?
On aug. 9, 2017 at 5:10 p.m., mailto:uh...@fantomas.sk)>
In v16.04 LTS, Ubuntu has switched to systemd.
"postfix reload" still seems to work just fine.
But I wonder if I should be using "systemctl reload postfix" instead.
Which method is preferred on systems that use systemd?
And if either method works, are there differences or reasons to prefer one
ov
I'm sorry but I fail to understand what value is your acid question bringing
to the conversation.
FWIW, Mathus, the remote side is simply printing a 5xx one line message "not
accepted" banner instead of the expected welcome 220 banner, not giving any
explanation to why, then closing t
Am Thu, 10 Aug 2017 10:19:25 -0700
schrieb "Michael Fox" :
> In v16.04 LTS, Ubuntu has switched to systemd.
>
> "postfix reload" still seems to work just fine.
> But I wonder if I should be using "systemctl reload postfix" instead.
>
> Which method is preferred on systems that use systemd?
> And
IMHO
I would think they both work for backwards compatibility and over time
"service postfix reload" will eventually be depreciated and no longer be a
valid command.
I expect that to take years.
-ALF
-Angelo Fazzina
Operating Systems Programmer / Analyst
University of Connecticut, UITS, SSG,
Mai Ling:
> FWIW, Mathus, the remote side is simply printing a 5xx one line
> message "not accepted" banner instead of the expected welcome 220
> banner, not giving any explanation to why, then closing the tcp
> session, without postfix even getting a chance to say HELO!
If the primary MX for a do
On Thu, Aug 10, 2017 at 05:42:44PM +, Fazzina, Angelo wrote:
> I would think they both work for backwards compatibility and over time
> "service postfix reload" will eventually be depreciated and no longer be a
> valid command.
Well. "postfix reload" != "service postfix reload".
Bastian
--
> Well at least in Redhat, if you do systemctl reload postfix it just
> executes postfix reload internally. So it makes absolutely no
> difference.
>
> # cat /usr/lib/systemd/system/postfix.service
> [Unit]
> Description=Postfix Mail Transport Agent
> After=syslog.target network.target
> Conflicts
I'm configuring master.cf to add amavisd-new. The amavisd-new documentation
(/usr/share/doc/amavisd-new/README.postfix.html) differs from the default
master.cf file regarding the chroot setting for the cleanup (and
pre-cleanup) service. I presume that the amavisd-new documentation is in
error and
On 8/10/2017 12:29 PM, Mai Ling wrote:
> However, the topic of this thread is: Can postfix retry a failed
> message, by attempting to retransmit using a different outgoing IP
> address of the machine it's running on?
>
> If I send a mail to the same destination using the old IP address, a
> regula
On 8/10/2017 2:46 PM, Michael Fox wrote:
> I'm configuring master.cf to add amavisd-new. The amavisd-new documentation
> (/usr/share/doc/amavisd-new/README.postfix.html) differs from the default
> master.cf file regarding the chroot setting for the cleanup (and
> pre-cleanup) service. I presume t
On 11/08/17 05:20, Michael Fox wrote:
# cat /usr/lib/systemd/system/postfix.service
Hmm. My Ubuntu system has no such file.
On *buntu/deb machines it's...
/lib/systemd/system/postfix.service
dpkg -L postfix | grep service
On Thu, August 10, 2017 6:33 pm, Peter wrote:
> On 10/08/17 16:51, Voytek wrote:
>> mail_version = 2.11.0
>
> This is not the stock postfix for CentOS 6, so if you want to upgrade it
> on the same server you might want to check where the current postfix came
> from. How it got there has to do wit
> The default master.cf as distributed by postfix has all services as
> chroot "n", and that is the recommended setting.
> -- Noel Jones
Thanks Noel.
Interesting. From
http://www.postfix.org/BASIC_CONFIGURATION_README.html#chroot_setup, the
recommendation seems to be to use chroot wherever pos
15 matches
Mail list logo