On Tue, 22 Jan 2019 at 06:22, Stephen McHenry
wrote:
> I've been running Postfix for many years now (so thanks to Wietse and all
> the others who have put in hard work to make it such a great mail system)
> and recently I built a new mail server and copied most of the config files
> from the old
On 22 Jan 2019, at 5:22 pm, James Brown mailto:jlbr...@bordo.com.au>> wrote:
>
> On 22 Jan 2019, at 5:18 pm, Larry Stone <mailto:lston...@stonejongleux.com>> wrote:
>>
>> On Jan 21, 2019, at 6:04 PM, Wietse Venema > <mailto:wie...@porcupine.org>>
On 21 Jan 2019, at 22:13, Viktor Dukhovni wrote:
> 12. The version numbering scheme for Berkeley DB changed from a
> five-part number to a three-part number of the form
> ... This release is numbered 18.1.x,
Do you know why the current version in FreeBSD ports is 6.2.32_1? (or the
On 22 Jan 2019, at 5:18 pm, Larry Stone wrote:
>
> On Jan 21, 2019, at 6:04 PM, Wietse Venema wrote:
>>
>> postfix-3.4-20190121-nonprod-logger has lightly-tested code for
>> logging to file without using syslogd.
>>
>
> I just successfully built it on a
I've been running Postfix for many years now (so thanks to Wietse and all
the others who have put in hard work to make it such a great mail system)
and recently I built a new mail server and copied most of the config files
from the old one.
After a couple of months, I began to notice that it
On Jan 21, 2019, at 6:04 PM, Wietse Venema wrote:
>
> postfix-3.4-20190121-nonprod-logger has lightly-tested code for
> logging to file without using syslogd.
>
I just successfully built it on a Mojave system and so far, all looks good. One
test email sent out (my Postfix is o
Hi viktor,
See the posted certificates from wire.
I am not getting why this is random behaviour. At some time only certificate
marked as expired and after some time same certificate gets marked as valid.
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
> On Jan 21, 2019, at 11:41 PM, James Brown wrote:
>
> Just tried it on MacOS Mojave machine. Sudo make install ends with:
>
> dict_db.c:768:2: error: "Unsupported Berkeley DB version"
> #error "Unsupported Berkeley DB version"
> ^
>
> I used:
>
> I tried adding ‘-lda’ to the AUXLIBS string
On 22 Jan 2019, at 11:04 am, Wietse Venema mailto:wie...@porcupine.org>> wrote:
>
> postfix-3.4-20190121-nonprod-logger has lightly-tested code for
> logging to file without using syslogd.
>
> This solves a usability problem in MacOS, may help to work around
> a logging
Viktor,
I didn't include it because I could not find it. Which is, yes, confusing
to me. I looked for other failures from lmtp, but did not seen anything.
Thanks,
Patrick
On Mon, Jan 21, 2019 at 1:23 PM Viktor Dukhovni
wrote:
> > On Jan 21, 2019, at 3:44 PM, Patrick Mahan wrote:
> >
> >
Whoops! You are correct, too many mailing lists, my apologies.
Patrick
On Mon, Jan 21, 2019 at 1:23 PM Wietse Venema wrote:
> Patrick Mahan:
> > service imap-login {
> > inet_listener imap {
>
> Wrong mailing list.
>
> Wietse
>
On Mon, Jan 21, 2019 at 07:04:56PM -0500, Wietse Venema wrote:
> postfix-3.4-20190121-nonprod-logger has lightly-tested code for
> logging to file without using syslogd.
I see that the postlogd(8) service correctly uses a unix-dgram
service to avoid message reordering, so the usual att
postfix-3.4-20190121-nonprod-logger has lightly-tested code for
logging to file without using syslogd.
This solves a usability problem in MacOS, may help to work around
a logging bottleneck with systemd, and solves 99% of the problem
for logging to stdout in a container (hopefully we have 100
Patrick Mahan:
> FreeBSD 11.2, Postfix 3.3.2, Dovecot 2.3.4
>
> Random user verification failures are occurring and I am not sure why.
>
> Here's an example -
>
> >From /var/log/maillog:
>
> Failure:
>
> Jan 21 12:20:41 ns postfix/smtpd[31736]: NOQUEUE: reject: RCPT from
>
Patrick Mahan:
> service imap-login {
> inet_listener imap {
Wrong mailing list.
Wietse
> On Jan 21, 2019, at 3:44 PM, Patrick Mahan wrote:
>
> Jan 21 12:20:41 ns postfix/smtpd[31736]: NOQUEUE: reject: RCPT from
> mta2.email.famousfootwear.com[136.147.183.86]: 450 4.1.1 :
> Recipient address rejected: unverified address: unknown mail transport error;
> from=
> to= proto=ESMTP
I am trying to change the imaps port-number to a non-standard port ()
since it seems that buisness.comcast.net is intercepting the standard imaps
port number and repeated emails requesting that they stop have been ignored.
This is only an issue when I am trying to access my personal mail
FreeBSD 11.2, Postfix 3.3.2, Dovecot 2.3.4
Random user verification failures are occurring and I am not sure why.
Here's an example -
>From /var/log/maillog:
Failure:
Jan 21 12:20:41 ns postfix/smtpd[31736]: NOQUEUE: reject: RCPT from
mta2.email.famousfootwear.com[136.147.183.86]: 450 4.1.1 :
On 2019-01-20 14:40, John Stoffel wrote:
> The only problem with Digital Ocean right now is that Charter/Spectrum
> in the US has blocked all (most? At least the one I'm using...) blocks
> assigned to DO for some insane reason.
The insane reason is phishing spam, and DO ignoring abuse notices.
> "Yuval" == Yuval Levy writes:
Yuval> On 2019-01-20 14:40, John Stoffel wrote:
>> The only problem with Digital Ocean right now is that Charter/Spectrum
>> in the US has blocked all (most? At least the one I'm using...) blocks
>> assigned to DO for some insane reason.
Yuval> Why insane?
On 2019-01-20 14:40, John Stoffel wrote:
The only problem with Digital Ocean right now is that Charter/Spectrum
in the US has blocked all (most? At least the one I'm using...) blocks
assigned to DO for some insane reason.
Why insane? Having been a DO customer for more than five years, I am
Thanks viktor. All Certificates are valid for these
certificates Im getting above logs. Is there any issue due to missing root
CA certificate as client has not received any root CA certificate(Subject
and issuer different in all certificates) in capture ? Correct me If am
wrong I can only see End
> On Jan 21, 2019, at 2:40 AM, phoenixsagar wrote:
>
> Logs are like :
> postfix/backend/smtp[95117]: CA certificate verification failed for
> abc-abc.mail.abc.outlook.com[111.111.111.111]:25: certificate has expired
The key context here is "CA certificate verification". The expired
Just updated Logs
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
24 matches
Mail list logo
