First statement: I'm new to Postfix
Second statement: I'm old enough that a 30mb harddrive was big then I started
working with computers ..
The Challenge
I want to be able to run my own "idp" type script when someone tries to connect
to my mailserver. Basically I want to refuse them even a
cure email.
--- Original Message ---
On Tuesday, December 27th, 2022 at 12:07 AM, Rob McGee wrote:
> On 12/26/2022 4:18 PM, mats wrote:
>
> > First statement: I'm new to Postfix
> > Second statement: I'm old enough that a 30mb harddrive was big then
code since it would be running under it's own context?
--- Original Message ---
On Tuesday, December 27th, 2022 at 12:02 AM, Wietse Venema
wrote:
> mats:
>
> > First statement: I'm new to Postfix
> > Second statement: I'm old enough that a 30mb harddr
ould be done to stop local delivery of a message
after the server has gotten code 550 for that message?
/Regards Mats
--
Mats Luspa
Phone: +46 (0)980 79 022
Institutet för rymdfysik Fax: +46 (0)980 79 050
Swedish Institute of Space Physics email: ma...@irf.se
Visiting/Delivery addr
somintefi...@telia.com -> (not found)
mailinfo.log:2015-02-13T16:31:52+02:00 outgoingmail-2
postfix/smtp[7438]: EF63DBD1E:
to=,
relay=mail.telia.com[62.20.233.128]:25, delay=5.4,
delays=0.01/0.01/0.31/5.1, dsn=4.3.0, status=deferred (bounce or trace
service failure)
/Regards Mats
Quotin
tracing it stops working and the (bounce or
trace service failure) reappears.
I hope there is any logical explanation this? I don't want to have the
tracing on to get it to work.
/Regards Mats
Quoting Viktor Dukhovni :
On Fri, Feb 13, 2015 at 05:35:34PM +0100, Mats Luspa wrote:
2015-02
s I put on debugging as I wrote before.
Maybe someone out there experienced the same problem?
/Regards Mats
Quoting Wietse Venema :
Mats Luspa:
Hello again!
This is very strange. When I automatically trace the bounce process
according to the documentation here:
http://www.postfix.org/DEBUG_READM
= 0^M
2015-02-13T23:47:13+02:00 outgoingmail-2 postfix/smtp[10241]:
E87B0BF06: to=,
relay=mail.irf.se[2001:6b0:27:ff::c]:60180, delay=0.13,
delays=0/0/0.01/0.12, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
438F8200D2)^M
2015-02-13T23:47:13+02:00 outgoingmail-2 postfix/qmgr[10234]:
E87B0BF06: removed^M
tem to debug if
you would prefer that. If you are familiar with linux-containers I
could also make a clone and you could get it.
I could also get the source code from the package, compile and add the
debugging code that you mentioned in the mail.
Mail me what method that you want to use.
Ok, thanks for your engagement in this topic. Maybe there can be a
problem with the host kernel also.
I will test to install this as an Docker on the same host machine and
see what happens.
/Regards Mats
Quoting Wietse Venema :
Wietse Venema:
$ uname -a
Linux ubuntu1410 3.16.0-30
Hello!
Thanks for your suggestion. It seems to be some Permission denies in
the trace-file that comes below:
--
read(15, "\27\3\3\0\340", 5)= 5
read(15,
"R_4\322w\5\231\277S\36\306\374\330\217\320$\306\242\247\26
Yes, apparmor is used. But I'm not an expert in configuring apparmor.
But maybe something there is preventing the linux-container to read
some part of the file system that affects postfix.
I must check it.
/Mats
Quoting Wietse Venema :
Mats Luspa:
connect(16, {sa_family=AF_
ned in the text.
One post in the link above claims that the bug has been fixed in
kernel 3.18.0-8.9.
However this is clearly not a postfix issue. I want to thank for the
suggestions and explanations from Wietse V and Viktor D that lead to
the right track to solve this.
/Regards Mats
Quot
]: warning:
inside mail_command_client
2015-02-15T17:51:31+02:00 outgoingmail-3 postfix/smtp[10831]: warning:
read public/flush socket: Permission denied
2015-02-15T17:51:31+02:00 outgoingmail-3 postfix/smtp[10831]: warning:
6D78614224: flush service failure
Quoting Wietse Venema :
Mats Luspa:
Y
14 matches
Mail list logo
