Hi,
After reading a bit the code and trying to understand it, here is what I think
happens here:
Given a bogus Message-ID, for example (notice it's missing angle brackets < >:
Message-ID:
1883biz_pay_after_purchase:0:0_572392900$ae7ed6e4d53b424c84aaf83b30c507e7
Dovecot is parsing Message-ID
Hi there,
I can confirm this behavior. A few months ago I introduced a milter which is
checking for multiple headers when the RFC says that there just should be one
of them For example "Message-Id".
I found the described problem in an email coming from Alibaba, which had an
invalid
These are real people with bank accounts? Get paid? Have money for breakfast
lunch dinner and a roof over their heads?
Just asking because my own bank account stupidly enough requires a phone number
to log in online whether or not I even have an email address.
And the POTS (Plain Old Telephone
Hi there, I can confirm this behavior. A few months ago I introduced a milter
which is checking for multiple headers when the RFC says that there just should
be one of them For example "Message-Id". I found the described problem in an
email coming from Alibaba, which had an invalid
>You wrote in the original email the message was rejected. Sorry I don't have
>login access to my gmail test account anymore since the google @#$%@#$% wanted
>to have me add a phone number.
In my original post I said that gmail was rejecting the forwards because
of duplicate headers, and that
> >Oct 1 13:31:46 sendmail[30321]: 291BVjjx030318:
> to=, delay=00:00:01, xdelay=00:00:01, mailer=esmtp,
> pri=122536, relay=gmail-smtp-in.l.google.com. [142.250.102.27],
> dsn=2.0.0, stat=Sent (OK 1664623906 gs19-
> 20020a1709072d1300b00777a40d515dsi4096082ejc.456 - gsmtp)
> >
> >I just
>Oct 1 13:31:46 sendmail[30321]: 291BVjjx030318: to=,
>delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=122536,
>relay=gmail-smtp-in.l.google.com. [142.250.102.27], dsn=2.0.0, stat=Sent (OK
>1664623906 gs19-20020a1709072d1300b00777a40d515dsi4096082ejc.456 - gsmtp)
>
>I just tested for
>
>Oct 1 13:31:46 sendmail[30321]: 291BVjjx030318: to=,
>delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=122536,
>relay=gmail-smtp-in.l.google.com. [142.250.102.27], dsn=2.0.0, stat=Sent (OK
>1664623906 gs19-20020a1709072d1300b00777a40d515dsi4096082ejc.456 - gsmtp)
>
>I just tested
> >
> >How are you redirecting, like this[1]? I tested this ages ago. I am
> mostly testing with own gmail account, so can't imagine this not
> working. It was an older 2.2 server I was testing this on.
> >
> >
> >[1]
> >if false # true
> >{
> > redirect :copy "s...@gmail.com";
> >}
> >
>
>
>How are you redirecting, like this[1]? I tested this ages ago. I am mostly
>testing with own gmail account, so can't imagine this not working. It was an
>older 2.2 server I was testing this on.
>
>
>[1]
>if false # true
>{
> redirect :copy "s...@gmail.com";
>}
>
Hello Marc,
It's
>
>
> We are using sieve filter to redirect incoming mails to an external
> mailbox (gmail) an we are seeing some forwarded e-mails being rejected
> by gmail because of duplicate headers.
>
How are you redirecting, like this[1]? I tested this ages ago. I am mostly
testing with own gmail
Hello,
We are using sieve filter to redirect incoming mails to an external mailbox
(gmail) an we are seeing some forwarded e-mails being rejected by gmail because
of duplicate headers.
I think was able to identify the probable cause of the duplicate headers:
It seems that when the original
12 matches
Mail list logo
