Hi,
I have a wildcard SSL certificate file in pfx format (Include private key
export from Windows Server). I'm little confuse with smtpd_tls_cert_file
,smtpd_tls_key_file settings. How can i prepare these cert_file and
key_file files with openssl command. Actually i know how i create private
key
My system is configured with default SMTPUTF8 settings, i.e.:
root@rincewind:~ # postconf -d | grep utf8
smtputf8_autodetect_classes = sendmail, verify
smtputf8_enable = ${{$compatibility_level} < {1} ? {no} : {yes}}
strict_smtputf8 = no
root@rincewind:~ # postconf -n | grep ut
Philip Paeps:
> My system is configured with default SMTPUTF8 settings, i.e.:
>
> root@rincewind:~ # postconf -d | grep UTF8
> smtputf8_autodetect_classes = sendmail, verify
> smtputf8_enable = ${{$compatibility_level} < {1} ? {no} : {yes}}
> strict_smtputf8 = no
> root@rincewi
On 2017-04-10 09:51:42 (-0400), Wietse Venema wrote:
> Philip Paeps:
> > My system is configured with default SMTPUTF8 settings [...]
> >
> > This works perfectly fine (probably because, sadly, SMTPUTF8 is still
> > quite rare in the wild) except occasionally I'll get an NDR for a
> > locally sub
> On Apr 10, 2017, at 6:02 AM, Selcuk Yazar wrote:
>
> I have a wildcard SSL certificate file in pfx format.
More accurately, you have a PKCS#12 file, which contains a password-
protected copy of the private key and the certificate chain.
> I'm little confuse with smtpd_tls_cert_file ,smtpd_tl
We continue to receive messages addressed to Postmaster from our MX
host. All appear to be related to a single original transmission.
The issue seems to be some sort of time-out with the Amavis proxy.
Is there some way of determining exactly what is wrong with this
specific sender's message?
T
James B. Byrne:
> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
> timeout talking to proxy 127.0.0.1:10024
> 67 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: proxy-reject:
> END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=
> to= proto=ESMTP helo=
The spam
On Mon, April 10, 2017 11:29, Wietse Venema wrote:
> James B. Byrne:
>> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
>> timeout talking to proxy 127.0.0.1:10024
>> 67 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]:
>> proxy-reject:
>> END-OF-MESSAGE: 451 4.3.0 Error: que
James B. Byrne:
[ Charset ISO-8859-1 converted... ]
>
> On Mon, April 10, 2017 11:29, Wietse Venema wrote:
> > James B. Byrne:
> >> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
> >> timeout talking to proxy 127.0.0.1:10024
> >> 67 Apr 8 10:50:27 inet08 postfix-p25/smtpd[
> "Viktor" == Viktor Dukhovni writes:
>> On Apr 4, 2017, at 5:26 PM, John Stoffel wrote:
>>
>> But I only want this replamcent to happen for email that comes from a
>> specific set of outside servers. I think I might have to run my own
>> milter here to do this. I really can't depend on
On 10.04.2017 18:33, James B. Byrne wrote:
>
> On Mon, April 10, 2017 11:29, Wietse Venema wrote:
>> James B. Byrne:
>>> The issue seems to be some sort of time-out with the Amavis proxy.
>>> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
>>> timeout talking to proxy 127.0.0.1
> On Apr 10, 2017, at 4:01 PM, John Stoffel wrote:
>
> Since I built 2.11.9 by hand, I'm willing to do this hack as well I
> think. It's a total hack too... and I'm still amazed I'm the only one
> seeing this. But maybe most people who use Office365 for spam
> filtering also use Exchange on th
12 matches
Mail list logo
