* on the Wed, Jun 03, 2015 at 12:48:32AM +0200, Thomas Keller wrote:
> Would it be possible / what would be the best way to set up some filter
> in Postfix, so that all plaintext emails would be encrypted upon
> delivery with my gpg public key. In effect, if would like like all
> people send me en
brad.chand...@mbchandler.net:
> On 2015-06-03 10:49 am, wie...@porcupine.org wrote:
> > brad.chand...@mbchandler.net:
> >> How does the memcache interact with the
> >> proxy:btree:/var/lib/postfix/postscreen_cache?
> >
> > It happens in the Postfix memcache client.
> >
> > When you specify a back
I managed to fix this on my own; please disregard.
Thank you.
On 2015-06-03 10:49 am, wie...@porcupine.org wrote:
brad.chand...@mbchandler.net:
How does the memcache interact with the
proxy:btree:/var/lib/postfix/postscreen_cache?
It happens in the Postfix memcache client.
When you specify a backup store in the Postfix memcache client
configuration file
On Wed, Jun 3, 2015 at 3:18 PM, Noel Jones wrote:
> On 6/3/2015 11:18 AM, francis picabia wrote:
>> On Wed, Jun 3, 2015 at 11:42 AM, Wietse Venema wrote:
>>> francis picabia:
> /etc/postfix/main.cf:
> smtpd_client_restrictions =
> check_client_access cidr:/etc/postfix/clie
I read the README_SASL document. I'm on CentOS 5.x using Cyrus SASL
2.1.22, attempting to get Postfix 3.0.1 to compile in SASL support
correctly, using the following flags:
# make makefiles CCARGS="-DUSE_SASL_AUTH -DUSE_CYRUS_SASL
-I/usr/include/sasl" AUXLIBS="-L/usr/lib/sasl -lsasl2"
On 6/3/2015 11:18 AM, francis picabia wrote:
> On Wed, Jun 3, 2015 at 11:42 AM, Wietse Venema wrote:
>> francis picabia:
/etc/postfix/main.cf:
smtpd_client_restrictions =
check_client_access cidr:/etc/postfix/client_access.cidr
/etc/postfix/client_access.cidr:
francis picabia:
> On Wed, Jun 3, 2015 at 11:42 AM, Wietse Venema wrote:
> > francis picabia:
> >> > /etc/postfix/main.cf:
> >> > smtpd_client_restrictions =
> >> > check_client_access cidr:/etc/postfix/client_access.cidr
> >> >
> >> > /etc/postfix/client_access.cidr:
> >> > 1.2.3.
On Wed, Jun 3, 2015 at 11:42 AM, Wietse Venema wrote:
> francis picabia:
>> > /etc/postfix/main.cf:
>> > smtpd_client_restrictions =
>> > check_client_access cidr:/etc/postfix/client_access.cidr
>> >
>> > /etc/postfix/client_access.cidr:
>> > 1.2.3.4/24 DUNNO
>> > 5.6.7.8/24 DU
On 3 Jun 2015, at 10:49, James B. Byrne wrote:
On Wed, June 3, 2015 10:41, Bill Cole wrote:
Note that if you want maximal protection for both message metadata
(headers and SMTP envelope) and content both in transit and after
delivery, you have a very large problem space that has ultimately
frus
brad.chand...@mbchandler.net:
> How does the memcache interact with the
> proxy:btree:/var/lib/postfix/postscreen_cache?
It happens in the Postfix memcache client.
When you specify a backup store in the Postfix memcache client
configuration file, the Postfix memcache client will update
both the
I've read over the how-to, man page, and all of the postscreen stuff as
I could find in the mailing list archives, but I'm still unsure about
something. How does the memcache interact with the
proxy:btree:/var/lib/postfix/postscreen_cache? Which one does postscreen
use to determine if a connect
On Wed, June 3, 2015 10:41, Bill Cole wrote:
> Note that if you want maximal protection for both message metadata
> (headers and SMTP envelope) and content both in transit and after
> delivery, you have a very large problem space that has ultimately
> frustrated some very smart people, including P
francis picabia:
> > /etc/postfix/main.cf:
> > smtpd_client_restrictions =
> > check_client_access cidr:/etc/postfix/client_access.cidr
> >
> > /etc/postfix/client_access.cidr:
> > 1.2.3.4/24 DUNNO
> > 5.6.7.8/24 DUNNO
> > 0.0.0.0/0 FILTER foo:bar
...
> How do I add the clie
On 3 Jun 2015, at 9:15, John Allen wrote:
Is there any way of testing for and refusing un-encrypted email?
The generic answer is "yes" but you need to define what you mean to pick
a mechanism.
If you mean email must be sent and received over an encrypted transport,
e.g. TLS, it is simply a
John Allen:
> > What level of encryption are you contextualizing? STARTTLS between
> > SMTP peers; or the message itself using S/MIME or PGP/GPG; or
> > something else?
> >
> The message itself (S/MIME or PGP/GPG).
> Its a medical practice. They have sending under control, but they are
> concerne
I agree with Thomas on this. If someone is spying on the server, any
past and future emails can be stolen. In case all incoming mails are
PGP-encrypted on the server, future emails can still be stolen, but
atleast any past correspondence is secure.
Yannik
Am 03.06.2015 um 03:50 schrieb Sebastian
On Wed, Jun 3, 2015 at 10:48 AM, Wietse Venema wrote:
> francis picabia:
>> >>> Let's say I want everything to go through the content filter unless
>> >>> it comes from 1.2.3.4/24 or 5.6.7.8/24 How is that configured?
>
> A cidr: based access map would be the most convenient here.
>
> /etc/postfi
On 2015-06-03 9:42 AM, James B. Byrne wrote:
On Wed, June 3, 2015 09:15, John Allen wrote:
Is there any way of testing for and refusing un-encrypted email?
secondary, would it be possible to do this based upon the recipient.
default would be encrypted, but email directed at some recipients may
b
francis picabia:
> >>> Let's say I want everything to go through the content filter unless
> >>> it comes from 1.2.3.4/24 or 5.6.7.8/24 How is that configured?
A cidr: based access map would be the most convenient here.
/etc/postfix/main.cf:
smtpd_client_restrictions =
check_client_
On Wed, June 3, 2015 09:15, John Allen wrote:
> Is there any way of testing for and refusing un-encrypted email?
> secondary, would it be possible to do this based upon the recipient.
> default would be encrypted, but email directed at some recipients may
> be
> in plain text.
>
What level of enc
Is there any way of testing for and refusing un-encrypted email?
secondary, would it be possible to do this based upon the recipient.
default would be encrypted, but email directed at some recipients may be
in plain text.
On Tue, Jun 2, 2015 at 1:30 PM, francis picabia wrote:
> On Tue, Jun 2, 2015 at 12:13 PM, Wietse Venema wrote:
>> francis picabia:
>>> A remaining concern is bypassing the content_filter
>>>
>>> I've scanned through http://www.postfix.org/FILTER_README.html
>>> and googled this issue.
>>>
>>> I t
23 matches
Mail list logo
