No. Well designed ones won't do that to you.
Scott K
On Friday, January 25, 2019 01:51:55 AM Matt Wong wrote:
> This gets closer - and as far as I tested, it's not the name, but rather
> the ip to wich inet_interfaces is set to. Default seems "all" - wich
> includes the IPs of all interfaces + l
This gets closer - and as far as I tested, it's not the name, but rather
the ip to wich inet_interfaces is set to. Default seems "all" - wich
includes the IPs of all interfaces + loopback - and it seems the error
is caused by some quirk that postfix doesn't want to deliever to any ip
it self is
On Thu, Jan 24, 2019 at 05:15:58PM -0600, Noel Jones wrote:
> On 1/24/2019 4:54 PM, Matt Wong wrote:
>
> > Well, I got a bit further: When listing mailq postfix complains
> > about "127.0.0.1 loop back to myself".
>
> Change the postfix "myhostname" parameter to something other than
> what James
On 1/24/2019 4:54 PM, Matt Wong wrote:
> Well, I got a bit further: When listing mailq postfix complains
> about "127.0.0.1 loop back to myself".
Change the postfix "myhostname" parameter to something other than
what James uses.
-- Noel Jones
On 1/24/2019 4:09 PM, Matt Wong wrote:
> Well, I'll give mini-smtp a try now - let's see if this fits my
> purposes better.
>
> About the brain-dead system: isn't it supposed that the config-tool,
> wich, correct me if I'm wrong, belongs to postfix itself is run at
> its start-up? Also, if config.
*cut out rage about linux*
Well, I got a bit further: When listing mailq postfix complains about
"127.0.0.1 loop back to myself".
https://james.apache.org/server/james_and_sendmail.html mentions some
this way and how sendmail once had to been told "yea, don't worry, I
know what I do" - is the
On Thursday, January 24, 2019 11:09:25 PM Matt Wong wrote:
> Well, I'll give mini-smtp a try now - let's see if this fits my purposes
> better.
>
> About the brain-dead system: isn't it supposed that the config-tool,
> wich, correct me if I'm wrong, belongs to postfix itself is run at its
> start-
Well, I'll give mini-smtp a try now - let's see if this fits my purposes
better.
About the brain-dead system: isn't it supposed that the config-tool,
wich, correct me if I'm wrong, belongs to postfix itself is run at its
start-up? Also, if config.postfix generates master.cf from sysconfig -
s
On 1/24/2019 3:12 PM, Matt Wong wrote:
> Hi Noel Jones,
>
> sadly, this didn't the trick. I can change /etc/postfix/master.cf
> and call postfix reload - then smtpd shuts down and james is able to
> start its smtp server. Strangely, when using systemctl restart
> postfix master.cf is rebuild from
Hi Noel Jones,
sadly, this didn't the trick. I can change /etc/postfix/master.cf and
call postfix reload - then smtpd shuts down and james is able to start
its smtp server. Strangely, when using systemctl restart postfix
master.cf is rebuild from /etc/sysconfig/postfix - smtpd is re-enabled
a
On 1/23/2019 1:47 PM, Matt Wong wrote:
> Ok, so the title isn't really helpful, so I try to explain it:
>
> I want to use Apache James as my primary MTA (please don't ask why -
> just take it as given). Major issue: james doesn't have a local
> sendmail command replacement. So I've looked up apach
Ok, so the title isn't really helpful, so I try to explain it:
I want to use Apache James as my primary MTA (please don't ask why -
just take it as given). Major issue: james doesn't have a local sendmail
command replacement. So I've looked up apache james doc wich is heavy
outdated. Also, I'm
12 matches
Mail list logo
