On Tue, 10 Apr 2018, Rupert Gallagher wrote:
Microsoft shits on your head, and you pay for it. Go on, enjoy it.
On Tue, Apr 10, 2018 at 17:19, Reindl Harald wrote:
Am 10.04.2018 um 17:17 schrieb Rupert Gallagher: > Microsoft should be blacklisted globally, until they fix
their > own softwar
Microsoft shits on your head, and you pay for it. Go on, enjoy it.
Sent from ProtonMail Mobile
On Tue, Apr 10, 2018 at 17:19, Reindl Harald wrote:
> Am 10.04.2018 um 17:17 schrieb Rupert Gallagher: > Microsoft should be
> blacklisted globally, until they fix their > own software. go on - you
>Microsoft should be blacklisted globally, until they fix their own software.
They even change the order of many headers (Receiveds included) remove the
ones they do not like, etc... i am sure they like playing dices...
PedroD
Microsoft should be blacklisted globally, until they fix their own software.
On Tue, Apr 10, 2018 at 16:00, Sebastian Arcus wrote:
> Hence why I have to have a local whitelist and skip verification for all MX's
> of the form *.outlook.com (which include Microsoft cloud hosted domains).
On 10/04/18 08:41, Daniele Duca wrote:
On 09/04/2018 20:40, Sebastian Arcus wrote:
This might not really answer your question, but I've had really good
results leaving all this to the MTA (Exim in my case). I actually go
for the whole hog full callout verification - checking with the MX
th
On 09/04/2018 20:40, Sebastian Arcus wrote:
This might not really answer your question, but I've had really good
results leaving all this to the MTA (Exim in my case). I actually go
for the whole hog full callout verification - checking with the MX
that the sender really exists. I know that
On 09/04/18 15:24, David Jones wrote:
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer but
it could be useful in meta rules.
This might
On Mon, 9 Apr 2018 09:24:23 -0500
David Jones wrote:
> I was wondering if anyone knows of an SA plugin or another method to
> determine if the envelope-from domain has a valid MX record that is
> listening on TCP port 25. I don't think it would be a major scorer
> but it could be useful in meta
Kevin A. McGrail skrev den 2018-04-09 16:46:
If you are interested, let me know.
i am interested to learn how to setup mimedefang, not how to test mx :=)
that will always be a job for mta to make sure this is valid
David Jones skrev den 2018-04-09 16:24:
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer
but it could be useful in meta rules.
thats a job
On 09/04/2018 16:24, David Jones wrote:
Been playing around with rspamd over the weekend to see how it
compares and so far not that impressed. It has a few features that
are interesting like the MX check but other than that it's not as
impressive as the author makes it out to be on the webs
Well, here's the code I use in filter_sender in MD to check for a validMX.
The module needs a public release with some updates and doesn't work great
with IPv6 but the code is solid and been in use for a long time at my firm.
#IF NOT A BOUNCE, THEN CHECK VALID MX RECORDS
if ($sender ne '<>') {
On 04/09/2018 09:58 AM, Dianne Skoll wrote:
On Mon, 9 Apr 2018 09:56:20 -0500
David Jones wrote:
On 04/09/2018 09:44 AM, Reindl Harald wrote:
you simply don't want connect to every innocent MX which inbound
mail is forged because for the sake of god you are attacking the
victim of spoofed mai
On Mon, 9 Apr 2018 09:56:20 -0500
David Jones wrote:
> On 04/09/2018 09:44 AM, Reindl Harald wrote:
> > you simply don't want connect to every innocent MX which inbound
> > mail is forged because for the sake of god you are attacking the
> > victim of spoofed mails and you are easily part of a di
On 04/09/2018 09:46 AM, Kevin A. McGrail wrote:
Hi Dave,
I do similar work in MIMEDefang using the a redis backend for caching
valid recipients combined with Net::validMX that can check to see if a
sender has valid MX before sending. I have a release of Net::validMX
I'm about to post this we
On 04/09/2018 09:44 AM, Reindl Harald wrote:
Am 09.04.2018 um 16:24 schrieb David Jones:
I was wondering if anyone knows of an SA plugin or another method to
determine if the envelope-from domain has a valid MX record that is
listening on TCP port 25. I don't think it would be a major scorer
Hi Dave,
I do similar work in MIMEDefang using the a redis backend for caching valid
recipients combined with Net::validMX that can check to see if a sender has
valid MX before sending. I have a release of Net::validMX I'm about to
post this week in fact.
If you are interested, let me know.
Reg
17 matches
Mail list logo