search for: acoss

...y internal/local, this is decided by sending SMTP everytime something is sent, based on MX records). Problem is that Dovecot/Sieve is using wrong SMTP server (one used for receiving e-mails which should NEVER be used for sending [and is never is, except sieve]). Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>: > Hi, > > I had the same problem and solved it at architectural design level. > > Instead of forcing Sieve to use a different SMTP server, I declared > some transports in the sending SMTP server to force it to route > internal domai...

...sent, based on MX records). Problem is that >> Dovecot/Sieve is using wrong SMTP server (one used for receiving >> e-mails which should NEVER be used for sending [and is never is, >> except sieve]). >> >> >> >> >> >> Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>: >> >>> Hi, >>> >>> I had the same problem and solved it at architectural design level. >>> >>> Instead of forcing Sieve to use a different SMTP server, I declared >>> some transports in the sending...

...direction="backward" in stepAIC(). Or if you did, it was still running, so whatever else you try will still be slow. The statement "R provides only the pvalues for each level" is wrong: look at the anova() function. Bob On 29 June 2017 at 11:13, Beno?t PELE <benoit.pele at acoss.fr> wrote: > Hello, > > i am a newby on R and i am trying to make a backward selection on a > binomial-logit glm on a large dataset (69000 lines for 145 predictors). > > After 3 days working, the stepAIC function did not terminate. I do not > know if that is normal but i wou...

Hello, i am a newby on R and i am trying to make a backward selection on a binomial-logit glm on a large dataset (69000 lines for 145 predictors). After 3 days working, the stepAIC function did not terminate. I do not know if that is normal but i would like to try computing a "homemade" backward with a repeated glm ; at each step, the predictor with the max pvalue would be

...TP everytime > something is sent, based on MX records). Problem is that > Dovecot/Sieve is using wrong SMTP server (one used for receiving > e-mails which should NEVER be used for sending [and is never is, > except sieve]). > > > > > > Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>: > >> Hi, >> >> I had the same problem and solved it at architectural design level. >> >> Instead of forcing Sieve to use a different SMTP server, I declared >> some transports in the sending SMTP server to force it to...

...that >>> Dovecot/Sieve is using wrong SMTP server (one used for receiving >>> e-mails which should NEVER be used for sending [and is never is, >>> except sieve]). >>> >>> >>> >>> >>> >>> Cit?t "KOCIK Fabien (Acoss)" <fabien.kocik at acoss.fr>: >>> >>>> Hi, >>>> >>>> I had the same problem and solved it at architectural design level. >>>> >>>> Instead of forcing Sieve to use a different SMTP server, I >>>> declared s...

Hi, in our setup, we have two SMTP servers: - one for receiving messages (this one is using Dovecot's LMTP for delivery) - one for sending messages (this one is used by our users as outgoing SMTP server) Only the first one has list of local domains, local e-mail accoutns etc. so the second one will ALWAYS use MX records for delivery - with this setup, we can allow to our users to

Hi Michael, > -----Original Message----- > From: R-help [mailto:r-help-bounces at r-project.org] On Behalf Of Michael > Friendly > Sent: Thursday, June 29, 2017 9:04 AM > To: Beno?t PELE <benoit.pele at acoss.fr>; r-help at r-project.org > Subject: Re: [R] Help : glm p-values for a factor predictor > > On 6/29/17 11:13 AM, Beno?t PELE wrote: > > My question is about the factor predictors with several levels. R > > provides only the pvalues for each level whereas i need an overal...

...ly does not allow to specify IPv4 addresses for the --tunnel-src and --tunnel-dst options of the policy match. This, however, is required for an IPv6 via IPSec IPv4 tunnel. Let's assume the IPSec tunnel endpoints are 1.2.3.4 and 5.6.7.8 and are interconnecting two IPv6 networks. Packets flowing acoss this connection shall be marked. This would require something like the following: ip6tables -t mangle -A INPUT --match policy --dir in --pol ipsec --mode tunnel --tunnel-dst 1.2.3.4 --tunnel-src 5.6.7.8 -j MARK --set-mark 0x08/0x08 The above does not work. Instead one has to use the following und...

Hi, I had the same problem and solved it at architectural design level. Instead of forcing Sieve to use a different SMTP server, I declared some transports in the sending SMTP server to force it to route internal domains directly to receiving SMTP server without going to the Internet. So, internal mails remains on internal network and there is only one SMTP server for all mail traffic. Sorry, I

Je serai absent(e) ? partir du 19/12/2011 de retour le 30/12/2011. Je r?pondrai ? votre message d?s mon retour.

Hi, I'm dealing for few days with replication issues between two dovecot containerized instances in Kubernetes environment. After some search, I found this thread that reports exactly the same symptoms I encountered : https://dovecot.org/pipermail/dovecot/2019-October/117353.html I can confirm that downgrade of dovecot to 2.3.7.2 fixes the issue. Testing usage of -T parameter with a very low