to configure this limit would cater to a broader range of user
requirements.
Your understanding is much appreciated.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Jaroslaw Rafa via Postfix-users"
An: "postfix-users"
Gesendet: Donnerstag, 25. Januar 2024 10
on their specific
needs sounds like a pragmatic solution. This approach would provide flexibility
for users who wish to log extensive information, such as antispam symbols in
headers.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Gerald Galster via Postfix-users"
An
(with some delay) remains the most effective solution for obtaining
delivery information.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: Viktor Dukhovni via Postfix-users
An: postfix-users@postfix.org
Gesendet: Wed, 24 Jan 2024 16:38:05 +0100 (CET)
Betreff: [pfx] Re: Feature
a clearer perspective.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Wietse Venema via Postfix-users"
An: "Postfix users"
Gesendet: Mittwoch, 24. Januar 2024 14:37:34
Betreff: [pfx] Re: Feature Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT
and custom builds.
I appreciate your input and encourage discussions that contribute to the
improvement of open-source projects like Postfix.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Jaroslaw Rafa via Postfix-users"
An: "postfix-users"
Gesendet: Mittw
requirements,
logging detailed header information becomes crucial. The existing limit can
pose challenges in capturing and analyzing essential data for these purposes.
I appreciate your consideration of these use cases and their implications.
Best regards,
Matthias Schneider
- Ursprüngliche
urge you to consider incorporating this enhancement into future
releases, as it would undoubtedly enhance the Postfix experience for users with
similar needs.
Thank you for your time and consideration.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Wietse Venem
.
Best regards,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Wietse Venema via Postfix-users"
An: "Postfix users"
Gesendet: Montag, 22. Januar 2024 16:14:03
Betreff: [pfx] Re: Feature Request: Adjustable Header Log Size Limit in
INFO/WARN/REJECT Header_Check
Sorry,
Hi,
i think this has something todo with smtpd_tls_fingerprint_digest:
smtpd_tls_fingerprint_digest = ${{$compatibility_level}
An: "postfix-users"
Gesendet: Montag, 22. Januar 2024 15:44:40
Betreff: [pfx] Enabling TLS1.3 and allow sending over SMTPS/465
Hi,
Two questions really, one
can receive the full header key/value by using the milter
protocol, but this can only be done synchron and not asynchron via log file
parsing.
I appreciate your consideration of this request and thank you for your ongoing
dedication to Postfix de
Thanks Wietse for your help.
before patch:
16:50:57.609 Recv body (104 MB): 0:01:07.126
after patch:
16:52:16.248 Recv body (104 MB): 0:00:00.361
Matthias Schneider
Am 20.08.19 um 16:27 schrieb Wietse Venema:
Matthias Schneider:
I have tested your patch, it's working fine. The speed
I have tested your patch, it's working fine. The speed is like unix socket!
Any chance it will go into next release?
Matthias Schneider
Am 20.08.19 um 15:47 schrieb Wietse Venema:
Matthias Schneider:
Once i do "ip link set dev lo mtu 21845" i will get vstream_tweak_tcp:
TCP_MA
.
I also get TCP_MAXSEG 21845 on a newly launched VPS on a cloud provider
(loopback mtu 65536).
net.ipv4.tcp_congestion_control = cubic
but i have tried "reno" too, no difference. I have no idea where the mtu
/ 3 happens.
Thanks
Matthias Schneider
Are you on PPPoE or some ot
he 64k packet
https://github.com/mschneider82/milter/blob/b4a6d7c78ac39b8a1d71b53b74bc08d95652d310/session.go#L101
Best regards
Matthias Schneider
Am 19.08.19 um 20:05 schrieb Wietse Venema:
Matthias Schneider:
Hi Wietse,
I suspect that the bottleneck is on the receiving side.
- Maybe the
connection in postfix?
Matthias Schneider
After switching from tcp to unix socket, postfix as milter client is
fast like a rocket (less than a second).
Just wondering which tcp parameter causes the long delay
Matthias Schneider
Am 19.08.19 um 10:34 schrieb Matthias Schneider:
Chris, can you tell me your postfix version/settings
Chris, can you tell me your postfix version/settings?
When i do a load-test on my milter application, i can also get 100mb in
about a second proceesed (with 65535 sized chunks).
But postfix (3.3.0 and 3.4.5) only sends about 24 body chunks per second
to my milter application. Its the only
ementation:
https://github.com/mschneider82/milter/blob/master/session.go#L288
I think the problem is that every chunk needs to be accepted by the milter.
109.999.104 bytes / 65535 = 1679 accepts
I have the same speed issue in the java library too.
Best regards
Matthias Schneider
be comparable)
Best regards
Matthias Schneider
Am 16.08.19 um 15:50 schrieb Wietse Venema:
On the Postfix side, edit src/milter/milter8.c and update its
MILTER_CHUNK_SIZE definition accordingly. It's only compile-time
configurable in Postfix, because it's only compile-time configurable
in libmilter
,
Matthias Schneider
Am 16.08.19 um 15:32 schrieb Matthias Schneider:
Any chance to get a config for MILTER_CHUNK_SIZE? It would be great so
have an easy and fast switch. I may have different settings on
different mail systems (because of 3rd party milters), its hard to
manage different customized
,
Matthias Schneider
Hi,
is it possible to configure a LMTP only server as relayhost= in postfix?
I'd like to relay all mails to my local lmtp server
Best Regards,
MS
/postfixstdoutlogger/
Best Regards
Matthias Schneider
The postfix-3.4.3-HISTORY file seems to be uptodate with latest changed
date 20190310
Am 14.03.19 um 10:10 schrieb Matthias Schneider:
Hi,
I just wanted to check the newest changes but the file is missing on
every mirror.
The requested URL
/mirrors/postfix-release/official/postfix
Hi,
I just wanted to check the newest changes but the file is missing on
every mirror.
The requested URL
/mirrors/postfix-release/official/postfix-3.4.4.RELEASE_NOTES was not
found on this server.
Can you please update the release notes?
Best regards
Matthias Schneider
: Connection refused
Aug 17 16:49:57 mta01 postfix-10.223.1.218/smtp[14811]: 3xY8Hj5zmDzDxjx:
to=<badr...@tempfail.example.com>, relay=none, delay=36,
delays=36/0/0/0, dsn=4.4.1, status=deferred (connect to
127.0.0.1[127.0.0.1]:25666: Connection refused)
Best regards
Matthias Schneider
, the last sendmail version I
tested had no curly brackets.
In the meanwhile we will update our internal milter class to support
both formats, but the {} may also broke other milter libraries.
Viktor, Wietse, Thank you for support!
Best regards
Matthias Schneider
sing default \"%s\"", myname, value);
argv_add(argv, name, value, (char *) 0);
}
}
myfree(saved_names);
vstring_free(canon_buf);
return (argv);
}
Thank you,
Matthias Schneider
- Ursprüngliche Mail -
Von: "Viktor Dukhovni&
.1:
6ZH.6ZHkDR{i}.3vN6VP5LlPz24hjY.{rcpt_addr}.matthias.schneider@
Thanks
Matthias Schneider
t (250 2.0.0 Ok: queued as
B15171A072C)
Is there a easy way to add this to smtp.c ?
Best Regards,
Matthias Schneider
Am 04.01.2016 um 15:29 schrieb Wietse Venema:
Matthias Schneider:
Hi,
I would like to have the TLS state of a message in the final status=send
log line.
Currently the TLS information is only findable by searching for the
smtp[pid],
on big mail logs this can result in many false positive search
the same (old?) version: Microsoft ESMTP
MAIL Service, Version: 6.0.3790.4675
Maybe there is a way to disable STARTTLS when this prompt is shown?
Best regards
Matthias Schneider
regards, Patrik.
Hello,
try:
openssl x509 -in cert.pem -fingerprint
on my system the returned SHA1 fingerprint is the same as in posttls-finger
Best regards,
Matthias Schneider
for smtp_tls_session_cache_database ? Can anyone
show me a config example?
Thanks!
Matthias Schneider
On Fri, Nov 14, 2014 at 10:10:52AM -0500, Wietse Venema wrote:
Matthias Schneider:
Hello,
I had a very high I/O load on process tlsmgr because the smtp_scache and
smtpd_scache files are written to often (smtp_scache.db ~70mb) .
data_directory = /var/lib/postfix
On Fri, Nov 14, 2014 at 05:22:34PM +0100, Matthias Schneider wrote:
Hello Viktor,
since my server is more smtp client than smtpd i have to tune the
smtp_tls_session_cache_database setting, do you recommend to set
smtp_tls_session_cache_database to empty or using a memcache server
: name_mask: all
postmap: inet_addr_local: configured 3 IPv4 addresses
postmap: inet_addr_local: configured 7 IPv6 addresses
postmap: dict_open: pcre:/etc/postfix/milter_header_checks
postmap: dict_pcre_lookup: /etc/postfix/milter_header_checks: a@bc
REJECT
Best regards
Matthias Schneider
please note that pcre is working fine with normal header_checks, the
problem is just with milter_header_checks :
# postconf -m
btree
cidr
environ
fail
hash
internal
memcache
nis
pcre
proxy
regexp
sdbm
socketmap
sqlite
static
tcp
texthash
unix
what does postconf -m list - most likely not pcre
i searched the code what returns the error, hope this will help.
if you have any suggestions or experimantal code changes i'll compile
and test them
with my addheader milter.
Best regards
Matthias Schneider
cleanup_milter.c:
381 static int cleanup_milter_header_checks(CLEANUP_STATE *state
I found a solution, turning off chroot for cleanup in master.cf
cleanup unix n - n - 0 cleanup
this should be added to the documention:
http://www.postfix.org/postconf.5.html#milter_header_checks
40 matches
Mail list logo
