READ the changelog!

2017-09-18
fixed in assp 2.5.6 *Fortress* build 17261: 
.....
our $CCchangeMSGDate = 0;                ## (0..31) change the 'Date:' 
MIME-header on CCmail (sendHamInbound), ForwardSpam (sendAllSpam) and 
resend mail
                                         ## MS-Exchange may require this, 
because duplicate mails will be removed silently, if they contain an equal 
'Date:...' MIME-header
                                         # bit 0 = 1 ( +1) -> set all bits 
(1 - 4) to 1 for backward compatibility ( same as 30 -> 2+4+8+16 )
                                         # bit 1 = 1 ( +2) -> force change 
at CCmail
                                         # bit 2 = 1 ( +4) -> force change 
at ForwardSpam
                                         # bit 3 = 1 ( +8) -> force change 
at resend mail
                                         # bit 4 = 1 (+16) -> general 
disable the automatic detection of a local MS-Exchange MTA by checking the 
SMTP banner / greeting
                                         ## The default is zero (0), which 
means: the 'Date:...' MIME-header is not forced to be changed in either 
case,
                                         ## but it will be changed, if a 
MS-Exchange MTA is detected using $ExchangeBannerRe against the SMTP 
banner / greeting.
                                         ## To disable this feature 
completely - set this value to 16.

 
Thomas




Von:    "K Post" <nntp.p...@gmail.com>
An:     "ASSP development mailing list" <assp-test@lists.sourceforge.net>
Datum:  01.10.2017 02:20
Betreff:        [Assp-test] $CCchangeMSGDate request for scenarios where 
Exchange is NOT detected



Thanks for implementing the changes in 17261 to give us more options about 
how to change the date. The granularity is vastly improved, but I have a 
big favor to ask. All of our mail first goes through another SMTP server 
which is NOT exchange before then being forwarded to Exchange for most 
users. 
Because ASSP never directly touches Exchange, ASSP will never 
automatically detect Exchange and let any of the new options have any 
impact, which means that starting with 16271, I can no longer force ASSP 
to change dates on resent messages.

I'm wondering if you might be able to either add more options to allow 
these changes even if Exchange isn't detected. Or maybe is would be 
simpler to add another option like:
$CCchangeMSGDateAssumeExchange
where we could set it to 1 so that ASSP skips the Exchange banenr check 
and just assumes that it's Exchange?

This wouldn't just be beneficial to me, but to others who have a firewall 
or other scenario where the banner doesn't give away that the destination 
is exchange or for people running non-Exchange MTA's who still need or 
want the date change feature.

Thanks for the consideration.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test





DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to