On 09/05/18 19:29, Emanuel Gonzalez via Exim-users wrote:
> malware acl condition: sophie /var/run/sophie : unable to connect to UNIX
> socket (/var/run/sophie): No such file or directory
Somewhere in your config you have a line
scanner = sophie
Nothing to do with spamd_address.
--
Jeremy
--
Thanks for the reply, in the exim configure i not add the parameter "scanner =
sophie".
i only add this config:
spamd_address = x.x.x.x 11333 variant=rspamd
denymalware = */defer_ok
message = This message contains a virus ($malware_name).
by default exim tries to connect with sopho
On 09/05/18 17:09, Mathieu via Exim-users wrote:
> So, is the only way to fix it is to upgrade to 4.90? (4.91 is available
> in Debian Backports)
Not the only, but probably the simplest for you.
--
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details
I really do not know if the problem is rspamd or exim since by default exim
tries to connect using sophie (sophos) antivirus:
malware acl condition: sophie /var/run/sophie : unable to connect to UNIX
socket (/var/run/sophie): No such file or directory
in the exim configure i set this:
Le 09/05/2018 à 16:23, Jeremy Harris via Exim-users a écrit :
> The MAIL FROM was rejected; we didn't get as far as the
> RCPT TO, so the rejection would apply to any recipient.
>
> I'm depending on your not having obfuscated that log (please
> don't or I'll be much less use to you),
Yes, I'm
On 09/05/18 14:53, Mathieu via Exim-users wrote:
> Le 09/05/2018 à 15:03, Jeremy Harris via Exim-users a écrit :
>> Perhaps you could find the time in your logs when the verify was
>> done? It might have recorded some insights.
>
> It brings this reject:
>
>> 2018-05-07 10:14:47
Le 09/05/2018 à 15:03, Jeremy Harris via Exim-users a écrit :
> Perhaps you could find the time in your logs when the verify was
> done? It might have recorded some insights.
It brings this reject:
> 2018-05-07 10:14:47 H=([127.0.0.1]) [10.1.2.3]
> X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128
On 09/05/18 13:04, Mathieu via Exim-users wrote:
> Le 09/05/2018 à 13:39, Jeremy Harris via Exim-users a écrit :
>>> What is the meaning of "callout=unknown" in the callout db? What could
>>> produce that cached output?
>>
>> "test hasn't been done".
>
> Why test wouldn't be done, but still saved
Le 09/05/2018 à 13:39, Jeremy Harris via Exim-users a écrit :
>> What is the meaning of "callout=unknown" in the callout db? What could
>> produce that cached output?
>
> "test hasn't been done".
Why test wouldn't be done, but still saved in the callout db? Is a temp
status while the test is
On 04/05/18 19:58, Morgan Blackthorne via Exim-users wrote:
> 1.) Accept mail from our various webservers on the local network using
> security groups
> 2.) Verify that the domain is a member of a domain whitelist and if so,
> send it out SES as a smarthost
> 3.) Rate limit how fast we forward
On 07/05/18 16:44, Mathieu via Exim-users wrote:
> What is the meaning of "callout=unknown" in the callout db? What could
> produce that cached output?
"test hasn't been done".
--
Cheers,
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
We're looking to use Amazon's SES service in our new AWS environment, but
we're very wary of getting blocked by them for going over the quota or
dealing with customers configuring from addresses that haven't been
verified in SES with the DKIM keys appropriately yet. Part of that involves
updating
Hello,
What is the meaning of "callout=unknown" in the callout db? What could
produce that cached output?
> $ sudo exim_dumpdb /var/spool/exim4 callout |grep -v @ |grep lists
> 07-May-2018 10:14:47 lists.example.fr callout=unknown
> postmaster=unknown random=unknown
I had to reduce
13 matches
Mail list logo
