the statistics-page of the webinterface gives me information on
Total Incoming Mails
Total Outgoing Mails
practically the same information is sent in the daily "status reports"...
well, the documentation says:
and i said:
so afaict, the SMTP whitelist does not fit my bill.
it seems to be mostly targetted at SMTP hosts that are setup as mail forwarders towards the PMG and which can be "fully trusted" (e.g. because they are under your control).
i do love greylisting, but:
is there a way to bypass greylisting for some hosts/networks?
the obvious problem is with large providers (outlook, googlemail, gmx,...) that keep resending from different IPs, thus keeping the mail in the greylisting for ages.
i know i can whitelist hosts, but...
the problem seems to be, that spamcop.net used to be a very reliable service and has vanished without warning or announcment into thin air this sunday morning.
See the Reddit and WikiPedia articles.
The way this was done looks actively hostile (and it took me ages to debug, with many...
@Stoiko Ivanov ich glaube, ich habe jetzt (nachdem ich debugging hochgedreht habe) eine spur, leider noch keine lösung...
remote verwendet Microsoft SMTPSVC als outgoing SMTP-server
scheinbar bevorzugen MS-SMTP-server BDAT anstelle von DATA
PMG/postfix announced CHUNKING (also BDAT-support)...
ja, das whitelisting wurde über "GUI->Configuration->Mail Proxy->Whitelist" gemacht.
ich werde mir mal debug_peer_list ansehen (blöderweise kann ich keine mails vom sender triggern...)
und ja, ein SMTP server der nur 2 minuten lang probiert ist "etwas seltsam", aber was soll ich tun ;-)
wir haben ein kleines problem mit einem sender network, wodurch von unser "Community Subscription" PMG installtionen keine emails von dort angenommen werden.
der sender ist "editorialmanager.com" (ein publisher für akademische journals), deren outgoing mailserver sind...
in the meantime i've patched my local postfix template (as i have overridden it to get before-queue working, i figured an update in the repository wouldn't help me much anyhow :-)), and it seems i can get posts
aha, here's a hint (transport private/scan: Connection refused)
Jan 27 13:45:13 mailgate postfix/qmgr: A3863205CE: from=<email@example.com>, size=772, nrcpt=1 (queue active)
Jan 27 13:45:13 mailgate postfix/qmgr: warning: connect to transport private/scan: Connection...
i'm running PMG-6.1-3, with before queue spam-filtering enabled.
since some time (probably about the same time as i enabled before queue, but i don't really remember), it seems that the mailgateway is unable to send administrative emails any more.
PMG is mailgate.example.com, and it's...
hard to tell, as i only get a notification after the fact
which parts do you want? what time-frame? which services?
i already attached an anoymized 2-line excerpt to the original question
26 inet n - - - 100 smtpd
since i've enabled the "before queue" filtering, i get notifications of smtp-errors every now and then:
the sender/receiver/sending-host tuple looks like totally legit (and includes "trusted" mailserverse; "trusted" in the sense that i trust them to do a good job and not send out spam; but not...
so you subscribed to legit newsletters, and receive the emails you asked for and then you wonder why?
for me it sounds like everything is working as expected.
(a "newsletter" is not necessarily spam; esp. if you can sign up manually)
I ended up with rewriting the header-field in the receiving (final) mailserver, replacing * with +.
Something like the following:
- In PMG, add a rule that adds __SPAMSTARS__ to the X-proxmox-Spam-Level header-field.
- in exim, add a data-ACL (acl_check_data, or via CHECK_DATA_LOCAL_ACL_FILE)...