Re: [qmailtoaster] spamdyke rejecting all incoming messages
This test worked..with clamav turned off, mail is flowing normally. So you recommend doing as you suggested earlier regarding upgrading clamav? On Thu, Oct 27, 2016 at 9:33 PM, Eric <ebr...@whitehorsetc.com> wrote: > You can turn ClamAV off in /var/qmail/control/simcontrol > just to quickly eliminate, or verify, the problem: > > From: > :clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif > To: > :clam=no,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif > > # qmailctl cdb > # qmailctl stop > # qmailctl start > > On 10/27/2016 7:29 PM, Eric wrote: > >> I'd also look in /var/log/messages, /var/log/maillog (remember >> corresponding times). >> >> You could try updating ClamAV as well, one version at a time, from old >> ClamAV versions in this folder: >> >> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/old/ >> >> to the newest stable ClamAV version in this folder: >> >> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/ >> >> to the newest testing ClamAV version in this folder: >> >> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/testing/x86_64/ >> >> >> >> On 10/27/2016 7:15 PM, Kelly Cobean wrote: >> >>> Don't laugh, but: >>> >>> CentOS release 5.11 (Final) >>> >>> >>> [root@www spamdyke]# freshclam >>> ClamAV update process started at Thu Oct 27 21:15:12 2016 >>> WARNING: Your ClamAV installation is OUTDATED! >>> WARNING: Local version: 0.97.5 Recommended version: 0.99.2 >>> DON'T PANIC! Read http://www.clamav.net/support/faq >>> main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, >>> builder: amishhammer) >>> daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63, >>> builder: neo) >>> bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63, >>> builder: neo) >>> >>> >>> On Thu, Oct 27, 2016 at 8:43 PM, Eric <ebr...@whitehorsetc.com >>> <mailto:ebr...@whitehorsetc.com>> wrote: >>> >>> What system OS and version are you running? >>> ClamAV? >>> >>> >>> On 10/27/2016 4:48 PM, Kelly Cobean wrote: >>> >>> Hey all, >>> My QMT install has been running for years and admittedly >>> I've done >>> very little maintenance/patching. I still run a few domains >>> with EZ-MLM >>> lists and individual accounts and recently, my server stopped >>> accepting >>> all inbound messages. There are only 2 messages in my queue and >>> I've >>> stopped and restarted qmail (qmailctl stop/start) and I've even >>> restarted the server. There's plenty of disk space on the >>> server. >>> >>> The error logs indicate the following: >>> >>> @4000581282090d55df2c tcpserver: status: 1/100 >>> @4000581282090d55eae4 tcpserver: pid 15044 from >>> 209.85.215.45 >>> @4000581282090d55eae4 tcpserver: ok 15044 >>> www.novagunrunners.com:66.151.32.133:25 :209.85.215.45 >>> ::35674 >>> @40005812820b0c77db3c CHKUSER accepted sender: from >>> <ke...@cobean.net::> remote >>> >> > rcpt <> : sender accepted >>> @40005812820b119a188c CHKUSER accepted any rcpt: from >>> <ke...@cobean.net::> remote >>> >> > rcpt >>> <kcob...@vipercrazy.com <mailto:kcob...@vipercrazy.com> >>> <mailto:kcob...@vipercrazy.com <mailto:kcob...@vipercrazy.com>>> >>> : accepted any >>> recipient for this domain >>> @40005812820b119a2444 policy_check: remote ke...@cobean.net >>> <mailto:ke...@cobean.net> >>> <mailto:ke...@cobean.net <mailto:ke...@cobean.net>> -> local >>> kcob...@vipercrazy.com <mailto:kcob...@vipercrazy.com> >>> <mailto:kcob...@vipercrazy.com <mailto:kcob...@vipercrazy.com>> >>> (UNAUTHENTICATED SENDER) >>> @40005812820b119a282c policy_check: policy allows >>> transmission >>> @40005812820c1bfa123c qmail-smtpd: qq soft reject (mail >>> server >>> temporarily rejected message (#4.3.0)): >>> MAILFROM:<
Re: [qmailtoaster] spamdyke rejecting all incoming messages
Don't laugh, but: CentOS release 5.11 (Final) [root@www spamdyke]# freshclam ClamAV update process started at Thu Oct 27 21:15:12 2016 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.97.5 Recommended version: 0.99.2 DON'T PANIC! Read http://www.clamav.net/support/faq main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: amishhammer) daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63, builder: neo) bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63, builder: neo) On Thu, Oct 27, 2016 at 8:43 PM, Eric <ebr...@whitehorsetc.com> wrote: > What system OS and version are you running? > ClamAV? > > > On 10/27/2016 4:48 PM, Kelly Cobean wrote: > >> Hey all, >> My QMT install has been running for years and admittedly I've done >> very little maintenance/patching. I still run a few domains with EZ-MLM >> lists and individual accounts and recently, my server stopped accepting >> all inbound messages. There are only 2 messages in my queue and I've >> stopped and restarted qmail (qmailctl stop/start) and I've even >> restarted the server. There's plenty of disk space on the server. >> >> The error logs indicate the following: >> >> @4000581282090d55df2c tcpserver: status: 1/100 >> @4000581282090d55eae4 tcpserver: pid 15044 from 209.85.215.45 >> @4000581282090d55eae4 tcpserver: ok 15044 >> www.novagunrunners.com:66.151.32.133:25 :209.85.215.45::35674 >> @40005812820b0c77db3c CHKUSER accepted sender: from >> <ke...@cobean.net::> remote >> rcpt <> : sender accepted >> @40005812820b119a188c CHKUSER accepted any rcpt: from >> <ke...@cobean.net::> remote >> rcpt >> <kcob...@vipercrazy.com <mailto:kcob...@vipercrazy.com>> : accepted any >> recipient for this domain >> @40005812820b119a2444 policy_check: remote ke...@cobean.net >> <mailto:ke...@cobean.net> -> local kcob...@vipercrazy.com >> <mailto:kcob...@vipercrazy.com> (UNAUTHENTICATED SENDER) >> @40005812820b119a282c policy_check: policy allows transmission >> @40005812820c1bfa123c qmail-smtpd: qq soft reject (mail server >> temporarily rejected message (#4.3.0)): MAILFROM:<ke...@cobean.net >> <mailto:ke...@cobean.net>> RCPTTO:kcob...@vipercrazy.com >> <mailto:rcptto%3akcob...@vipercrazy.com> >> @40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from: >> ke...@cobean.net <mailto:ke...@cobean.net> to: kcob...@vipercrazy.com >> <mailto:kcob...@vipercrazy.com> origin_ip: 209.85.215.45 origin_rdns: >> mail-lf0-f45.google.com <http://mail-lf0-f45.google.com> auth: (unknown) >> encryption: TLS reason: >> 451_mail_server_temporarily_rejected_message_(#4.3.0) >> @40005812820c24ba9874 tcpserver: end 15044 status 0 >> >> >> My spamdyke is probably old: >> >> [root@www spamdyke]# spamdyke --version >> spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at) >> silence (dot) org >> http://www.spamdyke.org/ >> >> >> I've made no changes on the server. Has anyone seen this before? I >> appreciate any help you can offer. >> >> > - > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com > >
Re: [qmailtoaster] qmailtoaster yum repo failing
Thank you Eric. I see the RPMs for SA, CAV and Dovecot (I'm still running Courier). Are these the only items still being actively maintained for QMT? Kelly On 09/14/2015 15:57, Eric Broch wrote: > Kelly, > > The qmail repo is no longer valid. I have rpms (x86, x86_64) here [2]. > > EricB > > On 9/14/2015 1:51 PM, Kelly Cobean wrote: > >> It's been quite awhile since I updated my mail server. I ran 'yum update' and it DL'd all of the system packages, but when it got to the QM repo, I got this error: >> >> Error Downloading Packages: >> qmailtoaster-plus-0.3.2-1.4.21.noarch: failure: qmailtoaster-plus-0.3.2-1.4.21.noarch.rpm from qtp-nodist: [Errno 256] No more mirrors to try. >> >> Anybody know if the repo is still valid? I'm following the instructions listed here: http://wiki.qmailtoaster.com/index.php/Migrating_from_QmailToaster [1] >> >> Thanks. >> >> - >> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com >> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com Links: -- [1] http://wiki.qmailtoaster.com/index.php/Migrating_from_QmailToaster [2] ftp://ftp.whitehorsetc.com/pub/qmail/CentOS5/qmt/rpms/
Re: [qmailtoaster] qmailtoaster yum repo failing
Odd that it's trying to download 0.3.2. Here's the output of 'qtp-whatmi' on the system: [root@www sbin]# qtp-whatami qtp-whatami v0.3.8 Mon Sep 14 16:07:38 EDT 2015 REAL_DIST=CentOS DISTRO=CentOS OSVER=5.8 QTARCH=x86_64 QTKERN=2.6.18-274.3.1.el5 BUILD_DIST=cnt5064 BUILD_DIR=/usr/src/redhat This machine's OS is supported and has been tested Looks like Yum is trying to pull an older version that what I'm already running? What's the current build version? On 09/14/2015 15:51, Kelly Cobean wrote: It's been quite awhile since I updated my mail server. I ran 'yum update' and it DL'd all of the system packages, but when it got to the QM repo, I got this error: Error Downloading Packages: qmailtoaster-plus-0.3.2-1.4.21.noarch: failure: qmailtoaster-plus-0.3.2-1.4.21.noarch.rpm from qtp-nodist: [Errno 256] No more mirrors to try. Anybody know if the repo is still valid? I'm following the instructions listed here: http://wiki.qmailtoaster.com/index.php/Migrating_from_QmailToaster Thanks. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] qmailtoaster yum repo failing
It's been quite awhile since I updated my mail server. I ran 'yum update' and it DL'd all of the system packages, but when it got to the QM repo, I got this error: Error Downloading Packages: qmailtoaster-plus-0.3.2-1.4.21.noarch: failure: qmailtoaster-plus-0.3.2-1.4.21.noarch.rpm from qtp-nodist: [Errno 256] No more mirrors to try. Anybody know if the repo is still valid? I'm following the instructions listed here: http://wiki.qmailtoaster.com/index.php/Migrating_from_QmailToaster Thanks. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] One user account can't login to Squirrelmail
Is the disable web access box checked if you look at the account in vqadmin? On 07/23/2014 13:57, Diana Calder wrote: I have an odd problem with one user account. When trying to login to Squirrelmail, the login will hang for several seconds then result in: ERROR: ERROR: Connection dropped by IMAP server. Query: LOGOUT All other accounts that have been tested can login to Squirrelmail just fine. The problem user account can check mail in The Bat! (email client) via POP3 or via IMAP. I have used vuserinfo to compare the account settings against other, correctly working, accounts and there are no differences in the flags or limits. A possible symptom or secondary issue is that the problem account is using 78% of its 1Gb quota, despite the fact that the user has cleared out most of his old mail via the POP3 client (that's the same percentage as before he cleared out the old email). He has about 700 messages in his Inbox and about 500 in his Sent, which really doesn't seem like enough to add up to ~780Mb, even if some have attachments. I have double that many messages and it only comes out to 9% (90 Mb) of a 1Gb quota. As a side note - when we moved to a CentOS6 VM with the compatible version of Qmailtoaster, we made the switch from Courier to Dovecot at the same time. That appears to have left a number of Courier directories behind in each account's Maildir. Does anyone have a cleanup script to get rid of these obsolete directories? - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Roundcube Survey
I am running roundcube in tandem with SM as well. I find that 99% of my users have selected RC as their daily client so I will likely shutdown SM at some point. On 05/28/2014 11:12, Dan McAllister wrote: On 5/27/2014 10:28 PM, Eric Shubert wrote: For those using Roundcube, please be so gracious as to answer a couple questions. Do you use it with nginx? (I expect mostly no answers) If not, have you used nginx for anything else? Thank you for your participation. I'm contemplating adding Roundcube to the 'stock' QMT. It's been long overdue. No, I don't use RC with nginx (don't use nginx for anything else either). Lastly, I think RC would be an excellent addition to QMT -- I run it in tandem with SquirrelMail on all of my servers. Dan McAllister QMT DNS/Mirror Admin -- IT4SOHO, LLC 33 - 4th Street N, Suite 211 St. Petersburg, FL 33701-3806 CALL TOLL FREE: 877-IT4SOHO 877-484-7646 Phone 727-647-7646 Local 727-490-4394 Fax We have support plans for QMail! - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Roundcube Survey
Oh, and I'm sorry I didn't answer the initial question. No, I'm not using Nginx, I'm using Apache. On 05/28/2014 12:05, Kelly Cobean wrote: I am running roundcube in tandem with SM as well. I find that 99% of my users have selected RC as their daily client so I will likely shutdown SM at some point. On 05/28/2014 11:12, Dan McAllister wrote: On 5/27/2014 10:28 PM, Eric Shubert wrote: For those using Roundcube, please be so gracious as to answer a couple questions. Do you use it with nginx? (I expect mostly no answers) If not, have you used nginx for anything else? Thank you for your participation. I'm contemplating adding Roundcube to the 'stock' QMT. It's been long overdue. No, I don't use RC with nginx (don't use nginx for anything else either). Lastly, I think RC would be an excellent addition to QMT -- I run it in tandem with SquirrelMail on all of my servers. Dan McAllister QMT DNS/Mirror Admin -- IT4SOHO, LLC 33 - 4th Street N, Suite 211 St. Petersburg, FL 33701-3806 CALL TOLL FREE: 877-IT4SOHO 877-484-7646 Phone 727-647-7646 Local 727-490-4394 Fax We have support plans for QMail! - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] A rudimentary question for multi-domain hosting
Thanks Dan, that's exactly what I was looking for. I wasn't sure if this was the proper way to configure the MX records, or if all of my domains should have MX records that point to a single A record in my primary domain, which is where the PTR for my IP points to and that is in my ME file. It sounds like either will work. On 04/28/2014 13:55, Dan McAllister wrote: Kelly: While Eric's reply is clear about the fact that the MX record has to use an A record reference (vs CNAME), I think the answer you need here is simply that the A-record has to point to the correct IP address. What name you put in the MX record is of little import, so long as it references an A record that points to the correct IP address. === By way of examples (for other users): Say my mail host is at 10.0.0.2, behind a NAT router with WAN IP address 1.2.3.4 (apologies to Google for using their IP in my example). - my mail host listens on ALL the standard ports (25, 80, 110, 143, 443, 465, 587, 993, 995) for web and mail hosting (all forwarded through my router). - my mail host uses a name of MAIL.QMTHOSTING.COM (that's one of MY OWN hosting domains, so no worries about using it here) - my clients each have their own domains (for grins, we'll use A.COM, B.COM, C.COM, etc) - in general, my clients DNS servers (whether hosted by me or not, with entries for their domains that look like: @ IN MX 10 MAIL MAIL IN A 1.2.3.4 Thus, to the outside world, they have an MX server at MAIL.A.COM, which resolves to 1.2.3.4. (Their domain name, their A record, my IP address). Now, where the SPAM detection for IP addressing starts is when an outside mail server connects: - sendingdomain.com wants to send to u...@a.com detects the MX record is MAIL.A.COM, which resolves (by A-record) to 1.2.3.4 - sendingdomain.com connects to 1.2.3.4 on port 25 and gets an EHLO response that the name of the server is MAIL.QMTHOSTING.COM - sendingdomain.com then does a DNS query for MAIL.QMTHOSTING.COM and gets an IP of 1.2.3.4 -- so far, so good - sendingdomain.com next does a DNS query for 1.2.3.4 (actually, 4.3.2.1.IN-ADDR.ARPA) and gets a PTR value of MAIL.QMTHOSTING.COM -- bingo! a match! - sendingdomain.com continues sending the message (presumably to a domain in the rcpthosts file)... The trouble comes when you want to connect your _CLIENTS_... - for WEBMAIL, I simply create an entry for each domain (HTTPS://MAIL.A.COM [1], etc) that redirects to the real ssl page HTTPS://MAIL.QMTHOSTING.COM [2]. That way the SSL certificate (which only has the name mail.qmthosting.com in it) works. (I do not allow webmail access except through https). - for IMAP mail, there are 3 options: a) connect to MAIL.A.COM on port 143 and use IMAP with _no security_ (BAD IDEA -- I only allow this on one host, and only because the client INSISTS upon it) b) connect to MAIL.A.COM on port 993 and use IMAP OVER SSL -- clients will have _varying degrees of difficulty _as the SSL Cert won't match the host name c) connect to MAIL.QMTHOSTING.COM on port 993 and use IMAP OVER SSL with my TRUSTED SSL CERTIFICATE (names match, so no errors, and no worries!) NOTE: Most clients choose option C -- in large part because I tell them to :) - The same general idea goes for POP access, only on ports 110 and 995. SMTP access is a little more tricky... it is a BEST PRACTICE to disallow SMTP-AUTH on port 25 (because it can be abused -- I'm not sure how, but all the major anti-virus and anti-spam companies tell me so, and I'm not of a need to determine exactly why -- I have bigger fish to fry!). Since this is the only un-authenticated access to the system, this port's SMTP service is plugged into SPAMDYKE -- which has been told to NOT allow SMTP-AUTH. But that is OK, because we're talking about CLIENT access to an SMTP server here: - I allow SMTP-AUTH with or without SSL on port 587 (if you choose to enable SSL, remember that the certificate is for the site mail.qmthosting.com) - I allow SMTP-AUTH only with SSL on port 465 (again, remember that the certificate is for the hostname mail.qmthosting.com). So, clients can configure their SMTP access as being on port 587 using mail.a.com, or port 465 using SSL and the host name mail.qmthosting.com. I really need to post some of this on the WIKI ... sigh when I'm less overworked :) Dan On 4/25/2014 7:41 PM, Kelly Cobean wrote: Sorry about the hijack Eric. Won't do that again. One last question. Should the MX records for the other domains indicate the hostname that is in the me file or should they be a record for a host in their own domain that maps to my server ip? Ie should I have 5 domains all with identical MX entries? Sent from my iPhone -- IT4SOHO, LLC 33 - 4th Street N, Suite 211 St. Petersburg, FL 33701-3806 CALL TOLL FREE: 877-IT4SOHO 877-484-7646 Phone 727-647-7646 Local 727-490-4394 Fax We have support plans for QMail! Links: -- [1] https://mail.a.com
[qmailtoaster] A rudimentary question for multi-domain hosting
Hi all, I run mail for 5 or 6 domains on my server. I have a few questions regarding multi-domain hosting 1. What is the appropriate entry for the /var/qmail/control/me file which I believe controls how qmail identifies itself for SMTP HELO/EHLO. 2. What should the PTR record for my IP indicate? Should it match the hostname listed in /var/qmail/control/me? 3. Is it normal for a server that identifies itself as mail.example.com to send mail for, say fr...@test.com. In other words, Is this an appropriate conversation? 220 READY EHLO mail.example.com OK MAIL FROM: fr...@test.com OK RECEIPT TO: b...@sample.net Is the mail server for sample.net going to care that a server which identifies itself as being mail.example.com is sending mail for fr...@test.com? I would imagine this is very common, but is this also not what spam often looks like? Thanks. Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: A rudimentary question for multi-domain hosting
Sorry about the hijack Eric. Won't do that again. One last question. Should the MX records for the other domains indicate the hostname that is in the me file or should they be a record for a host in their own domain that maps to my server ip? Ie should I have 5 domains all with identical MX entries? Sent from my iPhone On Apr 25, 2014, at 6:01 PM, Eric Shubert e...@shubes.net wrote: First, please don't hyjack threads by replying to an existing post and changing the subject. Start a new message instead. You can add the list address to your address book for convenience. On 04/25/2014 02:29 PM, Kelly Cobean wrote: Hi all, I run mail for 5 or 6 domains on my server. I have a few questions regarding multi-domain hosting 1. What is the appropriate entry for the /var/qmail/control/me file which I believe controls how qmail identifies itself for SMTP HELO/EHLO. Any one of your domains is ok. The host name should resolve in DNS, but it doesn't have be anything particular. 2. What should the PTR record for my IP indicate? Should it match the hostname listed in /var/qmail/control/me? That is best, although not required. There needs to be a PTR (rDNS) record for your IP address, and that PTR name must resolve to an IP address. That address doesn't necessarily need to match your host's IP address though, and the name of the PTR doesn't need to match anything in particular either. I makes sense if they do match though, and it may help deliverability. 3. Is it normal for a server that identifies itself as mail.example.com to send mail for, say fr...@test.com. In other words, Is this an appropriate conversation? 220 READY EHLO mail.example.com OK MAIL FROM: fr...@test.com OK RECEIPT TO: b...@sample.net There's no problem with that. Think of google, or any other service that hosts multiple domains. Is the mail server for sample.net going to care that a server which identifies itself as being mail.example.com is sending mail for fr...@test.com? I would imagine this is very common, but is this also not what spam often looks like? Yeah, it's pretty common. Spam may look like that too, but spam filters can't effectively use it without hitting a lot of legitimate email. -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: A rudimentary question for multi-domain hosting
Sent from my iPhone On Apr 25, 2014, at 6:08 PM, Eric Shubert e...@shubes.net wrote: On 04/25/2014 02:58 PM, Dan McAllister wrote: Whatever you decide to put into /var/qmail/control/me, just make sure its valid. - say you put mailhost.example22.com in there - First, make sure that mailhost.example22.com resolves to that host's IP address (either directly or via NAT) [ for example: 10.10.10.10 ] - Second, contact your ISP and make sure the PTR record for your IP [ 10.10.10.10 ] resolves to mailhost.example22.com Isn't 10.x a bad example here (given those are private addresses)? Shouldn't these all be public addresses we're talking about? Of course QMT can be behind a NATing router, but all IPs involved should refer to the public IP address which the router forwards to QMT. No? -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com Yeah, my server has a public ip on its interface. I got his point though. I'm a network engineer by trade so I'm kinda wingin' it when dealing with mail systems. :) Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] EZ-MLM issues with yahoo users sending to list with gmail members
If I'm way outside of scope here, please ignore my email. I thought since EZMLM is part of the QMT build, I'd ask. I have an EZMLM list that some yahoo users are members of. I also have some gmail users. When yahoo users send to the list, the gmail users aren't getting the emails. One of my users got a bounce back with the following, and I was wondering what, if anything, I can tweak in my config to overcome this (email addresses removed for privacy): Hi. This is the qmail-send program at mail.vipercrazy.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. user.remo...@gmail.com: User and password not set, continuing without authentication. user.remo...@gmail.com 74.125.196.26 failed after I sent the message. Remote host said: 550-5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.1 DMARC policy. Please contact administrator of yahoo.com domain if 550-5.7.1 this was a legitimate mail. Please visit 550-5.7.1 http://support.google.com/mail/answer/2451690 to learn about DMARC 550 5.7.1 initiative. 69si200255yhf.97 - gsmtp - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: EZ-MLM issues with yahoo users sending to list with gmail members
On 04/22/2014 12:30, Eric Shubert wrote: On 04/22/2014 07:39 AM, Kelly Cobean wrote: If I'm way outside of scope here, please ignore my email. I thought since EZMLM is part of the QMT build, I'd ask. I have an EZMLM list that some yahoo users are members of. I also have some gmail users. When yahoo users send to the list, the gmail users aren't getting the emails. One of my users got a bounce back with the following, and I was wondering what, if anything, I can tweak in my config to overcome this (email addresses removed for privacy): Hi. This is the qmail-send program at mail.vipercrazy.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. user.remo...@gmail.com: User and password not set, continuing without authentication. user.remo...@gmail.com 74.125.196.26 failed after I sent the message. Remote host said: 550-5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.1 DMARC policy. Please contact administrator of yahoo.com domain if 550-5.7.1 this was a legitimate mail. Please visit 550-5.7.1 http://support.google.com/mail/answer/2451690 to learn about DMARC 550 5.7.1 initiative. 69si200255yhf.97 - gsmtp - Dan or someone else might know more about this than me, but it appears to me that google is enforcing yahoo's DMARC policy, which apparently says that mail from yahoo isn't supposed to be coming from your ezmlm server. There's gotta some way for DMARC rules to allow for this. I'm guessing that ezmlm makes the outgoing messages appear to be coming from yahoo. Is there a configuration setting which would make them appear to be coming from the ezmlm list instead? I'm guessing this would bypass the DMARC check. Anyone else have thoughts on this? Yeah, my list server preserves the original senders email address when sending to the list, just like qmailtoaster-list does. I figure people won't know who an email is coming from if I don't. I'd change it if I have to, but preserving the original sender email is ideal. Upon some digging. http://www.mail-list.com/yahoo-dmarc-solution/?gclid=CJvT8s3U9L0CFe07OgodI3AAgQ Sigh. Freakin' Yahoo. Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] domain display issues in vqadmin
I have one domain in vqadmin that when I try to display the domain properties using view domain, I get a blank screen. All of my other domains display properly. If I try to view individual email accounts in the domain using show email account, that works fine. Has anyone run into this before or have any idea how to fix? Kelly
Re: [qmailtoaster] domain display issues in vqadmin
Eric/Tony, You guys are awesome. Thanks so much, that did the trick. Kelly On 04/07/2014 10:29, Eric Broch wrote: On 4/7/2014 7:25 AM, Kelly Cobean wrote: I have one domain in vqadmin that when I try to display the domain properties using view domain, I get a blank screen. All of my other domains display properly. If I try to view individual email accounts in the domain using show email account, that works fine. Has anyone run into this before or have any idea how to fix? Kelly Kelly, I did this: After entering the mysql database server software enter the following commands: mysql use vpopmail; mysql update dir_control set cur_users = 0 where domain = 'offending-domain.com' Eric - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] mail flow process
Hey all, Does anyone have a flow-chart showing how a message moves through the various QTP modules? It would really help when troubleshooting issues and I'm honestly very fuzzy on it all. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Help, I'm an open relay!!
I don't understand what's going on here, but somehow all of a sudden I am on the spamcop RBL. If I tail /var/log/qmail/smtp/current, I'm seeing a TON of emails getting relayed that are all .ru hosts and addresses. I've run every open relay test I could find and all of them say I'm good to go, but spamdyke says I'm accepting over 75000 emails a day and they're not hitting any of my inboxes. Can y'all help me diagnose and solve this? Here's a snippet of the current file: @4000533d52101655376c CHKUSER relaying rcpt: from fe...@782782.ru:kcob...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt 1dawmydgeaa...@prosoft-m.ru : client allowed to relay @4000533d521016554324 policy_check: local kcob...@vipercrazy.com - remote 1dawmydgeaa...@prosoft-m.ru (AUTHENTICATED SENDER) @4000533d52101655470c policy_check: policy allows transmission @4000533d52101703edfc CHKUSER accepted sender: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d521108b8a88c CHKUSER relaying rcpt: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt inf...@dvugadn.kht.ru : client allowed to relay @4000533d521108b8b444 policy_check: local bi...@vipercrazy.com - remote inf...@dvugadn.kht.ru (AUTHENTICATED SENDER) @4000533d521108b8b444 policy_check: policy allows transmission @4000533d52112c20499c simscan:[13710]:RELAYCLIENT:1.1458s:-:91.235.7.37:fe...@782782.ru:1dawmydgeaa...@prosoft-m.ru @4000533d52112cba283c spamdyke[13709]: ALLOWED from: fe...@782782.ru to: 1dawmydgeaa...@prosoft-m.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527623_qp_13732 @4000533d521139ada1f4 tcpserver: end 13709 status 0 @4000533d521139ada5dc tcpserver: status: 1/100 @4000533d5212129d193c simscan:[13718]:RELAYCLIENT:0.9592s:-:91.235.7.37:i...@3vlodke.ru:inf...@dvugadn.kht.ru @4000533d52121316601c spamdyke[13717]: ALLOWED from: i...@3vlodke.ru to: inf...@dvugadn.kht.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527624_qp_13752 @4000533d52121a62824c tcpserver: status: 2/100 @4000533d52121a628634 tcpserver: pid 13764 from 91.235.7.37 @4000533d52121a628634 tcpserver: ok 13764 www.novagunrunners.com:66.151.32.133:25 :91.235.7.37::64980 @4000533d5212201bdb34 tcpserver: end 13717 status 0 @4000533d5212201bdf1c tcpserver: status: 1/100 @4000533d521302016b8c tcpserver: status: 2/100 @4000533d521302017744 tcpserver: pid 13766 from 91.235.7.37 @4000533d521302017744 tcpserver: ok 13766 www.novagunrunners.com:66.151.32.133:25 :91.235.7.37::64990 @4000533d52132c0ba474 CHKUSER accepted sender: from pa...@143904.ru:kcob...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52133ae2b6f4 CHKUSER relaying rcpt: from pa...@143904.ru:kcob...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt 4-1696808-19797-20060901154637-v...@subscribe.ru : client allowed to relay @4000533d52133ae2c2ac policy_check: local kcob...@vipercrazy.com - remote 4-1696808-19797-20060901154637-v...@subscribe.ru (AUTHENTICATED SENDER) @4000533d52133ae2ca7c policy_check: policy allows transmission @4000533d521413dbfdf4 CHKUSER accepted sender: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52142423c32c simscan:[13765]:RELAYCLIENT:0.4157s:-:91.235.7.37:pa...@143904.ru:4-1696808-19797-20060901154637-v...@subscribe.ru @4000533d521424f524bc spamdyke[13764]: ALLOWED from: pa...@143904.ru to: 4-1696808-19797-20060901154637-v...@subscribe.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527626_qp_13785 @4000533d5214285cb1ec CHKUSER relaying rcpt: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt pavel_ma...@tut.by : client allowed to relay @4000533d5214285cb9bc policy_check: local bi...@vipercrazy.com - remote pavel_ma...@tut.by (AUTHENTICATED SENDER) @4000533d5214285cbda4 policy_check: policy allows transmission @4000533d5214317e9204 tcpserver: end 13764 status 0 @4000533d5214317e95ec tcpserver: status: 1/100 @4000533d521513228964 tcpserver: status: 2/100 @4000533d521513228d4c tcpserver: pid 13811 from 91.235.7.37 @4000533d521513229134 tcpserver: ok 13811 www.novagunrunners.com:66.151.32.133:25 :91.235.7.37::65030 @4000533d52152188a204 simscan:[13767]:RELAYCLIENT:0.5571s:-:91.235.7.37:o...@7-design.ru:pavel_ma...@tut.by @4000533d5215223220a4 spamdyke[13766]: ALLOWED from: o...@7-design.ru to: pavel_ma...@tut.by origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527627_qp_13803 @4000533d52152ef946b4 tcpserver: end 13766 status 0
[qmailtoaster] Re: Help, I'm an open relay!!
I don't understand what's going on here, but somehow all of a sudden I am on the spamcop RBL. If I tail /var/log/qmail/smtp/current, I'm seeing a TON of emails getting relayed that are all .ru hosts and addresses. I've run every open relay test I could find and all of them say I'm good to go, but spamdyke says I'm accepting over 75000 emails a day and they're not hitting any of my inboxes. Can y'all help me diagnose and solve this? Here's a snippet of the current file: @4000533d52101655376c CHKUSER relaying rcpt: from fe...@782782.ru:kcob...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt 1dawmydgeaa...@prosoft-m.ru : client allowed to relay @4000533d521016554324 policy_check: local kcob...@vipercrazy.com - remote 1dawmydgeaa...@prosoft-m.ru (AUTHENTICATED SENDER) @4000533d52101655470c policy_check: policy allows transmission @4000533d52101703edfc CHKUSER accepted sender: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d521108b8a88c CHKUSER relaying rcpt: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt inf...@dvugadn.kht.ru : client allowed to relay @4000533d521108b8b444 policy_check: local bi...@vipercrazy.com - remote inf...@dvugadn.kht.ru (AUTHENTICATED SENDER) @4000533d521108b8b444 policy_check: policy allows transmission @4000533d52112c20499c simscan:[13710]:RELAYCLIENT:1.1458s:-:91.235.7.37:fe...@782782.ru:1dawmydgeaa...@prosoft-m.ru @4000533d52112cba283c spamdyke[13709]: ALLOWED from: fe...@782782.ru to: 1dawmydgeaa...@prosoft-m.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527623_qp_13732 @4000533d521139ada1f4 tcpserver: end 13709 status 0 @4000533d521139ada5dc tcpserver: status: 1/100 @4000533d5212129d193c simscan:[13718]:RELAYCLIENT:0.9592s:-:91.235.7.37:i...@3vlodke.ru:inf...@dvugadn.kht.ru @4000533d52121316601c spamdyke[13717]: ALLOWED from: i...@3vlodke.ru to: inf...@dvugadn.kht.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527624_qp_13752 @4000533d52121a62824c tcpserver: status: 2/100 @4000533d52121a628634 tcpserver: pid 13764 from 91.235.7.37 @4000533d52121a628634 tcpserver: ok 13764 www.novagunrunners.com:66.151.32.133:25 :91.235.7.37::64980 @4000533d5212201bdb34 tcpserver: end 13717 status 0 @4000533d5212201bdf1c tcpserver: status: 1/100 @4000533d521302016b8c tcpserver: status: 2/100 @4000533d521302017744 tcpserver: pid 13766 from 91.235.7.37 @4000533d521302017744 tcpserver: ok 13766 www.novagunrunners.com:66.151.32.133:25 :91.235.7.37::64990 @4000533d52132c0ba474 CHKUSER accepted sender: from pa...@143904.ru:kcob...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52133ae2b6f4 CHKUSER relaying rcpt: from pa...@143904.ru:kcob...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt 4-1696808-19797-20060901154637-v...@subscribe.ru : client allowed to relay @4000533d52133ae2c2ac policy_check: local kcob...@vipercrazy.com - remote 4-1696808-19797-20060901154637-v...@subscribe.ru (AUTHENTICATED SENDER) @4000533d52133ae2ca7c policy_check: policy allows transmission @4000533d521413dbfdf4 CHKUSER accepted sender: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52142423c32c simscan:[13765]:RELAYCLIENT:0.4157s:-:91.235.7.37:pa...@143904.ru:4-1696808-19797-20060901154637-v...@subscribe.ru @4000533d521424f524bc spamdyke[13764]: ALLOWED from: pa...@143904.ru to: 4-1696808-19797-20060901154637-v...@subscribe.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527626_qp_13785 @4000533d5214285cb1ec CHKUSER relaying rcpt: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt pavel_ma...@tut.by : client allowed to relay @4000533d5214285cb9bc policy_check: local bi...@vipercrazy.com - remote pavel_ma...@tut.by (AUTHENTICATED SENDER) @4000533d5214285cbda4 policy_check: policy allows transmission @4000533d5214317e9204 tcpserver: end 13764 status 0 @4000533d5214317e95ec tcpserver: status: 1/100 @4000533d521513228964 tcpserver: status: 2/100 @4000533d521513228d4c tcpserver: pid 13811 from 91.235.7.37 @4000533d521513229134 tcpserver: ok 13811 www.novagunrunners.com:66.151.32.133:25 :91.235.7.37::65030 @4000533d52152188a204 simscan:[13767]:RELAYCLIENT:0.5571s:-:91.235.7.37:o...@7-design.ru:pavel_ma...@tut.by @4000533d5215223220a4 spamdyke[13766]: ALLOWED from: o...@7-design.ru to: pavel_ma...@tut.by origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527627_qp_13803 @4000533d52152ef946b4 tcpserver: end 13766 status 0
Re: [qmailtoaster] Help, I'm an open relay!!
Hey Sebastian, I thought leaked password as well at first, but there are at least two accounts I see under auth: mine and one other. I suppose it's possible that they were guessed/leaked, but it's awfully coincidental that it's two accounts in the same domain on a server running at least 6 domains. I only saw two IP addresses doing all this spamming, so I put those in iptables and things seem quiet for now. I'll change the passwords on those two accounts as well. I'm really glad spamcop has an easy way to delist a server once an issue is fixed. Thanks. Kelly On 04/03/2014 11:42, Sebastian Grewe wrote: Have you checked for hijacked accounts? Looks like all mails are sent from a single account and IP. Most likely a guessed/leaked password. Cheers, Sebastian On 03.04.2014, at 14:30, Kelly Cobean kcob...@vipercrazy.com wrote: I don't understand what's going on here, but somehow all of a sudden I am on the spamcop RBL. If I tail /var/log/qmail/smtp/current, I'm seeing a TON of emails getting relayed that are all .ru hosts and addresses. I've run every open relay test I could find and all of them say I'm good to go, but spamdyke says I'm accepting over 75000 emails a day and they're not hitting any of my inboxes. Can y'all help me diagnose and solve this? Here's a snippet of the current file: @4000533d52101655376c CHKUSER relaying rcpt: from fe...@782782.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 1dawmydgeaa...@prosoft-m.ru : client allowed to relay @4000533d521016554324 policy_check: local kcob...@vipercrazy.com - remote 1dawmydgeaa...@prosoft-m.ru (AUTHENTICATED SENDER) @4000533d52101655470c policy_check: policy allows transmission @4000533d52101703edfc CHKUSER accepted sender: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d521108b8a88c CHKUSER relaying rcpt: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt inf...@dvugadn.kht.ru : client allowed to relay @4000533d521108b8b444 policy_check: local bi...@vipercrazy.com - remote inf...@dvugadn.kht.ru (AUTHENTICATED SENDER) @4000533d521108b8b444 policy_check: policy allows transmission @4000533d52112c20499c simscan:[13710]:RELAYCLIENT:1.1458s:-:91.235.7.37:fe...@782782.ru:1dawmydgeaa...@prosoft-m.ru @4000533d52112cba283c spamdyke[13709]: ALLOWED from: fe...@782782.ru to: 1dawmydgeaa...@prosoft-m.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527623_qp_13732 @4000533d521139ada1f4 tcpserver: end 13709 status 0 @4000533d521139ada5dc tcpserver: status: 1/100 @4000533d5212129d193c simscan:[13718]:RELAYCLIENT:0.9592s:-:91.235.7.37:i...@3vlodke.ru:inf...@dvugadn.kht.ru [2] @4000533d52121316601c spamdyke[13717]: ALLOWED from: i...@3vlodke.ru to: inf...@dvugadn.kht.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527624_qp_13752 @4000533d52121a62824c tcpserver: status: 2/100 @4000533d52121a628634 tcpserver: pid 13764 from 91.235.7.37 @4000533d52121a628634 tcpserver: ok 13764 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64980 @4000533d5212201bdb34 tcpserver: end 13717 status 0 @4000533d5212201bdf1c tcpserver: status: 1/100 @4000533d521302016b8c tcpserver: status: 2/100 @4000533d521302017744 tcpserver: pid 13766 from 91.235.7.37 @4000533d521302017744 tcpserver: ok 13766 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64990 @4000533d52132c0ba474 CHKUSER accepted sender: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52133ae2b6f4 CHKUSER relaying rcpt: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 4-1696808-19797-20060901154637-v...@subscribe.ru : client allowed to relay @4000533d52133ae2c2ac policy_check: local kcob...@vipercrazy.com - remote 4-1696808-19797-20060901154637-v...@subscribe.ru (AUTHENTICATED SENDER) @4000533d52133ae2ca7c policy_check: policy allows transmission @4000533d521413dbfdf4 CHKUSER accepted sender: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52142423c32c simscan:[13765]:RELAYCLIENT:0.4157s:-:91.235.7.37:pa...@143904.ru:4-1696808-19797-20060901154637-v...@subscribe.ru @4000533d521424f524bc spamdyke[13764]: ALLOWED from: pa...@143904.ru to: 4-1696808-19797-20060901154637-v...@subscribe.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527626_qp_13785 @4000533d5214285cb1ec CHKUSER relaying rcpt: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt pavel_ma...@tut.by : client allowed to relay
Re: [qmailtoaster] Help, I'm an open relay!!
Ok, I'm gonna ask a real dumb question. When I ran squirrel mail and the old QmailRocks distro (yep, LONG time ago), I had a squirrelmail plugin to allow people to change passwords via the squirrel. Now I'm running QTP and Roundcube. I still have squirrelmail running, bu the password change results in a connection refused error. How the heck do users change their passwords in QTP? Do I have to do it for them using qmailadmin? Thanks. Kelly On 04/03/2014 11:42, Sebastian Grewe wrote: Have you checked for hijacked accounts? Looks like all mails are sent from a single account and IP. Most likely a guessed/leaked password. Cheers, Sebastian On 03.04.2014, at 14:30, Kelly Cobean kcob...@vipercrazy.com wrote: I don't understand what's going on here, but somehow all of a sudden I am on the spamcop RBL. If I tail /var/log/qmail/smtp/current, I'm seeing a TON of emails getting relayed that are all .ru hosts and addresses. I've run every open relay test I could find and all of them say I'm good to go, but spamdyke says I'm accepting over 75000 emails a day and they're not hitting any of my inboxes. Can y'all help me diagnose and solve this? Here's a snippet of the current file: @4000533d52101655376c CHKUSER relaying rcpt: from fe...@782782.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 1dawmydgeaa...@prosoft-m.ru : client allowed to relay @4000533d521016554324 policy_check: local kcob...@vipercrazy.com - remote 1dawmydgeaa...@prosoft-m.ru (AUTHENTICATED SENDER) @4000533d52101655470c policy_check: policy allows transmission @4000533d52101703edfc CHKUSER accepted sender: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d521108b8a88c CHKUSER relaying rcpt: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt inf...@dvugadn.kht.ru : client allowed to relay @4000533d521108b8b444 policy_check: local bi...@vipercrazy.com - remote inf...@dvugadn.kht.ru (AUTHENTICATED SENDER) @4000533d521108b8b444 policy_check: policy allows transmission @4000533d52112c20499c simscan:[13710]:RELAYCLIENT:1.1458s:-:91.235.7.37:fe...@782782.ru:1dawmydgeaa...@prosoft-m.ru @4000533d52112cba283c spamdyke[13709]: ALLOWED from: fe...@782782.ru to: 1dawmydgeaa...@prosoft-m.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527623_qp_13732 @4000533d521139ada1f4 tcpserver: end 13709 status 0 @4000533d521139ada5dc tcpserver: status: 1/100 @4000533d5212129d193c simscan:[13718]:RELAYCLIENT:0.9592s:-:91.235.7.37:i...@3vlodke.ru:inf...@dvugadn.kht.ru [2] @4000533d52121316601c spamdyke[13717]: ALLOWED from: i...@3vlodke.ru to: inf...@dvugadn.kht.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527624_qp_13752 @4000533d52121a62824c tcpserver: status: 2/100 @4000533d52121a628634 tcpserver: pid 13764 from 91.235.7.37 @4000533d52121a628634 tcpserver: ok 13764 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64980 @4000533d5212201bdb34 tcpserver: end 13717 status 0 @4000533d5212201bdf1c tcpserver: status: 1/100 @4000533d521302016b8c tcpserver: status: 2/100 @4000533d521302017744 tcpserver: pid 13766 from 91.235.7.37 @4000533d521302017744 tcpserver: ok 13766 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64990 @4000533d52132c0ba474 CHKUSER accepted sender: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52133ae2b6f4 CHKUSER relaying rcpt: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 4-1696808-19797-20060901154637-v...@subscribe.ru : client allowed to relay @4000533d52133ae2c2ac policy_check: local kcob...@vipercrazy.com - remote 4-1696808-19797-20060901154637-v...@subscribe.ru (AUTHENTICATED SENDER) @4000533d52133ae2ca7c policy_check: policy allows transmission @4000533d521413dbfdf4 CHKUSER accepted sender: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52142423c32c simscan:[13765]:RELAYCLIENT:0.4157s:-:91.235.7.37:pa...@143904.ru:4-1696808-19797-20060901154637-v...@subscribe.ru @4000533d521424f524bc spamdyke[13764]: ALLOWED from: pa...@143904.ru to: 4-1696808-19797-20060901154637-v...@subscribe.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527626_qp_13785 @4000533d5214285cb1ec CHKUSER relaying rcpt: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt pavel_ma...@tut.by : client allowed to relay @4000533d5214285cb9bc policy_check: local bi...@vipercrazy.com - remote pavel_ma...@tut.by (AUTHENTICATED SENDER
RE: [qmailtoaster] Help, I'm an open relay!!
Yes, very easily hacked. I'm glad vqadmin will show clear text passwords. I've changed the password and notified the user. Thanks. Kelly On 04/03/2014 12:46, Helmut Fritz wrote: I would shut down bi...@vipercrazy.com for now and see if the relaying stops. Do you know if that was an easily hacked password? FROM: Sebastian Grewe [mailto:sebast...@grewe.ca] SENT: Thursday, April 03, 2014 8:42 AM TO: qmailtoaster-list@qmailtoaster.com SUBJECT: Re: [qmailtoaster] Help, I'm an open relay!! Have you checked for hijacked accounts? Looks like all mails are sent from a single account and IP. Most likely a guessed/leaked password. Cheers, Sebastian On 03.04.2014, at 14:30, Kelly Cobean kcob...@vipercrazy.com wrote: I don't understand what's going on here, but somehow all of a sudden I am on the spamcop RBL. If I tail /var/log/qmail/smtp/current, I'm seeing a TON of emails getting relayed that are all .ru hosts and addresses. I've run every open relay test I could find and all of them say I'm good to go, but spamdyke says I'm accepting over 75000 emails a day and they're not hitting any of my inboxes. Can y'all help me diagnose and solve this? Here's a snippet of the current file: @4000533d52101655376c CHKUSER relaying rcpt: from fe...@782782.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 1dawmydgeaa...@prosoft-m.ru : client allowed to relay @4000533d521016554324 policy_check: local kcob...@vipercrazy.com - remote 1dawmydgeaa...@prosoft-m.ru (AUTHENTICATED SENDER) @4000533d52101655470c policy_check: policy allows transmission @4000533d52101703edfc CHKUSER accepted sender: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d521108b8a88c CHKUSER relaying rcpt: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt inf...@dvugadn.kht.ru : client allowed to relay @4000533d521108b8b444 policy_check: local bi...@vipercrazy.com - remote inf...@dvugadn.kht.ru (AUTHENTICATED SENDER) @4000533d521108b8b444 policy_check: policy allows transmission @4000533d52112c20499c simscan:[13710]:RELAYCLIENT:1.1458s:-:91.235.7.37:fe...@782782.ru:1dawmydgeaa...@prosoft-m.ru @4000533d52112cba283c spamdyke[13709]: ALLOWED from: fe...@782782.ru to: 1dawmydgeaa...@prosoft-m.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527623_qp_13732 @4000533d521139ada1f4 tcpserver: end 13709 status 0 @4000533d521139ada5dc tcpserver: status: 1/100 @4000533d5212129d193c simscan:[13718]:RELAYCLIENT:0.9592s:-:91.235.7.37:i...@3vlodke.ru:inf...@dvugadn.kht.ru [2] @4000533d52121316601c spamdyke[13717]: ALLOWED from: i...@3vlodke.ru to: inf...@dvugadn.kht.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527624_qp_13752 @4000533d52121a62824c tcpserver: status: 2/100 @4000533d52121a628634 tcpserver: pid 13764 from 91.235.7.37 @4000533d52121a628634 tcpserver: ok 13764 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64980 @4000533d5212201bdb34 tcpserver: end 13717 status 0 @4000533d5212201bdf1c tcpserver: status: 1/100 @4000533d521302016b8c tcpserver: status: 2/100 @4000533d521302017744 tcpserver: pid 13766 from 91.235.7.37 @4000533d521302017744 tcpserver: ok 13766 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64990 @4000533d52132c0ba474 CHKUSER accepted sender: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52133ae2b6f4 CHKUSER relaying rcpt: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 4-1696808-19797-20060901154637-v...@subscribe.ru : client allowed to relay @4000533d52133ae2c2ac policy_check: local kcob...@vipercrazy.com - remote 4-1696808-19797-20060901154637-v...@subscribe.ru (AUTHENTICATED SENDER) @4000533d52133ae2ca7c policy_check: policy allows transmission @4000533d521413dbfdf4 CHKUSER accepted sender: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52142423c32c simscan:[13765]:RELAYCLIENT:0.4157s:-:91.235.7.37:pa...@143904.ru:4-1696808-19797-20060901154637-v...@subscribe.ru @4000533d521424f524bc spamdyke[13764]: ALLOWED from: pa...@143904.ru to: 4-1696808-19797-20060901154637-v...@subscribe.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527626_qp_13785 @4000533d5214285cb1ec CHKUSER relaying rcpt: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt pavel_ma...@tut.by : client allowed to relay @4000533d5214285cb9bc policy_check: local bi...@vipercrazy.com - remote pavel_ma...@tut.by (AUTHENTICATED
Re: [qmailtoaster] Help, I'm an open relay!!
Wow...good call! That sucker was FULL. Thanks! Kelly On 04/03/2014 15:10, LHTek wrote: Make sure you clear your qmail cue after you shut the account(s) down. Been bitten by that one more than once. - FROM: Kelly Cobean kcob...@vipercrazy.com TO: qmailtoaster-list@qmailtoaster.com SENT: Thursday, April 3, 2014 11:13 AM SUBJECT: Re: [qmailtoaster] Help, I'm an open relay!! Hey Sebastian, I thought leaked password as well at first, but there are at least two accounts I see under auth: mine and one other. I suppose it's possible that they were guessed/leaked, but it's awfully coincidental that it's two accounts in the same domain on a server running at least 6 domains. I only saw two IP addresses doing all this spamming, so I put those in iptables and things seem quiet for now. I'll change the passwords on those two accounts as well. I'm really glad spamcop has an easy way to delist a server once an issue is fixed. Thanks. Kelly On 04/03/2014 11:42, Sebastian Grewe wrote: Have you checked for hijacked accounts? Looks like all mails are sent from a single account and IP. Most likely a guessed/leaked password. Cheers, Sebastian On 03.04.2014, at 14:30, Kelly Cobean kcob...@vipercrazy.com wrote: I don't understand what's going on here, but somehow all of a sudden I am on the spamcop RBL. If I tail /var/log/qmail/smtp/current, I'm seeing a TON of emails getting relayed that are all .ru hosts and addresses. I've run every open relay test I could find and all of them say I'm good to go, but spamdyke says I'm accepting over 75000 emails a day and they're not hitting any of my inboxes. Can y'all help me diagnose and solve this? Here's a snippet of the current file: @4000533d52101655376c CHKUSER relaying rcpt: from fe...@782782.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 1dawmydgeaa...@prosoft-m.ru : client allowed to relay @4000533d521016554324 policy_check: local kcob...@vipercrazy.com - remote 1dawmydgeaa...@prosoft-m.ru (AUTHENTICATED SENDER) @4000533d52101655470c policy_check: policy allows transmission @4000533d52101703edfc CHKUSER accepted sender: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d521108b8a88c CHKUSER relaying rcpt: from i...@3vlodke.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt inf...@dvugadn.kht.ru : client allowed to relay @4000533d521108b8b444 policy_check: local bi...@vipercrazy.com - remote inf...@dvugadn.kht.ru (AUTHENTICATED SENDER) @4000533d521108b8b444 policy_check: policy allows transmission @4000533d52112c20499c simscan:[13710]:RELAYCLIENT:1.1458s:-:91.235.7.37:fe...@782782.ru:1dawmydgeaa...@prosoft-m.ru @4000533d52112cba283c spamdyke[13709]: ALLOWED from: fe...@782782.ru to: 1dawmydgeaa...@prosoft-m.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: kcob...@vipercrazy.com encryption: (none) reason: 250_ok_1396527623_qp_13732 @4000533d521139ada1f4 tcpserver: end 13709 status 0 @4000533d521139ada5dc tcpserver: status: 1/100 @4000533d5212129d193c simscan:[13718]:RELAYCLIENT:0.9592s:-:91.235.7.37:i...@3vlodke.ru:inf...@dvugadn.kht.ru [2] @4000533d52121316601c spamdyke[13717]: ALLOWED from: i...@3vlodke.ru to: inf...@dvugadn.kht.ru origin_ip: 91.235.7.37 origin_rdns: (unknown) auth: bi...@vipercrazy.com encryption: (none) reason: 250_ok_1396527624_qp_13752 @4000533d52121a62824c tcpserver: status: 2/100 @4000533d52121a628634 tcpserver: pid 13764 from 91.235.7.37 @4000533d52121a628634 tcpserver: ok 13764 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64980 @4000533d5212201bdb34 tcpserver: end 13717 status 0 @4000533d5212201bdf1c tcpserver: status: 1/100 @4000533d521302016b8c tcpserver: status: 2/100 @4000533d521302017744 tcpserver: pid 13766 from 91.235.7.37 @4000533d521302017744 tcpserver: ok 13766 www.novagunrunners.com [3]:66.151.32.133:25 :91.235.7.37::64990 @4000533d52132c0ba474 CHKUSER accepted sender: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52133ae2b6f4 CHKUSER relaying rcpt: from pa...@143904.ru:kcob...@vipercrazy.com [1]: remote 91.235.7.37:unknown:91.235.7.37 rcpt 4-1696808-19797-20060901154637-v...@subscribe.ru : client allowed to relay @4000533d52133ae2c2ac policy_check: local kcob...@vipercrazy.com - remote 4-1696808-19797-20060901154637-v...@subscribe.ru (AUTHENTICATED SENDER) @4000533d52133ae2ca7c policy_check: policy allows transmission @4000533d521413dbfdf4 CHKUSER accepted sender: from o...@7-design.ru:bi...@vipercrazy.com: remote 91.235.7.37:unknown:91.235.7.37 rcpt : sender accepted @4000533d52142423c32c simscan:[13765]:RELAYCLIENT:0.4157s:-:91.235.7.37:pa...@143904.ru:4-1696808-19797-20060901154637-v...@subscribe.ru
[qmailtoaster] Windows 8 mail client and courier-IMAP SSL woes
I'm trying to set up my first Windows 8 laptop and the email client won't allow me to set up my email because it says I need to install an SSL certificate because I'm using SSL for the IMAP connection. I'm using the cert that got installed when I installed QMT on the server. Anyone have any insights on how to make this work? - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] mailing list
That's what qmailadmin should do. You can manage lists, accounts, robots all from qmailadmin. On 07/17/2013 14:48, David wrote: Ok, Is there a web/PHP/mysql system out there to add and remove customers from the list from an admin side? So for example if we have a customer who is no longer on our network we can just simply remove them, Thanks Dave On 07/17/2013 11:28 AM, David wrote: Hi All, I am wanting to configure a mailing list on our toaster box for our customer base and I need a good opt out web interface. The list will be private only to our customers and I want to give them an opt out link if they want off the list. Any ideas,thoughts or suggestions welcome. thanks Dave - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
RE: [qmailtoaster] mailing list
vqadmin is for adding/removing/managing domains. Adding and removing customers from an EZ-MLM list is done using qmailadmin. At least that's how I do it in my QTP install. On 07/17/2013 14:58, mattias wrote: no! think yo meen vqadmin or what is it have for name - FROM: Kelly Cobean [mailto:kcob...@vipercrazy.com] SENT: den 17 juli 2013 20:56 TO: qmailtoaster-list@qmailtoaster.com SUBJECT: Re: [qmailtoaster] mailing list That's what qmailadmin should do. You can manage lists, accounts, robots all from qmailadmin. On 07/17/2013 14:48, David wrote: Ok, Is there a web/PHP/mysql system out there to add and remove customers from the list from an admin side? So for example if we have a customer who is no longer on our network we can just simply remove them, Thanks Dave On 07/17/2013 11:28 AM, David wrote: Hi All, I am wanting to configure a mailing list on our toaster box for our customer base and I need a good opt out web interface. The list will be private only to our customers and I want to give them an opt out link if they want off the list. Any ideas,thoughts or suggestions welcome. thanks Dave - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Flushing the queue and one other question
I need to flush my qmail queue and for the life of me can't remember how. I looked around online and can't find anything newer than about 2004 in regards to this. Is there a good way using a stock QTP install or do I need additional tools? Also, when checking mail on my iOS device, I am seeing a message dated 12/31/69 that has no message content and I can't delete it. Is that corruption in my inbox? Any ideas how to fix this? Thanks
Re: [qmailtoaster] Re: Squirrelmail alternatives? Looking for recs
Using someone else's iPad perhaps? Only reason I can think of. Sent from my iPad On Dec 6, 2012, at 9:35 PM, Eric Shubert e...@shubes.net wrote: Why wouldn't you use the native mail program on an Ipad? I use a native mail program on any mobile device. (K-9 mail on android) -- -Eric 'shubes' On 12/06/2012 06:52 PM, Edwin Casimero wrote: Roundcube sucks on Ipad. Looks good on desktops and laptops. I use both. On Friday, 07 December, 2012 01:50 AM, Sebastian Grewe wrote: PS: when it comes to auto responses and password changes I have not been using Roundcube though. I would love to run it in Roundcube if that would be possible - maybe others have experience with that already? Cheers, Sebastian On 06.12.2012, at 18:44, Sebastian Grewe sebast...@grewe.ca wrote: Hey Diana, I am using RoundCube myself and I am very happy with it. It is exactly what you said: A Webmailer without all the bells and whistles others offer. Installation is easy and straight forward. You can try it out on any LAMP host and point it towards your IMAP/SMTP host to try it out. Or I make a quick account for you to see the UI ;-) Sidenote: I have written an Opscode Chef cookbook for it too. Cheers, Sebastian On 06.12.2012, at 18:24, Diana Calder dcal...@essexcountylibrary.ca wrote: Anyone using something other than Squirrelmail for webmail with Qmailtoaster? I'm working my way through researching the options listed in the Wiki but I'd like to get some feedback from someone who's actually using one of the alternative webmail packages. So far, it looks like atmail is gone (the free community version, at least), and AfterLogic lite, eGroupware, Horde, and RoundCube all look like they're worth taking a deeper look at. I'd prefer something that looks a little less dated than Squirrelmail and that has a good mobile interface. Our Intranet is a hosted Noodle instance, so I'm not really interested in extra bells and whistles like calendars and such - just good solid email features like a decent address book (though a nice shared one in addition to personal ones would be nice), the ability to set a vacation response, basic filtering, and allowing individual users to change their password. eGroupware is probably overkill for our needs and even Horde may be a little over the top - but they're also the two nicest looking. I'll be continuing to research but some helpful comments from the Qmailtoaster community would be greatly appreciated. Hoping for some good recommendations, Diana -- Best regards, Diana mailto:dcal...@essexcountylibrary.ca - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] QTP-newmodel and webmail in https
Hi all, I need a small indication of the scritp QTP-newmodel. I installed qmailtoaster but the webmail is functional only in http. if I type https://ipserver I get the welcome page of apache my question is this: scritp QTP-newmodel also automatically configures https webmail? if not, where can I get the info about? thanks -- Hi Giuseppe, The QTP configuration only includes configuration for http. Assuming you have a valid certificate for your webmail host, you can reference the Apache docs for setting up HTTPS for your server. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: DK problem
Sounds like this has more to do with the volume and or content of messages hitting the yahoo servers than with DK. If you read the link (http://help.yahoo.com/kb/index?page=contenty=PROD_MAIL_MLlocale=en_USid=SLN3436impressions=true) they are recommending that you inspect you mail outflow to see if someone is spamming from one of your accounts. Perhaps someone has had an account compromised? I'd look at your logs to see if one particular user is sending an inordinate amount of mail. Dear friends, I am facing the same problem with DK. Says all messages from my servers are permanently deferred. (see the copy of the bounce). What surprises me is why this problem is arising suddenly - my server is up for the past 3 years or more. This happens to the mails sent to yahoomail at present that too for the past 4-5 days. I have even disabled DK as per the advise given by Eric Shubert. It is not working. What can be done? Pl. advise. The bounce message: **  Hi. This is the qmail-send program at geophy.ngri.res.in. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. grsg...@yahoo.com: Connected to 66.94.238.147 but greeting failed. Remote host said: 421 4.7.1 [TS03] All messages from 203.153.42.81 will be permanently deferred; Retrying will NOT succeed. See http://postmaster.yahoo.com/421-ts03.html I'm not going to try again; this message has been in the queue too long. --- Below this line is a copy of the message. Return-Path: grsg...@ngri.res.in Received: (qmail 10679 invoked by uid 89); 15 Oct 2012 08:26:31 - Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=private; d=ngri.res.in; b=k2GRc7rechwTUy3452VnNHxJj0/tXM8E79DEmmCAWMKvTRhz5WLomQLqJsPGBPBB; Received: from unknown (HELO ngri.res.in) (127.0.0.1) by geophy.ngri.res.in with SMTP; 15 Oct 2012 08:26:31 - * Mails to gmail are going fine. ---seshagiri - Original Message - From: Eric Shubert e...@shubes.net To: qmailtoaster-list@qmailtoaster.com Cc: Sent: Thursday, October 11, 2012 1:43 AM Subject: [qmailtoaster] Re: DK problem On 10/10/2012 12:43 PM, Aleksander PodsiadÅy wrote: Sometimes there is the problem with domainkeys on this mailing list: 8-- Subject: failure notice Hi. This is the qmail-send program at mail.qmailtoaster.com. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. a...@mniow.pl: User and password not set, continuing without authentication. a...@mniow.pl 194.181.132.129 failed after I sent the message. Remote host said: 554 DomainKeys verify status: bad key   (#5.3.0) [...] Here are the message numbers:   13393 --- Enclosed is a copy of the bounce message I received. 8-- EOT DK is (and has been for some time) disabled on mail.qmailtoaster.com. QMT hosts with DK enabled occasionally have a problem sending to other QMT hosts, the symptom of which I've seen in the past as an error signing rejection when the host is receiving (not supposed to be signing) a message. I haven't seen the bad key error before in this situation, but it appears to be the opposite, where it should be signing and is checking instead. I consider DK on QMT to be presently broken, and disable it on my QMT hosts. Hopefully one day we'll get DKIM integrated into the stock QMT. To disable DK: # cd /var/qmail/bin # ln -sf qmail-queue.orig qmail-queue -- -Eric 'shubes' - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Processing SPAM
Hi guys, I was wondering how folks who use QT with Squirrelmail (i.e. a client that doesn't do client-side message processing) are dealing with messages flagged as SPAM by SA. I'd like to have SPAM marked messages moved to a spam folder, and I need to figure out how to do this on a per user basis. Does anyone have advice on how I'd do that? Thank you! Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Very Slow Server
Hi Mike, A couple of things I would try: 1. Have you tested DNS via DIG/NSLOOKUP to see if requests against authoritative servers are coming back in a timely fashion? 2. Can you try pointing your server to an external DNS server (8.8.8.8 is a favorite) to see if that alleviates the problem? Anything in the DJBDNS server logs to indicate timeout or other issues? Having a problem with a very slow server. I updated it about three weeks ago to the latest version of qmailtoaster. Everything was running fine until last week. I had made a change to our dns server so I thought that might be the problem. A day later I had a very difficult time getting into the server through ssh. I ended up turning off dns lookup for ssh and it seemed to work fine again. When I ping a dns name, it takes over twice as long to start the ping whereas the ip address will ping right away. The result of this dns issue is slowing down the network traffic. Keep in mind that this server has been running for over two years without issues. I checked the memory, cpu and hard drive usage. Everything checks out fine. I don't know why it just now started having problems. I have djbdns running a dnscache server on the loop back. I also have two other dns servers running tinydns that maintain my domain. Any suggestions would be great. Thanks, Mike - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Squirrelmail very slow!!!!
Message storage in NFS mount on main serversounds like where I'd be looking given that the web server is 99.3% idle. Have you tested NFS performance or looked at the system resource utilization on the main server? Hi guys, Thanks for help. I'm use a dedicated server for webmail, the messages storage are in NFS with main server. The apache doesnt show any error. So, there are my logs. Command 'top' Cpu(s): 0.2%us, 0.2%sy, 0.0%ni, 99.3%id, 0.2%wa, 0.0%hi, 0.2%si, 0.0%st Mem: 2075264k total, 2020436k used,54828k free,18168k buffers Swap: 4128760k total, 44k used, 4128716k free, 1458720k cached Thanks for support Em 06-09-2012 14:37, Gilbert T. Gutierrez, Jr. escreveu: Bom Dia Kalz, Several things... 1. What is the load on your server? 2. Are you seeing anything in logs? 3. Is this with every mailbox or with a specific mailbox? If you can provide more details, someone can help you. The issue could be any number of things. Gilbert On 9/5/2012 1:02 PM, Kalil Costa - Brasilsite wrote: Hi guys, My webmail is very very slow, at time I have waited 40 / 70 secs to open the main box. SMTP, POP3 and IMAP works fine. I use the last version of qmailtoaster (07/31/2011) Someone knows this issue ? Thanks a lot. Kalz - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] problems last version vqadmin 2.3.7 (error invalid language file)
Hi Pablo, Are you using Chrome by chance? http://serverfault.com/questions/157495/vqadmin-invalid-language-file-with-google-chrome hello friends, update the latest packages including vqadmin qmailtoaster 2.3.7 but when entering the panel I get the error invalid language file and I have no access to manage my domains. anyone know how this problem is fixed? I use Centos 5.8 64 bit Best regards Pablo - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] problems last version vqadmin 2.3.7 (error invalid language file)
Hi Pablo, It looks like a language file issue. What language spec is your browser passing to the server? Hi Kelly, I do not use chrome, use firefox version 15.0, you can fix it? best regards, Pablo 2012/9/4 Kelly Cobean kcob...@vipercrazy.com: Hi Pablo, Are you using Chrome by chance? http://serverfault.com/questions/157495/vqadmin-invalid-language-file-with-google-chrome hello friends, update the latest packages including vqadmin qmailtoaster 2.3.7 but when entering the panel I get the error invalid language file and I have no access to manage my domains. anyone know how this problem is fixed? I use Centos 5.8 64 bit Best regards Pablo - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Help about update QMT-ClamAV
Hi guys, I need some help, talking about updating the ClamAV, performed a successful update to ClamAV to ver. ClamAV 0.97.5 /# clamd -V/ but keep email header visible clamav: 0.97.3 : ( The update is performed by Stable Packages from the main gate QMT and all service restarted, but email header stands / 0.97.3 / Best regrads, Nikolay Hi Nikolay, This issue is addressed in the headers on the Qmailtoaster FAQ page. From that page: Execute the following command to rebuild the version info associated with simscan: # /var/qmail/bin/simscanmk -g You should see the following output: simscan versions cdb file built. /var/qmail/control/simversions.cdb This is not an issue with the current upgrade process. Good luck! Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] qmail not using spamassassin?
Hello, I have a functioning Qmailtoaster install and everything seems to be working well with one exception. When I look at the full headers of all the messages I receive, I see no indication that spam checking/scoring is being applied. I've been all over the net trying to figure out why spamassassin doesn't appear to be scanning mail but am striking out. When I run qmailctl stat, I see spamd and spamd/log all running. Can anyone tell me how to check if qmail is even piping messages through spamassassin? Thank you! Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] qmail not using spamassassin?
On 8/20/2012 12:13 PM, Kelly Cobean wrote: Hello, I have a functioning Qmailtoaster install and everything seems to be working well with one exception. When I look at the full headers of all the messages I receive, I see no indication that spam checking/scoring is being applied. I've been all over the net trying to figure out why spamassassin doesn't appear to be scanning mail but am striking out. When I run qmailctl stat, I see spamd and spamd/log all running. Can anyone tell me how to check if qmail is even piping messages through spamassassin? Thank you! Kelly - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 1) Check /var/qmail/control/simscan and make sure 'spam=yes' 2) examine /etc/tcprules.d/tcp.smtp make sure: QMAILQUEUE=/var/qmail/bin/simscan appears on the line that starts 127:blahblahblah (comma separated items) 3) qmailctl restart all from my faulty memory, the wiki appears unreachable at this time. nice site, only the bumblebee gallery images are available in apache :( david Thanks David. For #1, do you mean /var/qmail/control/simcontrol? If so, that file reads: :clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif this is the default configuration of this file. I did add the QMAILQUEUE line as mentioned in #2 above and restarted qmail via qmailctl. Unfortunately, I still don't see any spam headers in received email. Any other thoughts? If it matters, this is a recent install of qmailtoaster on CentOS 5 and my /var/qmail/bin/qmail-queue is sym-linked to /var/qmail/bin/qmail-dk for domain keys support. Not sure if that is relevant? Thanks again. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] qmail not using spamassassin?
On 8/20/2012 3:05 PM, Kelly Cobean wrote: I did add the QMAILQUEUE line as mentioned in #2 above and restarted qmail via qmailctl. Unfortunately, I still don't see any spam headers in received email. doh, issue a 'qmailctl cdb' command (after editing the tcp.smtp file, forgot that one), then do the 'qmailctl restart', then check the header of a fresh message. if that doesn't do the trick, post the output of 'qmailctl stat | sort' and the contents of the tcp.smtp file.(esp. the 127:blah line) to make sure everything is up and running and typo-free. when it is all working, you should see something like this: Received: (qmail 27878 invoked by uid 89); 20 Aug 2012 20:06:24 - Received: by simscan 1.4.0 ppid: 27861, pid: 27863, t: 14.1495s scanners: attach: 1.4.0 clamav: 0.97.5/m:54/d:15278 spam: 3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.ntcb.com X-Spam-Level: * X-Spam-Status: No, score=1.6 required=5.0 tests=DKIM_SIGNED,RDNS_NONE, SARE_SUB_OBFU_Q1 shortcircuit=no autolearn=no version=3.3.2 -- david Thanks David. I ran the 'qmailctl cdb' command and restarted qmail and still no joy. Here's a header from a message after this was done: eturn-Path: kcob...@gmail.com Delivered-To: kcob...@vipercrazy.com Received: (qmail 5964 invoked by uid 89); 20 Aug 2012 20:56:05 - Received: from unknown (HELO mail-wi0-f170.google.com) (209.85.212.170) by www.novagunrunners.com with (RC4-SHA encrypted) SMTP; 20 Aug 2012 20:56:05 - Received-SPF: pass (www.novagunrunners.com: SPF record at _spf.google.com designates 209.85.212.170 as permitted sender) Received: by wibhq12 with SMTP id hq12so3486056wib.3 for kcob...@vipercrazy.com; Mon, 20 Aug 2012 13:56:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=lPq6DQPgu4WZy9vCqIr3b3rDBoJWuZP6+6BS3H5LC6s=; b=Aou8Jwv5gNYBjriK/zqMJvPJh8LHd9rpucXa9IhVZ7MiIOLQiD4657+MRqoBGO5HHf BRDzHMqM+i0QVI+bxPUt/e85643T3vb/Cq539d0oXTmvYAbKWam8d4K8znUp90NkF6XB nULFwxLXxiIPuYqbupizbLVkC/tMdhKy7peiif6sMTFdEglhDr47flZYRD0yGI6YHbqM gFfC26hJ16I6/1D3Dv4/Udas8uMZ2VQdkjjM8/HFT04NzmQ4zGzVDOCoH/Lk/I7EA2QK PwDVcGPHIOTwQ2Z1paVWb5jkugk/C/MBYlgr0MUZ69sNmWBCFYD5QWQAJ8QmYeQTznG+ F6Hg== MIME-Version: 1.0 Received: by 10.216.167.135 with SMTP id i7mr7632748wel.97.1345496164633; Mon, 20 Aug 2012 13:56:04 -0700 (PDT) Received: by 10.194.63.202 with HTTP; Mon, 20 Aug 2012 13:56:04 -0700 (PDT) Date: Mon, 20 Aug 2012 16:56:04 -0400 Message-ID: CANzmTRrQJWFON=7qhe-qokl5fjaaf6vas_2rw-vkbricjdd...@mail.gmail.com Subject: Spamassassin Test Message From: Kelly Cobean kcob...@gmail.com To: kcob...@vipercrazy.com Content-Type: multipart/alternative; boundary=0016e6541f94f08bef04c7b8bcc4 And here is the output of my tcp.smtp file: 127.:allow,QMAILQUEUE=/var/qmail/bin/simscan,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private :allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONGRCPTLIMIT=10,DKSIGN=/var/qmail/control/domainkeys/%/private Thanks again for your help! - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] qmail not using spamassassin?
On 8/20/2012 3:52 PM, David Good wrote: On 8/20/2012 3:05 PM, Kelly Cobean wrote: I did add the QMAILQUEUE line as mentioned in #2 above and restarted qmail via qmailctl. Unfortunately, I still don't see any spam headers in received email. sorry, the QMAILQUE bit needs to be on the line that just starts with a colon, that is the default processing instruction line. the default tcp.smtp file has 2 lines 127:blah :blah,blah, blah,QMAILQUE(---move it to here) qmailctl cdb qmailctl restart THAT did the trick David. Thank you so much! Headers now look good: Return-Path: kcob...@gmail.com Delivered-To: kcob...@vipercrazy.com Received: (qmail 6114 invoked by uid 89); 20 Aug 2012 21:03:20 - Received: by simscan 1.4.0 ppid: 6107, pid: 6108, t: 0.4058s scanners: attach: 1.4.0 clamav: 0.97.5/m:54/d:15278 spam: 3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on www.novagunrunners.com X-Spam-Level: * X-Spam-Status: No, score=1.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RDNS_NONE autolearn=no version=3.3.2 Received: from unknown (HELO mail-we0-f172.google.com) (74.125.82.172) by www.novagunrunners.com with (RC4-SHA encrypted) SMTP; 20 Aug 2012 21:03:19 - Received-SPF: pass (www.novagunrunners.com: SPF record at _spf.google.com designates 74.125.82.172 as permitted sender) Received: by weyu54 with SMTP id u54so4297707wey.3 for kcob...@vipercrazy.com; Mon, 20 Aug 2012 14:03:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=b+nE1Xj2e4WxnsSlynyX2lv+7Q/gOJ1IpcMPXRt9XIg=; b=FtOV+wl4a0v2P2ATCTkO2Rxu1Aup14TVDjI6T+nPtP3CbCVMBx979CnegnsjSURSu5 FlCsbZcxkGn2akjjPM2uBEoXtBsXatnyYkxrXe4aUwJFQPaxRElB6KZ8xpP9PzoMMEvR p0ukH/wHJ9T5e0h9uRY+U3O9GVmKmzFpQJ1Q6U2L+HmrKmoxCYaZsIJEWpnidLY1qxTu dEhoKzDjMEDksa6CbjhFegsyb9m4QwUVHciCBk8+21ys+ypIG0t903IDjJgUaSY/3gU8 aB65mKd1PzhdznkMKwduDVSvs704Jage8agHFdezIh6VA2Ebyi5ZVhioVgkmFqVafOD3 dFzg== MIME-Version: 1.0 Received: by 10.180.105.6 with SMTP id gi6mr31857704wib.4.1345496598574; Mon, 20 Aug 2012 14:03:18 -0700 (PDT) Received: by 10.194.63.202 with HTTP; Mon, 20 Aug 2012 14:03:18 -0700 (PDT) Date: Mon, 20 Aug 2012 17:03:18 -0400 Message-ID: CANzmTRq9gkAWEx-=__d8dt5puuunuoz3wv8nfiwunrwvgvk...@mail.gmail.com Subject: One more time! From: Kelly Cobean kcob...@gmail.com To: kcob...@vipercrazy.com Content-Type: multipart/alternative; boundary=f46d04428cc8cdf67104c7b8d6f2 I reallly appreciate your help! - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: qmail not using spamassassin?
On 08/20/2012 01:59 PM, David Good wrote: On 8/20/2012 3:52 PM, David Good wrote: On 8/20/2012 3:05 PM, Kelly Cobean wrote: I did add the QMAILQUEUE line as mentioned in #2 above and restarted qmail via qmailctl. Unfortunately, I still don't see any spam headers in received email. sorry, the QMAILQUE bit needs to be on the line that just starts with a colon, that is the default processing instruction line. the default tcp.smtp file has 2 lines 127:blah :blah,blah, blah,QMAILQUE(---move it to here) qmailctl cdb qmailctl restart - Thanks for helping out, David. Just for the record, doing qmailctl restart should not be necessary in this instance. When cdb files are modified by the cdb option, they are automagically refreshed by whatever process uses them. The restart function only restarts the qmail-smtpd process on port 25 and the qmail-send process (only). I just had a look at the code, and come to think of it, it should probably be restarting the qmail-smtpd on port 587 as well. It's a little confusing, as restart only acts on qmail processes, while start and stop affect everything that supervise controls under the /var/qmail/supervise tree, including spamd, clamd, etc. Also FWIW, doing qmailctl is the same as service qmail. They both run the exact same code. -- -Eric 'shubes' Great info. Thank you Eric. Just out of curiosity, I did pretty much a textbook QT/QTP install...any idea how/why this text was missing from the tcp.smtp file? I had not edited this file prior to today. Thanks again to you and David for the quick help! - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: qmail not using spamassassin?
On 08/20/2012 06:29 PM, Kelly Cobean wrote: Just out of curiosity, I did pretty much a textbook QT/QTP install...any idea how/why this text was missing from the tcp.smtp file? I had not edited this file prior to today. I've no idea. I'll be doing a scratch install in a few days though, and try to keep my eye on it. Here's what I have as /etc/tcprules.d/tcp.smtp in the present pkg (2 lines): 127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 :allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan,DKSIGN=/var/qmail/control/domainkeys/%/private,NOP0FCHECK=1 TTBOMK, this file is coded as noreplace, which means that an install/upgrade will never change it if one exists. If there existed one from a previous install of some kind, that would persist. Out of curiosity, what does: # ls -ltr /etc/tcprules.d/tcp.smtp* show on the host? -- -Eric 'shubes' root@www ~]# ls -ltr /etc/tcprules.d/tcp.smtp* -rw-r--r-- 1 root root 293 Aug 20 16:50 /etc/tcprules.d/tcp.smtp.new -rw-r--r-- 1 root root 251 Aug 20 17:01 /etc/tcprules.d/tcp.smtp -rw-r--r-- 1 root root 2325 Aug 20 17:02 /etc/tcprules.d/tcp.smtp.cdb - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: qmail not using spamassassin?
On 08/20/2012 07:05 PM, Kelly Cobean wrote: On 08/20/2012 06:29 PM, Kelly Cobean wrote: Just out of curiosity, I did pretty much a textbook QT/QTP install...any idea how/why this text was missing from the tcp.smtp file? I had not edited this file prior to today. I've no idea. I'll be doing a scratch install in a few days though, and try to keep my eye on it. Here's what I have as /etc/tcprules.d/tcp.smtp in the present pkg (2 lines): 127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1 :allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONGRCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan,DKSIGN=/var/qmail/control/domainkeys/%/private,NOP0FCHECK=1 TTBOMK, this file is coded as noreplace, which means that an install/upgrade will never change it if one exists. If there existed one from a previous install of some kind, that would persist. Out of curiosity, what does: # ls -ltr /etc/tcprules.d/tcp.smtp* show on the host? -- -Eric 'shubes' root@www ~]# ls -ltr /etc/tcprules.d/tcp.smtp* -rw-r--r-- 1 root root 293 Aug 20 16:50 /etc/tcprules.d/tcp.smtp.new -rw-r--r-- 1 root root 251 Aug 20 17:01 /etc/tcprules.d/tcp.smtp -rw-r--r-- 1 root root 2325 Aug 20 17:02 /etc/tcprules.d/tcp.smtp.cdb - I think that tcp.smtp.new would be the original stock version from the qmail-toaster package. I wonder if maybe one of the subsequent packages (simscan perhaps) has a tcp.smtp file that needs to be updated. Could be that's where it came from. Simscan hadn't been updated in a while before the recent one. rpm shows qmail-toaster as owning file file though. H. Seems to me that qmail-toaster should be dependent upon simscan, but that's not how things are presently set up. I need to look into this in a bit more detail. Thanks for pointing this out, Kelly. -- -Eric 'shubes' Glad to help. Thanks for all your hard work putting this all together. I used a qmailrocks installation (on an FC4 box!) for almost 5 years prior to changing over to QTP last month and let me tell ya the QMR install was ROUGH! QT/QTP is worlds better, especially with all the script automation. These little speed bumps are nothing. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
