In order to simplify abuse handling the Tor2web user must be able to fill an abuse request (like current tor2web 2.0 based on glype) from:
The acceptance disclaimer of issue #11
The injected disclaimer/abuse header of issue #1
The abuse page contain a text that can be loaded from an external template.
The abuse page pre-fill the Hostname field with the Hostname of the HS the user is accessing (and for which he is reasonably reporting the abuse).
The abuse page must send an email to an operator trough a configured email account (into proxxor configuration file).
If possible doesn't rely on standard PHP mail() function that require a system dependancy of a properly configured mailer.
Configuring an email account (like a gmail account) with SMTPS/username/password would be easier as it make proxxor be self-contained and less dependent on system configuration.
In order to simplify abuse handling the Tor2web user must be able to fill an abuse request (like current tor2web 2.0 based on glype) from:
The abuse page contain a text that can be loaded from an external template.
The abuse page pre-fill the Hostname field with the Hostname of the HS the user is accessing (and for which he is reasonably reporting the abuse).
The abuse page must send an email to an operator trough a configured email account (into proxxor configuration file). If possible doesn't rely on standard PHP mail() function that require a system dependancy of a properly configured mailer.
Configuring an email account (like a gmail account) with SMTPS/username/password would be easier as it make proxxor be self-contained and less dependent on system configuration.