[toaster] Limit concurrent POP3 connections from an IP
Hi, Is there any way that we can control and limit the concurrent POP3 connections from an IP? This will prohibit some users to use from pop3 client software to repeatedly check for mailbox in very short period. Thanks. Regard, YM
Re: [toaster] Limit concurrent POP3 connections from an IP
Bill Shupp wrote: YM wrote: Hi, Is there any way that we can control and limit the concurrent POP3 connections from an IP? This will prohibit some users to use from pop3 client software to repeatedly check for mailbox in very short period. tcpserver cannot do this. couriertcpd can. Use courier-imap's POP server if you want that kind of limit control. There's also this patch: http://www.jms1.net/ucspi-tcp/ucspi-tcp-0.88-periplimit.6.patch Bill
[toaster] Spamassassin per-user rules
Hi, Is it possible to have per user rules with SpamAssassin in this configuration (ie using vpopmail)? If so, how do I do this? Thanks, Nick...
Re: [toaster] Limit concurrent POP3 connections from an IP
YM wrote: Hi Bill, Thank for your quick feedback. Do you mean that I have to use this patch together with courier-imap's POP server? No, it's a patch to add this functionality to tcpserver. I've never used it, though. So you're on your own. Bill
Re: [toaster] Spamassassin per-user rules
Nick Gilbert wrote: Hi, Is it possible to have per user rules with SpamAssassin in this configuration (ie using vpopmail)? If so, how do I do this? I use the vdelivermail - spamassassin + maildrop patches that I recently posted here on the list for vpopmail. Then, I run spamassassin with preferences in MySQL. Lastly, I add the sasql plugin to squirrelmail so that users can edit their preferences there. Regards, Bill
Re: [toaster] Server side filtering
Nick Gilbert wrote: I'd also like to know if there is a way to automatically sort mail into the correct IMAP folders based on headers at the server end. I used to use a .mailfilter file before but I'm not sure anything like this would work with vpopmail. Any pointers on how I can get this (or something similar) to work would be appreciated. Per my last email, use the vdelivermail-maildrop patches posted to the list recently. Bill
[toaster] spf_log patch
Hi all,
It's a problem not to know when an email is rejected by SPF, this patch
resolvs this issue.
Applied cleanly after toaster 0.7.2-patch, running in production.
Regards,
Eduardo Cortés.
--- qmail-smtpd.c.sin-spf-log 2005-05-03 16:25:00.0 +0200
+++ qmail-smtpd.c 2005-05-09 17:32:44.0 +0200
@@ -493,6 +493,38 @@
seenmail = 0;
out(250 flushed\r\n);
}
+
+void spf_log (char *sender, char *rcpt, char *title, char *description) {
+
+stralloc str_log = {0};
+
+if (!stralloc_copys (str_log, SPF )) die_nomem();
+if (!stralloc_cats (str_log, title)) die_nomem();
+if (!stralloc_cats (str_log, : from )) die_nomem();
+if (!stralloc_cats (str_log, sender)) die_nomem();
+if (!stralloc_cats (str_log, :)) die_nomem();
+if (remoteinfo)
+{
+ if (!stralloc_cats (str_log, remoteinfo)) die_nomem();
+}
+if (!stralloc_cats (str_log, remote )) die_nomem();
+if (fakehelo)
+{
+ if (!stralloc_cats (str_log, fakehelo)) die_nomem();
+}
+if (!stralloc_cats (str_log, :)) die_nomem();
+if (remoteip)
+{
+ if (!stralloc_cats (str_log, remoteip)) die_nomem();
+}
+if (!stralloc_cats (str_log, rcpt )) die_nomem();
+if (!stralloc_cats (str_log, rcpt)) die_nomem();
+if (!stralloc_cats (str_log, : )) die_nomem();
+if (!stralloc_cats (str_log, description)) die_nomem();
+if (!stralloc_0(str_log)) die_nomem();
+strerr_warn1(str_log.s,0);
+}
+
void smtp_mail(arg) char *arg;
{
int r;
@@ -524,6 +556,7 @@
case SPF_ERROR:
if (spfbehavior 2) break;
out(451 SPF lookup failure (#4.3.0)\r\n);
+ spf_log(mailfrom.s, addr.s, SPF lookup failure, error);
return;
case SPF_NONE:
case SPF_UNKNOWN:
@@ -567,6 +600,7 @@
}
}
}
+
void smtp_rcpt(arg) char *arg; {
if (!seenmail) { err_wantmail(); return; }
@@ -590,7 +624,11 @@
err_bmt();
return;
}
- if (flagbarfspf) { err_spf(); return; }
+ if (flagbarfspf) {
+ err_spf();
+ spf_log(mailfrom.s, addr.s, rejected, env_get(SPFRESULT));
+ return;
+ }
switch (chkuser_realrcpt (mailfrom, addr)) {
case CHKUSER_KO:
@@ -1205,6 +1243,7 @@
dohelo(remotehost);
}
+
# undef SERVERCERT
# undef CLIENTCA
Re: [toaster] Spamassassin per-user rules
Is it possible to have per user rules with SpamAssassin in this configuration (ie using vpopmail)? If so, how do I do this? I use the vdelivermail - spamassassin + maildrop patches that I recently posted here on the list for vpopmail. Then, I run spamassassin with preferences in MySQL. Lastly, I add the sasql plugin to squirrelmail so that users can edit their preferences there. Hmm.. this is all getting rather complicated for little me. Thanks very much for all your help but I'm coming to the conclusion that I'll probably have to use a commercial product. As my colleague always says Linux is only free if your time has no value - and I've already spent 3 evenings trying to get the various parts to work properly and now I find it can't even filter mail into folders. sigh Nick...
Re: [toaster] Spamassassin per-user rules
Nick Gilbert wrote: Hmm.. this is all getting rather complicated for little me. Thanks very much for all your help but I'm coming to the conclusion that I'll probably have to use a commercial product. Well, do whatever works for you. But it has been my experience that while some of this stuff can be difficult to setup, once you get it working you'll have a far better understanding of how it works, and you'll be much more qualified to maintain it. As my colleague always says Linux is only free if your time has no value That's a pretty loaded statement. I strongly disagree, but will refrain from engaging it on this list. - and I've already spent 3 evenings trying to get the various parts to work properly and now I find it can't even filter mail into folders. sigh Getting filtering working with the patches I described is trivial. And you can bypass them if are ok with manually configuring .qmail files for any user that wants filtering. I only use the patches because I want to use qmailadmin with the spam detection scheme. maildrop is pretty powerful, and well documented. My recommendation is to hold out on a commercial product, and read more docs. Regards, Bill
Re: [toaster] Spamassassin per-user rules
Bill Shupp wrote: I only use the patches because I want to use qmailadmin with the spam detection scheme. Woops.. that should read ... because I DON'T want to use qmailadmin's spam detection feature. This is primarily because it defaults to off, which is now what I want. Regards, Bill
Re: [toaster] Spamassassin per-user rules
Bill Shupp wrote: Woops.. that should read ... because I DON'T want to use qmailadmin's spam detection feature. This is primarily because it defaults to off, which is now what I want. Damn, I picked the wrong week to stop sniffing glue. The above statement is also wrong... should read ... it defaults to off, which is NOT what I want. Sorry folks... Bill
Re: [toaster] Spamassassin per-user rules
Hmm.. this is all getting rather complicated for little me. Thanks very much for all your help but I'm coming to the conclusion that I'll probably have to use a commercial product. Well, do whatever works for you. But it has been my experience that while some of this stuff can be difficult to setup, once you get it working you'll have a far better understanding of how it works, and you'll be much more qualified to maintain it. True. But the question is, will I *ever* understand it without spending more time than I would like to? I've only really just got into Linux and this isn't the most trivial of things to get working even with your excellent setup guide :) Bare in mind that I'm used to using products like MDaemon which installs in about 10 minutes and tend to work reliably for years. I was just trying to save myself the cash as I need a mail server for only a handful of people. As my colleague always says Linux is only free if your time has no value That's a pretty loaded statement. I strongly disagree, but will refrain from engaging it on this list. I don't agree either to be honest and I shouldn't have said it - but I do think there's a *little* truth in it. Linux solutions to tend to take a lot more time to get working than the commerical ones (unless you're unlucky with the commercial products) and if your time would be better spent doing something else, then going with a 'free' solution doesn't always end up being 'free'. Getting filtering working with the patches I described is trivial. And you can bypass them if are ok with manually configuring .qmail files for any user that wants filtering. I only use the patches because I want to use qmailadmin with the spam detection scheme. Bare in mind that before last week - I've never patched or installed anything in my life :) Maybe as I'll only have about 5 users, the vpopmail part of the install is more hassle than it's worth and I might have an easier time if I create 'normal' linux users and configure things with .qmail files like I used to on my old box (which someone else set up for me). Will that approach still work on a ShuppToaster(tm) or does the vpopmail stuff mangle the configuration too much? I only really *need* the smtp-auth, SpamAssassin, Simscan/clamav and webmail support because I'm not really going to be dealing with more than a few users. I *want* a linux install to work, but it scares me how much patching needs to be done to get VERY basic features into qmail that you'd think a lot of people would need (eg smtp-auth). I REALLY wish someone made a Qmail Toaster distribution that has all the common stuff already installed to start with such that almost nobody will need to patch it. That way you would effectively have a 'standard' install that was very well supported and not different because everyone's used a different distribution/patches etc. I'd pay for it. maildrop is pretty powerful, and well documented. My recommendation is to hold out on a commercial product, and read more docs. I'll take your advice and I'll persevere a little longer with qmail, but it might have to wait until the weekend as looking at the screen all day is doing my head in :) Nick...
