PATCH: check_recipient_a_access DISCARD leads to 451 4.3.5 Server configuration error

flowhosts: > Nov 14 10:53:54 fallback postfix/smtpd[7187]: warning: restriction > check_recipient_a_access returns OK for vasilnhdgz0sdiminut...@netgooya.com > Nov 14 10:53:54 fallback postfix/smtpd[7187]: warning: this is not > allowed for security reasons > Nov 14 10:53:54 fallback

Re: Is it compulsory for an outgoing smtp server to have FQDN.

On 16/11/2017 01:20, @lbutlr wrote: It is not compulsory, but the *vast* majority of servers that are not configured this way are spammers. You will reject some "legitimate" mail, but it is a tiny fraction of the illegitimate mail. When I tested this, more than 98% of the warnings were from

RE: Mail Routing Question

You can point the A record for aaa.com to one IP and the MX record for it to another. I.e. aaa IN A 192.168.1.1 IN MX 10 192.168.1.2 All the MX record does is tell the world what mail host to use for a given domain. So you may have a web server running on aaa.com but not your email

Mail Routing Question

I have a domain, say: aaa.com for which I receive mail. Currently I have A records in DNS for aaa.com and mail.aaa.com as well as a MX record for aaa.com. All three of them point to the same IP address which is where postfix is running. There is a political issue with the A record for

Re: Mail Routing Question

> On Nov 16, 2017, at 5:32 PM, Doug Hardie wrote: > > I have a domain, say: aaa.com for which I receive mail. Currently I have A > records in DNS for aaa.com and mail.aaa.com as well as a MX record for > aaa.com. All three of them point to the same IP address which is where

Re: Mail Routing Question

Doug Hardie skrev den 2017-11-16 23:32: Will changing the A record for aaa.com cause the loss of some incoming mail? no, if that changed ip accept delivery of that recipient domain back to what mx does ?, it only defines a seperate hostname to deliver mail to if mail and other servicefs on

postmap db

Hello list, When e.g. I have an access file with: domain.tld reject baduser@ reject Postfix will reject "u...@domain.tld" and "baduser@anydomain.anytld". When I want to test these db's using "postmap -q", postmap only tests the "real" entries in the database. Is there a *simple CLI* way

always_bcc on outgoing mail

Hi, I have always_bcc set on my postfix-3.1.4 system on fedora25 and it's working fine for incoming email, but not outgoing. Outgoing mail is sent via submission. I see there are other systems within our domain which do not use submission and are properly bcc'd. submission inet n - n

Re: Mail Routing Question

> On 16 November 2017, at 14:45, Viktor Dukhovni > wrote: > > > >> On Nov 16, 2017, at 5:32 PM, Doug Hardie wrote: >> >> I have a domain, say: aaa.com for which I receive mail. Currently I have A >> records in DNS for aaa.com and mail.aaa.com

Re: always_bcc on outgoing mail

On 17/11/17 13:48, Alex wrote: > submission inet n - n - - smtpd ... > -o receive_override_options=$submission_overrides ... > submission_overrides = no_unknown_recipient_checks, > no_address_mappings, no_header_body_checks The problem is no_address_mappings in

Re: postmap db

On Thu, Nov 16, 2017 at 10:20:09PM +0100, richard lucassen wrote: > When e.g. I have an access file with: > > domain.tld reject > baduser@ reject > > Postfix will reject "u...@domain.tld" and > "baduser@anydomain.anytld". > > When I want to test these db's using "postmap -q", postmap

Re: Mail Routing Question

On Thu, Nov 16, 2017 at 10:43:16PM +, Kevin Miller wrote: > You can point the A record for aaa.com to one IP and the MX record > for it to another. Yes, but not as per your example. > I.e. > aaa IN A 192.168.1.1 > IN MX 10 192.168.1.2 The RDATA for MX is "integer hostname". In your