Struggling with DKIM signing

Nick Howitt nick at howitts.co.uk
Wed Nov 6 11:06:43 CET 2024




On 06/11/2024 09:58, Matus UHLAR - fantomas wrote:
>>> On 05.11.24 16:14, Nick Howitt wrote:
>>>> Sorry, but I am trying to get something going that was based on the 
>>>> ClearOS configs but I've copied over too much and then mixed it 
>>>> with internet references.
>>>>
>>>> 127.0.0.1:10026 looks like a ClearOS thing and is not needed.
>>>>
>>>> The submission service still exists, so I should:
>>>> 1 - get rid of the 127.0.0.1:10026 but from master.cf.
>
> I guess the "but" does not belong there
LOL. Typo for bit.
>
>>>> 2 - in master.cf change the submission line "-o 
>>>> content_filter=smtp-amavis:[127.0.0.1]:10024" to "-o 
>>>> content_filter=smtp-amavis:[127.0.0.1]:10028" (just to avoid 10026 
>>>> for now)
>
> I guess you mean "main.cf here"
No. master.cf:

    submission inet n       -       y       -       - smtpd
       -o syslog_name=postfix/submission
       -o smtpd_tls_security_level=encrypt
       -o smtpd_sasl_auth_enable=yes
       -o smtpd_tls_auth_only=yes
       -o smtpd_reject_unlisted_recipient=no
       -o smtpd_sasl_type=dovecot
       -o smtpd_sasl_path=private/auth
       -o content_filter=smtp-amavis:[127.0.0.1]:10028


>
>>>> 3 - in amavis 50-user add:
>>>>      $inet_socket_port = [10024,10028];  # listen on two ports
>>>>      $interface_policy{'10028'} = 'ORIGINATING';
>>>>
>>>> And that should do it?
>
>> On 06/11/2024 09:28, Matus UHLAR - fantomas wrote:
>>> this should do it,
>>>
>>> I still wonder how do you send mail to amavis?
>>>
>>> is content_filter defined in main.cf ?
>
> On 06.11.24 09:36, Nick Howitt wrote:
>> Yes
>
>>> is content_filter defined in master.cf services submission and 
>>> submissions (smtps)?
>
>> For submission see 2 above. I don't use smtps. I know it is in common 
>> use, but I don't believe it was ever recognised as a standard.
>
>>> I guess you don't need to define it in 127.0.0.1:10025 as this is 
>>> where mail returns from content_filter.
>
>> That is already defined and receives amavis from port 10024. Now it 
>> also gets amavis from port 10028.
>
>
> do I guess your 127.0.0.1:10025 now has
>
>  -o content_filter=
>
> like mine, so it does not feed the message back to amavis
>
Yes, as posted somewhere earlier:

    127.0.0.1:10025 inet  n    -    n    -    - smtpd
         -o content_filter=
         -o local_recipient_maps=
         -o relay_recipient_maps=
         -o smtpd_restriction_classes=
         -o smtpd_client_restrictions=
         -o smtpd_helo_restrictions=
         -o smtpd_sender_restrictions=
         -o smtpd_recipient_restrictions=permit_mynetworks,reject
         -o mynetworks=127.0.0.0/8
         -o strict_rfc821_envelopes=yes
         -o smtpd_error_sleep_time=0
         -o smtpd_soft_error_limit=1001
         -o smtpd_hard_error_limit=1000
         -o
    receive_override_options=no_header_body_checks,no_unknown_recipient_checks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.amavis.org/pipermail/amavis-users/attachments/20241106/92676096/attachment.htm>


More information about the amavis-users mailing list