Hi,
so far, the RC1 works. There is only one thing that is bad:
Start and stop do not like directories inside /etc/postfix*
rns root@mx ~ # postfix stop
/usr/sbin/postconf: warning: read "ldap" configuration
"/etc/postfix-submiss
On 13/02/18 17:03, Viktor Dukhovni wrote:
> Sorry, you're right, the client has to enforce TLS, whether implicit
> or not. Some clients try multiple ports and multiple operating modes,
> so might also try port 25 in the clear, 465 with TLS and 587 with or
> without STARTTLS. Such clients are subj
> On Feb 12, 2018, at 10:58 PM, Peter wrote:
>
> There is one case that I can think of. Older clients (Thunderbird comes
> to mind) offered an opportunistic STARTTLS setting, so that if the
> server offered TLS it would connect with TLS but if not it would
> continue to connect via plain text.
On 13/02/18 16:30, Viktor Dukhovni wrote:
> There's not much gain. If both the client and the server are misconfigured
> on port 587, a client might send passwords and message content in the clear.
> If at least one insists on TLS, and the server does not offer SASL auth prior
> to TLS, there's no
> On Feb 12, 2018, at 9:05 PM, @lbutlr wrote:
>
>> Compatability with the clients that only implement one?
>
> Are there any? It's been a long time since I saw someone using an old enough
> Outlook to require 465.
There's not much gain. If both the client and the server are misconfigured
on
On 2/12/2018 9:05 PM, @lbutlr wrote:
On 2018-02-12 (18:28 MST), Harald Koch wrote:
I can't think of a single reason to have two submission ports.
Compatability with the clients that only implement one?
Are there any? It's been a long time since I saw someone using an old enough
Outlook to re
On 2018-02-12 (18:28 MST), Harald Koch wrote:
>
>> I can't think of a single reason to have two submission ports.
>
> Compatability with the clients that only implement one?
Are there any? It's been a long time since I saw someone using an old enough
Outlook to require 465.
--
The only reaso
>
> I can't think of a single reason to have two submission ports.
>
Compatability with the clients that only implement one?
On 2018-02-11 (15:12 MST), Viktor Dukhovni wrote:
>
> It remains to be seen whether the new RFC actually changes practices in
> the field, but there is now some "official" support for the born-again
> port 465 "submissions" service.
I can't think of a single reason to have two submission ports.
Will get back when I really know the definitive issue. Won't bother with
infrastructure issues here.
Am 13. Februar 2018 02:04:20 schrieb Server Messages :
I also have to check if my receiving server might be rejecting cause there
are not all dns settings correct on the vm or sort of things.
I also have to check if my receiving server might be rejecting cause there
are not all dns settings correct on the vm or sort of things. I hate vm
testing but as i am working on a complete and a bit complex server setup i
decided to don't hassle with a live server. But maybe a small cheap cloud
The thing here is my main line is connected to a vpn through a pfsense
firewall so i have to check why i cannot send through port 25 (it is open
of course) or what causes that the mail is not received. To be honest I did
not look really deep into it until now so i have to do some thorough
check
Server Messages:
> Hm as you mention it i am connected through a VPN so there has to be
> something else. Have to check that again.
Surely you can run more than one VPN?
Wietse
Hm as you mention it i am connected through a VPN so there has to be
something else. Have to check that again.
Thanks
Am 13. Februar 2018 01:03:39 schrieb Wietse Venema :
TG Servers:
Hi,
how can I best test postfix delivery from a local VM if port 25 is
blocked by ISP.
My only intention is
TG Servers:
> 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.
Use a VPN?
Wietse
> Or is there any other solution how I could get po
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!
> On Feb 12, 2018, at 3:27 PM, flymike wrote:
>
> With the milter option, can I still use transport_maps to set the custom
> nexthop?
Yes.
> I'm wondering if smtp_generic_maps are applied after or before
> transport_maps?
Milters happen on input when messages are received, transport
lookups
Thanks, Viktor.
With the milter option, can I still use transport_maps to set the custom
nexthop? I'm wondering if smtp_generic_maps are applied after or before
transport_maps?
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
I am generally using postfix-logwatch for tracking log files.
However, I was thinking about something that is working in real time,
scripts can be run by cron in some period time.
Then the best solution could be write some syslog phraser or redirect
syslog to some
application eg. written in Java t
> On Feb 12, 2018, at 12:10 PM, flymike wrote:
>
> I have a requirement to deliver via 'X' when sender = 'A' /and/ recipient =
> 'B', else deliver via configured defaults.
> I see how I could use sender_dependent_default_transport_maps to set nexthop
> to 'X' when sender = 'A' but I still need
I am generalny using postfix-logwatch for tracking log files.
However, I was thinking about something that is working in real time,
scripts can be run by cron in some period time.
Then the best could be write some syslog phraser or redirect syslog to some
application eg. written in Java to interpr
On 11.02.18 20:26, Harald Koch wrote:
Is this change in long-standing opinion of the IETF only because existing
implementations so often ignore STARTTLS, or is there actually a security
issue with STARTTLS (instead of implicit TLS)?
I guess it's about firewalls - you can run service without TLS
I have a requirement to deliver via 'X' when sender = 'A' /and/ recipient =
'B', else deliver via configured defaults.
I see how I could use sender_dependent_default_transport_maps to set nexthop
to 'X' when sender = 'A' but I still need to deal with the additional
condition that recipient = 'B'.
I
j.emerlik:
> I would like have policy service that will be able to write do data base
> some information eg. when exactly message was sent, message ID, DSN if
> soemthing goes wrong. That means it should be working with Postfix queue.
You can use "postqueue -j" to get a machine-readable queue lis
Viktor Dukhovni:
>
>
> > On Feb 12, 2018, at 10:06 AM, j.emerlik wrote:
> >
> > It is possible to write some policy service that will be working with
> > postfix queue ?
>
> No. That's a bad idea anyway. To track message flow, parse the logs.
The closest that comes to this is a daemon that
On 12.02.2018 16:44, j.emerlik wrote:
> I would like have database and there information : Message ID, Sent
> Date (or last date of send trying), DSN, number of send attempts,
> Mail_From, RCPT_TO.
That type of information should be extracted from the Postfix logs,
as existing tools like 'pflogsu
Hi dav,
My internet was down overnight, snow plough hit encapsulation point.
These are my postfix config files, plus my dovecot stuff.
Hope it helps.
John A
On 2018-02-11 06:12 PM, David Mehler wrote:
Hello,
Does anyone have Android's aquamail app successfully connecting to a
Postfix serv
I would like have database and there information : Message ID, Sent Date
(or last date of send trying), DSN, number of send attempts, Mail_From,
RCPT_TO.
It would be helpful to create statistics or check exacly what happened
with the messages sent, eg, six months ago.
2018-02-12 16:22 GMT+01:0
> On Feb 12, 2018, at 10:06 AM, j.emerlik wrote:
>
> It is possible to write some policy service that will be working with postfix
> queue ?
No. That's a bad idea anyway. To track message flow, parse the logs.
--
Viktor.
Hi, I would think you could write a script to do what you need ?
Here is one I use that is in Python.
[root@mta3 alf02013]# Summary
Usage: Summary -s -h {-|POSTFIX_LOG} [ POSTFIX_LOG .. ]
Summarize postfix mail log. Gzipped files are OK.
Print one line for each delivered email, wi
On 12.02.2018 16:06, j.emerlik wrote:
> I would like have policy service that will be able to write do data
> base some information eg. when exactly message was sent, message ID,
> DSN if soemthing goes wrong. That means it should be working with
> Postfix queue.
That's not really a specific desc
Hello,
My thanks to those who suggested the debug document. While that wasn't
it, the issue wasn't with postfix at all, it did get me looking at
Dovecot. Postfix does Sasl authentication using Dovecot. Dovecot gets
it's username and password from a MySQL database. The query Dovecot
was sending was
Lately I wrote in python postfix policy service that can do something for
me what I want.
Now I am thinking about next service butI don't know maybe it is not
possible.
That is my question:
There is posssible write some service similar to eg.
check_policy_service unix:private/policy-spf
It is
33 matches
Mail list logo
