Hi,
After maintaining an old version of Postfix for some longer time, I
finally decided to jump to version 2.11 and currently I'm tuning it up.
I'm having an issue with smtpd_relay_restrictions. At this time, the
configuration is the default one:
smtpd_relay_restrictions =
permit_
Hello,
to test my servers (that is:
I've got one domain at namecheap. Using their SMTP to send mails but my
own VPS for the apache hosting and I run an own Postfix SMTP on my
domain3.de as well) I wanted to send one email from domain2.com to
domain3.de.
Unfortunately I got greylisted which s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/21/2014 5:32 PM, nobody73 wrote:
> Sorry for the debug logs but i think the reason why of my
> "UNKNOWN" issue is beacause connecting from abroad the hosted
> smtpd server there is no match in $mynetworks statement as you
> can see
No, the "after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Sorry for the debug logs but i think the reason why of my "UNKNOWN"
issue is beacause connecting from abroad the hosted smtpd server there
is no match in $mynetworks statement as you can see
> match_hostname: mylaptop.client ~? 11.22.11.22/32 match_
On Mon, Jul 21, 2014 at 04:42:57PM -0500, Noel Jones wrote:
>
> It might be easiest to use a flat file, which allows both names and
> networks, rather than a hash: or cidr: table.
Thanks - I think this is how it was setup at one point, and that
explains why.
w
On 7/21/2014 4:25 PM, Will Yardley wrote:
> We have:
> smtpd_client_event_limit_exceptions =
> 192.168.0.0/16,127.0.0.1,cidr:/etc/postfix/config/white_list,hash:/etc/postfix/config/white_list_internal_servers,hash:/etc/postfix/config/anvil_whitelist
>
> configured for Anvil. The last file is for
We have:
smtpd_client_event_limit_exceptions =
192.168.0.0/16,127.0.0.1,cidr:/etc/postfix/config/white_list,hash:/etc/postfix/config/white_list_internal_servers,hash:/etc/postfix/config/anvil_whitelist
configured for Anvil. The last file is for rate-limiting exemptions
only, whereas the other 2 a
On Mon, Jul 21, 2014 at 5:51 PM, Noel Jones wrote:
> On 7/21/2014 10:34 AM, Thijssen wrote:
>> smtpd_recipient_restrictions =
>> reject_invalid_hostname,
>> reject_unknown_recipient_domain,
>> reject_unauth_pipelining,
>> permit_mynetworks,
>> permit_sasl_authenticated,
>>
On 7/21/2014 10:27 AM, Jaap van Wingerde wrote:
> After years of faithful service, Postfix sometimes says that a known
> virtual user is "unknown in virtual alias table". I checked and double
> checked main.conf, the virtual_alias_domains and virtual_alias_maps but
> I cannot find something wrong.
On 7/21/2014 10:34 AM, Thijssen wrote:
> One server I maintain receives huge amounts of spam. In my ongoing
> attempts at killing as many spam-mails as possible, among others I've
> been using dns blacklists under the reject_rbl_client option umbrella.
> For years this worked really well, combined
After years of faithful service, Postfix sometimes says that a known
virtual user is "unknown in virtual alias table". I checked and double
checked main.conf, the virtual_alias_domains and virtual_alias_maps but
I cannot find something wrong. I use Debian Wheezy, Postfix version
2.9.6-2.
--
Jaap
One server I maintain receives huge amounts of spam. In my ongoing
attempts at killing as many spam-mails as possible, among others I've
been using dns blacklists under the reject_rbl_client option umbrella.
For years this worked really well, combined with clamsmtpd, plus some
header and body check
12 matches
Mail list logo
