qmail Digest 21 May 2001 10:00:01 -0000 Issue 1371
Topics (messages 62778 through 62797):
Re: Administrivia: Move to EZMLM]
62778 by: James R Grinter
62779 by: Andre Oppermann
62780 by: David Talkington
Using fetchmail with qmail
62781 by: Alexandre Goncalves Jacaranda
62782 by: Robin S. Socha
62783 by: Clemens Hermann
62785 by: David Talkington
62788 by: Alexandre Goncalves Jacaranda
62790 by: Mikko Hänninen
62792 by: Mark Delany
62794 by: David Talkington
Re: QMail configuration problem
62784 by: Ed Weinberg
62786 by: Robin S. Socha
62787 by: Rick Updegrove
Re: qmail + mutt
62789 by: Mikko Hänninen
62797 by: Bruno Wolff III
Still want to use fetchmail with qmail
62791 by: Alexandre Goncalves Jacaranda
62793 by: Mark Delany
test
62795 by: Jaros³aw Bad¼mierowski
qmail as 'proxy' - comments?
62796 by: John P
Administrivia:
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
Andre Oppermann <[EMAIL PROTECTED]> writes:
> First Aleph1 didn't like qmail/ezmlm at all... but appearently there
> is nothing else out there which can do the job.
he's using ezmlm, with postfix judging by the headers.
James.
James R Grinter wrote:
>
> Andre Oppermann <[EMAIL PROTECTED]> writes:
> > First Aleph1 didn't like qmail/ezmlm at all... but appearently there
> > is nothing else out there which can do the job.
>
> he's using ezmlm, with postfix judging by the headers.
Ah, well, shit happens...
--
Andre
-----BEGIN PGP SIGNED MESSAGE-----
Andre Oppermann wrote:
>James R Grinter wrote:
>>
>> Andre Oppermann <[EMAIL PROTECTED]> writes:
>> > First Aleph1 didn't like qmail/ezmlm at all... but appearently there
>> > is nothing else out there which can do the job.
>>
>> he's using ezmlm, with postfix judging by the headers.
>
>Ah, well, shit happens...
Hmm. outgoing.securityfocus.com turns a deaf ear to the outside world,
but I had a chat with mail.securityfocus.com:25. That one sure looks
like qmail to me ...
- -d
- --
David Talkington
PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQEVAwUBOwfw1b1ZYOtSwT+tAQG18QgAmylLw7DevODaNf4Vk4VDpa0K/AxJnJ5u
vzxBDu5JpQ65GXInVvXnkTpGD4I+PgotzUxExo/Kzvyl+leTUsxBE633osXu5eWs
3ZCPXXpH54d2LZNYa6mY2iF0CJi3owyzm85GmHjSMj31hnk7JTGVD+iZ8V2v0d1F
7UhU+NamEFd4mP21A9RYFVSjECI5jvLPJibQ2/+i1bsI1cafu3NZby1v56Z/05vT
5DYsdxfa0UKiYdujuwZHJmrPTC1e/YZsynDOx3ruOpWiril2qYs5lwruwI0Hzu1o
+OU+HjAS7Xlx3TB7jZjGc1hDPuxKP57i0HML/tAHDmjzxMrrCZs0Yg==
=xeTM
-----END PGP SIGNATURE-----
Hi everybody, How can I use fetchmail program with qmail ?
Thanks, Alexandre Gonçalves Jacarandá
-----------------------------------------------
FREE! The World's Best Email Address @email.com
Reserve your name now at http://www.email.com
* Alexandre Goncalves Jacaranda <[EMAIL PROTECTED]> writes:
> How can I use fetchmail program with qmail ?
http://www.linuxdoc.org/HOWTO/mini/Qmail+MH-5.html
found within < 10s at
http://www.google.de/search?q=fetchmail+qmail+howto&hl=de&safe=off
--
Robin S. Socha - Your Worst Network Nightmare(tm).
`In Germany, they are not referred to as network administrators. They
prefer to be called "Sons Of The Third Reich".' (Kate: www.katewerk.com)
Am 20.05.2001 um 12:31:16 schrieb Alexandre Goncalves Jacaranda:
> Hi everybody, How can I use fetchmail program with qmail ?
To fetch mail from a qmail server via pop3/imap fetchmail works right
out of the box.
To fetch mail and deliver it local into maildirs getmail might be the
right approach.
/ch
-----BEGIN PGP SIGNED MESSAGE-----
Alexandre Goncalves Jacaranda wrote:
>Hi everybody, How can I use fetchmail program with qmail ?
There's really nothing special about such a configuration; fetchmail
just delivers mail to whoever is listening on 25. As long as qmail
will accept deliveries for localhost, it works great. I do this on my
laptop.
- -d
- --
David Talkington
http://www.spotnet.org
PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQEVAwUBOwgGpL1ZYOtSwT+tAQFxCQgAvTjzNv7POYjlmsUa8f+fM96LyZB4qGRs
aF41rW6RgLtOMAn/Hac398IoVrEkVj7pa593RUDRHO+AL54EOTqXHI7CzqJlShHT
40pKhfKQYdyQP8GEGSAETeFPvcRW9iAJ7Dt0g/vWub/xDBBKp6J1b8Hpeqh8wxZk
2mRrq+ZnbHk8yMRnMoKtvKADokUt9Y2ZgKEjXZToRXwnrKIfuNM8Dkx1zK1BcQgs
CwLZ9KubWEIGwVRv57IfYoCB6QHH37Sf9wLPQrylDeobxpxiQaSiyId+qwAPi8ZD
mcfdtoF9rvY4Emagce60hAXg+2O40csj1qpHifl/Mr0TEW2g2ai5nQ==
=4QiG
-----END PGP SIGNATURE-----
Thanks for help.
Alexandre Gonçalves Jacarandá
David Talkington <[EMAIL PROTECTED]> wrote on Sun, 20 May 2001:
> There's really nothing special about such a configuration; fetchmail
> just delivers mail to whoever is listening on 25. As long as qmail
> will accept deliveries for localhost, it works great. I do this on my
> laptop.
There is one gotcha, you have to enable the "forcecr" option in your
.fetchmail configuration, if you're using delivery via localhost port
25. This is documented as a "qmail quirk" (or something) in the
fetchmail documentation, but it *is* documented at least... Without
this setting, qmail will reject the emails due to the CR/LF line ending
issue.
At least, it used to be this way.
Regards,
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.wizzu.com/
// The Corrs list maintainer // net.freak // DALnet IRC operator/
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs/
Happiness is always just a remembrance away.
On Mon, May 21, 2001 at 12:20:36AM +0300, Mikko Hänninen wrote:
> David Talkington <[EMAIL PROTECTED]> wrote on Sun, 20 May 2001:
> > There's really nothing special about such a configuration; fetchmail
> > just delivers mail to whoever is listening on 25. As long as qmail
> > will accept deliveries for localhost, it works great. I do this on my
> > laptop.
>
> There is one gotcha, you have to enable the "forcecr" option in your
> .fetchmail configuration, if you're using delivery via localhost port
> 25. This is documented as a "qmail quirk" (or something) in the
> fetchmail documentation, but it *is* documented at least... Without
> this setting, qmail will reject the emails due to the CR/LF line ending
> issue.
Hmm. The fetchmail man page seems to say it quite well:
"The `forcecr' option controls whether lines terminated by
LF only are given CRLF termination before forwarding.
Strictly speaking RFC821 requires this, but few MTAs
enforce the requirement it so this option is normally off
(only one such MTA, qmail, is in significant use at time
of writing)."
FWIW. This problem cannot occur if the pop server is qmail-pop3d. I've
used fetchmail on a variety of non-qmail pop servers and have never
needed forcecr. I hasten to add that that doesn't mean that Mikko is
wrong, just that the you probably don't need this option excepting
when you fetch from dodgy pop servers!
On a related note, it seems that fetcmail has made some effort to
support qmail in a variety of ways, including the -Q option which is
specifically designed to extract envelope addresses from Delivered-To:
addresses created via virtualdomains (See the fetchmail -Q option).
Regards.
-----BEGIN PGP SIGNED MESSAGE-----
Mark Delany wrote:
> "The `forcecr' option controls whether lines terminated by
> LF only are given CRLF termination before forwarding.
>
>FWIW. This problem cannot occur if the pop server is qmail-pop3d. I've
>used fetchmail on a variety of non-qmail pop servers and have never
>needed forcecr. I hasten to add that that doesn't mean that Mikko is
>wrong, just that the you probably don't need this option excepting
>when you fetch from dodgy pop servers!
I feel foolish. I admit to having been caught off guard by this one.
When I switched to qmail on my workstation, I began pulling mail via
fetchmail just fine using my existing configuration, and have thought
no more of it. However, I do note a lot of bounces in the logs for
various and sundry reasons, of which I also think little because of
the volumes of mailing list traffic I receive.
Please forgive my ignorance, but will the need for forcecr vary
depending on the sending MUA, or upon the POP server from which I'm
retrieving (which in this case is the UW POP3)? (In other words, have
I been selectively bouncing mail because of this?)
- -d
- --
David Talkington
http://www.spotnet.org
PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQEVAwUBOwhiZr1ZYOtSwT+tAQGTzgf/SB3mE+w4S/FXsFerYi5Yigsx3F+DuvSn
wZXYc1Lfpt+L98ORTGamB3d+9EsYga0hdHYhNPMRH3L5ib4yuKLE9F2Ezd1/+50Z
5QWMq11s9oKNNrPfiu61Zm5/AWYPE6I3eOhwZ6na4/5dJ1oR8cp441rUfOIOAMh3
fL5NmW5AQUHXlN8mFvVdrOaeb2efQQGzMDUYUQ/IhAnhbxnYG9A1JUlvAck9tdDf
jA5ySDyGqiARXOykR5NZLuq/b8xPZ4Bxz7IjVd5q/8znROjVhd60ukbXZH8kMbnS
4V347KwkJ2QBsnxQd3X1z03gkH7a2//htwh4XI0MpmJte64eoCJiVw==
=WS98
-----END PGP SIGNATURE-----
What is all of this? My mail program cannot read it, and I will not
try to launch it.
smime.p7m?
On Sat, 19 May 2001 11:31:05 +0200, "Fares Gianluca"
<[EMAIL PROTECTED]> wrote:
>To: <[EMAIL PROTECTED]>
>Subject: QMail configuration problem
>From: "Fares Gianluca" <[EMAIL PROTECTED]>
>Date: Sat, 19 May 2001 11:31:05 +0200
>
>MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAaCAJIAEggifQ29u
>dGVudC1UeXBlOiBtdWx0aXBhcnQvYWx0ZXJuYXRpdmU7DQoJYm91bmRhcnk9Ii0tLS09X05leHRQ
>YXJ0XzAwMF8wMDAwXzAxQzBFMDU3LjJGMzZGMDAwIg0KDQpUaGlzIGlzIGEgbXVsdGktcGFydCBt
--- Deleted for brevety ---
Ed Weinberg, Q5 Comm, LLC.
[EMAIL PROTECTED]
tel 914-713-7222
fax 914-713-7227
Connecting you to the internet...
* Ed Weinberg <[EMAIL PROTECTED]> writes:
> "Fares Gianluca" <[EMAIL PROTECTED]> wrote:
>> MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAaCAJIAEggifQ29u
> What is all of this? My mail program cannot read it, and I will not
> try to launch it.
http://www.ietf.org/html.charters/smime-charter.html
> smime.p7m?
http://www.google.de/search?hl=de&safe=off&q=smime.p7m&btnG=Google-Suche&meta=
--
Robin S. Socha - Your Worst Network Nightmare(tm).
`In Germany, they are not referred to as network administrators. They
prefer to be called "Sons Of The Third Reich".' (Kate: www.katewerk.com)
From: "Ed Weinberg" <[EMAIL PROTECTED]>
> What is all of this? My mail program cannot read it, and I will not
> try to launch it.
>
> smime.p7m?
Ed, I am guessing that your MUA, "Forte Agent 1.8/32.548" cannot properly
decipher a "Digitaly Signed" e-mail? Or you have possibly misconfigured it
somehow?
Rick Up
Bruno Wolff III <[EMAIL PROTECTED]> wrote on Fri, 18 May 2001:
> My solution (which you might want to mention in your qmail help) is:
>
> set sendmail="/var/qmail/bin/qmail-inject -h"
> set write_bcc=yes
But won't this break the b(ounce) functionality? Although the
qmail-inject man page says it knows about the Resent-To etc. headers,
but how do it determine when a message is forwarded and when it isn't?
I'm simply using
sendmail="/var/qmail/bin/qmail-inject"
... and this works just fine. I do use "write_bcc=yes" but that's
because I want to see the Bcc header in my saved copies of outgoing
email, not because it's needed when sending.
Regards,
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.wizzu.com/
// The Corrs list maintainer // net.freak // DALnet IRC operator/
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs/
Half of the people in the world are below average.
On Mon, May 21, 2001 at 12:15:28AM +0300,
Mikko Hänninen <[EMAIL PROTECTED]> wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> wrote on Fri, 18 May 2001:
> > My solution (which you might want to mention in your qmail help) is:
> >
> > set sendmail="/var/qmail/bin/qmail-inject -h"
> > set write_bcc=yes
>
> But won't this break the b(ounce) functionality? Although the
> qmail-inject man page says it knows about the Resent-To etc. headers,
> but how do it determine when a message is forwarded and when it isn't?
>
> I'm simply using
>
> sendmail="/var/qmail/bin/qmail-inject"
>
> ... and this works just fine. I do use "write_bcc=yes" but that's
> because I want to see the Bcc header in my saved copies of outgoing
> email, not because it's needed when sending.
It works with bounces. If you read the qmail-inject man page you will see
that it looks at resent-* headers.
If you use the -h option to get addresses from the headers you need to
include bcc headers.
I actually tested bounces and bcc's before posting this recommendation.
I also tested a pathological case to confirm that my suggestion uses
the correct recipient address, where as the default setting puts double
quotes into the email address.
Hi again!!!
I follow some tips, but I can get fetchmail working with qmail. But now
I will give more details...
I installed qmail following Life with qmail and it's working.
I configured Mailbox delivery in my system and I've ISP that use
sendmail and when I tried to fetch mail mails this error occurs:
client/server synchronization error.
My fetchmailrc is:
# Configuration created Sun May 20 18:04:12 2001 by fetchmailconf
set postmaster "alex"
set bouncemail
set properties ""
poll pop3.superonda.com.br with proto POP3
user 'clark_vr' there with password 'xxxxxx' is alex here options
forcecr dropdelivered warnings 3600
antispam 571 550 501 554
Thanks, Alexandre Gonçalves Jacarandá
On Sun, May 20, 2001 at 06:26:36PM -0300, Alexandre Gonçalves Jacarandá wrote:
> Hi again!!!
> I follow some tips, but I can get fetchmail working with qmail. But now
> I will give more details...
> I installed qmail following Life with qmail and it's working.
> I configured Mailbox delivery in my system and I've ISP that use
> sendmail and when I tried to fetch mail mails this error occurs:
> client/server synchronization error.
> My fetchmailrc is:
>
> # Configuration created Sun May 20 18:04:12 2001 by fetchmailconf
> set postmaster "alex"
> set bouncemail
> set properties ""
> poll pop3.superonda.com.br with proto POP3
> user 'clark_vr' there with password 'xxxxxx' is alex here options
> forcecr dropdelivered warnings 3600
> antispam 571 550 501 554
> Thanks, Alexandre Gonçalves Jacarandá
This is no doubt a fetcmail <-> popserver issue and has nothing to do
with qmail, but try running fetchmail with the option that gives
debugging output. The fetchmail manpage tells you which option.
Regards.
test
Jaros³aw Bad¼mierowski
We run a Linux box (LRP) as a firewall on our office network. Currently
ports 25 and 110 are portforwarded to an internal server which runs qmail
(on RedHat 7.0).
Is there any point in setting up a forwarding-only version of qmail (perhaps
using QMTP?) on the firewall box, or on a separate box in say a DMZ? I know
a 'mail proxy' like this is recommended for Sendmail in some network
security books, and if we did it then the internal box would have no ports
open to the outside world*, but with qmail's inherent security, is it
necessary?
*although as I type this I'm guessing that POP3 would still need to go
through to the internal server due to the user's home directories being on
there
Comments appreciated,
Regards
John
