ASSP never has and never will create any MSGID - every mail has already
it's own unique MSGID. The MSGID is created by the Client/Server and is
already part of the mail header. ASSP looks in to the header and stores
the first found MSGID in to cache - hoping that the responding MailServer
give
Hi Thomas,
Yes , this is what I want… but that was another thread. (yes, yes… I have many
wishes)
This thread was about creating the MSGid. AFAIK it’s ASSP itself that is
creating the unique and cached MSGid. To make this work I will need to
configure my mailserver to use ASSP as a smart ho
Jean Pierre,
I know your next question - what about the "cip" (forwarding-IP) and
Backscatter : yes and no
yes - this IP will work for the Message-ID-tracking and for
DNS-Backscatter-check
no - it will never work for BATV - when BATV is checked, we have no
mail-header to get the cip, and a se
Jean-Pierre,
>But how about ?my problem? and the suggested solution?.?
In any of the next versions 2 you'll find under 'Backscatter Detection'
the choice 'Back250OKISP' ->
"If any Backscatter check failes for a bounced mail that is coming from an
ISPIP, ASSP will send "250 OK" to the ISP, bu