Re: Reject client from domains without MX records

Just in case someone is interested, finally i disabled sasl auth globally and fixed the previous error by adding/modifying the following lines at master.cf smtp inet n - - - - smtpd -o smtpd_sasl_auth_enable=yes As you can see i forgot to enable

Re: Reject client from domains without MX records

Thanks a lot! -- Sent from my Android mobile, excuse the brevity. On Mar 29, 2014 12:55 AM, "li...@rhsoft.net" wrote: > > > Am 29.03.2014 00:43, schrieb Pau Peris: > > I don't think that's about reading but about experise. Which takes time > after reading > > no, it's a matter of read, try and tr

Re: Reject client from domains without MX records

Am 29.03.2014 00:43, schrieb Pau Peris: > I don't think that's about reading but about experise. Which takes time after > reading no, it's a matter of read, try and try again, been there done that > I will reenable sasl globally again while i try to understand it all > I'm unsure if login send

Re: Reject client from domains without MX records

I don't think that's about reading but about experise. Which takes time after reading. I will reenable sasl globally again while i try to understand it all. I'm unsure if login sender mismatch can have any side effect for incoming email once global sasl auth is activated. Could you please explain

Re: Reject client from domains without MX records

sorry, you need to read manuals and try some things at your own if you can't handle it why do you remove auth globally? in general don't change defaults for no good reason Am 29.03.2014 00:21, schrieb Pau Peris: > Could you be more explicit or place an example on how should main.cf >

Re: Reject client from domains without MX records

Could you be more explicit or place an example on how should main.cf should stay after removing the sasl params and how should master.cf look please? Thank u so much!! Sent from my Android mobile, excuse the brevity. On Mar 28, 2014 10:21 PM, "li...@rhsoft.net" wrote: > > Am 28.03.2014 20:33, s

Re: Warning messages from bad return-path

Bruce Sackett: > I?m sorry - any sender on the one domain for the SMS software. > Call it usersms.com. [..] it?s the emails that are bouncing back, > to anyone who sends an SMS through that system. If the error report is generated by your mail server, then you can set up a transport map with

Re: Warning messages from bad return-path

I’m sorry - any sender on the one domain for the SMS software. Call it usersms.com It’s not the errors in the system logs, I can deal with those, it’s the emails that are bouncing back, to anyone who sends an SMS through that system. --Bruce Sackett – e: br...@oecnw.com - w: www.oecnw.com - p

Re: Warning messages from bad return-path

Bruce Sackett: > I am running into a problem where I have a poorly configured SMS > system sending through the mail server. The messages are delivered > properly, but then the sender receives a warning message: How many different senders are affected? How many different sites report delivery err

Re: Warning messages from bad return-path

Am 28.03.2014 22:43, schrieb Bruce Sackett: > I am running into a problem where I have a poorly configured SMS system > sending through the mail server. The > messages are delivered properly, but then the sender receives a warning > message: > > Failed to deliver to ‘ SMTP module(domain ) re

Warning messages from bad return-path

I am running into a problem where I have a poorly configured SMS system sending through the mail server. The messages are delivered properly, but then the sender receives a warning message: Failed to deliver to ‘ SMTP module(domain ) reports: return-path address <-6032673_14937_452964_11551.s

Re: Reject client from domains without MX records

Am 28.03.2014 20:33, schrieb Pau Peris: > I think everything was working fine but after update main.cf > file i'm seeing the following warning > for emails incoming outside the box, postfix/smtpd[15455]: warning: > restriction > `reject_authenticated_sender_login_mismatch' ignor

Re: Reject client from domains without MX records

I think everything was working fine but after update main.cf file i'm seeing the following warning for emails incoming outside the box, postfix/smtpd[15455]: warning: restriction `reject_authenticated_sender_login_mismatch' ignored: no SASL support The previous warning is show when i send an email

Re: Postfix: Block all inbound and outbound access but allow all for one user

Ok I was able to get half my objective done by using smtpd_restriction_classes following this postfix.org/RESTRICTION_CLASS_README.html#external . What I did was put that restriction AFTER permit_mynetworks but before permit_sasl_authenticated, which means I, the admin, can send out anywhere. Its r

Re: Reject client from domains without MX records

Finally, removing warn_if_rejected did the trick. Oh mine, stupid mistake, easy fix! Thanks a lot rhsoft!! On Thu, Mar 27, 2014 at 11:48 PM, Pau Peris wrote: > > Excuse me, i'll try to follow your rules. The HTML thing was due to the reader, i think it took web URL and emails into HTML tags. E

Re: Postfix: Block all inbound and outbound access but allow all for one user

Well I did look that over but I am looking for the opposite. It mentions it is left as an exercise for the reader to determine a scheme to block most users access and only allow some (or in my case, just myself, the admin). Also this only touches on outbound. I also need to restrict inbound for eve

Re: Postfix: Block all inbound and outbound access but allow all for one user

On 3/28/2014 4:06 AM, cybermass wrote: > Hi. I need to restrict access to only my internal domain but allow those in > permit_mynetworks to receive and send to any outside domain such as > gmail.com or so. So all users can only email each other in the local domain > but the admin in mynetworks may

Postfix: Block all inbound and outbound access but allow all for one user

Hi. I need to restrict access to only my internal domain but allow those in permit_mynetworks to receive and send to any outside domain such as gmail.com or so. So all users can only email each other in the local domain but the admin in mynetworks may access the outside. Should I use the transport