On 1/21/2012 5:08 AM, Mark Alan wrote:
> On Thu, 19 Jan 2012 17:10:00 -0500 (EST), Wietse Venema
> wrote:
>
>> I found these with: postconf | grep '[A-Z][A-Z][A-Z]:' :-)
>
> postconf | grep '[A-Z][A-Z][A-Z]:' :-) results in:
> bash: syntax error near unexpected token `)'
>
> ... and at my sy
On Thu, 19 Jan 2012 17:10:00 -0500 (EST), Wietse Venema
wrote:
> I found these with: postconf | grep '[A-Z][A-Z][A-Z]:' :-)
postconf | grep '[A-Z][A-Z][A-Z]:' :-) results in:
bash: syntax error near unexpected token `)'
... and at my system man grep refuses to show what that
last :-) switch
On Thu, Jan 19, 2012 at 05:24:31PM -0500, Wietse Venema wrote:
> /dev/rob0:
> > If you want to see smtpd_restriction_classes gone crazy, refer
> > to my "howto" link from the site below. The particular page &
> > sections you would want is 02-postfix-sqlite.howto: see the
> > main.cf and the access
/dev/rob0:
> If you want to see smtpd_restriction_classes gone crazy, refer to my
> "howto" link from the site below. The particular page & sections you
> would want is 02-postfix-sqlite.howto: see the main.cf and the
> access-rcpt.query file therein. Bring a bottle of aspirin.
That looks like
On 1/19/2012 3:24 PM, Nikolaos Milas wrote:
> On 19/1/2012 7:06 μμ, Noel Jones wrote:
>
>> or define the restriction in main.cf and refer to it
>> ...
>> (or make up your own macro names)
>
> Thank you all for your valuable suggestions.
>
> These "macro names" seem really interesting. Can we use
Nikolaos Milas:
[ Charset UTF-8 unsupported, converting... ]
> On 19/1/2012 7:06 ??, Noel Jones wrote:
>
> > or define the restriction in main.cf and refer to it
> > ...
> > (or make up your own macro names)
>
> Thank you all for your valuable suggestions.
>
> These "macro names" seem really int
On Thu, Jan 19, 2012 at 11:24:10PM +0200, Nikolaos Milas wrote:
> On 19/1/2012 7:06 μμ, Noel Jones wrote:
>
> >or define the restriction in main.cf and refer to it
> >...
> >(or make up your own macro names)
>
> Thank you all for your valuable suggestions.
>
> These "macro names" seem really int
On 19/1/2012 7:06 μμ, Noel Jones wrote:
or define the restriction in main.cf and refer to it
...
(or make up your own macro names)
Thank you all for your valuable suggestions.
These "macro names" seem really interesting. Can we use them in main.cf
too (to define sets of restrictions) and how
On 19/1/2012 8:54 μμ, Mark Alan wrote:
This will give you a fairly secure submission:
submission inet n - - - - smtpd
-o syslog_name=postfix-submission
-o tls_preempt_cipherlist=yes
-o smtpd_tls_mandatory_ciphers=high
-o smtpd_tls_exclude_ciphers=DES,3D
On Thu, 19 Jan 2012 18:43:28 +0200, Nikolaos Milas
wrote:
> submission inet n - n - - smtpd
>-o syslog_name=postfix/submission
>-o smtpd_enforce_tls=yes
>-o smtpd_sasl_auth_enable=yes
> ...
> Any other options (except smtpd_*) which we should also redef
On 1/19/2012 10:43 AM, Nikolaos Milas wrote:
> Hello,
>
> When defining options for the submission port (587) daemon in
> master.cf, we must re-define explicitly all smtpd_* settings or not,
> or some (*which?*) are inherited from the standard main.cf settings?
as others have responded, all setti
On Thu, Jan 19, 2012 at 06:43:28PM +0200, Nikolaos Milas wrote:
> When defining options for the submission port (587) daemon in
> master.cf, we must re-define explicitly all smtpd_* settings or
> not, or some (*which?*) are inherited from the standard main.cf
> settings?
All smtpd_* and relevan
Am 19.01.2012 17:43, schrieb Nikolaos Milas:
> Hello,
>
> When defining options for the submission port (587) daemon in master.cf, we
> must re-define explicitly all smtpd_*
> settings or not, or some (*which?*) are inherited from the standard main.cf
> settings? More specifically, should we
>
Hello,
When defining options for the submission port (587) daemon in master.cf,
we must re-define explicitly all smtpd_* settings or not, or some
(*which?*) are inherited from the standard main.cf settings? More
specifically, should we define separately:
submission inet n - n
14 matches
Mail list logo
