Problems after upgrade from 4.85 to 5.03

[Daniel Malmgren]

Yep, you're right. I realize now that they aren't scanned, it's only 
that they're logged to my MailWatch database anyway. And now that I 
think about it, I might have done some tweaks of my own to the MailWatch 
scripts to prevent that from happening. Only problem now is that the 
upgrade completely (and without warning) wiped all my old custom 
scripts, hope I've got a backup of them somewhere...

/Daniel


Den 2016-10-12 kl. 02:35, skrev Mark Sapiro:
> On 10/11/2016 01:10 PM, Daniel Malmgren wrote:
>> One last question: I don't want to scan outgoing mail, only incoming. In
>> 4.85 the following lines in /etc/MailScanner/rules/scan.messages.rules
>> fixed that for me. Now it seems to scan them anyway. How come?
>
> Works for me:
>
> $ cat rules/scan.messages.rules
>  From 127. no
> FromorTo default yes
> $
>
> mail.log
>
> Oct 11 17:32:04 msapiro postfix/smtpd[12206]: 00E7634028D:
> client=localhost[127.0.0.1]
> Oct 11 17:32:16 msapiro postfix/cleanup[12213]: 00E7634028D: hold:
> header Received: from msapiro.net (localhost [127.0.0.1])??by
> msapiro.net (Postfix) with SMTP id 00E7634028D??for
> <mark at ms2.msapiro.net>; Tue, 11 Oct 2016 17:31:59 -0700 (PDT) from
> localhost[127.0.0.1]; from=<mark at msapiro.net> to=<mark at ms2.msapiro.net>
> proto=SMTP helo=<msapiro.net>
> Oct 11 17:32:16 msapiro postfix/cleanup[12213]: 00E7634028D:
> message-id=<20161012000950.GA11294 at msapiro.net>
> Oct 11 17:32:21 msapiro MailScanner[12746]: New Batch: Scanning 1
> messages, 1341 bytes
> Oct 11 17:32:21 msapiro MailScanner[12746]: Requeue: 00E7634028D.AF42A
> to 476773402BF
> Oct 11 17:32:21 msapiro MailScanner[12746]: Unscanned: Delivered 1 messages
>