I'm in the process of migrating old server postfix 2.x to new server 3.x
new server uses almost identical postfix/dovecot/mysql virtual
domains/users configuration, so currently, both servers are set up for
aaa.tld, bbb.tld, ccc.tld
I've edited MX for aaa, aaa's email start arriving at new server
Thanks Viktor.
Ok. I had to read this about ten times but see what you are saying :)
Can i use a wildcard in global-recipients ?
Stu
On 09/01/2018 14:34, Viktor Dukhovni wrote:
On Jan 9, 2018, at 7:30 AM, Stuart Archer wrote:
I had assumed this would be a built in function to Postfix but
> On Jan 10, 2018, at 12:07 PM, Stuart Archer wrote:
>
> Can i use a wildcard in global-recipients ?
The lookup keys for access(5) tables with check_recipient_access are:
http://www.postfix.org/access.5.html
EMAIL ADDRESS PATTERNS
With lookups from indexed files such as DB or DBM
Dear all,
I am running postfix 3.3 and recently migrated all my virtual domains from
MySQL to Sqlite for performance reasons. So far, everything works fine however
up to 5-8 times a day, I am seeing an error message in my mail.log saying that
the Sqlite 3 database may be locked. Here is an exam
Viktor Dukhovni:
>
>
> > On Jan 10, 2018, at 12:07 PM, Stuart Archer wrote:
> >
> > Can i use a wildcard in global-recipients ?
>
> http://www.postfix.org/access.5.html
>
> EMAIL ADDRESS PATTERNS
>user@domain ...
>domain.tld ...
>.domain.tld ...
>user@ ...
Sebastian Wolfgarten:
> Dear all,
>
> I am running postfix 3.3 and recently migrated all my virtual
> domains from MySQL to Sqlite for performance reasons. So far,
> everything works fine however up to 5-8 times a day, I am seeing
> an error message in my mail.log saying that the Sqlite 3 database
Hi,
I am uncertain as to what’s causing the DB to get locked - I am also running
Roundcube (webmail) on the server, maybe that’s the reason. I will check the
permission roundcube uses to access the db, I think it can be read-only which
will hopefully fix the locking issue.
As a feature request
On 01/10/2018 09:28 PM, Sebastian Wolfgarten wrote:
> Hi,
>
> I am uncertain as to what’s causing the DB to get locked - I am also running
> Roundcube (webmail) on the server, maybe that’s the reason. I will check the
> permission roundcube uses to access the db, I think it can be read-only which
Hi,
I had two short questions regarding Postfix’s elliptic curve support for the
SMTP server.
1. Under the man documentation for: tls_eecdh_strong_curve the documentation
states “...approximately 128-bit security...”. Is that saying that it is
equivalent to 128-bits RSA or it provides an ell
> On Jan 10, 2018, at 5:38 PM, J Doe wrote:
>
> Hi,
>
> I had two short questions regarding Postfix’s elliptic curve support for the
> SMTP server.
>
> 1. Under the man documentation for: tls_eecdh_strong_curve the documentation
> states
> “...approximately 128-bit security...”. Is that sa
Sebastian Wolfgarten:
> Hi,
>
> I am uncertain as to what?s causing the DB to get locked - I am also running
> Roundcube (webmail) on the server, maybe that?s the reason. I will check the
> permission roundcube uses to access the db, I think it can be read-only which
> will hopefully fix the lo
> On Jan 10, 2018, at 7:45 PM, Wietse Venema wrote:
>
>> I am uncertain as to what?s causing the DB to get locked - I am also running
>> Roundcube (webmail) on the server, maybe that?s the reason. I will check the
>> permission roundcube uses to access the db, I think it can be read-only
>>
I'm in the process of enabling postscreen, and, just noticed started
getting these warnings today, after editing/adding postscreen
Jan 11 13:03:12 geko postfix/smtpd[5403]: warning: restriction
`check_sasl_access' ignored: no SASL support
Jan 11 13:03:54 geko postfix/smtpd[5403]: warning: restrict
On Thu, January 11, 2018 1:17 pm, Voytek wrote:
> I'm in the process of enabling postscreen, and, just noticed started
> getting these warnings today, after editing/adding postscreen
>
oops. forgot to add:
as a part of postscreen setup, I've altered
(was)
smtpd_sasl_auth_enable = yes
(current)
sm
RTFMing, I see that both opendkim and python-policyd-spf have
whitelisting capabilities (especially python-policyd-spf). But for the
most part, my legitimate incoming email passes DKIM or SPF, but often
not both. What I would like to do is accept email that passes either
DKIM or SPF, but the milter
On 1/10/2018 9:53 PM, li...@lazygranch.com wrote:
RTFMing, I see that both opendkim and python-policyd-spf have
whitelisting capabilities (especially python-policyd-spf). But for the
most part, my legitimate incoming email passes DKIM or SPF, but often
not both. What I would like to do is accept
On January 11, 2018 2:53:10 AM UTC, "li...@lazygranch.com"
wrote:
>RTFMing, I see that both opendkim and python-policyd-spf have
>whitelisting capabilities (especially python-policyd-spf). But for the
>most part, my legitimate incoming email passes DKIM or SPF, but often
>not both. What I would
On Wed, 10 Jan 2018 21:59:26 -0500
"Kevin A. McGrail" wrote:
> On 1/10/2018 9:53 PM, li...@lazygranch.com wrote:
> > RTFMing, I see that both opendkim and python-policyd-spf have
> > whitelisting capabilities (especially python-policyd-spf). But for
> > the most part, my legitimate incoming email
18 matches
Mail list logo
