I've also noticed the colon pre-prending problem in my tests with KMail. I
just assumed it was because I was making up my own headers when I was speaking
LMTP and SMTP by hand directly with dbmail-lmtpd and postfix/smtp...
Guess not!
Do the multiple colons appear correctly in the database? If so,
I have also noted that lines that have multiple colons in them will have
them stripped out.
i.e.
4test
becomes
: 4test
and even
4:test
becomes
4: test
strangeness indeed.
not only does it add a colon but it also adds a space after the colon
and strips multiple colons. Further packe
Has anyone else seen a strange imap behavior in the 2.0 release
candidates relating to colon characters?
It seems that in the body of my emails I am getting a colon added to the
beginning of each line.
-
This is
Another
Test
How about
Them
Colons
--
Hey, you're not Ilja! :-P More inline...
Paul J Stevens <[EMAIL PROTECTED]> said:
>
> Aaron Stone wrote:
> > Ilja,
> >
> > I still can't seem to get my Postfix talking to the LMTP daemon :-(
> > Something that I had never specifically tested, though, is what happens
> > when you connect to the
Hi,
with some help from a guy on [EMAIL PROTECTED] I found something:
The "250 Recipient <[EMAIL PROTECTED]> OK" message from
dbmail-lmtp is out of sync. The postfix/lmtp program stores this message
until the next message is sent, causing the messages between postfix and
dbmail-smtp to be horr
I'm going to go and get Cyrus and play with their lmtp server and see what
differs. Postfix seems to be strict about a few little things... it's possible
that they'd only tested with Cyrus or a small handful of others and therefore
have some extra assumptions about what an LMTP session is supposed
Hi all,
We've just released DBMail 2.0 Release Candidate 3
News item on www.dbmail.org:
DBMail 2.0 release candidate 3 can be downloaded from the download page.
This release has quite a lot of fixes:
* dbmail-lmtp returns useful messages to the MTA. A lot of work has
been done on this b
Ok, nevermind, it must be a broken mail client... I just spoke with Postfix
via 'telnet localhost 25' and my message was inserted properly via lmtp :-)
Aaron
Ilja Booij <[EMAIL PROTECTED]> said:
> Hi
>
> Reconnecting to the same process seems to work ok. I guess the problem
> from the imap-co
Hmm, I still don't really understand the problem. I've done some
ngrep-ing, to see what goes over the network.
This is a session that's OK:
T 2004/03/05 13:45:46.324232 127.0.0.1:10024 -> 127.0.0.1:46715 [AP]
220 test01 DBMail LMTP service ready to rock..
##
T 2004/03/05 13:45:46.324696 12
Hi
Reconnecting to the same process seems to work ok. I guess the problem
from the imap-code is not present here (or not expressed like it is in
the imap-server).
And Aaron, what's the problem with your postfix and dbmail-lmtp? Have
you made the right entry in main.cf:
dbmail-lmtp unix
Aaron Stone wrote:
Ilja,
I still can't seem to get my Postfix talking to the LMTP daemon :-(
Something that I had never specifically tested, though, is what happens when
you connect to the same process that you'd previously connected to and closed?
This sounds alot like the problems I have wi
Hi,
Robert, thanks for your suggestion. It seems to work perfectly here.
Messages now get delivered to users without a problem.
I'll take a look at lmtp.c to see if I can spot the difference between
the server getting a QUIT from the client and a reconnection on a new
message, and a cached c
Ilja,
I still can't seem to get my Postfix talking to the LMTP daemon :-(
Something that I had never specifically tested, though, is what happens when
you connect to the same process that you'd previously connected to and closed?
Looking at the output and reading over the code again led me to beli
13 matches
Mail list logo
