similar to: Specifying In-Reply-To, Message-ID and References headers in AM

>RFC822 is HISTORIC: please refer to RFC2822 instead. > >While UTC is sufficient for human beings, but not necessarily accurate >for machines, because of the leap year adjustment. TAI is the You mean leap seconds, not leap years. Since 1972, UTC == TAI modulo some number of seconds. Leap Seconds are announced officially by the IERS http://www.iers.org/iers/products/eop/leap.html

I was porting some email from one imap server location to another and ran into a feature of something. One of them writes message-id as 'Message-Id' and the other writes it as 'Message-ID'. Because of this, all the messages are forever different. All mail is delivered from postfix and will be in the future. But I'm asking which of these syntaxes is correct or if there is

Op 8/24/2017 om 7:05 PM schreef Kacper Guzik: > i Cant compile piegeon hole from github with this feature: > That's because this branch is based on master (v2.3). I created a rebased branch for v2.2: https://github.com/dovecot/pigeonhole/tree/vacation-to-header-ignore-envelope-2.2 Regards, Stephan. > 2822.c -fPIC -DPIC -o .libs/rfc2822.o > > *edit-mail.c:* In function

i Cant compile piegeon hole from github with this feature: 2822.c -fPIC -DPIC -o .libs/rfc2822.o *edit-mail.c:* In function '*edit_mail_set_cache_corrupted*': *edit-mail.c:1665:3:* *error: *too many arguments to function ' *edmail->wrapped->v.set_cache_corrupted*' (&edmail->wrapped->mail, field, reason); * ^* *edit-mail.c:* At top level:

Hello, Sometimes, when delivering mails, this warning appears in my syslog: > lda(...): Warning: Failed to parse return-path header: Invalid character in localpart dovecot-lda still exits with 0 and the mail is inserted into my inbox. Looking at the mails in question, I determined that the error is caused by a multiline Return-Path header. Here's a testcase: --- snip ---

Hello, On 31.01.2018 22:35, Stephan Bosch wrote: > Op 1/31/2018 om 6:17 PM schreef Christian Authmann: >> Hello, >> >> Sometimes, when delivering mails, this warning appears in my syslog: >> >>> lda(...): Warning: Failed to parse return-path header: Invalid >> character in localpart >> >> dovecot-lda still exits with 0 and the mail is inserted

Hey, I have an issue with misformatted vacation emails. Part of the initial mail ends up in the vacation response and the headers of the vacation response end up in the body. Which also leads to the wrong charset being used by (some) MUAs. (Should be utf-8 but the inital mal was ascii only). I think I narrowed the trigger of the bug down to a long Reference: header line. It only happens if the

Op 1/31/2018 om 6:17 PM schreef Christian Authmann: > Hello, > > Sometimes, when delivering mails, this warning appears in my syslog: > > > lda(...): Warning: Failed to parse return-path header: Invalid > character in localpart > > dovecot-lda still exits with 0 and the mail is inserted into my inbox. > > > Looking at the mails in question, I determined that the

Op 1/31/2018 om 10:44 PM schreef Christian Authmann: > Hello, > On 31.01.2018 22:35, Stephan Bosch wrote: >> Op 1/31/2018 om 6:17 PM schreef Christian Authmann: >>> Hello, >>> >>> Sometimes, when delivering mails, this warning appears in my syslog: >>> >>>> lda(...): Warning: Failed to parse return-path header: Invalid >>>

Hi, I have some controller code like this: def mailing_lists @ml = MailingList.find_by_identifier(@params[:id]) @messages = @ml.messages @headers["Content-Type"] = "application/atom+xml" @response.headers[''Last-Modified''] = @messages.last.created_on.httpdateunless @ messages.empty? minTime =

I've had complaints from users about "MISSING_DOMAIN" in header fields and I've tracked it down to having "." in an unquoted display name. By my reading of RFC2822 (especially section 4.1) A N Other <a.n.other at somewhere.org> "A. N. Other" <a.n.other at somewhere.org> are legal, but A. N. Other <a.n.other at somewhere.org> is

I have two identical disks /dev/sdb1 == source /dev/sdc1 == dest When I rsync the source -> dest rsync -a /tree2/ /tree2m the destination size id considerably larger. /dev/sdb1 17654736 6513064 10244848 39% /tree2 /dev/sdc1 17654736 7691192 9066720 46% /tree2m When I look down into the directories I find the following /tree2 ... SOURCE [root]# du -sk

On Nov 6, 2012, at 2:19 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > Binutils and LLVM > > As part of "owning our own toolchain", various people have expressed an interest and have been working on creating various tools that duplicate the functionality of tools available on other systems. I have summarized the information that I've gathered, and put it up

Platform: RedHat 7.0 Samba version: 2.2.7a Client platforms Windows 2000 Pro SP3 Number of clients: 7 This is my SAMBA configuration file # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Creation Date: 2002/10/21 15:26:01 # Global parameters [global] workgroup = SABER netbios name = SHADOW server string = SAMBA-PDC interfaces = eth0 192.168.1.13 encrypt

[This email is either empty or too large to be displayed at this time]

On 26/10/2017 18:38, Alexander Dalloz wrote: > Am 26.10.2017 um 12:20 schrieb David Zambonini: >> >> There seems to be a bug with RFC822 processing in ltmp proxying that >> doesn't >> quote local parts that, for example, contain spaces. > > Newer related RFCs are RFC 5321 and 5322. Typo, meant to say RFC2822, which they still supercede, not that the

If you haven't already found it, you should look inside tools/llvm-objdump/llvm-objdump.cpp, which is an easy-to-follow example of how these APIs work --Sean Silva. On Mon, Jun 11, 2012 at 5:41 PM, Marshall Clow <mclow.lists at gmail.com>wrote: > So, I'm trying to use this file to look inside COFF files. > Got the header. OK. > > Now I want to look at the sections.

So, I've written a tool called "obj2yaml". It takes an object file (currently just COFF), and dumps out a textual representation. Micheal Spencer has written a companion tool (not yet landed) called "yaml2obj". The primary use for these tools is for generating test cases for lld, though they are general purpose tools, and can be used to generate test cases (or debug) other

Delete it. =] Thanks. On Tue, Sep 4, 2012 at 9:53 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > In a discussion on IRC, Micheal was complaining about the semantics of > StringSet, specifically how the iterators work. > > DannyB mentioned that we have a Trie class, so I decided to check it out. > Lo and behold, I couldn't find _any_ uses of it, and when I deleted

On Wed, 28 Mar 2018 20:49:26 +0200 Reindl Harald via samba <samba at lists.samba.org> wrote: > > > Am 28.03.2018 um 20:21 schrieb Andrew Bartlett via samba: > > On Wed, 2018-03-28 at 19:11 +0100, Rowland Penny wrote: > >> On Thu, 29 Mar 2018 06:51:50 +1300 > >> Andrew Bartlett via samba <samba at lists.samba.org> wrote: > >> > >>