"Hijack cares
about the senders - not the recipients I do believe"
Yes, but Hijack should be OUTGOING only. These emails
were obviously incoming.
What do hijack the logs
say?
06/01/2005 08:53:13 QAFB901A600000E85 [EMAIL PROTECTED] is not
local.
06/01/2005 08:53:13 QAFB901A600000E85 Outgoing from 68.118.154.7: threshold 2 reached; SPAM: HOLDING PERMANENTLY That is a sample of one of the held emails (loglevel
high). It clearly says [EMAIL PROTECTED] is not
local, but that address is set up as an alias on our server (It forwards to
AOL). The domain burnsandco.com is local and it contains an address of
pattinelson.
Another:
06/01/2005 08:58:05 QB0DC018200000EDC [EMAIL PROTECTED] is not
local.
06/01/2005 08:58:05 QB0DC018200000EDC Outgoing from 68.118.154.7: threshold 2 reached; SPAM: HOLDING PERMANENTLY Again, this one clearly states that [EMAIL PROTECTED] is not local but the
address is set up on our server. This one is not an alias and is not
forwarded anywhere. The log shows between those two entries (among many
other "is not local" entries) that several messages coming in from the gateway
ARE in fact treated as local:
06/01/2005 08:56:50 QB09201A000000EC7 Incoming from 68.118.154.7: OK. and
06/01/2005 08:56:53 QB095019800000ECB Incoming from
68.118.154.7: OK.
Were all the held mail
prefaced with the gateway ip?
Yes, every single one of nearly 5000..
Do you have the line in
hijack.cfg "ALLOWIP <gateway ip > ?
I do now, but I shouldn't need to. The problem is
that Hijack somehow started incorrectly identifying local addresses.
For example if I go back to the previous day's log and look I see that
all emails coming from the gateway for local addresses are correctly identified
as local addresses and get an OK line.
05/31/2005 16:27:38
QC8BA021400003290 Incoming from 68.118.154.7:
OK.
05/31/2005 16:27:39 QC8BA020E00003292 Incoming from 68.118.154.7: OK. 05/31/2005 16:27:47 QC8C2022200003294 Incoming from 68.118.154.7: OK. 05/31/2005 16:27:53 QC8C8021A00003296 Incoming from 68.118.154.7: OK. 05/31/2005 16:28:00 QC8D0021400003298 Incoming from 68.118.154.7: OK. 05/31/2005 16:28:18 QC8E2020E0000329A Incoming from 68.118.154.7: OK. 05/31/2005 16:28:27 QC8EB02220000329C Incoming from 68.118.154.7: OK. 05/31/2005 16:28:27 QC8EB021A0000329E Incoming from 68.118.154.7: OK. 05/31/2005 16:28:48 QC9000222000032A3 Incoming from 68.118.154.7: OK. 05/31/2005 16:28:50 QC902021A000032A5 Incoming from 68.118.154.7: OK. 05/31/2005 16:29:01 QC90D020E000032A8 Incoming from 68.118.154.7: OK. 05/31/2005 16:29:01 QC90D0222000032AA Incoming from 68.118.154.7: OK. 05/31/2005 16:29:03 QC90F021A000032AC Incoming from 68.118.154.7: OK. 05/31/2005 16:29:04 QC9100214000032AE Incoming from 68.118.154.7: OK. 05/31/2005 16:29:14 QC91A020E000032B0 Incoming from 68.118.154.7: OK. 05/31/2005 16:29:19 QC91F021A000032B3 Incoming from 68.118.154.7: OK. 05/31/2005 16:29:21 QC9210214000032B5 Incoming from 68.118.154.7: OK. 05/31/2005 16:29:31 QC92B021A000032B9 Incoming from 68.118.154.7: OK. 05/31/2005 16:29:31 QC92B0214000032BB Incoming from 68.118.154.7: OK. 05/31/2005 16:29:33 QC92C020E000032BD Incoming from 68.118.154.7: OK. This
particular problem did not start until yesterday and ended when I put in the
ALLOWIP line. Looking through the entire log shows no incorrect
identifications on that day. This happened suddenly and I don't know why
(when last we spoke, neither did Declude).
|