On 9/26/2008, Henrik K ([EMAIL PROTECTED]) wrote:
Ok that's true. But it still doesn't make it right to have a non-working
envelope sender.
What is 'right' and what is reality are often very different things.
--
Best regards,
Charles
2008/9/25 Brian Evans - Postfix List [EMAIL PROTECTED]:
mouss wrote:
Henrik K wrote:
On Thu, Sep 25, 2008 at 03:30:18PM +0200, mouss wrote:
However, since there will be many more domains hosted on this server
is there not a better way?
yes, there is: remove your check_sender_mx_access. did
Juan Miscaro wrote:
2008/9/25 Brian Evans - Postfix List [EMAIL PROTECTED]:
[...]
The Problem the OP appears to fall into is that mail coming from outside
the mynetworks is being trapped to do a local DNS MX/A record.
It is probably pointing mail to the example.com as 127.0.0.1 (not
uncommon).
2008/9/25 Noel Jones [EMAIL PROTECTED]:
Juan Miscaro wrote:
So I have the following lines in main.cf:
smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
permit_mynetworks
Juan Miscaro wrote:
2008/9/25 Noel Jones [EMAIL PROTECTED]:
Juan Miscaro wrote:
So I have the following lines in main.cf:
smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
permit_mynetworks
2008/9/25 mouss [EMAIL PROTECTED]:
Juan Miscaro wrote:
2008/9/25 Noel Jones [EMAIL PROTECTED]:
Juan Miscaro wrote:
So I have the following lines in main.cf:
smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
On Thu, Sep 25, 2008 at 03:30:18PM +0200, mouss wrote:
However, since there will be many more domains hosted on this server
is there not a better way?
yes, there is: remove your check_sender_mx_access. did it ever catch
spam on your server? it never caught anything here.
I don't use it
Henrik K wrote:
On Thu, Sep 25, 2008 at 03:30:18PM +0200, mouss wrote:
However, since there will be many more domains hosted on this server
is there not a better way?
yes, there is: remove your check_sender_mx_access. did it ever catch
spam on your server? it never caught anything here.
I
Noel Jones wrote:
mouss wrote:
He already has permit_mynetworks and so on. so his problem is
different (and probably rare). He needs to exclude his domains from
check_mx_access.
Using a check_sender_access whitelist as posted earlier is one solution.
a few other obvious solutions:
- not
mouss wrote:
Henrik K wrote:
On Thu, Sep 25, 2008 at 03:30:18PM +0200, mouss wrote:
However, since there will be many more domains hosted on this server
is there not a better way?
yes, there is: remove your check_sender_mx_access. did it ever
catch spam on your server? it never caught
So I have the following lines in main.cf:
smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
2008/9/24 Sahil Tandon [EMAIL PROTECTED]:
Juan Miscaro [EMAIL PROTECTED] wrote:
So I have the following lines in main.cf:
smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
permit_mynetworks
Juan Miscaro [EMAIL PROTECTED] wrote:
'example.com' is a domain for which my mailserver accepts mail for.
On the Postfix machine, what is the output of 'dig +short mx
example.com'?
The way I understand it,
check_sender_mx_access checks whether the MX host(s) for the MAIL FROM
address
Juan Miscaro wrote:
So I have the following lines in main.cf:
smtpd_recipient_restrictions =
reject_non_fqdn_recipient
reject_non_fqdn_sender
reject_unknown_sender_domain
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
14 matches
Mail list logo
