On Sunday 06 September 2009 02:16:23 Stroller wrote:
Why hasn't greylisting been mentioned? I greylist and it ends up
blocking at least 99% of spam in my experience.
There are some disadvantages to greylisting mentioned here:
http://en.wikipedia.org/wiki/Greylisting#Disadvantages
I
Every other solution out there has this one little problem that people
seem to
ignore.
Per RFC, if you accept the connection and the mail, you will deliver it.
That's what it says. It also says this since days long before spam
problems,
but still. We all conveniently ignore this if we are
When I try to send an email to a ucla.edu email address from my hosted
server, the message bounces and I'm directed to this page:
http://info.smtp.ucla.edu/faq.php
which says:
The gateway disallows direct connections from residential broadband
systems, from other dynamically allocated IP
On 6 Sep 2009, at 00:52, Grant wrote:
When I try to send an email to a ucla.edu email address from my
hosted
server, the message bounces and I'm directed to this page:
http://info.smtp.ucla.edu/faq.php
which says:
The gateway disallows direct connections from residential broadband
On 6 Sep 2009, at 00:05, Grant wrote:
...
The remainder of those you're inefficiently filtering are Linux
enthusiasts
running Postfix on their Gentoo boxes.
Yeah, I was planning on setting up postfix on my home Gentoo box too.
I guess I could relay through my ISP to avoid delivery problems
On 3 Sep 2009, at 22:14, Alan McKinnon wrote:
On Thursday 03 September 2009 22:51:04 Stroller wrote:
Relay through your ISP.
Using Postfix this is /etc/transports (and `postmap /etc/postfix/
transport` and restart Postfix)
If you have any influence at ucla.edu tell them how much their policy
On Friday 04 September 2009 17:23:15 Stroller wrote:
You may be in a slightly exceptional position in that the bandwidth
cost - of syncing to Spamhaus and the additional DNS lookups - may be
prohibitive. UCLA are not.
Whatever the proportion of legitimate mail this policy rejects, this
On 4 Sep 2009, at 21:49, Alan McKinnon wrote:
On Friday 04 September 2009 17:23:15 Stroller wrote:
...
Every other solution out there has this one little problem that
people seem to
ignore.
Per RFC, if you accept the connection and the mail, you will deliver
it.
That's what it says. It
When I try to send an email to a ucla.edu email address from my hosted
server, the message bounces and I'm directed to this page:
http://info.smtp.ucla.edu/faq.php
which says:
The gateway disallows direct connections from residential broadband
systems, from other dynamically allocated IP
Relay through your ISP.
Using Postfix this is /etc/transports (and `postmap /etc/postfix/
transport` and restart Postfix)
If you have any influence at ucla.edu tell them how much their policy
sucks.
Stroller.
On 3 Sep 2009, at 21:45, Grant wrote:
When I try to send an email to a
On Thu, Sep 3, 2009 at 3:45 PM, Grantemailgr...@gmail.com wrote:
When I try to send an email to a ucla.edu email address from my hosted
server, the message bounces and I'm directed to this page:
http://info.smtp.ucla.edu/faq.php
which says:
The gateway disallows direct connections from
Ooops... please ignore. I just noticed you said from my hosted
server.
You can still try complaining to them. Good luck!!
Stroller.
On 3 Sep 2009, at 21:51, Stroller wrote:
Relay through your ISP.
Using Postfix this is /etc/transports (and `postmap /etc/postfix/
transport` and
On Thursday 03 September 2009 22:51:04 Stroller wrote:
Relay through your ISP.
Using Postfix this is /etc/transports (and `postmap /etc/postfix/
transport` and restart Postfix)
If you have any influence at ucla.edu tell them how much their policy
sucks.
ucla.edu have the perfect policy.
On Thu, 3 Sep 2009 13:45:46 -0700
Grant emailgr...@gmail.com wrote:
When I try to send an email to a ucla.edu email address from my hosted
server, the message bounces and I'm directed to this page:
...
Does anyone know how to fix this?
If you have an open mail relay server, you can use
14 matches
Mail list logo
