Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

2019-06-03 Thread Wietse Venema
Jos Chrispijn: [ Charset windows-1252 converted... ] > On 3-6-19 13:09, Wietse Venema wrote: > > postmap hash:/postfix/tables/spamtrap what is this? > > # spamtrap 180711 > partmaps@?? DISCARD > > in main.cf > check_recipient_access? hash:/postfix/tables/spamtrap, > > I

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

2019-06-03 Thread Jos Chrispijn
On 3-6-19 13:09, Wietse Venema wrote: postmap hash:/postfix/tables/spamtrap what is this? # spamtrap 180711 partmaps@   DISCARD in main.cf check_recipient_access  hash:/postfix/tables/spamtrap, I added this some time ago referring to

Re: special catch-all processing

2019-06-03 Thread Wietse Venema
Hajo Locke: > Hello List, > > i have a question to processing of catch-all adresses between different > versions.? I see a difference between postfix 3.1 and 3.3 which i cant > explain. > I have this scenario: > > Using virtual table i have a catch-all forward from a subdomain to a domain > >

Re: smtp relay server security

2019-06-03 Thread Viktor Dukhovni
> On Jun 3, 2019, at 9:02 AM, De Petter Mattheas > wrote: > > For the moment we have a rule that only allow mail from exchange server > address to postfix (relay server), but when somebody spoofs this address mail > gets accept and you can send your mail to anybody as anybody. > > When I

Re: smtp relay server security

2019-06-03 Thread Jon Radel
On 6/3/19 10:31 AM, Matus UHLAR - fantomas wrote: > >>> For the moment we have a rule that only allow mail from exchange server >>> adres to postfix (relay server), >> >> show us. >> >> # mynetworks = xxx.xxx.xxx.xxx/32, 127.0.0.1/32 >> smtpd_recipient_restrictions = >>

RE: smtp relay server security

2019-06-03 Thread De Petter Mattheas
They are in are in the same network only admin's can access the network, the users are in another vlan and can's ssh or rdp to the server. But I just wan't to make sure everything is secure and covered. That is the reason for the question. I thought authentication was possible without creating

Re: smtp relay server security

2019-06-03 Thread Matus UHLAR - fantomas
On 03.06.19 14:19, De Petter Mattheas wrote: Answers in after the # indenting the original answer usually giver much more readable result. outlook does support indenting... On 03.06.19 13:02, De Petter Mattheas wrote: How can we secure are postfix smtp relay server? complicated

Re: Different SSL certificate per virtual domain

2019-06-03 Thread Kris Deugau
Viktor Dukhovni wrote: Google and Microsoft deliver outbound mail for hundreds of thousands of domains from a common pool of outbound names. Nobody seems to mind. Some of us do mind, but there's really nothing we can do about it because any spam-control measures we might try would block far

RE: smtp relay server security

2019-06-03 Thread De Petter Mattheas
Hello Answers in after the # On 03.06.19 13:02, De Petter Mattheas wrote: >How can we secure are postfix smtp relay server? complicated question... >For the moment we have a rule that only allow mail from exchange server >adres to postfix (relay server), show us. # mynetworks =

Re: smtp relay server security

2019-06-03 Thread Matus UHLAR - fantomas
On 03.06.19 13:02, De Petter Mattheas wrote: How can we secure are postfix smtp relay server? complicated question... For the moment we have a rule that only allow mail from exchange server adres to postfix (relay server), show us. but when somebody spoofs this address mail gets accept

smtp relay server security

2019-06-03 Thread De Petter Mattheas
Hello How can we secure are postfix smtp relay server? For the moment we have a rule that only allow mail from exchange server adres to postfix (relay server), but when somebody spoofs this address mail gets accept and you can send your mail to anybody as anybody. When I check:

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

2019-06-03 Thread Wietse Venema
Jos Chrispijn: > Hi Jan, > > On 30-5-19 14:47, Jan Ceuleers wrote: > > Jos, what I think everybody is trying to tell you is that your cron job > > has swept the problem under the rug, for now, but that it is still there. > > Yes, I noted, thanks for that. > > What I have done is running this

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

2019-06-03 Thread Jos Chrispijn
Hi Jan, On 30-5-19 14:47, Jan Ceuleers wrote: Jos, what I think everybody is trying to tell you is that your cron job has swept the problem under the rug, for now, but that it is still there. Yes, I noted, thanks for that. What I have done is running this batch after a Postfix or Dovecot

special catch-all processing

2019-06-03 Thread Hajo Locke
Hello List, i have a question to processing of catch-all adresses between different versions.  I see a difference between postfix 3.1 and 3.3 which i cant explain. I have this scenario: Using virtual table i have a catch-all forward from a subdomain to a domain @sub.example.com @example.com