Page 1 of 1

Users Cannot Release Spam Messages

Posted: 19 Feb 2015 19:40
by murphyk
Hello,

I'm trying to implement EFA-3.0.0.6. I've run into an issue where users cannot release quarantined/spam messages. I'm trying to migrate from ESVA to EFA.

With the default setting for /etc/MailScanner/reports/en/recipient.spam.report.txt, the “{Spam Not Delivered}” message is sent to the user, however no link appears, the "{Spam Not Delivered}" message seems to cut off right at "...quarantined...click here..." then no link. I believe the variable for token is not being passed correctly. I see that the mysql->efa->tokens table is completely empty, even after ~100 messages have passed through. I do have the “Spam Actions = store notify” instead of “store custom(spam)”, so I don't know if that is the reason the token database is empty.

I tried to input the same information from ESVA's /etc/MailScanner/reports/en/recipient.spam.report.txt , which has the &to=$to variable, versus token, but that didn't work and led me to the .cgi file point to token stuff in /var/www/cgi-bin/release-msg.cgi.

Also, the Botnet plugin seems to be flagging a lot of domains for Botnet, where as ESVA did not.

Is there anything I can do?

Re: Users Cannot Release Spam Messages

Posted: 20 Feb 2015 20:57
by shawniverson
. I do have the “Spam Actions = store notify” instead of “store custom(spam)”, so I don't know if that is the reason the token database is empty.
That is your problem.

custom(spam) is used in place of notify that appends the token in EFA.

Re: Users Cannot Release Spam Messages

Posted: 23 Feb 2015 16:46
by murphyk
Thanks for the help. I noticed that right after I posted.

Another question: Our reports are being sent daily, which is great, but it is listing "UNKOWN" for e-mails like "postmaster@domain.com", which is the e-mail used for releasing messages to people. It's also "UNKNOWN" reporting normal/regular e-mails, is this because of custom(nonspam) not running?

Re: Users Cannot Release Spam Messages

Posted: 23 Feb 2015 23:31
by shawniverson
What does the spam report say for one of the messages being flagged as unknown?

Re: Users Cannot Release Spam Messages

Posted: 24 Feb 2015 13:22
by murphyk
Sorry, it is the quarantine report that is saying "Reason: UNKNOWN."

In the e-mail report, all that is sent is:

Code: Select all

Received ----- From ----------------Subject ---- Reason ------- Action
Date/time ----- sender@domain ----- subject ---- UNKNOWN ------ View

Re: Users Cannot Release Spam Messages

Posted: 24 Feb 2015 22:59
by shawniverson
What about on this page for a particular email....looks like this....
Capture.PNG
Capture.PNG (22.92 KiB) Viewed 9483 times

Re: Users Cannot Release Spam Messages

Posted: 25 Feb 2015 12:07
by murphyk
Selection_006.jpg
Selection_006.jpg (78.3 KiB) Viewed 9482 times

Re: Users Cannot Release Spam Messages

Posted: 25 Feb 2015 22:18
by shawniverson
Ahh..whitelisted...in other words, not spam?

Do you even want non-spam showing up in your reports?

I would suggest you hang on, 3.0.0.7 is about to go live and should resolve this.

https://github.com/E-F-A/v3/issues/30

Re: Users Cannot Release Spam Messages

Posted: 26 Feb 2015 12:53
by murphyk
I was looking at quarantine_report.php and saw the calls for the messages. I was hesitant on changing anything because it looked like the messages from postmaster, for example, were marked null for isspam and nonspam is marked 0. I saw your change and I bet that will work.

Re: Users Cannot Release Spam Messages

Posted: 06 Mar 2015 16:58
by murphyk
We recently had a message come in that was designated to 4 different people and was marked as spam, but the user could try to release it. However, only one person was able to release it. After anyone else tried, this message came up:

Code: Select all

Your message has not been released from quarantine.
Our system indicates that this message has already been released once, or the original notification message has expired. Notification messages to release spam expire after 3 days. Your message can be released again by accessing your spam quarantine.
I see that the message ID for the URL in the e-mail is different and matches for the user, however there is only 1 token ID which I believe caused this. Luckily, we were able to release it from the Web interface just fine.

Code: Select all

/cgi-bin/release-msg.cgi?datenumber=20150306&id=2492360AF1.A78F1&token=a5313a454279738375c304ecccfdcd8a

Code: Select all

/cgi-bin/release-msg.cgi?datenumber=20150306&id=2ACDB60AF2.A3CE2&token=a5313a454279738375c304ecccfdcd8a
Any thoughts?