courier-sqwebmail Mailing List for Courier Mail Server (Page 56)
Brought to you by:
mrsam
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(22) |
Aug
(35) |
Sep
(51) |
Oct
(28) |
Nov
(56) |
Dec
(40) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(31) |
Feb
(58) |
Mar
(20) |
Apr
(71) |
May
(23) |
Jun
(31) |
Jul
(11) |
Aug
(6) |
Sep
(15) |
Oct
(8) |
Nov
(23) |
Dec
(8) |
2006 |
Jan
(38) |
Feb
(29) |
Mar
(22) |
Apr
(18) |
May
(75) |
Jun
(19) |
Jul
(101) |
Aug
(33) |
Sep
(8) |
Oct
(3) |
Nov
(26) |
Dec
(35) |
2007 |
Jan
(31) |
Feb
(23) |
Mar
(4) |
Apr
(21) |
May
(1) |
Jun
(2) |
Jul
(20) |
Aug
(3) |
Sep
(9) |
Oct
(6) |
Nov
(14) |
Dec
(17) |
2008 |
Jan
(7) |
Feb
(8) |
Mar
(4) |
Apr
(4) |
May
(3) |
Jun
(12) |
Jul
(24) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
(9) |
Jun
(14) |
Jul
(12) |
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
(1) |
2010 |
Jan
|
Feb
|
Mar
(7) |
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(13) |
2011 |
Jan
(7) |
Feb
|
Mar
(4) |
Apr
(2) |
May
(10) |
Jun
(3) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(9) |
2012 |
Jan
|
Feb
|
Mar
(25) |
Apr
(5) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(7) |
Dec
|
2013 |
Jan
|
Feb
(3) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(1) |
Oct
|
Nov
(1) |
Dec
(1) |
2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(9) |
Aug
(6) |
Sep
(1) |
Oct
(25) |
Nov
|
Dec
(2) |
2015 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2017 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
2018 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
|
Nov
(6) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
(25) |
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2021 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
2023 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
(3) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: sqwebmail <sqw...@is...> - 2004-09-21 13:22:51
|
According last documentation of sqwebmail in Upgrading paragraph on Install.html file you can see: Upgrading from versions prior to "4.1" The problem is that last stable version of sqwebmail is 4.0.7, and the documentation talk about 4.1. Perhaps there is an error about version. Where you can read: "Upgrading from versions prior to 4.1" should be "Upgrading from versions prior 4.0" Could anyone help me with this problem? Thanks you in advance. |
From: Payal R. <pay...@sc...> - 2004-09-21 11:50:49
|
On Tue, Sep 21, 2004 at 07:13:29AM -0400, Sam Varshavchik wrote: > >part from the page when sqwebmail is invovked as, > >http://< ip >/cgi-bin/sqwebmail > > > >Can someone tell how to do it? > > Edit the HTML and make them hidden fields. Thanks for the mail. But which HTML file are you referring to? With warm regards, -Payal |
From: Sam V. <mr...@co...> - 2004-09-21 11:13:41
|
Payal Rathod writes: > Hi, > I want to remove the " Timezone " and "Restrict access to your IP address..." > part from the page when sqwebmail is invovked as, > http://< ip >/cgi-bin/sqwebmail > > Can someone tell how to do it? Edit the HTML and make them hidden fields. |
From: Payal R. <pay...@sc...> - 2004-09-21 10:01:48
|
Hi, I want to remove the " Timezone " and "Restrict access to your IP address..." part from the page when sqwebmail is invovked as, http://< ip >/cgi-bin/sqwebmail Can someone tell how to do it? With warm regards, -Payal |
From: Sam V. <mr...@co...> - 2004-09-21 01:29:22
|
I'm planning to make the following structural changes. This is the only chance for someone to talk me out of it. Right now, the authentication library, the authlib subdirectory, is present in the courier, courier-imap, and sqwebmail source tarballs. It gets separately compiled by all three packages. The authlib subdirectory contains code to verify login ids and passwords using the configured authentication module - be it system accounts, or virtual accounts using the= userdb, MySQL, PostgreSQL, or LDAP authentication module. I'm planning on spinning off the entire authentication library into a separate, standalone package. The new build procedure will be, as follows: 1. Download, compile, and install the courier-authlib tarball. 2. Configure the authentication library. Use the diagnostic tools (authinfo, authtest) to verify that everything is working correctly. 3. Download Courier, Courier-IMAP, and SqWebMail, and proceed to install the package in the usual fashion. I believe that the new approach offers the following benefits: =E2=80=A2 Smaller Courier, Courier-IMAP, and SqWebMail packages, going on fo= rwards. =E2=80=A2 Consolidated documentation. Instructions for setting up MySQL, PostgreSQL, and the rest, are currently duplicated twice, making it a maintenance pain. After consolidation documentation can be easily improved,= and overhauled. There will be an initial hump to ride over, to reconcile the minor differences in the authentication documentation in Courier, Courier-IMAP, and SqWebMail. Going forward, though, everything will be in one place. =E2=80=A2 The authentication API appears to be fairly stable and robust. It= will not be necessary to update the courier-authlib package with every upgrade. Updates to courier-authlib are expected to be very rare. =E2=80=A2 There is a small minority of established systems that use the stan= dalone SqWebMail and Courier-IMAP packages. The consolidated courier-authlib library will, as a bonus, provide an official way to use only one set of config files, in this configuration. I can only see one possible drawback. Only the daemonized configuration will= now be possible. The non-daemonized version of the authentication library will be removed. It is clear that the daemonized configuration is proven to= be more flexible, and is the only way to go. The daemonized configuration has been the default configuration for several years. I can only see the following minuses from losing the non-daemonized configuration. I believe the minuses are greatly outranked by the pluses. =E2=80=A2 There are some third party configuration libraries that only work = in a non-daemonized configuration. I'm aware of one such library, vmailmgr. Unless it's been updated to work in daemonized mode, it will no longer work. =E2=80=A2 There are also some other third-party hacks that also only work in= a non-daemonized configuration. There's at least one relay-after-imap or relay-after-pop hack for qmail, that only works in a daemonized configuration. I believe that relay-after-X hacks have been obsolete for several years now. Every mail client worth mentioning these days implemented authenticated SMTP, and the relay-after-X hacks need to go. =E2=80=A2 Currently, there are also some borderline configurations possible = in a non-daemonized configuration, such as using different authentication modules= completely for imap and pop3, or different authentication modules for non-encrypted and encrypted connections. This will no longer be possible, but I doubt that there's any valid reason to use such a strange setup. Overview of the planned courier-authlib package: 1. Uses the existing configure options. 2. Uses standard FHS install paths. 3. Installs: A) Various authdaemond builds, and the authdaemond startup script B) Configuration files C) Test binaries D) A small devel library that contains the authdaemon client code. Courier, Courier-IMAP, and SqWebMail will link against this lib. E) A migration script The migration script will look for any existing configuration files in any known directory used by older versions of Courier and SqWebMail. Presently I know of the following directories that could possibly hold old configuration files, on known platforms: /etc/courier /usr/lib/courier/etc /usr/lib/courier-imap/etc /usr/local/etc/courier /usr/local/lib/courier/etc /usr/local/lib/courier-imap/etc /usr/local/share/sqwebmail If there are some existing ports of Courier that dump the configuration files somewhere else, I need to know. The migration script searches this directory list, looking for configuration= files, and installs them in the new courier-authlib configuration directory,= unless courier-authlib's directory already contains working configuration files. 4. A new make target, 'make upgrade', runs the migration script. Therefore, the process for installing courier-authlib will be: configure make make install make upgrade make install-configure make install-configure, as always, runs sysconftool to build configuration files from their templates. 'make upgrade' must be executed before 'make install-configure', because 'make install-configure' installs default configuration files, and 'make upgrade' will not pull old configuration files if courier-authlib's configuration directory already has configuration= files installed. The migration script is a separate script, and is not a part of the Makefile, so that the migration script can be executed by Courier ports, as part of the upgrade process (followed by sysconftool). I believe that the upgrade process will be trouble-free. |
From: sqwebmail <sqw...@is...> - 2004-09-16 09:56:09
|
According last documentation of sqwebmail in Upgrading paragraph you can see: Upgrading from versions prior to "4.1" The problem is that last stable version of sqwebmail is 4.0.7, and the documentation talk about 4.1. Perhaps there is an error about version. Where you can read: "Upgrading from versions prior to 4.1" should be "Upgrading from versions prior 4.0" Could anyone help me with this problem? Thanks you in advance. |
From: <rog...@ro...> - 2004-09-12 22:13:15
|
I have a fairly unique setup. EVERYTHING is a virtual domain, but I'm not using any of the domain managers (i.e. vpopmail or vmailmgr). I tried playing with oMail because it dealt directly with Maildir format, and soon found that I had to write a short perl routine to login by using the user's complete email address, and using it to read a file to determine the pop/imap address, which would then authenticate. (I don't think oMail has been worked on for a few years - it's quite limited.) The problem (for me) is that sqwebmail authenticates the *nix account, and when it sends an email for the user, it appends the server hostname as the envelope sender. That is disasterous for me, as all "local" accounts are configured to trash any email sent to them (bounces or anything else sent to US...@ho...rver will be deleted) - everything must be sent to a valid email address in a virtual domain. Can anyone please suggest where and how I might call a Perl program to do this lookup for the pop address, and then copy the complete email address to whatever variable is used for the envelope sender address (and the "From" sender variable as per the compose form), and then substitute the complete email address with the pop address for authentication? I'm okay with Perl but haven't done much of any C for quite a while. Thanks. -- Roger Walker "HIS Pain - OUR Gain" |
From: Sam V. <mr...@co...> - 2004-09-10 23:02:54
|
michele writes: > =C2=AB HTML content follows =C2=BB > Hi, i've my server with qmail+vpopmail+sqwebmail; it works fine, but > within > sqwebmail if i send a new message, this goes to the sent folder, but qmail= > does not send the message, as i can see in the log: no entry for the sent > message, no errors. > I've tryed to reinstall sqwebmail, but the problem persists. sqwebmail sends the message by running the sendit.sh script, usually installed in /usr/local/share/sqwebmail. Verify that the script is doing the right thing. |
From: michele <mic...@og...> - 2004-09-10 15:04:19
|
Hi, i've my server with qmail+vpopmail+sqwebmail; it works fine, but = within=20 sqwebmail if i send a new message, this goes to the sent folder, but = qmail=20 does not send the message, as i can see in the log: no entry for the = sent=20 message, no errors.=20 I've tryed to reinstall sqwebmail, but the problem persists.=20 Please help me,=20 Thanks=20 Mik=20 |
From: Sam V. <mr...@co...> - 2004-09-10 12:32:55
|
Upayavira writes: >> =E2=80=A2 sqwebmail is not running under the same userid and groupid that= owns >> the maildir on the filesystem. > > Hmm. It is running as root. Surely root has access to the Maildir? After obtaining the account's uid and gid sqwebmail drops root and completes= the request running under the account's uid and gid. |
From: Upayavira <uv...@up...> - 2004-09-10 06:30:01
|
Sam Varshavchik wrote: > Upayavira writes: > >> Hi, >> >> I'm trying to get exim4 (as MTA), Courier IMAP and Courier webmail=20 >> working as a package. I seem to have got IMAP working, but when I log=20 >> into webmail, I get: > > IMAP has nothing to do with sqwebmail. I said that because they both access the same Maildir folders - so the=20 fact that IMAP was working, suggested that the Maildirs were okay. >> Internal error (module sqconfig.c, line 77) - contact system=20 >> administrator >> >> Any ideas what that means? >> >> I've got messages delivered into my Maildir folder - I can see them=20 >> there. > > It means that sqwebmail is unable to update an internal configuration=20 > file, in the maildir. Aaaaah. Thank you. > Possible reasons: > > =95 You are out of disk space. I was out of space on / (Maildirs are on /home). I cleared some out,=20 restarted apache2, sqwebmail and courier-authdaemon, and still got the sa= me. > =95 sqwebmail is not running under the same userid and groupid that own= s=20 > the maildir on the filesystem.=20 Hmm. It is running as root. Surely root has access to the Maildir? > According to whatever authentication method you're using with=20 > sqwebmail (which of course you didn't mention, obviously expecting=20 > everyone else to figure it out telepathically),=20 (I didn't mention it more because there's soooo much I could mention,=20 and as a complete mail newbie, I didn't know where to start.) I'm using authdaemon, with authpam, using system accounts. That seems to=20 work for IMAP, i.e. IMAP can log in. > the login account's home directory is X, and the accounts userid and=20 > groupid are Y and Z; however after changing to home directory X, and=20 > its maildir, the process is unable to save a configuration file=20 > because it does not have the filesystem permissions to do so (either=20 > the permissions on the filesystem are set incorrectly, or Y and Z are=20 > not the real owners of X, and its maildir). Hmmm. The user account is called upayavira. The Maildir is owned by=20 upayavira, with user rwx------ permissions on pretty much everything.=20 How could it be any other way? Surely my maildir is owned by me, and=20 should be owned only by me? I should also add, I'm using the deb packages from Debian Sarge. Thanks for any more help you are able to offer. Regards, Upayavira (who has spent plenty of time answering questions on=20 mailing lists, and needs to switch to the other side for a while!) |
From: Sam V. <mr...@co...> - 2004-09-09 23:53:11
|
Upayavira writes: > Hi, > > I'm trying to get exim4 (as MTA), Courier IMAP and Courier webmail > working as a package. I seem to have got IMAP working, but when I log > into webmail, I get: IMAP has nothing to do with sqwebmail. > Internal error (module sqconfig.c, line 77) - contact system administrator > > Any ideas what that means? > > I've got messages delivered into my Maildir folder - I can see them there. It means that sqwebmail is unable to update an internal configuration file, in the maildir. Possible reasons: =E2=80=A2 You are out of disk space. =E2=80=A2 sqwebmail is not running under the same userid and groupid that ow= ns the maildir on the filesystem. According to whatever authentication method you're using with sqwebmail (which of course you didn't mention, obviously expecting everyone else to figure it out telepathically), the login account's home directory is X, and the accounts userid and groupid are Y and= Z; however after changing to home directory X, and its maildir, the process is unable to save a configuration file because it does not have the filesystem permissions to do so (either the permissions on the filesystem are set incorrectly, or Y and Z are not the real owners of X, and its maildir). |
From: Upayavira <uv...@up...> - 2004-09-09 08:54:22
|
Hi, I'm trying to get exim4 (as MTA), Courier IMAP and Courier webmail working as a package. I seem to have got IMAP working, but when I log into webmail, I get: Internal error (module sqconfig.c, line 77) - contact system administrator Any ideas what that means? I've got messages delivered into my Maildir folder - I can see them there. Regards, Upayavira |
From: Sam V. <mr...@co...> - 2004-09-07 11:10:19
|
Marvin Aguilar writes: > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I'm having a little problem wit= h my webmail. im installed postfix > + courierpop3 + sqwebmail on my redhat linux 7.3 . When im using a email > client like outlook express i=C2=A0 can send and receive emails. My proble= m is, > when i used my web-based email (sqwebmail)=C2=A0and try to send an email t= o my > local domain,=C2=A0 for example i login to my webmail using sqwebmail ( > <URL:mailto:ma...@vh...>ma...@vh...) and my domain is vhin.com > and i try to send an email to my account or any account in my domain, it > is sent successfully=C2=A0but=C2=A0i can't receive it and my mail is being= spooled > at /var/spool/mail. sqwebmail has nothing to do with sending or receiving mail. sqwebmail sends= mail by running your mail server's sendmail wrapper, and your mail server is= responsible for sending and delivering the message. Check the documentation= for your mail server. |
From: <mar...@ya...> - 2004-09-07 06:40:12
|
hi, I'm having a little problem with my webmail. im installed postfix + courierpop3 + sqwebmail on my redhat linux 7.3 . When im using a email client like outlook express i can send and receive emails. My problem is, when i used my web-based email (sqwebmail) and try to send an email to my local domain, for example i login to my webmail using sqwebmail ( ma...@vh...) and my domain is vhin.com and i try to send an email to my account or any account in my domain, it is sent successfully but i can't receive it and my mail is being spooled at /var/spool/mail. But if i try to send an email to other domain like my account at yahoo, ma...@ya... i can receive it. Can anyone please help me? thanks a lot Regards, Marvin --------------------------------- Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now |
From: Jim H. <jh...@ar...> - 2004-09-06 17:56:55
|
> behaviour? Are we becomeing like Microsoft ignoring > the others? Quoting another open source project (KMail): --The golden rule of implementing standards is "Be strict in what you produce, but be tolerant in what you accept.". Being strict here means using RFC 2231 for filename encoding. Being tolerant means also to accept the broken attachment names Outlook produces.-- I don't know if sqwebmail accepts Outlook's broken attachment names or not but -certainly- I do not want it producing broken attachment names. Jim |
From: Ricardo S. <ri...@ya...> - 2004-09-06 16:27:05
|
Hi. --- Sam Varshavchik <mr...@co...> wrote: > Ricardo Santos writes: > > I have sqwebmail-4.0.7 (problem also with > > sqwebmail-4.0.6). When I send an email with an > > attachment with spaces in its name and read that > email > > on Outlook (any version) the attachment name es > > > Looks like it isn't a sqwebmail problem code > but > > maybe from a prerequisite or dependency program or > > library in the host system or even an elaborated > > ./configure or use of an especific auth-module. > > No. Outlook does not implement RFC 2231-formatted > mail headers. I see... > > I used to work with sqwebmail-3.3.2 on Suse 7.1 > and > > vpopmail-5.2.1 without any problem, a couple of > months > > RFC 2231 was implemented in sqwebmail 3.4.0, which > was released about two > years ago. > > RFC 2231 was standardized seven years ago. If you > would like to know why > Microsoft's software does not implement a seven year > old standard for > formatting mail headers, only Microsoft can answer > that question for you. I saw that RFC 2231 is implemented in the Exchange 2000 Server SDK and in the Exchange Server 2003 SDK. http://search.microsoft.com/search/results.aspx?st=b&na=88&View=en-us&qu=RFC+2231 It's strange that the server has this implementation but the clients. So what to do? I have hundreds of clients useing Outlook. Should I have to wait 5 years to Microsoft implement an 7 years old RFC like Sqwebmail did? I wonder how mail admins with Outlook clients are dealing with this problem. Did they hack code? Installed Netscape MUA? Changed it's job? > > > The mail file inside the maildir with a > > problematic attachment looks like: > > > > > --=_0_13980_1094247328 > > Content-Disposition: attachment; > > filename*0*=utf-8'en-us'Friends%20Theme.mp3 > > Content-Type: audio/mpeg; > > name*0*=iso-8859-1''Friends%20Theme.mp3 > > Content-Transfer-Encoding: base64 > > Right. See RFC 2231. I did, it looks good, but if we know that in some (or a lot of) cases Microsoft wasn't, isn't (and won't??) respect this documents why to ignore this situation and implement them (the RFC's) without any transparent way (not any note in bugs, readme, install, todo) to deal with Microsoft's software behaviour? Are we becomeing like Microsoft ignoring the others? Finally. My enterprise email solution is very good, very fast, and with a low cost of maintenancy and operation (thanks to the open source). What do I do to solve or deal with this problem? _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush |
From: Jim H. <jh...@ar...> - 2004-09-04 16:36:54
|
I had this problem and I believe I created a file /etc/courier/defaultdomain and put my domain in there... as in # echo love.com > /etc/courier/defaultdomain sift through the mailing list archives or read http://www.courier-mta.org/courier.html I know that is where I found the answer. Jim On Saturday 04 September 2004 01:35, Marvin Aguilar wrote: > Hi, > > I was successful in configuring sqwebmail 4.0.7. I have only one domain > and they can login without typing the full domain name. But when it logs > in it shows the machine name as the domain. Does anybody know how to change > that. for example... ma...@ai... aileen is the name of > machine..... how can change it to ma...@lo.......... thanks > > > > Regards, > > Marvin > > > --------------------------------- > Yahoo! Messenger - Communicate instantly..."Ping" your friends today! > Download Messenger Now > > !DSPAM:413954a1316778066910310! |
From: <mar...@ya...> - 2004-09-04 05:35:29
|
Hi, I was successful in configuring sqwebmail 4.0.7. I have only one domain and they can login without typing the full domain name. But when it logs in it shows the machine name as the domain. Does anybody know how to change that. for example... ma...@ai... aileen is the name of machine..... how can change it to ma...@lo.......... thanks Regards, Marvin --------------------------------- Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now |
From: Sam V. <mr...@co...> - 2004-09-03 23:32:05
|
Ricardo Santos writes: > > Hi. > > I have sqwebmail-4.0.7 (problem also with > sqwebmail-4.0.6). When I send an email with an > attachment with spaces in its name and read that email > on Outlook (any version) the attachment name es > Looks like it isn't a sqwebmail problem code but > maybe from a prerequisite or dependency program or > library in the host system or even an elaborated > ./configure or use of an especific auth-module. No. Outlook does not implement RFC 2231-formatted mail headers. > I used to work with sqwebmail-3.3.2 on Suse 7.1 and > vpopmail-5.2.1 without any problem, a couple of months RFC 2231 was implemented in sqwebmail 3.4.0, which was released about two years ago. RFC 2231 was standardized seven years ago. If you would like to know why Microsoft's software does not implement a seven year old standard for formatting mail headers, only Microsoft can answer that question for you. > The mail file inside the maildir with a > problematic attachment looks like: > > --=_0_13980_1094247328 > Content-Disposition: attachment; > filename*0*=utf-8'en-us'Friends%20Theme.mp3 > Content-Type: audio/mpeg; > name*0*=iso-8859-1''Friends%20Theme.mp3 > Content-Transfer-Encoding: base64 Right. See RFC 2231. |
From: Ricardo S. <ri...@ya...> - 2004-09-03 22:26:55
|
Hi. I have sqwebmail-4.0.7 (problem also with sqwebmail-4.0.6). When I send an email with an attachment with spaces in its name and read that email on Outlook (any version) the attachment name es changed to something like att000004.dat, I have noticed that if the file extention is described on mime.types file the file name is changed to something like att000004.mp3 (mp3 file listed on mime.types file). No problem sqwebmail to sqwebmail or outlook to outlook. I have looked in http://www.mail-archive.com sqwebmail archives and there are various reports with this problem with versions of sqwebmail 3.X but no answer or tip to solve this. Looks like it isn't a sqwebmail problem code but maybe from a prerequisite or dependency program or library in the host system or even an elaborated ./configure or use of an especific auth-module. I used to work with sqwebmail-3.3.2 on Suse 7.1 and vpopmail-5.2.1 without any problem, a couple of months ago I upgrated many things in a diferent server (the only thing that survives since then is a tgz with my Maildirs so all the instalation was from zero), my new environment is: SuSE 9.0 2.4.21-144-smp4G i386 vpopmail 5.4.5 with oracle (It shuldn't have to concert with this problem but, isn't it?) sqwebmail-4.0.7 ./configure --enable-cgibindir=/home/apache/cgi-bin --enable-imagedir=/home/apache/htdocs-webmail/webmail --with-db=gdbm --with-authvchkpw --without-authpwd --without-authshadow --without-authpam --without-authuserdb --without-authldap --without-authdaemon --without-fcgi --without-ispell --enable-https=auto --enable-hardtimeout=3600 --enable-softtimeout=1200 --enable-autopurge=7 --enable-maxpurge=14 --enable-mimetypes=/etc/mime.types --with-maxargsize=1048576 --with-maxformargsize=3145728 --with-maxmsgsize=13107200 --enable-changepass --with-gzip --with-calendar --with-calendarpurge=30 --with-trashquota The mail file inside the maildir with a problematic attachment looks like: ---cut begin--- Subject: test 14 attach Date: Fri, 03 Sep 2004 16:35:17 -0000 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=_0_13980_1094247328"; charset="utf-8" This is a MIME-formatted message. If you see this text it means that your mail software cannot handle MIME-formatted messages. --=_0_13980_1094247328 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: quoted-printable ni=C3=B1o =C3=A1rbol --=_0_13980_1094247328 Content-Disposition: attachment; filename*0*=utf-8'en-us'Friends%20Theme.mp3 Content-Type: audio/mpeg; name*0*=iso-8859-1''Friends%20Theme.mp3 Content-Transfer-Encoding: base64 ---cut ends--- Somebody please please please help me. _______________________________ Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now. http://promotions.yahoo.com/goldrush |
From: Laurent W. <lw...@te...> - 2004-09-03 12:59:09
|
Hi, HTML validator (http://validator.w3.org/) fails to readmsg templates On an address header display, a </span> is missing with sqwebmail 4.0.6 Here is a sample output (lines feeds are mine): <tr valign="baseline"> <th align="right" class="message-rfc822-header-name"> To: <span class="tt"> </span> </th> <td> <span class="message-rfc822-header-contents"> <a href="XXX?folder=INBOX&form=quickadd&pos=23&newname=lwa%40XXX&newaddr=lwa%40XXX" style="text-decoration: none" onmouseover="window.status='Ajouter au carnet d\'addresses'; return true;" onmouseout="window.status=''; return true;" > <span class="message-rfc822-header-address"> lwa@XXX </a> <------- no </span> here </span> </td> </tr> I'm unsure of the need of the starting <span>. A <a class="message-rfc822-header-address" ...> should be enough. |
From: Laurent W. <lw...@te...> - 2004-09-03 12:56:09
|
Hi, I'm using sqwebmail 4.0.6. When I send a message with a long Subject header containing non ASCII characters, the header is RFC2047 encoded and wrapped. The problem is that the split may appear into the RFC2047 atom. For example, when I send a message with the Subject, =E0=E8=E2=E4 =E9=E8=EA=EB =EE=EF =F4=F6 =F9=FB=FC =C2 =CA =CE =D4 =DB =C4= =CB =CF =D6 =DC =E7 =C7=20 It is converted to the two lines : Subject: =3D?UTF-8?B?w6DDqMOiw6Qgw6nDqMOqw6sgw67DryDDtMO2IMO5w7vDvCDDgiDD= iiDD jiDDlCDD?=3D =3D?UTF-8?B?myDDhCDDiyDDjyDDliDDnCDDpyDDhyDDnw=3D=3D?=3D Which is illegal and cause reading trouble to some mail agent (including sqwebmail) See below for a patch who allow the split only on spaces, the header become : Subject: =3D?UTF-8?B?w6DDqMOiw6Qgw6nDqMOqw6sgw67DryDDtMO2IMO5w7vDvCDDgiDD= iiDDjiDDlCDD?=3D =3D?UTF-8?B?myDDhCDDiyDDjyDDliDDnCDDpyDDhyDDnw=3D=3D?=3D --- sqwebmail/newmsg_create.c.orig Wed Aug 4 16:10:53 2004 +++ sqwebmail/newmsg_create.c Wed Aug 4 16:11:27 2004 @@ -121,10 +121,9 @@ =20 for (spc=3D0, i=3D0; hdr[i]; i++) { - if (i + offset >=3D 75) + if (i + offset >=3D 75 && spc) { - if (spc) - i =3D spc; + i =3D spc; offset =3D 0; break; } |
From: Sam V. <mr...@co...> - 2004-09-03 11:13:21
|
Laurent Wacrenier writes: > Hi, > > I've send bug reports (but to the old list address) about RFC2047 > encoded headers who finished cut in the middle of the encoding and > about a missing </span>. I got no answer and I don't see them in the > Changelog. Do you want I repost them to the new list address ? Yes. |
From: <mar...@ya...> - 2004-09-03 10:39:12
|
Hi guys, i'm having a little problem with my sqwebmail, actually my webmail works fine its can send and receive email .. etc... .The only problem i encounter is that when i send an email to someone, they can see the hostname of my email server . for example jo...@ai... john is my account name, aileen is the email server name and love.com is my domain name. How can i change that setting that they can only see jo...@lo...? actually it can be change manually but i need to specify it everytime i send an email. btw im using postfix + courier pop3 + sqwebmail 4.0.7. --------------------------------- Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now |