Menu
▾
▴
Re: [Assp-test] Is hidden parameter $CCchangeMSGDate still honored?
|
From: K P. <nnt...@gm...> - 2018-01-28 20:38:20
|
EXCELLENT. Thank you FYI, this used to work so either I somehow deleted the $main:: prefix or ASSP was previously more forgiving. Whatever the case, I'm excited to make the change! Thank you On Fri, Jan 26, 2018 at 10:59 AM, Thomas Eckardt <Tho...@th... > wrote: > >mlog(0,"info: CCchangeMSGDate set to $CCchangeMSGDate"); > > this is wrong > > the name of the variable is > > $main::CCchangeMSGDate > > so the definition line should be > > $main::CCchangeMSGDate = 30; > > and the mlog line: > > mlog(0,"info: CCchangeMSGDate set to $main::CCchangeMSGDate"); > > Thomas > > > > > > Von: "K Post" <nnt...@gm...> > An: "ASSP development mailing list" <ass...@li.... > net> > Datum: 26.01.2018 16:10 > Betreff: Re: [Assp-test] Is hidden parameter $CCchangeMSGDate > still honored? > ------------------------------ > > > > First, some clarification. Resend works, but resending an already > received message (That exchange already saw) doesn't becasue the date > doesn't seem to be changing anymore for me. > > I was able to grab a file from the resend mail folder before it went out > via smtp. > > Question: does the date get changed when the file is copied into the > folder or does it happen when the file is actually resent? I ask because > the file that I grabbed from the resend folder did not have the date line > modified, nor did it have a X-ASSP-OriginalMailDate line in it at all. > > I added a line in the set sub just to make sure the variable was actually > being set. It appears to be okay there. > mlog(0,"info: CCchangeMSGDate set to $CCchangeMSGDate"); > which gives me > Jan-26-18 09:42:11 Info: CCchangeMSGDate set to 30 > So that's good, but it doesn't seem to be doing anything after moving to > the 2018 versions of ASSP. > > If I manually change the date line in a file, save it, then resend, the > message is received without issue. The date is the date that I changed it > to, not the date it was resent. There is no x-assp-originalmaildate line. > > I don't know what else to test or what in the world I could have done to > break this previously working functionality.. And ideas? > > Thanks > > > > > On Fri, Jan 26, 2018 at 9:04 AM, K Post <*nnt...@gm...* > <nnt...@gm...>> wrote: > okay, thanks, something else must be going on on my end. No resent mail > seems to be going through. > thanks > > On Thu, Jan 25, 2018 at 6:16 AM, Thomas Eckardt < > *Tho...@th...* <Tho...@th...>> wrote: > There is nothing changed related to this parameter > > I've made a test with - $CCchangeMSGDate = 30: > > original Date header: > > - Date: Wed, 24 Jan 2018 20:56:27 -0500. > > new Date Header after resent: > > - Date: Thu, 25 Jan 2018 12:09:35 +0100 > - X-ASSP-OriginalMailDate: Wed, 24 Jan 2018 20:56:27 -0500 > > Thomas > > > > > > Von: "K Post" <*nnt...@gm...* <nnt...@gm...>> > An: "ASSP development mailing list" < > *ass...@li...* <ass...@li...>> > Datum: 24.01.2018 15:59 > Betreff: Re: [Assp-test] Is hidden parameter $CCchangeMSGDate > still honored? > ------------------------------ > > > > > Can you check on this for me? Still a problem. > > On Thu, Jan 11, 2018 at 10:13 AM, K Post <*nnt...@gm...* > <nnt...@gm...>> wrote: > 18008. I'm having trouble with resends after our upgrade. I didn't change > anytnig in CorrectASSpcfg.pm > > I have: > our $CCchangeMSGDate = 30; > > but when I resend now, it doesn't arrive in exchange. If I edit the date > in the msg file, it does. This wasn't happening previously. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! *http://sdm.link/slashdot* > <http://sdm.link/slashdot> > _______________________________________________ > Assp-test mailing list > *Ass...@li...* <Ass...@li...> > *https://lists.sourceforge.net/lists/listinfo/assp-test* > <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* > <http://sdm.link/slashdot> > _______________________________________________ > Assp-test mailing list > *Ass...@li...* <Ass...@li...> > *https://lists.sourceforge.net/lists/listinfo/assp-test* > <https://lists.sourceforge.net/lists/listinfo/assp-test> > > > > ------------------------------------------------------------ > ------------------ > 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 > Ass...@li... > 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 > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > |
