Ticket #710 (closed maintenance: fixed)

Opened 3 years ago

Last modified 3 years ago

Incorrect email address for Sam on Transition Culture

Reported by: chris Owned by: chris
Priority: minor Milestone: Maintenance
Component: Parrot server Keywords:
Cc: sam, ed Estimated Number of Hours: 0.0
Add Hours to Ticket: 0 Billable?: yes
Total Hours: 0.25

Description

I'm seeing quite a few emails like this:

From: Mail Delivery System <Mailer-Daemon@parrot.webarch.net>
Date: Tue, 01 Apr 2014 08:04:28 +0100
To: tc@parrot.webarch.net
Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  samrossiter@transitionentwork.org
    Unrouteable address

------ This is a copy of the message, including all the headers. ------

Return-path: <tc@parrot.webarch.net>
Received: from tc (uid=1011)
        by parrot.webarch.net with local (Exim 4.80)
        (envelope-from <tc@parrot.webarch.net>)
        id 1WUskG-0005Rv-Sa
        for samrossiter@transitionentwork.org; Tue, 01 Apr 2014 08:04:28 +0100
To: samrossiter@transitionentwork.org
Subject: [Wordfence Alert] Problems found on Transition Culture
X-PHP-Originating-Script: 1011:class-phpmailer.php
Date: Tue, 1 Apr 2014 07:04:28 +0000
From: WordPress <wordpress@transitionculture.org>
Message-ID: <11e64e1b3cdb24f69d0069ecdc224524@transitionculture.org>
X-Priority: 3
X-Mailer: PHPMailer 5.2.4 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8

Wordfence found the following new issues on "Transition Culture".

NOTE: Upgrading to the paid version of Wordfence gives you two factor authentication (sign-in via cellphone)
and country blocking which are both effective methods to block attacks.
You can also schedule when your scans occur with Wordfence Premium.
Click here to sign-up for the Premium version of Wordfence now.
https://www.wordfence.com/wordfence-signup/


Alert generated at Tuesday 1st of April 2014 at 08:04:28 AM
Critical Problems:

* The Plugin "Spam Destroyer" needs an upgrade.

Change History

comment:1 in reply to: ↑ description Changed 3 years ago by chris

  • Add Hours to Ticket changed from 0.0 to 0.25
  • Status changed from new to closed
  • Resolution set to fixed
  • Total Hours changed from 0.0 to 0.25

Replying to chris:

samrossiter@…

Unrouteable address

The error is caused by a typo in the domain name.

I was intending to update Sam's address in the user table, but he doesn't have an account:

sudo -i
su-user tc
cd sites/default/
wp user list

And there are no matches in the database when using the wp command line tool:

wp search-replace "samrossiter@transitionentwork.org" "samrossiter@transitionnetwork.org" --dry-run
wp search-replace "transitionentwork.org" "transitionnetwork.org" --dry-run

So grepping the files:

grep -rl transitionentwork.org .

No match, grepping the database dump:

sudo -i
grep transitionentwork.org /var/backups/mysql/sqldump/tc.sql
... INSERT INTO ... ('alertEmails','samrossiter@transitionentwork.org'), ...

This isn't seralized so it's easy to update on the !MySQL command line:

sudo -i
mysql tc
mysql> describe r0bh_wfConfig;
+-------+--------------+------+-----+---------+-------+
| Field | Type         | Null | Key | Default | Extra |
+-------+--------------+------+-----+---------+-------+
| name  | varchar(100) | NO   | PRI | NULL    |       |
| val   | longblob     | YES  |     | NULL    |       |
+-------+--------------+------+-----+---------+-------+
mysql> update r0bh_wfConfig set val="samrossiter@transitionnetwork.org" where name="alertEmails";
mysql> select * from r0bh_wfConfig where name="alertEmails";
+-------------+-----------------------------------+
| name        | val                               |
+-------------+-----------------------------------+
| alertEmails | samrossiter@transitionnetwork.org |
+-------------+-----------------------------------+

That should have fixed it.

Last edited 3 years ago by chris (previous) (diff)
Note: See TracTickets for help on using tickets.