Always Learning via Exim-users schrieb:
Hi,
> If you reject emails from MTAs having no rDNS or no resolving HELO (or
> EHLO) names or having a HELO name that is different from the sending
> MTA's host name, most of your spam will not reach your users.
Of course I do that!
But unfortunately I al
On 2018-05-26, Jeremy Harris via Exim-users wrote:
> On 26/05/18 15:05, Luca Bertoncello via Exim-users wrote:
>> Well, this "info@"-address is a forward to many recipients, not just one...
>
> Oh, a mail-exploder. OK, no cutthrough routing possible. This is
> effectively a mailinglist, and you
1: By simply dropping the date header and inserting a new with the
server time. Problem solved. If the header was correct, it will still
be correct when replaced.
2: Yeah, but many clients handle date: header astonishly bad too. For
example sorting the email by date: header instead of actual receiv
On Sat, May 26, 2018 at 09:52:28PM +0200, Sebastian Nielsen via Exim-users
wrote:
> How I do to rewrite the date header from email clients in exim4 config
> so it are replaced with the server date/time?
>
> The problem is that some clients and software are submitting an
> incorrect date header (l
I don't reject invalid HELO's or invalid rDNS and get very Little
spam, because I just ban all those shitty TLDs.
I have found out that most spam uses those new shitty TLDs so just
banning these shitty TLDs in the MIME from and MAIL from is a good
solution:
MAIL from stage:
deny
message = B
On Sat, 2018-05-26 at 09:03 +0200, Luca Bertoncello wrote:
> Well, unfortunately this address catches many Spam/junk E-Mails and, of
> course, my Exim (4.88) tries to forward them.
> Virus are blocked and will __NOT__ be forwarded, but Spam is some other and,
> of course, I cannot be sure if an E
On 26/05/18 20:52, Sebastian Nielsen via Exim-users wrote:
> How I do to rewrite the date header from email clients in exim4 config
> so it are replaced with the server date/time?
>
> The problem is that some clients and software are submitting an
> incorrect date header (like 1 jan 1960) causing
How I do to rewrite the date header from email clients in exim4 config
so it are replaced with the server date/time?
The problem is that some clients and software are submitting an
incorrect date header (like 1 jan 1960) causing the email to be
delivered to the bottom of user's clients and sometim
On 26/05/18 15:05, Luca Bertoncello via Exim-users wrote:
> Well, this "info@"-address is a forward to many recipients, not just one...
Oh, a mail-exploder. OK, no cutthrough routing possible. This is
effectively a mailinglist, and you need to put real effort into
curating it. Things like: on t
Jeremy Harris via Exim-users schrieb:
> But you're better-off never accepting the message. Consider doing
> cutthrough-routing for these; this means that if the site you are
> forwarding to (Google) refuses the message even as late as after-data
> (which, given they need to analyse the body, is
> I have an "info@"-address that forwards the E-Mails to other
> addresses, some on them outside my servers.
>
> Well, unfortunately this address catches many Spam/junk E-Mails and, of
> course, my Exim (4.88) tries to forward them.
> Virus are blocked and will __NOT__ be forwarded, but Spam is so
On 26/05/18 08:03, Luca Bertoncello via Exim-users wrote:
> My problem: I have an "info@"-address that forwards the E-Mails to other
> addresses, some on them outside my servers.
>
> Well, unfortunately this address catches many Spam/junk E-Mails and, of
> course, my Exim (4.88) tries to forward t
Hi list!
My problem: I have an "info@"-address that forwards the E-Mails to other
addresses, some on them outside my servers.
Well, unfortunately this address catches many Spam/junk E-Mails and, of
course, my Exim (4.88) tries to forward them.
Virus are blocked and will __NOT__ be forwarded, but
13 matches
Mail list logo