Hi,
how can I best test postfix delivery from a local VM if port 25 is
blocked by ISP.
My only intention is to setup another VM and make a network between them
and then send mails between them.
Or is there any other solution how I could get postfix from a VM to the
"world"?
Thanks!
Am 13. Februar 2018 09:52:53 schrieb Matus UHLAR - fantomas
<uh...@fantomas.sk>:
On 13.02.18 00:04, TG Servers wrote:
how can I best test postfix delivery from a local VM if port 25 is
blocked by ISP.
if you ISP doesn't unblock you, and you want to behave as mail server, you
have p
I had a typo in my config it it now listening on 127.0.0.1:11332 but I
am getting the same startup errors actually.
Am 17.02.2018 um 21:57 schrieb TG Servers:
> Hi,
>
> I am getting the following error messages when starting up postfix 3.2.4
>
> 2018-02-17T21:50:34.594521+01
Hi,
I am getting the following error messages when starting up postfix 3.2.4
2018-02-17T21:50:34.594521+01:00 ms2 postfix/cleanup[9220]: fatal:
host/service localhost/11332 not found: Name or service not known
2018-02-17T21:50:35.594843+01:00 ms2 postfix/pickup[8886]: warning:
Ok thanks will turn off all chroots and go stepwise forward tomorrow
Thanks
Am 17.02.2018 um 23:42 schrieb Wietse Venema:
> TG Servers:
>> Hi,
>>
>> I am getting the following error messages when starting up postfix 3.2.4
>>
>> 2018-02-17T21:50:34.5945
It's binded to both, the problem seems to be somewhere in chrooting as
Wietse already supposed, will try that tomorrow
Am 17.02.2018 um 23:48 schrieb Benny Pedersen:
> TG Servers skrev den 2018-02-17 22:45:
>> I had a typo in my config it it now listening on 127.0.0.1:11332 but I
>
Hi,
am I right with the assumption that tls_verify_cert in the mysql table
uses the native provided ssl-verify-server-cert algorithm provided by
MariaDB?
Because it doesn't work as expected with IP and it is known that the
MariaDB mechanism is broken as of now regarding verifying against IPs in
Hi,
is there a way in postfix to disable milters for outoging to mail to
dedicated IPs, or better, dedicated recipient addresses?
I am just fed up from fixing DKIM signatures to a way that it is
insecure just to get mail accepted from several mailing list
implementations because they are munging
On 19/05/2019 16:04, Wietse Venema wrote:
> Wietse Venema:
>> TG Servers:
>>> Hi,
>>>
>>> is there a way in postfix to disable milters for outoging to mail to
>>> dedicated IPs, or better, dedicated recipient addresses?
>>>
On 27 April 2019 21:18:14 "Bill Cole"
wrote:
On 27 Apr 2019, at 14:20, Phil Stracchino wrote:
On 4/26/19 5:15 PM, Bill Cole wrote:
On 26 Apr 2019, at 9:46, Phil Stracchino wrote:
I don't see a fundamental risk in rejecting mail from servers
claiming
a HELO hostname that doesn't
thanks for your reply.
I get dmarc pass from everywhere normally and also from every tool. this
is a majordomo problem because with other lists that are not on
majordomo there is no problem I can see. there are also articles
existing regarding this "bug" I saw now. it just does not rewrite the
Hi,
since I first tposted yesterday to this mailing list I got 100s of
rejected DMARC reports because Majordomo is not able to or configured
correctly to handle DMARC records.
The headers are not re-written correctly and so DKIM from my mail is
expected in 100s of mails from different IPs
st-id:list-owner:list-unsubscribe:\
list-subscribe:list-post:(o)openpgp:(o)autocrypt';
... o are oversigned headers
I will have to check this against opendkim then, thanks
On 19/04/2019 13:42, Benny Pedersen wrote:
> TG Servers skrev den 2019-04-19 12:45:
>> thanks for your reply.
>
&g
according to RFC this would be the full list for rspamd
sign_headers = 'from:reply-to:subject:date:\
to:cc:resent-to:resent-cc:resent-from:resent-date\
in-reply-to:references:';
although they leave it open as "subjective" regarding message-id,
in-reply-to and references
On 19/04/2019 16:13,
The problem is the header that is appended by majordomo it seems
according to this
https://outofcontrol.ca/blog/patch-majordomo-to-work-with-dmarc
The postfix sender IP from my mail server is 116.203.154.189 which is
verified correctly against DKIM and SPF
Then majordomo forwards the mails to the
Yes thanks Nick I am signing with rspamd and will have to check the
signed headers there
as this seems not compliant, I already checked that from the other
mails, thanks for the hint to you, too
On 19/04/2019 13:16, Nick wrote:
> On 2019-04-19 10:43 BST, TG Servers wr
to RFC6376 (opendkim standard) now and
the problem should be gone here, too.
/dev/null is always the nice way :)
Cheers
On 19/04/2019 15:48, B. Reino wrote:
> On Fri, 19 Apr 2019, TG Servers wrote:
>
>> Yes thanks Nick I am signing with rspamd and will have to check the
>&
yes it seems mailman changes reply-to, I just took the fields out of
RFC6376 now...
On 19/04/2019 17:47, Benny Pedersen wrote:
> TG Servers skrev den 2019-04-19 16:48:
>> according to RFC this would be the full list for rspamd
>>
>> sign_headers = 'from:reply-to:subject:da
Dominic, you should get the mails now, don't you?
On 20 April 2019 12:04:30 Dominic Raferd wrote:
On Fri, 19 Apr 2019 at 14:11, Benny Pedersen wrote:
i have now disabled milters from trusted maillists ips
How did you do this? It might help me. I have missed some of this thread
because
On 20/04/2019 14:59, Richard Damon wrote:
> On 4/20/19 8:08 AM, Reto wrote:
>> On Sat, Apr 20, 2019 at 07:31:06AM -0400, Richard Damon wrote:
>>> Where the issue comes is with DMARC, which restricts the DKIM protocol
>>> to be aligned with the From line of the message, and thus the MLM can't
20 matches
Mail list logo
