Hello
denySMTPConnectionsFrom has this behavior
IP numbers and Hostnames in noPB, acceptAllMail, ispip, whiteListedIPs,
noProcessingIPs, noBlockingIPs will pass.
Could it be possible to have the behavior above also for
denySMTPConnectionsFromAlways , or at least for ips listed in
Please forget this feature for your environment, I want this feature
exactly as it works. Use the
- Deny Connections from these IP's* (denySMTPConnectionsFrom) instead.
--
Come build with us! The BlackBerry(R) Developer
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
Of course this is just a feeling as I did not check (sniff) the
packets exchanged by the servers. (and pls excuse my bad English)
It is not necessary to sniff. A basic simple telnet session is
sufficient to show the reply.
Quote Fritz It is not necessary to sniff.
Ok, done and confirmed it is working. Thanks Fritz.
Regards,
Fochi
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need
On 10/28/2009 9:38 PM, Hill, Brett wrote:
The point of listing and IP address in denySMTPConnectionsFromAlways is not
to be nice. The only reason any IP address should be in there is because all
it sends is spam. So, if you have listed an IP address in there that may or
may not send spam,
Quote Brett
Another reason denySMTPConnectionsFromAlways was created was to
save processing time and bandwidth
That gets you back to the whole idea of wasting processing time and
bandwidth
Quote Alex Frunza
... I'm not breaking any RFCs if I put an IP in my router's firewall...
IMHO, that
I've tried the new 1.6.0 (0.4.07) and it is almost there:
The log now shows the [SMTP Error] 554 5.7.2 Service denied
message. That is good.
But the sending server persists retrying till the timeout.
The same server acknowledges immediately when it receives a
(SpamError) 554 5.7.1 Mail
I see that a new parameter (DenyError) was introduced.
But I did not see it working yet.
Please let me know if I missed anything or what I should do to enable
the use of (DenyError).
The lines bellow are the only log files I see for IP blocked by
denySMTPConnectionsFromAlways
2009-10-28
Hilário Fochi Silveira wrote:
In my tests, when I use denySMTPConnectionsFromAlways, I
thought I should have an immediate return from my external
server with the failure reason.
But I did not receive any hint that the mail was not
delivered. Thus I suppose ASSP is just dropping the
Would it not be the responsibility of the sending mail server to
inform the sending user that the message could not be delivered?
Yes, and in that particular case (denyalways) it makes sense to just
drop the connection; think at it just like null routing the connecting
IP; if an IP is into the
Write on! It's like blocking some IP's at the router, in fact I'm not
sure ASSP will even present the banner, I haven't tested it. But
denySMTPconnectionsFrom might give such a response? It should start a
bit later than denySMTPconnectionsFromAlways. Anyone tested?
On 10/27/2009 10:43 AM,
I am testing (denySMTPConnectionsFromAlways) and noticed that
apparently it does not send a 5xx error message.
In cases where this is a false positive, the unfortunate senders will
never know their mail did not reach the final destination.
Should it have a parameter were admins could set ASSP
quote if one doesn't give a heck about RFCs ... just drop it
On the oposite, I'm not an expert in RFCs but I think the closest it
comes to RFC, the best.
In my tests, when I use denySMTPConnectionsFromAlways, I thought I
should have an immediate return from my external server with the
Hilário Fochi Silveira wrote:
quote if one doesn't give a heck about RFCs ... just drop it
On the oposite, I'm not an expert in RFCs but I think the
closest it comes to RFC, the best.
In my tests, when I use denySMTPConnectionsFromAlways, I
thought I should have an immediate return
Hello
I have DoDenySMTPstrict set to block . I executed some test (adding my
ips) and
denySMTPConnectionsFromAlways seems to have no effect.
All the ips on denySMTPConnectionsFromAlways are not blocked at all.
Anyone having the same problem ?
Graziano
no I was not correct , it WORKS however I was confused by the log
strictly denied by denySMTPConnections or droplist
I think that
strictly denied by denySMTPConnectionsFromAlways or droplist
could be better
Graziano
Hello
I have DoDenySMTPstrict set to block . I executed some test
Just a note; if you didn't already do so, I suggest you to
add an entry to your denySMTPConnectionsFromAlways
list reading as follows
64.18.128.0/19 RackVibe spammers
the whole range shown above is a can of worms, not just
that, lately (and now too) I'm observing flurries of connection
attempts
64.18.128.0/19 RackVibe spammers
just in case, this is a small samples of hostnames
sitting on that range, judge by yourself :)
64.18.149.2 st1.journalpreport.com
64.18.149.3 gre1.journalqreport.com
64.18.149.4 bg1.journalrreport.com
64.18.149.5 rs1.journalsreport.com
64.18.149.6
GrayHat wrote:
Also, and since we're at it, I'd be curious if someone of you
is observing the same behaviour
I haven't seen any connections from that range, yet.
--
This SF.net email is sponsored by:
High Quality
19 matches
Mail list logo
