On Sun, Mar 17, 2013 at 7:20 AM, <patrick.proniewski_at_free.fr> wrote:
> - opendkim won't sign emails I send from my workstation to my server via an ssh tunnel (or if i use telnet port 25 to send an email from localhost)
> -------------------------------------------------------
> transcript for a mail submitted via ssh tunnel (or telnet on localhost):
>
> rack postfix/smtpd[57044]: connect from localhost[127.0.0.1]
> rack milter-greylist: (unknown id): Sender IP 127.0.0.1 and address <patpro_at_mydomain.tld> are SPF-compliant, bypassing greylist
> rack postfix/smtpd[57044]: NOQUEUE: client=localhost[127.0.0.1]
> rack postfix/smtpd[57049]: connect from localhost[127.0.0.1]
> rack postfix/smtpd[57049]: 5E0BE1CC020: client=localhost[127.0.0.1], orig_client=localhost[127.0.0.1]
> rack postfix/cleanup[57050]: 5E0BE1CC020: message-id=<727D4403-CE21-4282-A3F3-0C056924C270_at_mydomain.tld>
> rack postfix/smtpd[57049]: disconnect from localhost[127.0.0.1]
> rack postfix/qmgr[29993]: 5E0BE1CC020: from=<patpro_at_mydomain.tld>, size=2220, nrcpt=1 (queue active)
> rack amavis[50721]: (50721-14) Passed CLEAN {RelayedInternal}, LOCAL [127.0.0.1]:13772 [127.0.0.1] <patpro_at_mydomain.tld> -> <root_at_mydomain.tld>, Message-ID: <727D4403-CE21-4282-A3F3-0C056924C270_at_mydomain.tld>, mail_id: 0ha-G1TZRb7p, Hits: -3.4, size: 1712, queued_as: 5E0BE1CC020, 1762 ms
> rack postfix/smtpd[57044]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 5E0BE1CC020; from=<patpro_at_mydomain.tld> to=<root_at_mydomain.tld> proto=ESMTP helo=<[127.0.0.1]>
> rack postfix/local[57051]: 5E0BE1CC020: to=<patpro_at_mydomain.tld>, orig_to=<root_at_mydomain.tld>, relay=local, delay=0.06, delays=0.04/0/0/0.02, dsn=2.0.0, status=sent (delivered to command: /usr/local/bin/procmail -a "$EXTENSION")
> rack postfix/qmgr[29993]: 5E0BE1CC020: removed
>
> -------------------------------------------------------
You have LogWhy set to yes in your opendkim.conf. If opendkim was
seeing the message, there would be a line there that says why it
decided not to sign it. Since there is no line from opendkim, we can
only conclude that postfix is not actually submitting it to opendkim
when you submit the messages from the ssh tunnel or from the
commandline.
I don't know enough about postfix configuration to know if the milter
_should_ be getting called from your configuration.
> Any idea? (and by the way, what is the expected behavior of MilterDebug? At "3" it looks like it won't log more than "0".
I haven't delved into that myself, maybe Murray or SM can provide more info.
...Todd
--
The total budget at all receivers for solving senders' problems is $0.
If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine
Received on Sun Mar 17 2013 - 23:30:31 PST