Fetchmail and MailScanner

[Drew Marshall]

On 20 Aug 2008, at 09:44, Ismail OZATAY wrote:

> Hi Edward ,
>
> I always read every incoming mail carefully. Also i know that Fabio  
> Silva 's problem is still going on because using smtphost setting  
> will never fix that problem. Fetchmail is routing all emails to smtp  
> so source seems interface's ip which is set before by smtphost.
>
> Here is my .fetchmailrc file;
>
> set daemon 20
> set syslog
> set postmaster root
> set invisible
> poll mail.test.net with proto POP3 and options no dns
>        user 'test' with pass "123456"  is 'realuser at internal.net'
>        keep
>        norewrite
>        smtphost 192.168.100.3
>
> Here is my incmoing mail header ;
>
> Received: from mail.test.net (mail.internal.net [192.168.100.3])
>    by mail.ismail.net (Postfix) with ESMTP id 99A49E8288
>    for <realuser at internal.net>; Wed, 20 Aug 2008 09:55:27 +0300 (EEST)
>
> As you see coming source is 192.168.100.3 so mailscanner thinks that  
> it is localhost. My question was how can i leave message source  
> untouched ?
MailScanner will only think something is what you tell it via a  
ruleset. To use Mailwatch, you will need to whitelist the loopback  
interface (127.0.0.1) assuming you have a fairly standard set up in  
the Mailwatch config file. MailScanner with therefore scan all mail  
received on any other interface including your 192.168.100.3 address.  
What Postfix calls this (Via the hosts file or PTR record) is  
irrelevant to MS.

HTH

Drew

--
In line with our policy, this message has been scanned for viruses and dangerous
 content by Technology Tiger's Mail Launder system <www.mail-launder.com>
Our email policy can be found at www.technologytiger.net/policy

Technology Tiger Limited is registered in Scotland with registration number: 310997
Registered Office 55-57 West High Street Inverurie AB51 3QQ