Re: TLS warning

Telus is so broken in several ways. I complain and the friendly support person acts as if nothing is wrong. As I understand it, you need to be sending to their SMTP server from 'within their network'. Either on their LTE or on their home/business internet service. So when you leave your wifi o

Re: Why am I accepting this email?

On 24 May 2017, at 9:25, D'Arcy Cain wrote: I have no server called nan.vex.net But your DNS says that mail for any addresses @nan.vex.net that might exist are handled by mail.vex.net, regardless of whether that name represents an actual server or whether mail.vex.net actually can handle th

Re: TLS warning

On 2017-05-25 03:20 PM, li...@lazygranch.com wrote: Right from the Telus website : -- "Clear the Requires a secure connection (SSL) check box" ‎ "Authenticate using: Clear text‎" ‎http://business.telus.com/en/business/support/global/how-to/how-to-set-up-your-email-on-any-computer --- Se

Re: TLS warning

Right from the Telus website : -- "Clear the Requires a secure connection (SSL) check box" ‎ "Authenticate using: Clear text‎" ‎http://business.telus.com/en/business/support/global/how-to/how-to-set-up-your-email-on-any-computer --- Seriously Canada? And this is the advice to their busine

Re: Issue with SASL authentication

On 05/25/2017 06:20 PM, Daniel Bareiro wrote: > Hi! > > On 24/05/17 21:18, Daniel Bareiro wrote: > >> Hi again. >> >> On 24/05/17 17:46, Daniel Bareiro wrote: >> >>> Maybe this question is not 100% about Postfix, but it is related. I am >>> configuring a Postifx server with SASL authentication. >>>

Re: TLS warning

On 05/25/17 12:28, James B. Byrne wrote: > Yes, I cannot image why members of the so called 'five-eyes' > consortium would not actively promote signal security among their > populations. > > Must be an oversight. Or a lack thereof -- Phil Stracchino Babylon Communications ph...@caerl

Re: TLS warning

On Thu, May 25, 2017 05:23, li...@lazygranch.com wrote: > > > This paper is a good read on email security. It goes into the various > means that a man in the middle can reduce security, one of which is > enabled by selecting opportunistic encryption. (Of which in all > practicality you don't have

Re: Issue with SASL authentication

Hi! On 24/05/17 21:18, Daniel Bareiro wrote: > Hi again. > > On 24/05/17 17:46, Daniel Bareiro wrote: > >> Maybe this question is not 100% about Postfix, but it is related. I am >> configuring a Postifx server with SASL authentication. >> >> When I do a test to authenticate, I get an error: >>

Re: TLS warning

> On May 25, 2017, at 5:23 AM, li...@lazygranch.com wrote: > > "Neither Snow Nor Rain Nor MITM . . . > An Empirical Analysis of Email Delivery Security" > https://jhalderm.com/pub/papers/mail-imc15.pdf > Video by one of the authors. > https://www.youtube.com/watch?v=_aogXeTbERs It is a good acad

Re: TLS warning

> On May 25, 2017, at 5:23 AM, li...@lazygranch.com wrote: > > Given the email issues in recent political campaigns, I'm seeing a > number of articles suggesting setting up DMARC for quarantine. DMARC is an abuse of the IETF process (informational RFC) to promote and deploy a deeply flawed speci

Re: Multiple recipients in BCC will not relay if it contains one bad email address.

Thanks for you response Noel, I had included the postconf -n information in my post I guess its a link. Thanks once again for you very useful feedback. postconf.txt -- View this message in context: http://postfix.1071664.n5.nabb

Re: removing private data from headers

Hi Albrecht, tested it and it works as it shoud. big thanks 2017-05-25 14:41 GMT+02:00 : > Interesting.. > > smtp_header_checks did the trick, header_checks did not. > > 2017-05-25 14:26 GMT+02:00 Albrecht Dreß : > >> Am 25.05.17 14:20 schrieb(en) spamv...@googlemail.com: >> >>> since three day

Re: Multiple recipients in BCC will not relay if it contains one bad email address.

On 5/24/2017 5:23 PM, madrida wrote: > Hi Everyone first time posting, I am hoping you can help me. We have an issue > when an email sent to multiple emails via BCC is deleted if an invalid email > address is in the list. The email is discarded all together and I don't see > any logs other then the

Re: removing private data from headers

Interesting.. smtp_header_checks did the trick, header_checks did not. 2017-05-25 14:26 GMT+02:00 Albrecht Dreß : > Am 25.05.17 14:20 schrieb(en) spamv...@googlemail.com: > >> since three days I'm trying to remove my internal and external IP from >> the Message header when I'm sending mails. But

Re: removing private data from headers

Am 25.05.17 14:20 schrieb(en) spamv...@googlemail.com: since three days I'm trying to remove my internal and external IP from the Message header when I'm sending mails. But no solution has worked so far. What I did: created a new service in master.cf A simpler solution (working for me) for al

removing private data from headers

Hi all, since three days I'm trying to remove my internal and external IP from the Message header when I'm sending mails. But no solution has worked so far. What I did: created a new service in master.cf header-cleanup unix n – – – 0 cleanup -o syslog_name=postfix/header-cleanup -o header_checks

Re: Postfix and FUSE: Function not implemented

alexvojproc: > To avoid running out of room on my mail server, I mounted a storage bucket > using FUSE and created a user with this as its home directory. To avoid > permissions issues, I used the arguments "allow_other" and > "default_permissions" and made sure my user owned its home directory. Ev

Postfix and FUSE: Function not implemented

To avoid running out of room on my mail server, I mounted a storage bucket using FUSE and created a user with this as its home directory. To avoid permissions issues, I used the arguments "allow_other" and "default_permissions" and made sure my user owned its home directory. Even after this, Postfi

Re: Relay access denied

Thanks Viktor, I knew my sloppy configuration must have been at fault. Everything related to this works now. - Alex -- View this message in context: http://postfix.1071664.n5.nabble.com/Relay-access-denied-tp90614p90623.html Sent from the Postfix Users mailing list archive at Nabble.com.

Re: TLS warning

On Thu, 25 May 2017 03:02:39 -0400 Rick Leir wrote: > > > On 2017-05-25 02:31 AM, Philip Paeps wrote: > > On 2017-05-24 14:54:34 (+0200), Bastian Blank > > wrote: > >> On Wed, May 24, 2017 at 02:41:01AM -0700, li...@lazygranch.com > >> wrote: > >>> ‎You shouldn't be accepting sslv3 due to the

Re: TLS warning

On 2017-05-25 02:31 AM, Philip Paeps wrote: On 2017-05-24 14:54:34 (+0200), Bastian Blank wrote: On Wed, May 24, 2017 at 02:41:01AM -0700, li...@lazygranch.com wrote: ‎You shouldn't be accepting sslv3 due to the poodle attack. https://en.m.wikipedia.org/wiki/POODLE Please explain how exact