Page 1 of 1

Delivery failures ;o)

Posted: Sat Feb 18, 2012 9:31 am
by David Ricker
Hee hee.........Wayne, is that what's called a generation gap?!

Lol

Dave

"Wayne G. O'Shea" wrote:
What the @#&% was that in English my son!??!

----- Original Message -----
From: "Daryl C. W. O'Shea" <dos@dostech.ca>
To: <rebel-builders@dcsol.com>
Sent: Sunday, September 12, 2004 9:42 PM
Subject: Re: Delivery failures
On Fri, 10 Sep 2004, Mike Davis wrote:
Not sure what caused that one, but I have been having a lot of problems
with
Shaw cable... and since there are 5 list members from shaw.ca, it crops
up a
lot. I put quite a bit of time into tracking down the problem with
Shaw,
and after contacting them they said, "yeah, that sounds about right...
can't
you just configure your system to accept any and all mail from shaw.ca?"
Well yes, but that kind of defeats the point in filtering spam!
Whitelisting all of the list member addresses on your border relay would
be just as effective as letting them through to the list and then bouncing
them. Unless you're getting a lot of spam from list member addresses, but
that's another issue.

What I've done for now is configure the filter to accept all mail
addressed
to the list... then the list server will have to bounce the bogus
addresses.
This may sound like a real good solution, but the list gets several
thousand
e-mails a day from bogus addresses, and having the filter in place means
my
server never has to process those messages... by turning that filter
off,
every message will be imported into the e-mail database, then when the
list
server finds that the address is not valid, it will generate a bounce
message that must then be sent out. Most likely the bounce message will
be
addressed to an invalid address meaning that I'll get a bounce message
back
in return. You can see how this can put a much bigger load in the
system.
Just don't bounce invalid (non list member) email to the list. In the
event that someone legitimate tries to email the list but hasn't signed up
they're not going to be any worse off than if the message bounced (unless
you're including contact info in your bounce messages, in which case
you're going to get even more spam). Hopefully a legit person (who
hasn't subscribed) will have the common sense to email you directly or go
to your website after a few attempts at sending mail to the list.

But until shaw.ca finds a better way to deal with their spam problems
then
just turning their inbound mail servers off, I'm not sure what else to
do.
By the way, that's what's happening Jerry when your mail gets bounced
with a
550 error code... that means my mail server was not able to connect to
shaw.ca inbound servers and verify that your address is valid. I hope
you're sending copies of all the error messages to shaw too, because
it's
not my problem to fix.
You're asking Shaw to open their servers, and thus their users, to be more
vulnerable to spam (spam harvesters connect to SMTP servers and do brute
force attacks to find out a systems legitimate addressess) so that you
get less spam. You can see why they don't want to do it. What you're
asking them to do isn't even required by any RFCs.


Another way to prevent your gateway server from accepting spam is to do
xRBL and SBL lookups on each connection. Depending on your Windows mail
server, you may or may not be able to do that though. MDaemon
(www.altn.com) for Windows will do that.


Daryl




-----------------------------------------------------
List archives located at:
https://www.dcsol.com/default.htm
username "rebel" password "builder"
Subscription services located at:
https://www.dcsol.com/public/code/html-subscribe.htm
List administrator: mike.davis@dcsol.com
-----------------------------------------------------



-----------------------------------------------------
List archives located at:
https://www.dcsol.com/default.htm
username "rebel" password "builder"
Subscription services located at:
https://www.dcsol.com/public/code/html-subscribe.htm
List administrator: mike.davis@dcsol.com
-----------------------------------------------------
--
David A. Ricker
Fall River, Nova Scotia
Canada






-----------------------------------------------------------------
List archives located at: https://mail.dcsol.com/login
username "rebel" password "builder"
Unsubscribe: rebel-builders-unsubscribe@dcsol.com
List administrator: mike.davis@dcsol.com
-----------------------------------------------------------------

Delivery failures ;o)

Posted: Sat Feb 18, 2012 9:31 am
by Wayne G. O'Shea
Yep, I worked with first generation 'puters and he's current day!

----- Original Message -----
From: "David Ricker" <ricker@inherentsys.ca>
To: <rebel-builders@dcsol.com>
Sent: Monday, September 13, 2004 8:54 PM
Subject: Re: Delivery failures ;o)

Hee hee.........Wayne, is that what's called a generation gap?!

Lol

Dave

"Wayne G. O'Shea" wrote:
What the @#&% was that in English my son!??!

----- Original Message -----
From: "Daryl C. W. O'Shea" <dos@dostech.ca>
To: <rebel-builders@dcsol.com>
Sent: Sunday, September 12, 2004 9:42 PM
Subject: Re: Delivery failures
On Fri, 10 Sep 2004, Mike Davis wrote:
problems
with
crops
up a
Shaw,
right...
can't
shaw.ca?"
Whitelisting all of the list member addresses on your border relay
would
be just as effective as letting them through to the list and then
bouncing
them. Unless you're getting a lot of spam from list member addresses,
but
that's another issue.

addressed
addresses.
thousand
means
my
off,
the
list
bounce
will
be
message
back
system.
Just don't bounce invalid (non list member) email to the list. In the
event that someone legitimate tries to email the list but hasn't
signed up
they're not going to be any worse off than if the message bounced
(unless
you're including contact info in your bounce messages, in which case
you're going to get even more spam). Hopefully a legit person (who
hasn't subscribed) will have the common sense to email you directly or
go
to your website after a few attempts at sending mail to the list.

problems
then
to
do.
bounced
with a
to
hope
it's
You're asking Shaw to open their servers, and thus their users, to be
more
vulnerable to spam (spam harvesters connect to SMTP servers and do
brute
force attacks to find out a systems legitimate addressess) so that you
get less spam. You can see why they don't want to do it. What you're
asking them to do isn't even required by any RFCs.


Another way to prevent your gateway server from accepting spam is to
do
xRBL and SBL lookups on each connection. Depending on your Windows
mail
server, you may or may not be able to do that though. MDaemon
(www.altn.com) for Windows will do that.


Daryl




-----------------------------------------------------
List archives located at:
https://www.dcsol.com/default.htm
username "rebel" password "builder"
Subscription services located at:
https://www.dcsol.com/public/code/html-subscribe.htm
List administrator: mike.davis@dcsol.com
-----------------------------------------------------



-----------------------------------------------------
List archives located at:
https://www.dcsol.com/default.htm
username "rebel" password "builder"
Subscription services located at:
https://www.dcsol.com/public/code/html-subscribe.htm
List administrator: mike.davis@dcsol.com
-----------------------------------------------------
--
David A. Ricker
Fall River, Nova Scotia
Canada






-----------------------------------------------------
List archives located at:
https://www.dcsol.com/default.htm
username "rebel" password "builder"
Subscription services located at:
https://www.dcsol.com/public/code/html-subscribe.htm
List administrator: mike.davis@dcsol.com
-----------------------------------------------------





-----------------------------------------------------------------
List archives located at: https://mail.dcsol.com/login
username "rebel" password "builder"
Unsubscribe: rebel-builders-unsubscribe@dcsol.com
List administrator: mike.davis@dcsol.com
-----------------------------------------------------------------