> This is correct. The default configuration allows for a site-specified
> selection of the userid who will own everything. Creating a new "courier"
> userid is a valid option, but so is recycling some suitable stock system
> userid, such as "daemon". Ditto for the groupid. Notwithstanding t
> > We are working on some issues with the Debian package of
> > courier-authlib. The current package uses --prefix=/usr and so the
> > shared libraries get installed in /usr/lib/courier-authlib. However
> > section 10.2 of the Debian policy requires that shared libraries be
> > installed in /usr/l
Hi,
We are working on some issues with the Debian package of
courier-authlib. The current package uses --prefix=/usr and so the
shared libraries get installed in /usr/lib/courier-authlib. However
section 10.2 of the Debian policy requires that shared libraries be
installed in /usr/lib unless there
> ><[EMAIL PROTECTED]>: business-mail2.vcn.com [209.193.73.60]:
> STARTTLS
> ><<< 454 TLS not available: missing RSA private key (#4.3.0)
> >
> >Now I realize that this is an error on their mail server, but I've
> >attempted to con
Greetings,
Whenever I try to email my mother (no joking) I get the following error:
<[EMAIL PROTECTED]>: business-mail2.vcn.com [209.193.73.60]:
>>> STARTTLS
<<< 454 TLS not available: missing RSA private key (#4.3.0)
Now I real
> Haven't tried it yet but I have seen courier password changing plugin
> here: http://www.squirrelmail.org/plugin_view.php?id=21
>
> Hope it helps.
> David
That is exactly what I was looking for. My only difficulty now is
getting [1]courierpassd to work with Debian. I submitted an RFP (bug
#2446
> > I was just discussing virtual-user password changing with a friend,
> > and how annoying it is not to have a way to easily change passwords
> > via either squirrelmail or imp.
>
> This is because both of them are nothing more than glorified IMAP clients,
> and IMAP has no facility to change p
> Does anyone have any practical or philosophical arguments on where to
> put virtual mail users' maildirs?
>
> Eg, they could be in /home/virtualmail/$domain/$username.
>
> But on the other side, if the domain 'belongs' to a system user,
> wouldn't it make more sense to put it in
> /home/$user
Does anyone have any decent sqwebmail templates?
Also, I couldn't help but noticing [1]riwos. Are there any plans to
merge some of their changes back into sqwebmail?
Charles
1. http://www.riikari.net/riwos/index.html
--
This is not
A clever verse
I tried
And tried
But just
Got worse
http://fro
Now that I am succesfully rejecting messages to non-existant users
(thanks again Sam), I want to reject messages that SpamAssassin
identifies as Spam (with a threshold I select). I noticed on the Courier
History page that rejecting Spam was an important issue in the
development of Courier. Referenc
> I'll remain skeptical, and you'll have to prove your assertions by
> showing some hard evidence, because that's not how Courier works.
>
> sqwebmail.com is a virtual domain on my server.
>
> EHLO default
> 250-mail.courier-mta.com Ok.
> 250-STARTTLS
> 250-XVERP=Courier
> 250-XEXDATA
> 250-XSECU
> >> Check whether the domain account home directory has global read and
> >> execute permissions. When receiving mail, courieresmtpd runs as
> >> the courier user. If it has read and execute permissions on the
> >> home directory it will refuse to accept any mail that does not have
> >> a matchi
> >> > Is there away to eliminate double bounces?
> >> >
> >> > I am specifically concerned with the following scenario: Spam sent to
> >> > inexistant local addresses is initially accepted by courier,
> >>
> >> Courier does not accept mail to nonexistent local addresses.
> >>
> >> Problem solve
> >>Maildroprc is only used when delivering mail to mailboxes... When
> >>would courier accept mail that wasn't going to be delivered to a
> >>valid user?
> >
> >
> > I should have been more specific there. I was referring to messages that
> > would not be delivered to a valid *local* user. The
> > Is there away to eliminate double bounces?
> >
> > I am specifically concerned with the following scenario: Spam sent to
> > inexistant local addresses is initially accepted by courier,
>
> Courier does not accept mail to nonexistent local addresses.
>
> Problem solved.
I guess my setup doe
> > I invoke it using maildrop by adding the following line to
> > ~/.mailfilter:
> >
> >xfilter "/usr/bin/spamc"
> >
> > I used to invoke it globally, but then realized I didn't want to check
> > mail that would never be delivered to a valid user, and this was the
> > only obvious way I saw
Hi,
I've looked through the documentation, the mailing list archives, and
Google, and have not found an answer to my question, so I am posting it
here:
Is there away to eliminate double bounces?
I am specifically concerned with the following scenario: Spam sent to
inexistant local addresses is i
> Hello.
> Is it possible to use spamassasin as courier filter?
> If not, how can I use spamassassin with maildrop? links to any guides =
> will be very helpful...
I invoke it using maildrop by adding the following line to
~/.mailfilter:
xfilter "/usr/bin/spamc"
I used to invoke it globally,
> >What I really want is to be able to limit the number of simultaneous
> >delivery threads to one. I don't mind enqueueing messages while
> >waiting for delivery, as in the long-term the server can always keep
> >up with the incoming mail flow. However I would like to prevent more
> >than one mess
Hi,
First of all let me express my gratitude for all of the helpful mail
server tools that Courier provides. It far exceeded my expectations
based on past experiences with other similar programs.
I was wondering whether or not it is possible to limit the number of
simultaneous delivery threads. I
20 matches
Mail list logo
