From: carconni (carconniearthlink.net)
Date: Tue Aug 12 2008 - 15:20:54 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Actually Wesley, it does. You see, if you continue to send
undeliverable mail to an ISP like Yahoo, you can get flagged. See
here: http://help.yahoo.com/l/us/yahoo/mail/postmaster/
postmaster-01.html & http://help.yahoo.com/l/us/yahoo/mail/postmaster/
postmaster-31.html.

If you send to too many dead or invalid addresses, you run the risk
of looking like a spammer. Since we know we aren't being used as an
open relay, we are trying to reduce the number of bad email
addresses. If an address that was previously blacklisted turns out
to later be a valid address, the client will notify us and we will
remove that address at their request. In addition, sometimes, you
have a user who just doesn't want the email anymore but doesn't know
how or (doesn't read the unsubscribe directions at the bottom of the
email) and it's all too easy to click the spam button in their mail
client. I've checked my dns and reverse dns and we are using
domainkeys - I'm just looking for more options to address this problem.

Thanks you though for looking at my post.

On Aug 12, 2008, at 12:29 PM, Wesley wrote:

> carconni wrote:
>>
>> I need to set up a "blacklist" of sorts on our mail server. One
>> of our client servers handles approximately a million emails a day
>> and we've been experiencing some delivery delays. In addition, we
>> occasionally get blocked for SPAM and while getting unlisted is
>> easy, I'd like to find more ways of preventing it. Is there a
>> means of setting up a file that postfix will check before
>> delivery? I don't want to restrict based on domain, but rather by
>> address and I would prefer not to use my alias file to move bad
>> addresses to /dev/null. Because our client base is so varied and
>> in many cases we don't have access to the email database, I need
>> to try and find alternatives on the mail server itself.
>>
>> For example, lets say one of our client's users signed up for
>> notifications on a particular service, but she's new to it all and
>> she types in the wrong address. Our application system sends an
>> email to the user and it bounces back from the ISP as
>> undeliverable because of a bad address. How can prevent mail from
>> being delivered to that bad address in the future? So if
>> Betty1yahoo.com comes back as a 450/550, I want to be able to
>> block mail sent to Betty1yahoo.com but not block any other mail
>> that may be going to yahoo.com
>>
>> I've taken a look at http://www.postfix.org/postconf.
>> 5.html#smtpd_client_restrictions but I'm not sure how to apply it
>> for what I need, can anyone advise me on how to set this up?
>> (I've also looked at http://www.postfix.org/
>> ADDRESS_VERIFICATION_README.html; but the README states quite
>> clearly that this feature is designed for low traffic sites)
>>
>> Thank you very much
>>
>>
> Not that I can help you with that but what if the address is
> created after that you've blocked it?
>
> And is this the reason that your clients server gets blocked? seems
> unlikely.
>
> --
> Wesley
>
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]