Le 30/09/2024 à 20:34, Wietse Venema via Postfix-users a écrit :
Workaround: specify "smtpd_sasl_auth_enable = yes". That means
Postfix needs some of the Dovecot machinery even if most of it will
remain unused.
That was fast! That works perfectly, many thanks.
_
Wietse Venema via Postfix-users:
> > $ telnet wzv smtp
> > Trying 168.100.3.7...
> > Connected to wzv.
> > Escape character is '^]'.
> > 220 wzv.porcupine.org ESMTP Postfix
> > XCLIENT LOGIN=whatever
> > 220 wzv.porcupine.org ESMTP Postfix
> > MAIL FROM:<>
> > 25
Wietse Venema via Postfix-users:
> Antonin VERRIER via Postfix-users:
> > Hello,
> >
> > I'm a bit confused about whether Postfix considers a client
> > authenticated using XCLIENT to be SASL-authenticated or not.
>
> If XCLIENT receives a SASL login name, Postfix assumes that client
> is authen
Antonin VERRIER via Postfix-users:
> Hello,
>
> I'm a bit confused about whether Postfix considers a client
> authenticated using XCLIENT to be SASL-authenticated or not.
If XCLIENT receives a SASL login name, Postfix assumes that client
is authenticated.
> Apparently "permit_sasl_authenticated
Le 30/09/2024 à 19:10, Jaroslaw Rafa via Postfix-users a écrit :
"smtpd_relay_restrictions=permit_mynetworks,reject" should do what you want.
While I don't know the exact value of your "mynetworks" parameter, it almost
always includes localhost 🙂.
But that doesn't work since the IP address that
Dnia 30.09.2024 o godz. 18:53:29 Antonin VERRIER via Postfix-users pisze:
> For context, I'm using Dovecot submission service, which handles
> connections from SMTP client and, if authentication is successful,
> proxies them to a dedicated Postfix port and provides client data
> using XCLIENT.
>
>
Paul:
> Hi
>
> Can? a postfix smtp client be made to? send xclient data to a xclient
> enabled local smtpd service ?
This is not documented, therefore not supported.
Also:
$ postconf -H | grep 'smtp_.*xclient'
produces no output, whereas
$ postconf -H | grep 'smtp_.*xforward'
does.
John Jetmore:
> On Mon, Oct 30, 2017 at 3:34 PM, Noel Jones wrote:
>
> > On 10/30/2017 1:43 PM, John Jetmore wrote:
> > > 2. Is it correct that STARTTLS must always precede XCLIENT? It
> > > appears that postfix owns the XCLIENT extension, is there any
> > > non-postfix implementor for whom the o
On Mon, Oct 30, 2017 at 3:34 PM, Noel Jones wrote:
> On 10/30/2017 1:43 PM, John Jetmore wrote:
> > 2. Is it correct that STARTTLS must always precede XCLIENT? It
> > appears that postfix owns the XCLIENT extension, is there any
> > non-postfix implementor for whom the order might be different or
On 10/30/2017 1:43 PM, John Jetmore wrote:
> (Apologies if this is a duplicate post. I sent the first one before
> I confirmed my list membership and I don't see it in the online
> archives so I am assuming it wasn't sent)
>
> Hi postfix-users. I am the author of the swaks SMTP tool. A user
> po
On Mon, May 25, 2015 at 12:21:18AM +, Viktor Dukhovni wrote:
> On Mon, May 25, 2015 at 01:28:09AM +0200, furio ercolessi wrote:
>
> > Now, I would like to add the XCLIENT facility to do some
> > antispam testing on B, using the original IPs that
> > connected to A. So I put A's IP address in
On Mon, May 25, 2015 at 01:28:09AM +0200, furio ercolessi wrote:
> Now, I would like to add the XCLIENT facility to do some
> antispam testing on B, using the original IPs that
> connected to A. So I put A's IP address in
> smtpd_authorized_xclient_hosts in the B's config,
> and verified that B
Den 2012-04-16 05:21, Benny Pedersen skrev:
my own defence on this is to
http://www.postfix.org/postconf.5.html#smtp_discard_ehlo_keywords
http://www.postfix.org/postconf.5.html#smtpd_discard_ehlo_keywords ups
Den 2012-04-09 02:15, Daniel L. Miller skrev:
Apr 8 17:02:35 bubba assp/smtpd[7414]: warning:
unknown[110.53.26.206]: SASL LOGIN authentication failed:
UGFzc3dvcmQ6
This is much better. My remaining question is - is there a way I can
get even that first connection line to reference the remot
JC Putter:
> can someone you me an example of how to enable this ? basicly a
> smtp servers forward my mail to my postfix server, i want to enable
> xclient to filter the sender information.
Wietse:
> See: http://www.postfix.org/postconf.5.html#smtpd_authorized_xclient_hosts
JC Putter:
> great th
great thanks wietse
On Sun, Jun 6, 2010 at 2:34 PM, Wietse Venema wrote:t
> JC Putter:
> > hi i want to enable xclient extentions for my postfix server, i looked
> at
> > http://www.postfix.org/XCLIENT_README.html
> >
> > can someone you me an example of how to enable this ? basicly a smtp
> se
JC Putter:
> hi i want to enable xclient extentions for my postfix server, i looked at
> http://www.postfix.org/XCLIENT_README.html
>
> can someone you me an example of how to enable this ? basicly a smtp servers
> forward my mail to my postfix server, i want to enable xclient to filter the
> send
jeff geng:
> Wietse:
>
> If We modify
> #ifdef USE_SASL_AUTH
> if (var_smtpd_sasl_enable)
> if (got_proto == 0)
>smtpd_sasl_auth_reset(state);
> #endif
>
> to
> #ifdef USE_SASL_AUTH
> if (var_smtpd_sasl_enable)
> if (got_login == 0)
>s
Wietse:
If We modify
#ifdef USE_SASL_AUTH
if (var_smtpd_sasl_enable)
if (got_proto == 0)
smtpd_sasl_auth_reset(state);
#endif
to
#ifdef USE_SASL_AUTH
if (var_smtpd_sasl_enable)
if (got_login == 0)
smtpd_sasl_auth_reset(state);
#endif
the
Wietse Venema:
> > > + UPDATE_STR(state->sasl_username, attr_value);
> > > + printable(state->sasl_username, '?');
> > > + UPDATE_STR(state->sasl_method, "xclient");
> > >
> > > Why not use the real authentication mechanism?
> > >
> >
> > Otherwise, if XCLIENT pas
jeff geng:
> Wietse:
> Please see my reply marked as blue.
> :)
>
> jeff geng
>
> 2010/1/5 Wietse Venema
>
> > jeff geng:
> > > Wietse:
> > >
> > > Happy new year :)
> > >
> > > We use niginx's smtp function to redirect mail to postfix server. But in
> > > postfix, XCLIENT command can't support
Wietse:
Please see my reply marked as blue.
:)
jeff geng
2010/1/5 Wietse Venema
> jeff geng:
> > Wietse:
> >
> > Happy new year :)
> >
> > We use niginx's smtp function to redirect mail to postfix server. But in
> > postfix, XCLIENT command can't support the LOGIN paremeter.
> > Severial months
jeff geng:
> Wietse:
>
> Happy new year :)
>
> We use niginx's smtp function to redirect mail to postfix server. But in
> postfix, XCLIENT command can't support the LOGIN paremeter.
> Severial months ago, I write a patch for postfix-2.5.3. Now nginx official
> website also supply a patch for thi
Geert Hendrickx a écrit :
> On Thu, Jan 29, 2009 at 12:22:13PM +0100, mouss wrote:
>> Jan 29 00:38:17 imlil postmx/smtpd[26222]: NOQUEUE: reject: RCPT from
>> unknown[147.203.208.166]: 550 5.7.1 Client host rejected: cannot find
>> your hostname, [147.203.208.166];
>> from=<3ff.4.69709687-17084...@
Geert Hendrickx:
> On Thu, Jan 29, 2009 at 12:22:13PM +0100, mouss wrote:
> > Jan 29 00:38:17 imlil postmx/smtpd[26222]: NOQUEUE: reject: RCPT from
> > unknown[147.203.208.166]: 550 5.7.1 Client host rejected: cannot find
> > your hostname, [147.203.208.166];
> > from=<3ff.4.69709687-17084...@cherr
On Thu, Jan 29, 2009 at 12:22:13PM +0100, mouss wrote:
> Jan 29 00:38:17 imlil postmx/smtpd[26222]: NOQUEUE: reject: RCPT from
> unknown[147.203.208.166]: 550 5.7.1 Client host rejected: cannot find
> your hostname, [147.203.208.166];
> from=<3ff.4.69709687-17084...@cherryimprovise.com> to=
> proto
Artem Bokhan a écrit :
> Ok, let's start with beginning...
>
> What is the difference between NAME and REVERSE_NAME from postfix's view?
> What is the difference between "SMTP client hostname" and "PTR record
> value"?
>
NAME is "verified". REVERSE_NAME is not. so you have 3 cases:
- NAME=REVER
Ok, let's start with beginning...
What is the difference between NAME and REVERSE_NAME from postfix's view?
What is the difference between "SMTP client hostname" and "PTR record
value"?
The NAME attribute specifies an SMTP client hostname (not an SMTP client
address), [UNAVAILABLE] when clien
Bokhan Artem:
> So how postfix interprets NAME and REVERSE_NAME?
> I want to understand, how not to break, for example,
> "reject_unknown_client_hostname" and "reject_unknown_reverse_client_hostname"
> behavior, when passing names via XCLIENT but not via postfix resolver.
>
> Wietse Venema ?
So how postfix interprets NAME and REVERSE_NAME?
I want to understand, how not to break, for example, "reject_unknown_client_hostname" and
"reject_unknown_reverse_client_hostname" behavior, when passing names via XCLIENT but not
via postfix resolver.
Wietse Venema пишет:
Artem Bokhan:
>XCLIE
Artem Bokhan:
> >XCLIENT NAME ADDR PROTO HELO REVERSE_NAME
>
> Do NAME and REVERSE_NAME from XCLIENT agree with this description from
> smtpd_peer.c ?
NAME agrees with the XCLIENT documentation - it is meant to be
something that other MTAs can implement too so it must not depend
on Postfix impl
31 matches
Mail list logo
