Re: Port 587 users question

2016-11-27 Thread lists
I should have mentioned the mail system is on a VPS and I'm the only user. And yes, trouble makers are on the Internet.  What lead me to this was I did bzgrep "max auth" and noticed both smtp and submission was found. (max auth as in checking anvil rate limiting). Since I'm the only person that

Re: Port 587 users question

2016-11-27 Thread btb
On Nov 27, 2016, at 16.15, li...@lazygranch.com wrote: > > I hate to bug the list for what is probably a dumb question, but is there any > situation where an unauthorized user needs to connect to port 587? I'm > wondering if there is some oddball "edge" case. well, i suppose it would depend up

Re: Milters and notification on DISCARD

2016-11-27 Thread Stavros Tsolakos
Hi. > Including spamming innocent people with notifications for email > that they did not send. You are right, but in my case it is about blocking sending to people outside a local 'ecosystem'. So spamming is quite unlikely since there are no relay servers configured either. Anyway, thank you fo

Re: Milters and notification on DISCARD

2016-11-27 Thread Wietse Venema
Stavros Tsolakos: > > What is the nature of the client? If it is an MTA, then it must > > return a message to sender; if it is an MUA, then don't count on > > such clients to put a non-delivery notice in the sender's inbox. > > Yes, it is a MUA. Several MUAs actually: a Rainloop webmail client, a

Port 587 users question

2016-11-27 Thread lists
I hate to bug the list for what is probably a dumb question, but is there any situation where an unauthorized user needs to connect to port 587? I'm wondering if there is some oddball  "edge" case. My thought is to use my ipfw table of known trouble makers to block 587.  ‎

Re: Milters and notification on DISCARD

2016-11-27 Thread Stavros Tsolakos
Hi. > What is the nature of the client? If it is an MTA, then it must > return a message to sender; if it is an MUA, then don't count on > such clients to put a non-delivery notice in the sender's inbox. > Yes, it is a MUA. Several MUAs actually: a Rainloop webmail client, a CLAWS mail client et

Re: Milters and notification on DISCARD

2016-11-27 Thread Wietse Venema
Stavros Tsolakos: > milter-reject: END-OF-MESSAGE from localhost[127.0.0.1]: 4.5.1 Rejected > because I said so; What is are Milter call and arguments that send the response? > "Rejected because I said so" is a test reason I have written. Still, the > client reports a failure but no failure messa

Re: Milters and notification on DISCARD

2016-11-27 Thread Stavros Tsolakos
Hi. >> I have tried REJECTing it, however sending just failed without further >> explanation for the user, although the reason appeared fine in the log >> file. To avoid client specific issues, I would need something similar to >> the undeliverable mail notifications emails sent to the sender's ma

Re: Milters and notification on DISCARD

2016-11-27 Thread Wietse Venema
Stavros Tsolakos: > Hi list. > > I am really new to postfix and email-under-the-hood in general. > > I have written a milter which in some cases DISCARDs the message, so > that it may not be sent at all. Is there a way of making postfix notify > the sender that their email was discarded? Yes, it

Re: Procmail Advice

2016-11-27 Thread Wietse Venema
@lbutlr: > On Nov 26, 2016, at 11:30 AM, E. Recio wrote: > > On 11/22/2016 10:47 AM, @lbutlr wrote: > >>=20 > >> reject_unknown_reverse_client_hostname, > >>=20 > >> but I also use: > >> reject_non_fqdn_recipient, > >> reject_unknown_sender_domain, > >> reject_invalid_hostname, > > > Wow, these s

Milters and notification on DISCARD

2016-11-27 Thread Stavros Tsolakos
Hi list. I am really new to postfix and email-under-the-hood in general. I have written a milter which in some cases DISCARDs the message, so that it may not be sent at all. Is there a way of making postfix notify the sender that their email was discarded? I have tried REJECTing it, however send

Re: Procmail Advice

2016-11-27 Thread @lbutlr
On Nov 26, 2016, at 11:30 AM, E. Recio wrote: > On 11/22/2016 10:47 AM, @lbutlr wrote: >> >> reject_unknown_reverse_client_hostname, >> >> but I also use: >> reject_non_fqdn_recipient, >> reject_unknown_sender_domain, >> reject_invalid_hostname, > Wow, these settings cut down on spam by a lot!

Re: AW: Possible Bug ? postfix 3.1.0-3 fails on mysql table lookup

2016-11-27 Thread John Fawcett
On 11/27/2016 01:47 PM, John Fawcett wrote: > On 11/23/2016 10:54 PM, j...@conductive.de wrote: >> On 2016-11-23 21:57, John Fawcett wrote: >>> On 11/22/2016 01:35 AM, Joel Linn wrote: Hey Guys, this issue has decayed a bit but I now finally found the time (and the nerves) to in

Re: AW: Possible Bug ? postfix 3.1.0-3 fails on mysql table lookup

2016-11-27 Thread John Fawcett
On 11/23/2016 10:54 PM, j...@conductive.de wrote: > On 2016-11-23 21:57, John Fawcett wrote: >> On 11/22/2016 01:35 AM, Joel Linn wrote: >>> Hey Guys, >>> >>> this issue has decayed a bit but I now finally found the time (and the >>> nerves) to integrate the fix in my system. >>> I'm running Ubuntu