Hi list,
for some weird reasons...
... I need to know the date where a mail was sent
by the previous host (in the mail header chain) to
our MTA.
From checking HeaderEval.pm I conclude that:
(if I'm correct)
date_received -> gives me the date where my MTA
did accept/take the
Hi Bowie,
On 18.02.2011 15:10, Bowie Bailey wrote:
[...]
You want the date the mail was sent to your MTA? How is that different
than the date it was received by your MTA?
No - this would be really the same then. :)
But let me clarify...
... each received header contains the date where a mail
Hi Bowie,
hi list,
On 18.02.2011 16:25, Bowie Bailey wrote:
[...]
That information should be in the headers. For example, from your email:
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 14:39:31 +
It
Hi list,
Ok - think of it as beeing solved.
I could make something 'useful' after
digging more in HeaderEval.pm.
But later then... this raises another issue.
I'll open a separate thread on this one.
Thanks.
frank\
--
43rd Law of Computing:
Anything that can go wr
fortune: Segmentation
f'ed both rulesets - but I cannot spot anything useful.
Thanks for your kind attention - any help is appreciated!
cheers,
frank\
--
43rd Law of Computing:
Anything that can go wr
fortune: Segmentation violation -- Core dumped
##
# Frank Reppin
## get delivery timings...
#loadplugin D
On 19.02.2011 23:41, mouss wrote:
Le 19/02/2011 04:58, Frank Reppin a écrit :
Hi list,
Ok - think of it as beeing solved.
I could make something 'useful' after
digging more in HeaderEval.pm.
did you take a look at the code that implements DATE_IN_FUTURE_* rules?
Yes - this was qu
hi list,
it all comes down to this single rule:
ifplugin Mail::SpamAssassin::Plugin::HeaderEval
header __RCVD_IN_2WEEKSeval:received_within_months('0', '0.46')
describe __RCVD_IN_2WEEKS Received: within the past 2 weeks
endif
which was removed in '72_active.cf' in the most current
SMTP; 11 Apr 2013 17:50:16 +0200
MY MAIL SERVERS detects the DYN IP and triggers the wrong rules.
given this example - you're probably looking for the
notfirsthop
or
lastexternal
features from Mail::SpamAssassin::Conf(3).
cheers,
Frank Reppin
--
43rd Law of Computing:
Any
reylisting.
However - we've got it sorted with them quite fast
after I've notified them via
del...@messaging.microsoft.com
about this issue.
HTH,
Frank Reppin
On 8/19/15 3:57 AM, Marc Perkel wrote:
Not quite sure who to ask so I'm hoping to get lucky here.
I'm in the fr
