Re: load balanced emails servers pair

Another approach is to load balance with DNS. You setup a domain that resolves to the set of IP addresses of your mail servers. You might even imploy priority in the DNS records for weighted load sharing. You have the persistence of the session as a bonus. Not so efficient always but way more

Re: load balanced emails servers pair

One approach could be to setup a load balancer (lvs, haproxy) in front of the servers to share the IMAP load. Make also the sessions persistent to avoid issues with authentication. Alex On February 9, 2017 11:57:09 AM GMT+02:00, Patrick Chemla wrote: >Thanks

Re: BBC mapping

On 2/9/2017 11:47 AM, @lbutlr wrote: > >> On Feb 7, 2017, at 5:10 PM, Wietse Venema wrote: >> >> @lbutlr: >>> if !/backup.*@/ >>> /^([^+_]*).*@(.*)/ backup+${1}.${2}@domain.tld >>> endif >>> >>> […] >>> >>> However, I would like to exclude a specific domain from this

Re: BBC mapping

> On Feb 7, 2017, at 5:10 PM, Wietse Venema wrote: > > @lbutlr: >> if !/backup.*@/ >> /^([^+_]*).*@(.*)/ backup+${1}.${2}@domain.tld >> endif >> >> […] >> >> However, I would like to exclude a specific domain from this backup = >> including all mail TO and FROM the

AW: The "from" header looks like paypal but it is coming from somewhere else.

Im Auftrag von P.V.Anthony > Since the email contains the following. > > From: =?utf-8?Q?service=40paypaI=2Ecom=2Esg?= > > > What do you all think about that? > > P.V.Anthony > Perhaps if /^From:.*paypal.*/ if !/\<.+@(.\.)?paypal\.(de|com)\>$/

Re: SASL LOGIN authentication failed: no mechanism available

Hi Viktor, I switched to dovecot and the email went through fine this time! You rock! Thanks so much for the help! Viktor Dukhovni wrote: On Thu, Feb 09, 2017 at 04:05:25PM +, Viktor Dukhovni wrote: On Thu, Feb 09, 2017 at 12:45:44PM -0300, Nick wrote: I have just tried

Re: SASL LOGIN authentication failed: no mechanism available

On Thu, Feb 09, 2017 at 04:05:25PM +, Viktor Dukhovni wrote: > On Thu, Feb 09, 2017 at 12:45:44PM -0300, Nick wrote: > > > I have just tried adding multiple symlinks, restarted postfix and saslauthd > > but the same error persists, > > Time to configure "debug_peer_list" to include the IP

Re: SASL LOGIN authentication failed: no mechanism available

On Thu, Feb 09, 2017 at 12:45:44PM -0300, Nick wrote: > I have just tried adding multiple symlinks, restarted postfix and saslauthd > but the same error persists, Time to configure "debug_peer_list" to include the IP address of the client that is triggering the errors. More may become apparent

Re: SASL LOGIN authentication failed: no mechanism available

Hi Viktor, Thanks for the help! Postfix is from Ubuntu apt official repo, version is 2.11. # postconf -d | grep mail_version mail_version = 2.11.0 I have just tried adding multiple symlinks, restarted postfix and saslauthd but the same error persists, # ls -lah /usr/lib/sasl2/smtpd.conf

Re: SASL LOGIN authentication failed: no mechanism available

Hi chaouche, I appreciate the quick help, I provided the config files on my very first email, below is the smtpd.conf file, let me know if you want me to paste all the config files again, # cat /etc/postfix/sasl/smtpd.conf pwcheck_method: saslauthd mech_list: plain login auxprop_plugin:

Re: SASL LOGIN authentication failed: no mechanism available

On Thu, Feb 09, 2017 at 12:05:08PM -0300, Nick wrote: > Hi Chris, > > Thank you for the prompt reply, package its already installed. What Postfix version? Is Postfix from the Debian package, or your own build? Upthread you mention /etc/postfix/sasl/smtpd.conf, that would not be used if your

Re: SASL LOGIN authentication failed: no mechanism available

Hi Nick, I'm curious to know what's inside your /etc/postfix/sasl/smtpd.conf file ?

Re: SASL LOGIN authentication failed: no mechanism available

Hi Chris, Thank you for the prompt reply, package its already installed. root@server:~# dpkg --get-selections | grep -i sasl2 libsasl2-2:amd64install libsasl2-modules:amd64install libsasl2-modules-db:amd64install sasl2-bininstall

Re: The "from" header looks like paypal but it is coming from somewhere else. [signed]

It is a DKIM issue. Google "strict DKIM alignment" This is something usually defined in DMARC, but you could have a local definition that forces strict DKIM alignment for sensitive domains, like "all domains containing *paypal* or *bank*". Dominic Raferd skrev: (9

Re: The "from" header looks like paypal but it is coming from somewhere else. [signed]

On 9 Feb 2017 12:53, wrote: That is the mailchimp server. (Technically rocketsciencegroup.com) So has the email originator figured out some sort of unintended use of mailchimp? *From: *Sebastian Nielsen *Sent: *Thursday, February 9, 2017 2:24 AM *To:

Re: The "from" header looks like paypal but it is coming from somewhere else. [signed]

That is the mailchimp server. (Technically rocketsciencegroup.com) So has the email originator figured out some sort of unintended use of mailchimp? 

Re: The "from" header looks like paypal but it is coming from somewhere else. [signed]

The problem here is that DKIM isn't aligned to paypal.com Enforce strict DKIM alignment on sensitive domains like paypal smime.p7s Description: S/MIME Cryptographic Signature

Re: load balanced emails servers pair

Thanks all for your answers. I have at last setup the NAS, and mails are received there. So I will set the second server and second MTA, and both will receive emails. Next step is to give users access to both servers to retreive emails. As a load-balancer could help easily for http/https

Re: SASL LOGIN authentication failed: no mechanism available

On 2017-02-09 09:09, Nick - ServerBuddies Support wrote: Hello guys, For some reason Im unable to send any email from this postfix server, Im getting the following error: Feb 9 03:00:35 buf postfix/smtpd[6424]: warning: SASL PLAIN authentication failed: no mechanism available For debian

SASL LOGIN authentication failed: no mechanism available

Hello guys, For some reason Im unable to send any email from this postfix server, Im getting the following error: Feb 9 03:00:35 buf postfix/smtpd[6424]: warning: SASL PLAIN authentication failed: no mechanism available No more errors than the one below appears on logs. Im using rimap for