[Kolab-devel] Forged Sender from local IP's

Sascha Wilde wilde at intevation.de
Fri Mar 14 13:16:54 CET 2008


Sascha Wilde <wilde at intevation.de> writes:
> Richard Bos <ml at radoeka.nl> writes:
>> On Fri, Feb 08, 2008 at 01:06:33PM +0200, Thomas Black wrote:
>>> Ever since upgrading from 2.2beta2 to 2.2beta3 and 2.2rc1 I'm getting
>>> these errors in my mail log and filter log:
>>> 
>>> Feb 08 12:52:20 Kolab Filter [error] [horde] Invalid From: header.
>>> xxxxxxxx looks like a forged sender <ID: <47AC3458.4090300 at xxxxx>>
>>> [pid 25405 on line 180 of "/kolab/lib/php/Kolab/Filter/Content.php"]
>>> 
>>> It seems to be happening when unauthenticated SMTP is used from my
>>> defined local network, which should work (network ranges defined in my
>>> admin interface.
[...]
> I'm currently working on a solution to this problem.

Meanwhile I fixed the problem.  For details see  kolab/issue2466 (How
should Kolab Filter handle mails from privileged networks?).

cheers
sascha
-- 
Sascha Wilde                                      OpenPGP key: 4BB86568
Intevation GmbH, Osnabrück             http://www.intevation.de/~wilde/
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/devel/attachments/20080314/86620fa0/attachment.sig>


More information about the devel mailing list