New Installation Help

Will aragonx at dcsnow.com
Mon Mar 25 18:52:02 UTC 2024


On 3/25/2024 2:41 PM, Mark Sapiro wrote:
> On 3/25/24 10:52, Will wrote:
>> Hi,
>>
>> Brilliant!  That solved my first issue.  Thank you so very much! Can 
>> we get that included on (https://www.mailscanner.info/postfix/)?  
>> That is what I was using to configure my system.
>
> Was that entry there but commented? I think Postfix may ship that way. 
> We should not that in https://www.mailscanner.info/postfix/
>
Yes, it was there but commented out.
>> Now my 2nd issue is that the milter wants to reject my test emails.  
>> Is there a way for me to tell why?
>>
>> Mar 25 13:42:44 dcsnow postfix/smtpd[51681]: connect from 
>> mail-il1-f176.google.com[209.85.166.176]
>> Mar 25 13:42:44 dcsnow postfix/smtpd[51681]: B128610A0C41: 
>> client=mail-il1-f176.google.com[209.85.166.176]
>> Mar 25 13:42:44 dcsnow postfix/cleanup[51687]: B128610A0C41: 
>> message-id=<CADk0RN5j+yHk6377WsRuMoKSyZi-oz9KBTc8tCk7SrMw+z6Mrw at mail.gmail.com>
>> Mar 25 13:42:45 dcsnow postfix/cleanup[51687]: B128610A0C41: 
>> milter-discard: END-OF-MESSAGE from 
>> mail-il1-f176.google.com[209.85.166.176]: milter triggers DISCARD 
>> action; from=<wyonker at gmail.com> to=<wyonker at dcsnow.com> proto=ESMTP 
>> helo=<mail-il1-f176.google.com>
>
> This is normal and expected. Postfix receives the message and 
> processes it, calling the milter at various steps. The milter 
> ultimately tells postfix to discard the original message, but it has 
> queued the message for MailScanner in /var/spool/MailScanner/milterin. 
> MailScanner picks it up from there and if it is to be delivered, 
> delivers it back to Postfix via QMQP.
>
Okay but it is actually rejecting the mail and sending reject messages 
to the senders!  Did I not include the correct bits in the log?



More information about the MailScanner mailing list