Linkcheck:
[ Charset windows-1252 converted... ]
> > Drop the quotes!
>
> I just have whilst following advice from David Burgin - in fact I
> commented out the macro entirely but still the same - dkim ok but
> UNPARSEABLE_RELAY still present.
Of course. You are now back to the milter macros li
> Drop the quotes!
I just have whilst following advice from David Burgin - in fact I
commented out the macro entirely but still the same - dkim ok but
UNPARSEABLE_RELAY still present.
> Where does Postfix documentation say that you need to use quoted strings?
It doesn't, I agree. And forgot
Thanks for your help. I checked as you suggested and got
milter_connect_macros=j {daemon_name} v (no quotes, no underscore). I
commented out my own version and ran with the default, which correctly
includes the mail server name in the dkim check but still has
UNPARSEABLE_RELAY.
I suppose it m
On 02/12/2019 12:12, Linkcheck wrote:
> Thanks, but I already had that. Although I had the "v" before the daemon_addr
> when I first tried it...
> milter_connect_macros="i j {daemon_name} v {daemon_addr} _"
>
> I have now tried it with the v where you suggest it but still gives
> UNPARSEABLE_R
Linkcheck:
[ Charset windows-1252 converted... ]
> Thanks, but I already had that. Although I had the "v" before the
> daemon_addr when I first tried it...
>milter_connect_macros="i j {daemon_name} v {daemon_addr} _"
Drop the quotes! Where does Postfix documentation say that
you need to use q
Dnia 2.12.2019 o godz. 11:12:15 Linkcheck pisze:
> Thanks, but I already had that. Although I had the "v" before the
> daemon_addr when I first tried it...
> milter_connect_macros="i j {daemon_name} v {daemon_addr} _"
>
> I have now tried it with the v where you suggest it but still gives
> UNP
Thanks, but I already had that. Although I had the "v" before the
daemon_addr when I first tried it...
milter_connect_macros="i j {daemon_name} v {daemon_addr} _"
I have now tried it with the v where you suggest it but still gives
UNPARSEABLE_RELAY. Also, I understand the quotes are essential
Dnia 1.12.2019 o godz. 14:18:32 Linkcheck pisze:
> Ok, thanks. I can live with that.
>
> But what about UNPARSEABLE_RELAY? How can I preoperly fix that? Do I
> really have to nullify the rule or is there something in postfix
> that I've got wrong?
I fixed this in one of SpamAssassin's Perl modul
On 01/12/2019 15:18, Linkcheck wrote:
> But what about UNPARSEABLE_RELAY? How can I preoperly fix that? Do I really
> have to nullify the rule or is there something in postfix that I've got wrong?
Try appending _ to the default connect macros. That does it for me.
milter_connect_macros = j {daem
Ok, thanks. I can live with that.
But what about UNPARSEABLE_RELAY? How can I preoperly fix that? Do I
really have to nullify the rule or is there something in postfix that
I've got wrong?
On 01/12/2019 12:01, Linkcheck wrote:
> I applied the recommendations from this thread (for which, many thanks!) with
> some help from the spamassassin forum. Almost all of it works now with the
> following exception. On postfix restart the following message is logged.
>
> "Could not retrieve se
I applied the recommendations from this thread (for which, many thanks!)
with some help from the spamassassin forum. Almost all of it works now
with the following exception. On postfix restart the following message
is logged.
"Could not retrieve sendmail macro "i"!. Please add it to
confMILTE
Jaroslaw Rafa wrote
> Dnia 4.11.2019 o godz. 04:31:51 linkcheck pisze:
> I don't know as I don't use DMARC. I only DKIM sign outgoing mail, I don't
> verify DKIM nor DMARC on incoming mail. Just try what order works best.
Ok. Thanks for all the help. :)
--
Sent from: http://postfix.1071664.n5
Dnia 4.11.2019 o godz. 04:31:51 linkcheck pisze:
>
> Pickup only gets run from sendmail which is called by content_filter OR by
> apache. So that now makes sense. Taken me hours to see that. :(
>
> So what I need is, as you said, to remove content_filter in master.cf and in
> main.cf to put in a
@lbutlr wrote
> On 01 Nov 2019, at 10:03, linkcheck <
> postfix@.co
> > wrote:
>> Jaroslaw Rafa wrote
> Apache should not be posting mail via pickup. Use an SMTP plugin that
> authenticates just like anyone else.
If the mail and web servers were separate I would agree but there is a lot
of overh
Sorry for the delay in replying. I've been looking at this and trying to make
it work in my head, but keep coming up with DKIM running twice. Please bear
with me. Your setup of...
smtpd_milters = inet:localhost:10025, unix:spamass/spamass.sock
non_smtpd_milters = inet:localhost:10025
...suggests
On 01 Nov 2019, at 10:03, linkcheck wrote:
> Jaroslaw Rafa wrote
>> Dnia 31.10.2019 o godz. 12:16:56 linkcheck pisze:
>> The best answer is to use spamassassin as a milter, not as a post-queue
>> content filter as you have (and as I had).
>> After I changed configuration to run spamassassin as mil
> Also, note that the problem I'm trying to solve is apache posting through
> pickup, which does not DKIM sign due to DKIM being applied before pickup, as
> I understand it.
To have DKIM applied to messages posted via pickup, you have to include DKIM
milter in non_smtpd_milters= . This parameter
Jaroslaw Rafa wrote
> Dnia 31.10.2019 o godz. 12:16:56 linkcheck pisze:
> The best answer is to use spamassassin as a milter, not as a post-queue
> content filter as you have (and as I had).
> After I changed configuration to run spamassassin as milter, everything is
> signed only once.
Thanks, bu
Dnia 31.10.2019 o godz. 12:16:56 linkcheck pisze:
>
> What changes to main/master do I need to make in order to DKIM sign all mail
> once only, preferably before spamassassin?
Not long ago I asked a similar question here.
The best answer is to use spamassassin as a milter, not as a post-queue
co
20 matches
Mail list logo
