One other item. Since, the sender doesn't get a bounce-back message, he/she
never knows if their mail went through or not... and that's probably the biggest
problem the boss has with not producing a bounce back to the sender. I think,
at the very least, he'd like to have something bounce back to the sender, so
that the sender at least knows that their mail did not get through and that they
need to contact us to get put on the list. (And the list is generally
closed... there is no one taking automated outside requests to join the list.
> Dan, I couldn't agree with you more. It's a request from the boss. He wants
> people trying to mail to us and who get the bounce find out what the alternate
> address is automatically to get into the list (an alias). He feels that most
> spam coming in is sent in an automated fashion (and that if we bounced back a
> message, only humans will be able to interpret it, and therefore, the
> spammers won't). He's not concerned if some human spammers get the address (I
> can just see them now getting the address and adding it to their list of
> addresses to spam, but he doesn't see that as being as big a deal as not
> allowing outsiders who are not members of the list still get the chance to
> the list some way.) Anyway, he wanted me to find out if there was a way to
> customize the bounce message and to whom the bounce message should go (and I
> assume it's going to require patching resend or something like that.)
> Anyway, since the boss requested it, I figured I at least had to find out if
> it's possible and how it would be done.
> > Steve Rifkin wrote:
> > > Now, that I've got restrict2post working, when someone outside the
> > > lists sends to the list, the list owner gets a bounced (non-member
> > > message.
> > Congratulations ! :)
> > >
> > > How do I get some kind of customized bounced message sent back to the
> > > well?
> > Bad idea when you consider the possible mail loops that can be created doing
> > >
> > > There are some lists here that for the senders that are non-members and
> > > a bounce, we want to send a message back to them automatically with some
> > > site-details.
> > This should never happen. Senders that are non-members should already be in
> > restrict_post configuration. Those that are not "should be" handled by a
> > not an automated process. Automating the process would be nearly the same
> > just having an open list to begin with.
> > Dan Liston