['noDKIMAddresses','Do not any DKIM Check for this Addresses *',
'Mail from any of these addresses will not be tagged and checked for
DKIM. Accepts specific addresses (u...@domain.com), user parts (user)
or entire domains (@domain.com).'
Description suggest that noDKIMAddresses is only for sende
[feature suggestion] dkim spam lover - don't do dkim test for
specified recipient
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, a
missing option - noSpoofingCheckNP - Do noSpoofing for no processing.
Since noProcessingTo is missing since assp 1.x noSpoofingCheckNP is
very much needed because if you define local adress in noProcessing
then if sender spoofs this local sender adress it will get delivered
to any mailbox at the
2016-03-10 16:19:43 23183-510279 [Worker_1] 198.2.183.126
to:
g...@aa.com DKIM-Signature found
2016-03-10 16:19:43 23183-510279 [Worker_1] 198.2.183.126
to:
g...@aa.com info: domain officevibe.com has published a DMARC record
2016-03-10 16:19:43 23183-510279 [Worker_1] 198.2.183.126
to:
g...@aa.
2016-02-25 7:58 GMT+01:00 Thomas Eckardt :
>>DoNoSpoofingMXIP - option to do DoNoSpoofing test only if A record of
>>any MX record of recipient domain is in the list of LocalMXips
>
> So you would have to maintain 'LocalMXips' and 'localDomains' instead only
> 'localDomains'
>
> I can't see an
>>Why should anyone wants to disable this check,
>>if the sender and recipient domain are different localDomains?
You know that your domain is localdomain (since you are recieving mail
on it) but you can't be really sure if other domains in localDomain
list are still localDomains - it this list ac
er know about this feature. Even he reads the SPF
> RFC's , he can never know that assp can do a SPF-check for header
> addresses.
>
> Thomas
>
>
>
> Von:"krz...@gmail.com "
> An: ASSP development mailing list
> Datum: 25.02.2016 00:17
&
[feature suggestion] DoSPFinHeader activated per local maibox =
recipient basis (testing all senders) - allow mailbox user to chose if
he wants it or not.
--
Site24x7 APM Insight: Get Deep Visibility into Application Perfo
[feature suggestion] separate DoSPFinHeader and blockstrictSPFRe
Currently if you want to spf test From header (DoSPFinHeader) you have
to do strict testing (which means ~all is seen as -all).
--
Site24x7 APM Insight: Get
[feature suggestion] option to do DoNoSpoofing only if sender domain
if same as recipient domain
reason: For me its pretty much only usefull scenario for DoNoSpoofing.
Spamers often set From header adress in domain same as recipient
domain so it blocks a lot of spam. I personaly don't care about
bl
DoNoSpoofingMXIP - option to do DoNoSpoofing test only if A record of
any MX record of recipient domain is in the list of LocalMXips
reason: DoNoSpoofing is executed for localDomains list. On larger
system its quite impossible to know when domain that you put in
localDomains has been since changed
2015-05-10 14:17 GMT+02:00 Thomas Eckardt :
> How looks the .eml file stored by assp?
so far I only recieved information about such cases when noprocessing
- and I think assp does not store noprocessing emails (?) - at least
there is no info on log about it.
2015-05-10 01:20:42 13641-1158621 [Wor
I'm getting multiple reports that assp is destroying their messages,
even though they are on noprocesslist. Assp seems to add Recieved
header in the body of the message, while body is overwriten. All
messages I got are without To header and all end in "Message-ID:
<3[10"
X-Account-Key: account6
X-
There were 2 issues at work here but mosty as I discovery now blackRe is
aplied even is recipient is at processOnlyAddresses
If it is intended then description really could do with an improvement
because "If an incoming email matches this Perl regular expression it will
be strictly considered spam"
There were 2 issues at work here but mosty as I discovery now blackRe is
aplied even is recipient is at processOnlyAddresses
If it is intended then description really could do with an improvement
because "If an incoming email matches this Perl regular expression it will
be strictly considered spam"
poTestMode=1
recipi...@domain.com is not on processOnlyAddresses
X-Assp-Version: 2.4.4(15106)
bombReNP=0
following emails shold be noprocessing but are not for unknown reason. Why
could that be?
email 1:
2015-04-22 14:02:13 04133-2535013 [Worker_5] [TLS-in] 108.174.3.154 <
s-4s34c6qkst1a7xh4me8si
his solves the problem for the not existing local addresses. The behavior
> in case of multiple valid envelope recipients is not changed.
> This code change requires to validate recipients with assp
> (localaddresses_flat, LDAP, VRFY) !
>
> I'm thinking about to remove this featur
g
was aplie.
2015-04-16 17:44 GMT+02:00 krz...@gmail.com :
> Although this information is nowere in assp log but in headers of that
> email I see that this email (X-Assp-Intended-For) was sent to many other,
> non existent, adreses in @domain.pl. I'm guessing that assp proxies email
Although this information is nowere in assp log but in headers of that
email I see that this email (X-Assp-Intended-For) was sent to many other,
non existent, adreses in @domain.pl. I'm guessing that assp proxies email
because these non-exising adresses were not on processOnlyAddresses - but
how co
ASSP version 2.4.4(15106) (todays release);
problem with poTestMode is still occuring. With patch proposed by me it
also occured apparently - so problem is probably some else in the code.
2015-04-16 16:07:26 [Worker_2] adr...@domain.pl matches adr...@domain.pl in
processOnlyAddresses
2015-04-16
personal blackRe and whiteRe (per recipient) in future maybe...?
(same way whiteListedDomains works)
\breplica watches\b|\bMegaDik\b=>*@any_local_domain
\breplica watches\b|=>u...@localdomain.com
--
BPM Camp - Free Virtual
>
> The MTA should parse the first 'RECEIVED' line to get these information.
Of course, it could, it should, but you know what mta are - dinosaurs.
Doing anything on mta level is sooo hard (and thats why assp is designed to
work before mta).
---
>
> ASSP uses SenderBase or WHOIS-IP to do the same (getting the country
> .. of a connected IP).
my system of geoip check is only for authenticated smtp users. That means
this is not anitspam system but a anti-abuse, hack-detection system for
smtp accounts. Smtp users can set for their accou
There is a need to pass IP od client to mta. I'm using this for
implementing geo-ip scan for smtp authenticated users at mta level (also
that would be nice functionality for assp maybe). I'm using modification to
hello passed to mta:
@@ -19703,9 +19703,11 @@
$l .= "\r\n";
}
ected.
>
> >and also sent to sendAllSpam
>
> Yes, this is by design. There is no special collection rule for the case
> (spam/discard.. and forward spam) if a spamlover is detected.
>
> Thomas
>
>
>
> Von:"krz...@gmail.com "
> An: ASSP deve
allow literal LOCALUSER in SpamError , SenderInvalidError and bombError
why?
for example to allow those error messages to have url-s for web auto
whitelist system, for example: http://domain.org/whitelist.php?e=LOCALUSER
--- assp.pl-old 2015-04-13 21:31:31.0 +0200
+++ assp.pl 2015-04-
>> I don't think that this is true - but simply show the log (set
>> ConnectionLog + SessionLog high) for such a mail
verbose logging revealed cause of this issue (not all emails marked as spam
went to sendAllSpam) (issue of spfSpamLovers not always working is still
mystery to me):
mta closed con
think that this is true - but simply show the log (set
> ConnectionLog + SessionLog high) for such a mail. Means, a mail that is
> blocked in the body part (NOT the header).
> How ever keep in mind, that there are several exceptions where a blocked
> mail is not forwarded.
>
> Thomas
&g
sting with wildcard option)
I know plenty of users that would be glad to have such test enabled on
their mailboxes (as they don't use mailing list etc).
2015-04-03 20:09 GMT+02:00 krz...@gmail.com :
> It would be great if assp would provide a method for enabling spf
> checking on From header
ASSP version 2.4.3(15075)
When ValidateSPF is in scoring mode spfSpamLovers is not matched and
does not work at all. It should (since all other spamlovers do work in
respective scoring settings)
When ValidateSPF is in block mode spfSpamLovers do work, however if it
matches than scoring spfValence
ASSP version 2.4.3(15075)
When ValidateSPF is in scoring mode spfSpamLovers is not matched and
does not work at all. It should (since all other spamlovers do work in
respective scoring settings)
When ValidateSPF is in block mode spfSpamLovers do work, however if it
matches than scoring spfValence
# check if this email is to be processed at all if in ProcessOnlyTestMode
if( $poTestMode && ! ($this->{noprocessing} & 1)) {
$this->{noprocessing} = 1;
if(matchSL($uh,'processOnlyAddresses')){
$this->{noprocessing} = 0;
$thi
assp 2.4.1(14132) - ok
assp 2.4.3 15059 - broken
assp 2.4.3(15075) - broken:
poTestMode=1
processOnlyAddresses - list of email adresses
after upgrading this configuration does not work anymore. All emails
are proxied through:
[MessageOK] 104.173.215.48 to: bbb message ok - (envelope sender
xxx
It would be great if assp would provide a method for enabling spf
checking on From header (yes, i know, brakes rfc) for specified local
email mailboxes with a possibility of disabling it for specified
sender domains
sugestion for new option:
Additional SPF Check on the Header from for local specif
It appears that "fix" for this issue is switching to database backend
BerkeleyDB or sqlite and switching everything that can be to "DB:".
After that high cpu load is gone, however assp still regulary freezes
as it did before.
2015-03-11 2:25 GMT+01:00 krz...@gmail.com :
&g
It appears that "fix" for this issue is switching to database backend
BerkeleyDB or sqlite and switching everything that can be to "DB:".
After that change so far problem on this server is gone.
--
Dive into the World of P
witch on 'slmatchLogging' , if you try to find out address matching
> problems.
>
> Thomas
>
>
>
>
>
> Von:"krz...@gmail.com "
> An: ASSP development mailing list
> Datum: 27.02.2015 04:51
> Betreff:Re: [Assp-test] processOnl
Does assp provide any method of blocking emails that don't have at all
adress from RCPT TO in To header? If not then I think it should
because spamers are using this method...
--
Dive into the World of Parallel Programming
ddresses')
|| matchSL($uh,'processOnlyAddresses') ) )
{
$this->{noprocessing} = 1;
+$this->{passingreason} = "$uh (RCTP TO adress) is on
procesOnlyAdresses";
}
}
if (matchSL($uh,'spamaddresses')
logfile only adres
from To: header is visible (!!) This huge inconsistency makes such
issue extremly hard to diagnose - it took me over 12 hours.
2015-02-26 20:06 GMT+01:00 krz...@gmail.com :
> Feb-26-15 19:50:43 [Main_Thread] AdminUpdate: [root 87.206.51.160]
> allLogRe changed from &#x
Feb-26-15 19:50:43 [Main_Thread] AdminUpdate: [root 87.206.51.160]
allLogRe changed from '' to 'mc...@aff-ele.com.pl'
Feb-26-15 20:01:30 [Worker_4] mc...@aff-ele.com.pl matches
mc...@aff-ele.com.pl in processOnlyAddresses
Feb-26-15 20:01:30 [Worker_4]
nwbijtor...@zul.com.pl,mc...@aff-ele.com.pl doe
sing. Some are processed and marked as spam.
2015-02-26 17:23 GMT+01:00 krz...@gmail.com :
> processOnlyAddresses = e...@ele.com.pl
> poTestMode=1
> noProcessingDomains=
> noProcessingIPs=
> noProcessing=
>
> This configuration works fine for many emails. Many emails are
> p
this is a clib function). Looks like, this OS function needs
> to constantly reread /etc/localtime .
>
> Switching on 'WorkerLog' and 'SignalLog' to the highest level could help
> to investigate the problem. Enableing 'debug' could also help.
>
> Th
processOnlyAddresses = e...@ele.com.pl
poTestMode=1
noProcessingDomains=
noProcessingIPs=
noProcessing=
This configuration works fine for many emails. Many emails are
processed and goes to spam. However lately spammers figured that using
diffrent MAIL FROM than From header is a nice trick. Those e
A month has passed and not even single suggestion how to debug a
problem. Is assp project dead?
strace made for 10 seconds on server that is not experiencing problem
root@sv1 [/root]# strace -f -p 29554 -c
Process 29554 attached with 8 threads - interrupt to quit
^CProcess 29554 detached
Process
I've tried newest version of assp (ASSP version 2.4.3(14349)). I've
tried perl perl-5.18.2 with fresh set of modules, perl-5.14.4 with
fresh set of modules. No change, still 99% of cpu on server is basicly
consumed by assp.
--
Also C column of ps shows 99 on affected server while on all others
this does not happen, ever. Same thing using atop to monitor -
constant cpu hammering on by assp on server "sv24" (affected one)
root@sv24 [/root]# ps -fu assp
UIDPID PPID C STIME TTY TIME CMD
assp 13522
ource
> temporarily unavailable and it will go back to WAIT.
>
> I do see a lot of gettimeofday in strace too and I think I get a couple
> of minutes delay in things being written to the logs which is odd.
>
> What monitoring service do you have and how does it identify ASSP
I have assp (ASSP version 2.4.1(14132)) running on multiple servers.
Those servers have exacly same configuration, os (mirrored), hardware.
On one of these servers assp is causing high cpu ussage. After
restarting assp cpu usage is rising constantly and "slowly". After
about 4 hours it it 100% on i
There is such whitelisting bug when using DoInvalidFormatHelo. I did
use it to recreate DoIPinHelo functionality and disabled DoIPinHelo,
so I managed to walk around this bug for now.
2014-12-11 6:58 GMT+01:00 krz...@gmail.com :
> DoFakedWL = 1
>
> Dec-05-14 10:33:26 72006-2995428
DoFakedWL = 1
Dec-05-14 10:33:26 72006-2995428 [Worker_2] 178.32.201.69
info: found message size announcement: 1.59 kByte
Dec-05-14 10:33:26 72006-2995428 [Worker_2] 178.32.201.69
Message-Score: added 150 (fiphValencePB) for
Suspicious HELO - contains IP: '171-32-201-69.ovh.net', total score
for
in description? - because it sounds like it defenetly
should be recomended and enabled by default option.
2014-12-07 9:52 GMT+01:00 aquilinux :
> Dumb question: are your helo checks configured not to score/block
> whitelisted?
>
> Regards,
> aqx
>
> Il giorno dom 7 dic 2014 08:15 krz..
ASSP version 2.4.1(14132)
whiteListedDomains contains "sen...@domain.com => *@mydomain.com"
# cat maillog.txt |grep '72006-2995428'
Dec-05-14 10:33:26 72006-2995428 [Worker_2] 178.32.201.69
info: found message size announcement: 1.59 kByte
Dec-05-14 10:33:26 72006-2995428 [Worker_2] 178.32.201.6
ed to move handling of 465 traffic to mta.
2014-05-15 23:50 GMT+02:00 krz...@gmail.com :
> I have problems with listenPortSSL (implicit ssl) in assp. It is
> running fine for about 5-40 minutes usualy and it stops, port accept
> connections but server does not reply nor anything new appear
I really can't get DoReversed test to work. All below IPs has in fact
ptr records. What is wrong?
May-19-14 16:36:00 10158-3578181 [Worker_1] [PTRmissing] 83.19.126.250
to: xxx [monitoring] (PTR missing) - Cache
May-19-14 16:38:10 10289-2484347 [Worker_2] [PTRmissing] 83.219.160.18
to: xxx [moni
: got at least 10 accept errors
at listener 0.0.0.0:465 - assp is unable to renew the listener,
because we are not running as root - assp will skip processing this
listener for 130 seconds from now
2014-05-16 0:24 GMT+02:00 krz...@gmail.com :
> After reducting timeout to 2 seconds there are
After reducting timeout to 2 seconds there are not "Bad file
descriptor" errors in logs, but ssl port still fails after a while
(10-60 minutes). Even od debug 3 it does not show anything relevant in
maillog.txt
2014-05-15 23:50 GMT+02:00 krz...@gmail.com :
> I have problems with
I have problems with listenPortSSL (implicit ssl) in assp. It is
running fine for about 5-40 minutes usualy and it stops, port accept
connections but server does not reply nor anything new appear in assp
log.
I've tried timeout 5,10,300s. Always same thing.
May-15-14 23:14:08 [Worker_1] Error: Wo
Assp 2.x is missing those nice options from assp 1.x:
NotSpamTag 'If an incoming email matches this text string it will be
considered not-spam. This can be used in SpamError to ask for
resending the mail with this text in the subject.
NotSpamTagRandom ASSP will use MSGIDSec to make
a NotSpamTag. T
Block Local Addresses from External Sender Alltogether (DoNoSpoofing,
default=score)
is a nice option with posiblility of scanning From header. However if
you run system where users can "park" (add) any domain to the you
server (this) configuration it is possible that someone will add on
purpose so
After upgrading to newest assp 1.9.9 I found that it is unusable. Assp
performs now
"Suspicious HELO: IP in HELO, default=15 + (fiphValencePB, default=15)"
test for local, authenticated users! and rejects emails with
"Spam Error for Local Messages (SpamErrorLocal)"
even though I don't have enabled
I'm using assp 1.9.9. Collecting spam seems to be scricly connected to
sendAllSpam. If for example some type of spam is set not to be
collected it won't be send to sendAllSpam. Thats not right because I
would like to sendAllSpam to catch all spam but I only want to collect
from specific filters for
Sure I could block it even with iptables. But why? I see there were
many non-crashing mails from this IP in the past. I see also that some
of my users sent mail to this mailserver so I would block their return
comunication chanell.
2013/7/12 Fritz Borgstedt :
> ASSP development mailing list
> sch
My third server is now crashing. Before crash there is only info about
new connection in log.
Jul-12-13 16:22:13 Connected: 176.9.34.204:39200 -> 78.46.170.110:25
(listenPort) -> 127.0.0.1:125
Jul-12-13 16:58:05 Connected: 176.9.34.204:47462 -> 78.46.170.110:25
(listenPort) -> 127.0.0.1:125;
J
So far senders did not retry delivery unfortunetly :( So I don't know
yet if turning off bayesian did any good.
I'll try to get those two emails that crash assp out of recipient
mailbox when (if) they arrive. Too bad that I can't specyfy collection
in assp by sender adress. I had this crashing issu
I dont want to blacklist sender nor close transmision for him. This is
not an attack. I recognise sender adress and not-spam (ham)
newsletter. I've got on another server assp crashing too - also after
bayesian, with other sender. I'll try to get this email so problem can
be fixed.
If assp has probl
I dont want to blacklist sender nor close transmision for him. This is
not an attack. I recognise sender adress and not-spam (ham)
newsletter. I've got on another server assp crashing too - also after
bayesian, with other sender. I'll try to get this email so problem can
be fixed.
If assp has probl
I think this might be connected to
http://www.perlmonks.org/?node_id=1030569
somebody says there that perl 5.17 broke "use re 'eval'"
--
See everything from the browser to the database with AppDynamics
Get end-to-end visib
Lets start again.
I've taken now
http://switch.dl.sourceforge.net/project/assp/ASSP%20Installation/ASSP%201.9.X/ASSP_1.99_13189_install.zip
It works ok with older perl v5.8.8
I've tried running with newer perl v5.18.0 (thinking that this might
help my other issue). It crashes after 1-2 minutes of
~95% (but not all) segfaults (crasheh) occured after " Bayesian Check
- Prob: 0.0". I've tested with "stock" spamdb - same thing. I've
disabled bayesian filtering now - we'll see if assp stop crashing. Is
there any way to collect by assp this email from
e-biule...@elektroinzynieria.pl? So far i
that is content of my whiteorg.txt file
\bpaypal\.com
\bfacebook\.com
\bamazon\.com
\bdotpay\.pl
(ends with empty line)
Also line ~18259 of assp.pl look like this:
if ($DoOrgWhiting) {
if ( $orgname =~ ( '(' . $whiteSenderBaseRE . ')' )
|| $domainname =~ ( '('
My assp ASSP Version: 1.99(13183) (and all other previous versions)
(perl v5.8.8) crashes about 8-20 times a day, on 2/10 of my servers.
It is probably specyfic to some incoming connection/email. I can't
trace it. Do you have any suggestions how to trace reason behind seg
fault? Strace run on assp
ASSP Version: 1.99(13183)
crashes with current version of perl - 5.18.0
Jul-09-13 01:45:24 Terminating ASSP: mainloop exception: Eval-group
not allowed at runtime, use re 'eval' in regex
m/((?^:(?is)(\bpaypal\.com|\bfacebook\.com|\bamazon\.com|\bdotpay\.pl)(?{length($1)>32?substr($1,0,32-3).'...'
assp did not crashed one since I've blocked IP by iptables (before it
was 40-60 times a day). So yeah... something in smtp session can crash
assp and logging totaly does not help
--
Everyone hates slow websites. So do we.
I've been using same version of assp for long time on 10 servers. Few
days ago on two servers assp stated to crash (it terminates, without
any message to log) (about 40 times a day). I did not make any
changes. To check if problem was resolved in new versions I've
upgraded to 1.98(13056) but proble
2013/1/7 Fritz Borgstedt :
> The string has a special format: "ip=127.0.0.1 helo=anyhost.local".
> It allows to replace ip or helo or both if keywords ip/helo exist.
>
Ok. I tried puting there
ip=127.0.0.1 helo=anyhost.local
or even
"ip=127.0.0.1 helo=anyhost.local"
but it does not work at all:
also it would be nice if there were separate settings instead of HideIPandHelo
HideIP
and
HideHelo
(in my case I was looking for modyfing helo only - in source code and
I saw there is already HideIPandHelo there (not working at all
however))
---
HideIPandHelo does not work
assp 1.9.8(12363)
Received: from katana ([213.238.74.186] helo=katana) by ASSP.nospam with
ESMTPS(RC4-MD5) (ASSP 1.9); 7 Jan 2013 07:00:49 +0100
katana should here be replaced with text in HideIPandHelo config. It
does not work for some reason. String from Hide
I got no-delay loving enabled on my mailbox. I could try to disable it
for a while (although I prefere it enabled)
Another that got through (no delay was still active)
Return-path:
Envelope-to: ad...@mydomain.org
Delivery-date: Fri, 28 Dec 2012 18:26:50 +0100
Received: from [127.0.0.1] (port=511
Some emails still does not get tagged as spam and I dont know how to
check it out:
Return-path:
Envelope-to: ad...@mydomain.org
Delivery-date: Thu, 27 Dec 2012 14:52:23 +0100
Received: from [127.0.0.1] (port=53243 helo=178.125.132.60)
by sv1.MYDOMAIN.org with smtp (Exim 4.80.1)
(e
Thanks
2012/12/23 Fritz Borgstedt :
> You my set MaxRelayingErrors to an higher value.
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant supp
To clarify that recipient adress was one of hundrets in Cc or Bcc ...
So more verbose rejection message or maybe droping (omiting) that
adress is needed (if in Ccc or Bcc not in To), or maybe even pass to
mta and let it reject with bounce?
--
No, recipient email only "loves" no-delaying (no greylisting). 99%
still gets tagged as spam ok but still there are some unexplained
exceptions. Another:
Return-path:
Envelope-to: ad...@mydomain.org
Delivery-date: Sat, 22 Dec 2012 22:41:44 +0100
Received: from [127.0.0.1] (port=34923 helo=188.50.
Newest assp 1.9.x. Some messages are still not taged as spam even when
above scoring limit
Return-path:
Envelope-to: ad...@mydomain.org
Delivery-date: Sat, 22 Dec 2012 03:58:09 +0100
Received: from [127.0.0.1] (port=41678 helo=114.139.134.236)
by sv1.MYDOMAIN.org with smtp (Exim 4.80.1)
Here are the headers. Similary every 1-4 days one email that should be
tagged as spam gets through, so probably I could find more
Received: from 98.16.151.147 ([98.16.151.147] helo=98.16.151.147) by
sv1.MYDOMAIN.org with SMTP (ASSP 1.9); 12 Dec 2012 00:36:25 +0100
Received: from unknown (H
Yes it is set by to my 50. I like to score high for that. Without it
this message would not be recognized as spam - also also I wasn't for
some reason.
--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Dec-12-12 00:36:26 98.16.151.147 to:
ad...@mydomain.org Message-Score: added 7 for bombSubjectRe: 'waiting
(7)', total score for this message is now 7;
Dec-12-12 00:36:26 [BombSubject] 98.16.151.147
to: ad...@mydomain.org [scoring:7] -- bombSubjectRe: 'waiting (7)' --
[Your new intimate life is w
One could argue that some domain that you placed on such list could
disable you delaying completly by placing there 255.255.255.255/0 but
I guess it is more than unlikely
--
LogMeIn Rescue: Anywhere, Anytime Remote support
Not wise if open to anyone. But this could be info about how to do it
after some authentication and WHO could do it (you are domain owner
and you use 2 servers at two organizations to send emails using From:
and To: to one mailserver that have spf spoofing blocked).
---
I was suggesting that assp read it during it's startup or config
reload, not during smtp session. You could just put don't delay ip
ranges (read from spf record) of domains: gmail.com, amazon.com etc
noDelaySPF
Why delay if you know that these servers will retry later.
How about diffrent SpamError just for DoNoSpoofing? One could explain
how to get yourself into noSpoofingCheckDomain while not confusing
normal false-positive spam sender (which gets SpamError)
--
LogMeIn Rescue: Anywhere,
same thing would be usefull for noProcessingIPs and whiteListedIPs -
read ranges from inputed domains SPFs (not emails there but maybe
facebook.com, twitter.com, ebay.com, youtube.com)
--
LogMeIn Rescue: Anywhere, Anytime
(feature resuest) noDelaySPF
It would read IP ranges from dns spf record (txt) from domains listed
in this field.
You would put there something like gmail.com, ebay.com etc - servers
you know will retry so there is no point in delaying message.
93 matches
Mail list logo
