Recent content by qbercik

I run smtp daemon in verbose mode (smtp -v in master.cf) and logs point me to `postfix/postscreen`. I run connection from one of new hosts (new in this way, that I didn't connect to this smtp server before): 1 connection: $ nc -v 3.238.134.126 25 Connection to 3.238.134.126 25 port [tcp/smtp]...

AWS environment probably not as there is no load balancer at front. I run few portfix servers as well and non of them have this issue. I did another very basic deployment on Debian 10 in AWS N.Virginia (AMI ID: ami-0b493722cea9f95f6) EC2 instance t3.medium (2vpcu, 4GB RAM). Very dirty...

netcat against localhost is fine: $ nc -v 127.0.0.1 25 localhost [127.0.0.1] 25 (smtp) open 220 smtp1.example.com ESMTP ^C This deployment is done in AWS on Debian 10. I made another deployment and situation is this same. 1st connection from new host do this "220-" and after "220 ". After...

This is how it's looks in my situation: $ nc -v -w1 10.56.68.12 25 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 10.56.68.12:25. 220-smtp1.example.com ESMTP 220 smtp1.example.coml ESMTP ^C and since now, for another 24 hours I will only get reposes with "220 " code: $ nc -v...

Hi, I deployed Proxmox Mail Gateway 6.3 and so far it's working well in my test environment. I want to monitor this smtp service using Zabbix simple check, but there is a problem. Zabbix simple check expect "Service Ready" response from server in format "220 ", but when I connect to Proxmox...