Database issue not assigning token.

Report bugs and workarounds
Post Reply
ethandee178
Posts: 14
Joined: 26 May 2015 16:28

Database issue not assigning token.

Post by ethandee178 » 27 Aug 2018 12:39

Often time when I come in on a monday, my customers will tell me they can't release their mail.
Aside from some other possibly unrelated issues, the most common issue is that the 'token=' is blank in the link.
I've written a script to easily release these. But I know it is annoying to my customers.
Any one had this issue? Dealt with it?
Seems like it could be database related. Is there a database clean/tuning command I could run that might help?
Thanks.

BTW this is that easy release script:

#!/bin/bash

while true; do
until [[ $msgID == ??????????.????? ]]; do
if [[ $msgID == "exit" ]]; then
exit
fi
read -p "Message ID?: " msgID
done
fullpath=`find /var/spool/MailScanner/quarantine -iname *"$msgID"*`
echo $fullpath
/usr/sbin/sendmail.postfix -t <$fullpath
msgID=""
done

User avatar
shawniverson
Posts: 2592
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: Database issue not assigning token.

Post by shawniverson » 27 Aug 2018 21:47

Never, ever, use -t!

You could be releasing mail to everybody! Not just your own recipients!

Is the token really gone, or are the tokens expiring? Monday seems peculiar....
Version 3.0.2.6 released! Update now to keep your eFa secure!

ethandee178
Posts: 14
Joined: 26 May 2015 16:28

Re: Database issue not assigning token.

Post by ethandee178 » 17 Sep 2018 13:31

Another Monday with the same issue.
When I say the token is 'gone' I mean in the release link, it says 'token='
If I assign a token manually it releases no problem.
I also cloned and edited a page which I call release-msg-bak.cgi which doesn't check for the token.
It also releases it no problem.
The original (release-msg.cgi) is where I got the '-t' from.
I just copy and pasted.

User avatar
shawniverson
Posts: 2592
Joined: 13 Jan 2014 23:30
Location: Rushville, Indiana, USA
Contact:

Re: Database issue not assigning token.

Post by shawniverson » 18 Sep 2018 21:46

Yeah, that's why that script is deprecated and going away...

So there is a token for the email IDs in the SQL maillog table, just not in the report?

Just Mondays? Are you on 3.0.2.6? I want to try to reproduce this problem.

The token is important to prevent someone from exploiting the message release code.
Version 3.0.2.6 released! Update now to keep your eFa secure!

Post Reply