Chris Siebenmann (Fr 07 Apr 2017 17:16:34 CEST):
> > how does verify = sender work. I can't find anything that says what
> > it does exactly in the docs. I'm seeing a valid sender get rejected
> > several times before being finally accepted.
>
> As Jeremy Harris covered,
No I haven't. This could be already fixed in a newer jem version.
2017-04-07 15:26 GMT+03:00 Jeremy Harris :
> On 07/04/17 12:04, Александр Кириллов via Exim-users wrote:
> > Thanks for this one. It helps.
> >
> > # In particular, the Exim maintainers have had multiple reports
> how does verify = sender work. I can't find anything that says what
> it does exactly in the docs. I'm seeing a valid sender get rejected
> several times before being finally accepted.
As Jeremy Harris covered, 'verify = sender' attempts to route the
sender address and uses the result. One
On 07/04/17 15:31, Dave Restall - System Administrator,,, wrote:
> how does verify = sender work.
It runs the sender address though the routers to see if it
is routable.
--
Jeremy
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
Hi,
how does verify = sender work. I can't find anything that says what
it does exactly in the docs. I'm seeing a valid sender get rejected
several times before being finally accepted. I added a warn line
in the config :-
warn! verify = sender
logwrite = oops sender verify failed
On 07/04/17 12:04, Александр Кириллов via Exim-users wrote:
> Thanks for this one. It helps.
>
> # In particular, the Exim maintainers have had multiple reports of problems
> # from Russian administrators of issues until they disable this check,
> # because of some popular, yet buggy, mail
Thanks for this one. It helps.
# In particular, the Exim maintainers have had multiple reports of problems
# from Russian administrators of issues until they disable this check,
# because of some popular, yet buggy, mail composition software.
And the prize for the popular, yet buggy, mail
Thanks Mike and Jeremy. The problem has been resolved by putting all the
attachment names in one line. I think the continuation line was playing havoc
as Mike suspected. For the time being, it is rightly Warning for the pdf
attachments.
Regards
Sujit
From: Mike Brudenell
> From: ?
> I've tried nearly anything I could think of:
>
> Commit by
> Commit\ by
Insert into beginning of Exim config:
check_rfc2047_length = false
> From: Jasen Betts
> RFC2047 sec 2 and section 6 say that all encoded words
>
On 07/04/17 09:18, Mike Brudenell via Exim-users wrote:
> Is there also a possible problem with the space character before the
> "\" continuation character after the dll file type? When I've written LDAP
> expressions before I remember having to be very careful not to put spaces
> before the
Hi,
I'm pretty sure it's unrelated to you not getting the warning message, but
there's an error in your *match* pattern: you have two consecutive vertical
bars between the dll and pdf extensions (albeit with a line continuation
inbetween).
In passing, as all the file type patterns begin with "."
11 matches
Mail list logo