Y Giridhar Appaji Nag wrote:
Looks like you can do something like this and look for clues:
- Create a new mozilla profile with the IMAP and other settings that are
same as the one that you were originally using.
- Import this new mozilla profile to an MT profile.
- Import to MT, the mozilla
tags 274987 + unreproducible
thanks
Manuel Bilderbeek wrote:
Y Giridhar Appaji Nag wrote:
Looks like you can do something like this and look for clues:
- Create a new mozilla profile with the IMAP and other settings that are
same as the one that you were originally using.
- Import this
Alexander Sack wrote:
Manuel Bilderbeek wrote:
Yup, but there's not even a hit on ^^.
ups, you need to escape it. In case you did not notice, try:
grep '\^\^' somefile
I did that, don't worry :)
(Otherwise I wouldn't get hits on our e-mails about this...)
About the other suggestions from
Manuel Bilderbeek wrote:
ups, you need to escape it. In case you did not notice, try:
grep '\^\^' somefile
I did that, don't worry :)
(Otherwise I wouldn't get hits on our e-mails about this...)
About the other suggestions from Giridhar: I'm willing to experiment
if you tell me what to do in
Alexander Sack wrote:
I think the best way would be if you can somehow start with a new
mozilla profile (e.g. a new test user on your system), then import it to
thunderbird (during initial start of thunderbird) to reproduce this.
I've done that also. If I create a new user and login as that user
On 05/04/14 09:29 +0200, Manuel Bilderbeek said ...
Alexander Sack wrote:
Manuel Bilderbeek wrote:
Yup, but there's not even a hit on ^^.
ups, you need to escape it. In case you did not notice, try:
grep '\^\^' somefile
I did that, don't worry :)
(Otherwise I wouldn't get hits
On 05/04/12 19:44 +0200, Alexander Sack said ...
since this problem only appears if you import old stuff from mozilla, I
suspect
that the problem is not in the IMAP layer, but somehow the old IMAP settings
are
trashed during migration.
Alex/Manuel,
Do you think it would be a good idea
Hi all,
Alexander Sack wrote:
Thanks Giridhar for you support.
Yes, thank you all for the support :)
since this problem only appears if you import old stuff from mozilla, I suspect
that the problem is not in the IMAP layer, but somehow the old IMAP settings are
trashed during migration.
Probably
Y Giridhar Appaji Nag wrote:
Do you think it would be a good idea to try and create a new profile
with Mozilla first and then import the profile to MT to reproduce this?
Just like the problem originally started off?
We have already done that. It is not reproducible that way. (See mail of
February
On 05/04/13 09:36 +0200, Manuel Bilderbeek said ...
Y Giridhar Appaji Nag wrote:
Do you think it would be a good idea to try and create a new profile
with Mozilla first and then import the profile to MT to reproduce
this? Just like the problem originally started off?
We have already
Manuel Bilderbeek wrote:
Yup, but there's not even a hit on ^^.
ups, you need to escape it. In case you did not notice, try:
grep '\^\^' somefile
Thanks
--
GPG messages preferred. | .''`. ** Debian GNU/Linux **
Alexander Sack| : :' : The universal
[EMAIL
On 05/04/11 09:32 +0200, Manuel Bilderbeek said ...
Y Giridhar Appaji Nag wrote:
1. Take a packet trace using ethereal when sending an email. It is
Fine with me, but you'll have to explain to me step by step what to do,
as I'm not familiar with this tool, i.e. I have never used it.
$
Hi,
Here are some results, after sending an almost empty mail.
Y Giridhar Appaji Nag wrote:
Look at the IMAP stream in the list of packets and right click on each
of those streams and select follow TCP stream in the pop-up menu and
analyse the stream for errors etc.
Here is all of them:
5790 list
On 05/04/12 17:00 +0200, Manuel Bilderbeek said ...
Here are some results, after sending an almost empty mail.
Y Giridhar Appaji Nag wrote:
Look at the IMAP stream in the list of packets and right click on each
of those streams and select follow TCP stream in the pop-up menu and
analyse
Y Giridhar Appaji Nag wrote:
3 NO Mailbox does not exist
Excellent. So there lies the problem, assuming INBOX.Sent is the name
of your sent mail folder.
Yep, I think so.
So, the problem seems to be that MT is using INBOX.INBOX^^Sent, which
doesn't exist according to the IMAP server.
Indeed. And
Manuel Bilderbeek wrote:
Y Giridhar Appaji Nag wrote:
Thanks Giridhar for you support.
Manuel,
since this problem only appears if you import old stuff from mozilla, I suspect
that the problem is not in the IMAP layer, but somehow the old IMAP settings are
trashed during migration.
Please
Y Giridhar Appaji Nag wrote:
1. Take a packet trace using ethereal when sending an email. It is
possible that the IMAP server is acting wierd and sending a failure
response, or perhaps, MT isn't sending the right IMAP commands when
copying the mail to Sent Folder. It would help to understand
I was wondering if the following options can be tried out? We probably
should be able to nail down the problem reported in this bug with these
1. Take a packet trace using ethereal when sending an email. It is
possible that the IMAP server is acting wierd and sending a failure
response, or
18 matches
Mail list logo
