Skip to main content

imapproxy will find a new home

This is a message sent out to imapproxy-info mailing list by the maintainer Dave McMurtrie:

Good morning,

I'm writing today to let you know that I'm officially retiring from my duties as, well, the sole keeper of all things imapproxy.

You've probably noticed that over the past year I haven't exactly been lighting this project on fire. In fact, I've been doing pretty much the bare minimum I had to do to keep it alive. Patches have come in and I've ignored them. Questions have been raised to me and I've ignored them, too. I can assure you all that it's been a matter of laziness and not hubris. Well, it's been a mixture of laziness and the fact that I've been extremely busy in my day job. I never took the time to make imapproxy into a "real" project with a real team of people working on it
and it suffered because of that.

I had considered just shutting the whole thing down, but there are still a couple people who run it so I embarked on a quest to find a new home for the software. The first group I thought of was the Squirrelmail team. imapproxy and Squirrelmail are a great complement to each other, and the Squirrelmail team is actually a team and not one guy like I am, so they're much more likely to be responsive to patch review and putting out new releases. Also, I've been running Squirrelmail myself for many years at more than one place of employment and I've been very impressed with their level of user support. They're a fine group, and I felt they would make for a much better caretaker of imapproxy than I have been.

With much trepidation, I contacted the Squirrelmail folks to gauge interest. I'm pleased to let you know that after much thought and discussion they're willing to take over the imapproxy project and keep it alive. Details of the transition are still being discussed, but it's already in the works. The imapproxy.org domain has been transferred over and they're now hosting the old website.

Many thanks go out to all the kind folks who have supported imapproxy (and indirectly, me) over the years.

Thanks!

Dave
--
Dave McMurtrie, SPE
Email Systems Team Leader
Carnegie Mellon University,
Computing Services


I myself, have been using imapproxy for 7 years and impressed with its performance. 4 years with squirrelmail and 3 years with roundcube. It helps a lot to enhance the performance of my mailserver. Hope the new maintainer will keep up the good job of Dave.

Thanks Dave. :)

Comments

Popular posts from this blog

mplayer-gui error : Error in skin config file

After installing mplayer-gui package, I can't start it.

$ gmplayer MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Error in skin config file on line 6: PNG read error in /usr/share/mplayer/skins/default/main Config file processing error with skin 'default'
After googling a bit, I found out that it was due to the png files in dir /usr/share/mplayer/skins/default. This is the default skin directory. To fix this error, I have to install ImageMagick package because I want to use the convert program to convert all of the png files to format png24. Thus, cd /usr/share/mplayer/skins/default; for FILE in *.png ; do sudo convert $FILE -define png:format=png24 $FILE ; done
Rerun gmplayer and all should be fine.
Have fun!
UPDATE (02-10-2017)

It doesn't work on Ubuntu 16.04 (xenial) but there's a workaround here.

You can update your syst…

Transparent proxy with squid 2.6

I have upgraded my squid from 2.5 STABLE13 to 2.6 STABLE18. Transparent proxy is setup differently in this version. You need this directives in squid.conf (usually in /etc or /usr/local/etc or /usr/local/squid/etc, check with your distro).

acl our_networks src 192.168.2.0/24 127.0.0.1
http_access allow our_networks
http_port 192.168.2.1:3128 transparent
always_direct allow all

where 192.168.2.1 is your proxy server IP address.


If you have flushed your iptables, create new rule:

iptables -t nat -A PREROUTING -i eth0 -p tcp –dport 80 -j REDIRECT –to-port 3128

where 3128 is the port where squid is running.
References:
http://www.deckle.co.za/squid-users-guide/Transparent_Caching/Proxy

postfix - mailbox size limit and message size limit

postfix is my MTA of choice. I use it for my mailserver because its simplicity , security and sendmail-compatible (the widely used smtp in the world but not as secure). It is also extensible by plugging other servers for various purposes (antispam, antivirus,database etc).

I had one problem with file attachment larger than 10MB. Users couldn't send it although I have setup squirrelmail (SM) to be able to attach files summed up more than 20MB and I had modified php settings as per here. The problem was not in SM setting. It was postfix. By default, attachment size that can be sent by postfix is 10MB ~ 10240000 byte. How did I know it? I looked in log file (for my system it is in /var/log/mail/errors. For other system, the file to look is /var/log/maillog). The line looked like this:

Feb 26 16:30:53 webmail postfix/sendmail[30775]: fatal: me@mymailserver.org(74): Message file too big


Solution
Open /etc/postfix/main.cf with a text editor of choice and find message_size_limit directive an…