Hi,
P.V.Anthony wrote:
Hi,
Currently have the following setting in main.cf but I do not know how
to create an exception. Because there are some authenticated users
that should not be rejected by
reject_authenticated_sender_login_mismatch.
I'm a noobie to postfix myself but I'll have an e
Hi,
I have defined two smtpd_restriction_classes for two different domains.
I'm using these classes for integration with
smtpd_recipient_restrictions. At this time, I'd like to define custom
smtp_body_checks and smtp_header_checks for each of these domains (or
classes), so any outgoing e-mail
On 03/08/2015 08:04 PM, Mick wrote:
I'm a noobie to postfix myself but I'll have an educated guess and say
'reject_authenticated_sender_login_mismatch' will REJECT if sender does
not match the sasl_username without any exception. If you want to allow
an sasl_username to send messages for an non
Nicol?s:
> Hi,
>
> I have defined two smtpd_restriction_classes for two different domains.
> I'm using these classes for integration with
> smtpd_recipient_restrictions. At this time, I'd like to define custom
> smtp_body_checks and smtp_header_checks for each of these domains (or
> classes),
Dynamic linking results in smaller binaries (
http://www.postfix.org/INSTALL.html#shared_enable), and memory savings, but
what about dynamic loading of database clients? Does this work the same
way, or is this something different from dynamic linking? It's not
altogether clear to me. What does it m
On Sat, Mar 07, 2015 at 05:59:23PM +0800, P.V.Anthony wrote:
> How to create an exception to reject_authenticated_sender_login_mismatch in
> main.cf.
Postfix 2.11 or later:
http://www.postfix.org/postconf.5.html#check_sasl_access
Presumably some SASL users need to be able to send fr
On Mon, Mar 09, 2015 at 03:36:42AM +0800, Jeffrey 'jf' Lim wrote:
> Dynamic linking results in smaller binaries (
> http://www.postfix.org/INSTALL.html#shared_enable), and memory savings, but
> what about dynamic loading of database clients? Does this work the same
> way, or is this something diff
On Mon, Mar 9, 2015 at 3:55 AM, Viktor Dukhovni
wrote:
> On Mon, Mar 09, 2015 at 03:36:42AM +0800, Jeffrey 'jf' Lim wrote:
>
> > Dynamic linking results in smaller binaries (
> > http://www.postfix.org/INSTALL.html#shared_enable), and memory savings,
> but
> > what about dynamic loading of databa
On Mon, Mar 09, 2015 at 04:07:17AM +0800, Jeffrey 'jf' Lim wrote:
> > The benefit of dynamic loading of table drivers is simplified
> > dependency management for O/S release engineers. They can ship a
> > system with an MTA without having to bundle support for every
> > database client library un
Currently my master.cf looks like this:
192.168.1.10:25 inet n - - - - smtpd -o
myhostname=dns1.sebbe.eu -o smtpd_tls_cert_file=/etc/postfix/dns1.crt -o
content_filter=smtp-downconvert:127.0.0.1:10025
192.168.1.10:26 inet n - - -
Does Always BCC bcc all incoming AND outgoing mail?
Is there a way to have it BCC only incoming mail?
--
It's against my programming to impersonate a deity.
On Sun, Mar 08, 2015 at 08:09:51PM -0600, @lbutlr wrote:
> Does Always BCC bcc all incoming AND outgoing mail?
>
> Is there a way to have it BCC only incoming mail?
Postfix has no notion of "incoming mail". All mail comes in (to
the queue) and then it goes out.
To apply different rewriting rul
P.V.Anthony wrote:
On 03/08/2015 08:04 PM, Mick wrote:
I'm a noobie to postfix myself but I'll have an educated guess and say
'reject_authenticated_sender_login_mismatch' will REJECT if sender does
not match the sasl_username without any exception. If you want to allow
an sasl_username to send
P.V.Anthony wrote:
On 03/08/2015 08:04 PM, Mick wrote:
I'm a noobie to postfix myself but I'll have an educated guess and say
'reject_authenticated_sender_login_mismatch' will REJECT if sender does
not match the sasl_username without any exception. If you want to allow
an sasl_username to send
Darn formatting! I can't read it myself. Gr! Attached as a text
file. Hope attachments are allowed.
Mick.
#!/usr/bin/perl
# sasluser.p
# PERL Script abused by Snakebyte
# version 0.01
$action="action=DUNNO\n\n";
$sender="";
$sasl_username="\n";
#
# SASL users that are allowed to play at
On Mon, Mar 09, 2015 at 03:36:53AM +, Mick wrote:
> Darn formatting! I can't read it myself. Gr! Attached as a text file.
> Hope attachments are allowed.
I would not deploy this policy script. It requires a new Perl
process for each request. That's a rather bad idea. It does not
treat
On Mon, Mar 09, 2015 at 12:43:14AM +0100, Sebastian Nielsen wrote:
> How can this be accomplished?
Don't mix the relay and inbound services in the same Postfix.
Setup one Postfix to receive inbound mail from outside.
Setup another Postfix to handle outbound mail from inside.
For extra brownie
Solved it already.
Did split up the OpenDKIM process into 2 instances, one running as verifier,
placed before any content modification, and one running as signer, placed
after any content modification.
I also moved the SPF signature validator to the instance before content
modification. That wa
Viktor Dukhovni wrote:
On Mon, Mar 09, 2015 at 03:36:53AM +, Mick wrote:
Darn formatting! I can't read it myself. Gr! Attached as a text file.
Hope attachments are allowed.
I would not deploy this policy script. It requires a new Perl
process for each request. That's a rat
On Mon, Mar 09, 2015 at 04:40:41AM +, Mick wrote:
> >I would not deploy this policy script. It requires a new Perl
> >process for each request. That's a rather bad idea. It does not
> >treat the sender address in a case-insensitive manner.
>
> I hadn't thought of that. If the mail server bu
On Mon, Mar 09, 2015 at 05:27:21AM +0100, Sebastian Nielsen wrote:
> Did split up the OpenDKIM process into 2 instances, one running as verifier,
> placed before any content modification, and one running as signer, placed
> after any content modification.
> I also moved the SPF signature validator
I understand. What I do with the SPF signature checker, is to
unconditionally add a header that looks like this:
X-SPF-Signature: none (dukhovni.org: No applicable sender policy available)
receiver=server-desktop; identity=mailfrom;
envelope-from="postfix-us...@dukhovni.org"; client-ip="2604:8d0
On Mon, Mar 09, 2015 at 07:16:59AM +0100, Sebastian Nielsen wrote:
> I understand. What I do with the SPF signature checker, is to
> unconditionally add a header that looks like this:
> X-SPF-Signature: none (dukhovni.org: No applicable sender policy available)
> receiver=server-desktop; identity=
23 matches
Mail list logo
