On Wed, Mar 31, 2004 at 07:22:17PM +0100, sq sub wrote:
> I have tried as brian suggests writing the message out to a file from
> sendit.sh and the output show the same corruption, so the problem lies with
> sqwebmail, anyone any idea?
Next:
(1) what was the ./configure line you used to build sqwebmail?
(2) what authentication module(s) are you using? i.e. what do you get from
the following two commands:
# cat authmodulelist
# grep authmodulelist authdaemonrc
(3) when you login, the username is displayed at the top-right of the screen
- is this correct or is it also corrupted?
All this information comes out of the auth modules, so if there's a bug
there then it would provide a bad username - garbage in, garbage out.
If you're using authvchkpw, then what version of libvpopmail do you have?
libvpopmail has had problems with uninitialised buffers in the past.
If you're using authpam: please post the exact matching line from
/etc/passwd. This again is so that we can try to replicate the problem.
Finally, what's the exact O/S that you're running under, and the version of
gcc used to compiled it?
Regards,
Brian.
>
> On Wed, Mar 31, 2004 at 04:09:56PM +0100, sq sub wrote:
> >I have now tried all of the following combinations and as you see the user
> >"from" email address is still corrupted (this is the log from qmail-send)
>
> OK. Unfortunately my account doesn't work for posting to the sqwebmail list,
> so I'm going to drop out of the conversation until it's fixed.
>
> Until then, I suggest you replace sendit.sh with a test script: something
> like
>
> #!/bin/sh
> date >>/tmp/sendit.$$
> echo "Params: $@" >>/tmp/sendit.$$
> echo "Message:" >>/tmp/sendit.$$
> cat - >>/tmp/sendit.$$
> exit 0
>
> Each time you send a message, it will appear in /tmp/sendit.NNNNN which you
> can read, and prove whether the header is corrupted there (in which case
> it's sqwebmail's fault) or not (in which case it's qmail's fault)
>
> Good luck,
>
> Brian.
>
> >
> >After install-configure
> >
> >@40000000406ad46537409994 new msg 52224
> >@40000000406ad4653740b104 info msg 52224: bytes 378 from
> ><[EMAIL PROTECTED]@[EMAIL PROTECTED]> qp 8261 uid 89
> >@40000000406ad466010aa7ac starting delivery 52: msg 52224 to remote
> >[EMAIL PROTECTED]
> >@40000000406ad466010abf1c status: local 0/10 remote 1/20
> >@40000000406ad466084f5b84 delivery 52: success:
> >192.168.1.1_accepted_message./Re
> >mote_host_said:_250_Roger/
> >@40000000406ad466084f76dc status: local 0/10 remote 0/20
> >@40000000406ad466084f7eac end msg 52224
> >
> >
> >
> >after edit CHARSET
> >
> >@40000000406ad4b6041cc9ac new msg 52224
> >@40000000406ad4b6041ce11c info msg 52224: bytes 384 from
> ><[EMAIL PROTECTED]@[EMAIL PROTECTED]> qp 8307 uid 89
> >@40000000406ad4b60a008df4 starting delivery 55: msg 52224 to remote
> >[EMAIL PROTECTED]
> >@40000000406ad4b60a00a94c status: local 0/10 remote 1/20
> >
> >
> >after adding
> >
> >./configure --disable-autorenamesent \
> >--without-authdaemon \
> >--with-authvchkpw \
> >--enable-unicode=iso-8859-1,utf-8
> >to configure
> >then make; make install-strip; them make install-configure
> >i still get:
> >
> >@40000000406ad69016719cf4 new msg 52226
> >@40000000406ad6901671b464 info msg 52226: bytes 380 from
> ><[EMAIL PROTECTED]@[EMAIL PROTECTED]> qp 12144 uid 89
> >@40000000406ad6901fd0d814 starting delivery 60: msg 52226 to remote
> >[EMAIL PROTECTED]
> >@40000000406ad6901fd0f36c status: local 0/10 remote 1/20
> >@40000000406ad69026ea16ec delivery 60: success:
> >192.168.1.1_accepted_message./Re
> >mote_host_said:_250_Roger/
> >@40000000406ad69026ea362c status: local 0/10 remote 0/20
> >@40000000406ad69026ea3a14 end msg 52226
> >
> >then an edit to CHARSET to leave just iso-8859 i still get:
> >
> >@40000000406ad77a17348f34 new msg 52226
> >@40000000406ad77a1734a6a4 info msg 52226: bytes 380 from
> ><[EMAIL PROTECTED]@[EMAIL PROTECTED]> qp 12245 uid 89
> >@40000000406ad77a228355b4 starting delivery 63: msg 52226 to remote
> >[EMAIL PROTECTED]
> >@40000000406ad77a2283710c status: local 0/10 remote 1/20
> >@40000000406ad77a2a08fa8c delivery 63: success:
> >192.168.1.1_accepted_message./Re
> >mote_host_said:_250_Roger/
> >@40000000406ad77a2a0915e4 status: local 0/10 remote 0/20
> >@40000000406ad77a2a091db4 end msg 52226
> >
> >
> >
> >>This is my configure settings. it's about a simple as it gets. $
> >>./configure --disable-autorenamesent \
> >> --without-authdaemon \
> >> --with-authvchkpw
> >>
> >>I have seen some people talking about the CHARSET which as you can see I
> >>am not setting about, do you think that may have something to do with it?
> >>
> >>Brian Candler writes:
> >>
> >>>On Mon, Mar 29, 2004 at 12:07:37PM +0100, sq sub wrote:
> >>>>I have been using sqwebmail 3.3.7 for some time and it's ok.
> >>>>
> >>>>after upgrading to v4.0.2 I now get corruption in the user name part of
> >>>>the email address when I send an email. it looks like random stuff then
> >>>>the last two characters are ok then followed by the @and domain.
> >>>>
> >>>>The system is running on redhat 7.2 (yes it's old!)
> >>>>
> >>>>does anyone have the same issue?
> >>>
> >>>Looks like someone else does, posted a couple of weeks ago:
> >>>http://marc.theaimsgroup.com/?l=sqwebmail&m=107936857313811&w=2
> >>>
> >>>I have not seen a solution to this issue though. I haven't yet upgraded
> >>>to
> >>>this version myself either.
> >>>
> >>>What ./configure options did you use when compiling sqwebmail? Then we
> >>>might
> >>>be able to replicate your problem.
> >>>
> >>>Regards,
> >>>
> >>>Brian.
> >>
> >
>
