What I am looking for is pretty simple. How to get it to work with
"inet_protocols = all" like my existing server is currently set up to do
and not be limited to ipv4 only.
And it is already set to use 127.0.0.1 so why it is using [::1] instead
when the old server uses 127.0.01, that is part o
Am 2024-06-28 09:01, schrieb Curtis J Blank via Postfix-users:
What I am looking for is pretty simple. How to get it to work with
"inet_protocols = all" like my existing server is currently set up to
do and not be limited to ipv4 only.
And it is already set to use 127.0.0.1 so why it is using
Does one roundcube installation support only one SASL backend? For
example I configure it to access aol then it cannot access gmail.
Other webmail such as snappy can connect to many smtp/imap backends,
such as yahoo/outlook/gmail, they can be set up in one installation.
Thanks
___
On 28.06.24 02:01, Curtis J Blank via Postfix-users wrote:
What I am looking for is pretty simple. How to get it to work with
"inet_protocols = all" like my existing server is currently set up to
do and not be limited to ipv4 only.
simply allow receiving messages from ::1 on port 10025.
10025
Dnia 28.06.2024 o godz. 00:16:31 Curtis J Blank via Postfix-users pisze:
> When "inet_protocols = all" the connection to filter.mynetwork.local
> localhost
> port 10025 to hand off the message to spamassassin for scanning fails with
> "Relay access denied". What I finally noticed is that the connec
Στις 28/6/24 12:14, ο/η Jeff Peng via Postfix-users έγραψε:
Other webmail such as snappy can connect to many smtp/imap backends,
such as yahoo/outlook/gmail, they can be set up in one installation.
roundcube does the same as snappy , by manually editing config.inc.php
(iirc). eg...:
$config[
On 28/06/24 19:01, Curtis J Blank via Postfix-users wrote:
What I am looking for is pretty simple. How to get it to work with
"inet_protocols = all" like my existing server is currently set up to do
and not be limited to ipv4 only.
And it is already set to use 127.0.0.1
No it is not, it is s
On 28/06/2024 19:14, Jeff Peng via Postfix-users wrote:
Does one roundcube installation support only one SASL backend? For
example I configure it to access aol then it cannot access gmail.
Other webmail such as snappy can connect to many smtp/imap backends,
such as yahoo/outlook/gmail, they ca
On 2024-06-28 at 05:23:27 UTC-0400 (Fri, 28 Jun 2024 11:23:27 +0200)
Matus UHLAR - fantomas via Postfix-users
is rumored to have said:
Who exactly listens on port 10025? looks like postfix sends mail to
itself, or is it another postfix instance?
Historically that has been a port commonly used
Thank you, Alexander, Matus, Jaroslaw, Peter, and Bill, just the kind of
ideas I was looking for.
My old postfix server is running 2.11 and I have not dealt much with
postfix really since then because like I said it just worked, did what I
needed it to do. Currently I'm working with 3.9 and I
* Curtis J. Blank via Postfix-users:
> What I am looking for is pretty simple. How to get it to work with
> "inet_protocols = all" like my existing server is currently set up to do
> and not be limited to ipv4 only.
Well, you seem to be in a good mood. ;-)
> And it is already set to use 127.0.
Always in a good mood. It's a waste not to be. When I'm focused on
something I just state the facts as I understand them and sometimes that
doesn't come across well.
Yeah I know localhost can be either that's why I used 127.0.0.1 in the
config and don't/didn't use localhost anywhere, as I late
A bit off topic but it just happened to dawn on me that that Ethernet
Tap I referred to was a H4000. My brain works that way. Just to see if
my memory hadn't failed me I googled it. Yep H4000. And I even found a
Wiki page on it with a picture of the backbone cable and the H4000. And
the tool to
On 29/06/24 03:17, Curtis J Blank via Postfix-users wrote:
Well Peter all the "mynetworks =" that I have defined explicitly state
127.0.0.1 not localhost and all the logging shows 127.0.0.1 not
localhost. So that is why I say I am using 127.0.0.1. So I cannot follow
Ralph's suggestion changing
On 29/06/24 05:59, Curtis J Blank via Postfix-users wrote:
Always in a good mood. It's a waste not to be. When I'm focused on
something I just state the facts as I understand them and sometimes that
doesn't come across well.
Yeah I know localhost can be either that's why I used 127.0.0.1 in th
Peter, my misunderstanding, sorry. This is what I discovered today in
my testing. I explicitly used 127.0.0.1 and not localhost or so I
thought, I explain that below.
Back on topic. I did some more testing. This was the spampd options used:
SPAMPD_OPTIONS="--host=localhost:10025 --relayhost=lo
Yeah I thought of including the config but that OP was long due to all
the logging so I didn't want to make it longer. I did say in my OP I
would provide anything if requested.
-Curt
On 6/28/24 21:11, Peter via Postfix-users wrote:
On 29/06/24 05:59, Curtis J Blank via Postfix-users wrote:
Al
OK I tired this. What "mydestination" is set to does not matter whether
it's localhost or 127.0.0.1 if spampd is set to use localhost and not
127.0.0.1 it will not work.
So I'm convinced that was the root cause of my problem, spampd set to
use localhost when postfix is set to use 127.0.01 expl
On 29/06/24 15:16, Curtis J Blank via Postfix-users wrote:
Peter, my misunderstanding, sorry. This is what I discovered today in
my testing. I explicitly used 127.0.0.1 and not localhost or so I
thought, I explain that below.
Back on topic. I did some more testing. This was the spampd options
I don't know how many times now I have said this but I will day it again.
I have postfix set up to only listen on/use 127.0.0.1 *not* ::1.
And. I am not using spamd, it listens on port 783. I am using spampd
which shows up as perl because is it written in perl and it listens on
10025.
Here
On 29/06/24 18:09, Curtis J Blank via Postfix-users wrote:
I don't know how many times now I have said this but I will day it again.
I have postfix set up to only listen on/use 127.0.0.1 *not* ::1.
What postfix listens on is irrelevant, this has to do with which IP
postfix connects to spamp
No I am not confusing inbound and outbound and for this I'm only
concerned about inbound and actually only on ports 10024-26 that are for
lack of a better way to put it a customization.
-Curt
postconf -Mf
smtp inet n - n - - smtpd
submission inet n -
22 matches
Mail list logo
