|
I am currently using a
bounce-back system where 2 headers are placed in an email with codes that
indicate where bounces should go:
smtpfrom: Test <[EMAIL PROTECTED]>
Return-Path: [EMAIL PROTECTED]
The 2 numbers are keys to a
user table and list table.
Here's the problem. If say 12
people subscribe from AOL, AOL seems to receive 1 email for all 12 of those
people, and expands it themselves. If the people receive these emails the
numbered header comes through with flying colors. If any of these addresses are
bad and AOL generates a bounce-back, it pulls one of the emails headers and
sends the bounce back info to it. If more than one are bad, they all go to the
same arbitrary email address. Then this one arbitrary email address gets put on
hold by my system, even though their email address might be
good.
Anyone else using a similar
system?
Anyone else have a
fix?
A better
system?
Thanks
--
|
