reject_unknown_helo_hostname and an address literal

2013-05-12 Thread Nikolas Kallis
Hello, If I use the 'smtpd_helo_restrictions' option parameter 'reject_unknown_helo_hostname', will a hostname that is an address literal be rejected? Regards, Nikolas Kallis

Clarification on 'reject_non_fqdn_helo_host name''s behaviour

2013-06-07 Thread Nikolas Kallis
in form, as required by the RFC." What the documentation says is incorrect. Under '3.6 Domains' of RFC 2821, it says a host name can be an address literal. So, if I use 'reject_non_fqdn_helo_host name' and a SMTP client uses an address literal for its host name, will Postfix reject the mail? - Thanks Regards, Nikolas Kallis

Bug report: 'reject_non_fqdn_helo_hostname' not handling address literals

2013-06-07 Thread Nikolas Kallis
Hello, Postfix has a bug in it where argument 'reject_non_fqdn_helo_hostname' causes Postfix to reject mail from a client who is using an address literal as their 'helo' command. This in breach of RFC 2821 under section 4.1.1.1. Regards, Nikolas Kallis

Re: Clarification on 'reject_non_fqdn_helo_host name''s behaviour

2013-06-07 Thread Nikolas Kallis
What the documentation says is incorrect. Under '3.6 Domains' of RFC 2821, it says a host name can be an address literal. So, if I use 'reject_non_fqdn_helo_host name' and a SMTP client uses an address literal for its host name, will Postfix reject the mail? Of course not. According to my mail

Re: Bug report: 'reject_non_fqdn_helo_hostname' not handling address literals

2013-06-07 Thread Nikolas Kallis
Postfix has a bug in it where argument 'reject_non_fqdn_helo_hostname' causes Postfix to reject mail from a client who is using an address literal as their 'helo' command. Your claim is valid. Address literals in HELO must be enclosed in []. I am a little confused. Were you just correcting me

Re: Clarification on 'reject_non_fqdn_helo_host name''s behaviour

2013-06-07 Thread Nikolas Kallis
Notice helo equals '37.212.64.248' - an address literal. Please READ the RFC. That form is INVALID. I think you are referring to the square brackets - I knew about them. I didn't pick up the logic in the system message. Sorry. Never the less, '37.212.64.248' is not a domain name, so 'reject_

Defeating 'reject_non_fqdn_helo_hostname'

2013-06-07 Thread Nikolas Kallis
e-mail server enforcing 'reject_non_fqdn_helo_hostname' accept my mail, or would the PTR record have to resolve to '123.243.137.139' exactly (not '123-243-137-138.static.tpgi.com.au')? There is allot I don't know about DNS. Does anyone know if a PTR record can be set to resolve to an IP address? - Thanks Regards, Nikolas Kallis

'reject_non_fqdn_helo_hostname' not working?!

2013-06-07 Thread Nikolas Kallis
bled; how did this unsolicited e-mail get through? Regards, Nikolas Kallis

Re: 'reject_non_fqdn_helo_hostname' not working?!

2013-06-07 Thread Nikolas Kallis
On 07/06/13 23:11, Mark Goodge wrote: On 07/06/2013 14:06, Nikolas Kallis wrote: Hello, I just got an unsolicited e-mail from the domain 'bbbmail.com', which is hosted at '46.235.78.1'. '46.235.78.1' does not resolve to a host name, therefore 'bbbmail.com

Re: 'reject_non_fqdn_helo_hostname' not working?!

2013-06-07 Thread Nikolas Kallis
On 07/06/13 23:29, Mark Goodge wrote: On 07/06/2013 14:16, Nikolas Kallis wrote: On 07/06/13 23:11, Mark Goodge wrote: On 07/06/2013 14:06, Nikolas Kallis wrote: Hello, I just got an unsolicited e-mail from the domain 'bbbmail.com', which is hosted at '46.235.78.1'. &#

Re: Using TLS for certain domains

2013-06-07 Thread Nikolas Kallis
On 08/06/13 05:29, Noel Jones wrote: On 6/7/2013 1:40 PM, polloxx wrote: Dear list, We need to implement TLS for one of our customers using our Postfix infrastructure (serving multiple domains) for inbound mail. The final delivery for that domain is a Exchange server, but we have a anti-virus s

Difference between 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname'

2013-06-07 Thread Nikolas Kallis
From what I understand, 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' detect malformed 'helo', but 'reject_non_fqdn_helo_hostname' does not detect malformed 'helo' if 'helo' is a malformed address literal. I.E: Given 'foo/bar.com' and '[900.111.111.900]': 'reject_non_fqdn_

Re: 'reject_non_fqdn_helo_hostname' not working?!

2013-06-08 Thread Nikolas Kallis
On 08/06/13 17:49, Stan Hoeppner wrote: Nikolas, please do not reply off-list. Always reply to the list unless there is a good reason not to (such as a shouting argument with another user, a thread drifts wildly off topic, you are asked to, etc). On 6/7/2013 11:20 PM, Nikolas Kallis wrote: On

'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' neccessary?!

2013-06-09 Thread Nikolas Kallis
Is using 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' even neccessary when using 'reject_unknown_helo_hostname'? The way I see it is if there is no FQDN and the host name is invalid, then 'reject_unknown_helo_hostname' won't be able to verify the DNS A and MX record anyw

Re: 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' neccessary?!

2013-06-09 Thread Nikolas Kallis
On 10/06/13 03:00, Viktor Dukhovni wrote: On Mon, Jun 10, 2013 at 01:17:19AM +1000, Nikolas Kallis wrote: Is using 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' even neccessary when using 'reject_unknown_helo_hostname'? You seem to have dec

Re: 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' neccessary?!

2013-06-09 Thread Nikolas Kallis
On 10/06/13 03:11, Viktor Dukhovni wrote: On Mon, Jun 10, 2013 at 03:07:59AM +1000, Nikolas Kallis wrote: Is using 'reject_non_fqdn_helo_hostname' and 'reject_invalid_helo_hostname' even neccessary when using 'reject_unknown_helo_hostname'? You seem to have dec