Hi,
I have a probably unusual request.
For pedagogical reasons (teaching "network"), I would like the postfix
server of my classroom to be as much verbose as possible on its smtp
port (i.e. like sendmail use to be)
I mean: comprehensive help messages on the "help" command, explicit
errors message
Hi
I need to limit the domains in "mail from" for autenticated users to
prevent sending emails with a "third party" domain. I have read the
documentation and did not reached any conclusion.
My best guess is that is some configuration that may be passed as an
option to submission and smtps.
Hi,
did you already ctrl+f for 'reject_sender_login_mismatch' and
'smtpd_sender_login_maps' in http://www.postfix.org/postconf.5.html
?
regards,
Max
On 28/09/2021 13:36, João Silva wrote:
Hi
I need to limit the domains in "mail from" for autenticated users to
prevent sending emails with a
On 2021-09-28 at 03:50:11 UTC-0400 (Tue, 28 Sep 2021 09:50:11 +0200)
Christophe Lohr
is rumored to have said:
Hi,
I have a probably unusual request.
For pedagogical reasons (teaching "network"), I would like the postfix
server of my classroom to be as much verbose as possible on its smtp
port
I have been reading the documentation for smtpd_sender_login_maps and
for what i understood I must create a db of the form
@domain user1,user2
From the docs:
"In all cases the result of table lookup must be either "not found" or a
list of SASL login names separated by comma and/or whitesp
I have been reading the documentation for smtpd_sender_login_maps and
for what i understood I must create a db of the form
@domain user1,user2
From the docs:
"In all cases the result of table lookup must be either "not found" or
a list of SASL login names separated by comma and/or whitespac
On 28/09/2021 14:41, post...@ptld.com wrote:
I have been reading the documentation for smtpd_sender_login_maps and
for what i understood I must create a db of the form
@domain user1,user2
From the docs:
"In all cases the result of table lookup must be either "not found" or
a list of SASL
On Tue, Sep 28, 2021 at 09:50:11AM +0200, Christophe Lohr wrote:
> Well.. so, my question is: how to configure postfix to be more verbose?
> (not in the log files, but on the smtp connexions)
This would be a programming exercise. The relevant source files are:
src/smtpd/smtpd.c -
On 28.09.21 14:31, João Silva wrote:
I have been reading the documentation for smtpd_sender_login_maps and
for what i understood I must create a db of the form
@domain user1,user2
From the docs:
"In all cases the result of table lookup must be either "not found" or
a list of SASL login n
Viktor Dukhovni:
> Most likely it is easier to just write a Perl or Python script, or
> Haskell or Go program that is an ESMTP server that emits detailed error
> messages. Choose a language in which it is easy to write a parser that
> emits detailed error diagnostics.
I would suggest using a stat
On 28/09/2021 15:42, Matus UHLAR - fantomas wrote:
On 28.09.21 14:31, João Silva wrote:
I have been reading the documentation for smtpd_sender_login_maps and
for what i understood I must create a db of the form
@domain user1,user2
From the docs:
"In all cases the result of table lookup
On 9/28/21 10:23 AM, Viktor Dukhovni wrote:
On Tue, Sep 28, 2021 at 09:50:11AM +0200, Christophe Lohr wrote:
Well.. so, my question is: how to configure postfix to be more verbose?
(not in the log files, but on the smtp connexions)
This would be a programming exercise. The relevant source
On Tue, Sep 28, 2021 at 03:50:06PM +0100, João Silva wrote:
> It would be nice to have a option to specify a list of allowed domains.
This is not meaningful, because the lookup result is a list of SASL
identities, which are just opaque octet strings, there's no notion of
"domain" there.
In fact,
On 28/09/2021 16:39, Viktor Dukhovni wrote:
On Tue, Sep 28, 2021 at 03:50:06PM +0100, João Silva wrote:
It would be nice to have a option to specify a list of allowed domains.
This is not meaningful, because the lookup result is a list of SASL
identities, which are just opaque octet strings,
Jo?o Silva:
> A table with the format
>
> alias@domain alias_owner
>
> is allowed?
You can stick anything in there, but for meaningful results,
- alias@domain must be an envelope sender address, and
- alias_owner must be a SASL login name.
Wietse
On 28/09/2021 17:24, Wietse Venema wrote:
Jo?o Silva:
A table with the format
alias@domain alias_owner
is allowed?
You can stick anything in there, but for meaningful results,
- alias@domain must be an envelope sender address, and
- alias_owner must be a SASL login name.
Wietse
E
Sending to spamassassin group, and no answer will by appair, possible this
are outdated?
Please how I can fix this connection refused, disabling IPv6 also not help.
Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II
Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1
Connection refused speaks to the socket not running. What does netstat -na
report?
-Dan
> On Sep 28, 2021, at 11:38 AM, Maurizio Caloro wrote:
>
> Sending to spamassassin group, and no answer will by appair, possible this
> are outdated?
> Please how I can fix this connection refused, disabl
On Tue, Sep 28, 2021 at 08:38:33PM +0200, Maurizio Caloro wrote:
> Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II
The "spamd" server appears to be running...
> Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed,
> retrying (#1 of 3): Connection refused
> Sep 28
Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1
failed, retrying (#1 of 3): Connection refused
Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1
failed, retrying (#2 of 3): Connection refused
Sep 28 15:11:24 nmail spamc[4525]: connect to spamd on 127.0.0.1
failed,
Yup, either fix spamd so it listens on localhost (you'd see a LISTEN on port
783, which is missing), or correct your spamc flags to include -U
/var/spool/postfix/spamass/spamd.sock
-Dan
> On Sep 28, 2021, at 11:45 AM, Viktor Dukhovni
> wrote:
>
> On Tue, Sep 28, 2021 at 08:38:33PM +0200, Mau
Hello,
When creating /var/spool/postfix/hold as symlink to another folder I get
the following error from Postfix :
* "move to hold queue failed: No such file or directory"
...even when doing "chmod 777" on the target directory.
Do you know if postfix is unable to work with "hold" as symlink
On Wed, Sep 29, 2021 at 01:49:39AM +0200, (lists) Denis BUCHER wrote:
> When creating /var/spool/postfix/hold as symlink to another folder I get
> the following error from Postfix :
If any Postfix services are chrooted, the destination needs to be a
subdirectory of the Postfix queue directory an
On Wed, Sep 29, 2021 at 01:49:39AM +0200, "(lists) Denis BUCHER"
wrote:
> Hello,
>
> When creating /var/spool/postfix/hold as symlink to another folder I get the
> following error from Postfix :
>
> * "move to hold queue failed: No such file or directory"
>
> ...even when doing "chmod 777" o
On Wed, Sep 29, 2021 at 02:19:53PM +1000, raf wrote:
> If you really have a problem that you think would be
> solved by relocating the hold queue, you could mount
> another file system over the hold queue directory.
> That might work. But it might a bad idea. Not sure.
Sorry, not possible. Postf
25 matches
Mail list logo
