Re: [qmailtoaster] Rocky 9 Migration

On 23 Feb 2024, at 9:10, Gary Bowling wrote: LoadModule php5\_module modules/libphp5.so On my Rocky 9 box, this file does not exist and I cannot find that it is even suppose to exist. But I'm not sure how php is suppose to work on Apache without it. Hi Gary, Glad you worked it

Re: [qmailtoaster] Status of Domain Keys in QMT

a part of the sources but signing is done by a perl wrapper around qmail-remote. See here <https://qmailtoaster.org/dkim.html> . DKIM checking can be done by either spamassassin or rspam and is not necessary in QT. On 10/1/2023 12:18 PM, Quinn Comendant wrote: Hi all, What is the current stat

[qmailtoaster] Status of Domain Keys in QMT

Hi all, What is the current status of Domain Keys in QMT? I've been following the advice given in (“Unfortunately, domain keys are broken in Toaster. It's recommended that you disable them for the time being.”), but wonder if there

Re: [qmailtoaster] rocky 9 from centOS 7 suggestions?

On 10 Mar 2023, at 11:16, Gary Bowling wrote: What's the status these days of a repository that "just works" for installing the toaster? I'd love an update on this too. I'm planning an upgrade to Rocky 9 this year as well. I'm a developer, so not afraid of scripts, but had assumed that QMT

Re: [qmailtoaster] Outlook users get "unsupported encryption type" error after Windows update

Hi Andreas, I've had some users report this as well. Previously, they were getting this same error when receiving mail; upgrading to Dovecot (from Courier) resolved that. Now the issue seems to also exist with qmail-smtp. I'm not sure what is broken, because connections to port 587 support

Re: [qmailtoaster] UIDVALIDITY value changed during Courier-to-Dovecot migration

On 19 Oct 2022, at 0:41, Quinn Comendant wrote: The so-called UIDVALIDITY value of the mailbox “INBOX” has changed. MailMate has to resynchronize the mailbox, that is, purge the local cache and refetch the messages of the mailbox. I think this may have been caused by the mailboxes actually

[qmailtoaster] UIDVALIDITY value changed during Courier-to-Dovecot migration

I've done a test upgrade of a cloned server from Courier to Dovecot. So far, it's working well with most email clients, but when I reconfigure MailMate to connect to the new server, it gives me this error ([screenshot](https://send.strangecode.com/f/screen-shot-2022-10-18-at-23-51-55.png)):

Re: [qmailtoaster] Outlook users get "unsupported encryption type" error after Windows update

On 13 Oct 2022, at 12:12, Jeff Koch wrote: I think this would indicate that our Dovecot IMAP supports TLSv1.2 and should work with the Outlook updates. Am I missing something? FWIW, I applied [Janno Sannik's

Re: [qmailtoaster] Outlook users get "unsupported encryption type" error after Windows update

On 13 Oct 2022, at 12:12, Jeff Koch wrote: I think this would indicate that our Dovecot IMAP supports TLSv1.2 and should work with the Outlook updates. Yes, looks like a successful TLS 1.2 connection. When testing with openssl, I would add the `-tls1_2` option to force use of that protocol:

Re: [qmailtoaster] Outlook users get "unsupported encryption type" error after Windows update

The Windows system update on October 11, 2021 included a change to disable TLS 1.0 and 1.1 by default. - Windows blog post: [Plan for change: TLS 1.0 and TLS 1.1 soon to be disabled by default](https://blogs.windows.com/msedgedev/2020/03/31/tls-1-0-tls-1-1-schedule-update-edge-ie11/) -

[qmailtoaster] Outlook users get "unsupported encryption type" error after Windows update

Today we received several complaints from Outlook users who are unable to connect to QMT servers. They get this error: Task "u...@example.com - Sending: reported error (Ox800CCC1A) : 'Your server does not support the connection encryption type you have specified. Try changing the encryption

Re: [qmailtoaster] Best Config for new server

I will probably use Rocky when I rebuild my server, because it is one of the options on GCP, it has an EOL of June 2031. Q - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands,

Re: [qmailtoaster] Host email server on AWS cloud

Or don't send mail from AWS IP addresses at all; use a mail forwarding service such as MailChannels. Quinn - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:

Re: [qmailtoaster] Let's Encrypt "DST Root CA X3" expires today

On 30 Sep 2021 13:02:51, Quinn Comendant wrote: > I have a RoundCube server that is now unable to connect to an IMAP > server (older qmailtoaster running couriertls). The error in the > imap4-ssl log is "sslv3 alert certificate expired". I was able to solve this by updating t

[qmailtoaster] Let's Encrypt "DST Root CA X3" expires today

Hello all, The Let's Encrypt "DST Root CA X3" root certificate expired today, September 30, 2021. https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ For most users, this isn't an issue because the newer "ISRG Root X1" certificate is trusted on all new devices. Users with

Re: [qmailtoaster] dot-qmail files

You can find .qmail documentation at `man dot-qmail`. I'd like to see your scripts, if you'd like to share. Quinn - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:

Re: [qmailtoaster] 15 years later: Remote Code Execution in qmail (CVE-2005-1513)

having a reasonable value in > /var/qmail/control/databytes > > Have you checked your deployed systems? > > I need to dig into how qmail-local is being called, so I can figure > out whether it has softlimits yet, but I need to get my kids to > school. :) > > -Chri

[qmailtoaster] 15 years later: Remote Code Execution in qmail (CVE-2005-1513)

Hello all, I just came across this security bulletin that affects qmail: https://www.qualys.com/2020/05/19/cve-2005-1513/remote-code-execution-qmail.txt “TLDR: In 2005, three vulnerabilities were discovered in qmail but were never fixed because they were believed to be unexploitable in a default

Re: [qmailtoaster] Does not support TLS

On Fri, 15 Jun 2018 10:47:55 +0700, Quinn Comendant wrote: > And it's true, here's the capabilities shows in a SMTP connection: > […] Correction: it's indicated as available by the "STARTTLS" tag. ¯\_(ツ)_/¯ And indeed, now it seems to be working, I'm getting "Supports TLS

Re: [qmailtoaster] Does not support TLS

Another issue it reported is "SMTP Transaction Time: 15.174 seconds - Not good on Transaction Time". Is that an intentional delay due for "tar pitting"? Quinn - To unsubscribe, e-mail:

[qmailtoaster] Does not support TLS

I tested a server with mxtoolbox.com, and it gave an error that the server "Does not support TLS": "Your SMTP email server does advertise support for TLS. After connecting to your mail server we issue an EHLO command to introduce ourselves and to request that your server announce which

Re: [qmailtoaster] Discrepancy between vpopmail ↔︎ assign/vdominfo

On Tue, 5 Jun 2018 22:18:23 -0600, Eric Broch wrote: > How do you manage vpopmail, by CLI, VQAdmin, qmailAdmin? Always by CLI tools from /home/vpopmail/bin/* Q - To unsubscribe, e-mail:

[qmailtoaster] Discrepancy between vpopmail ↔︎ assign/vdominfo

There is a QMT server with 136 domains. It has 136 domains in its vpopmail DB and 136 domains under /home/vpopmail/domains. However, the /var/qmail/users/assign file has 157 distinct domains, and vdominfo reports 155 domains. The /home/vpopmail/bin/* tools are used exclusively for managing

Re: [qmailtoaster] Too many /tmp/clamav-*.tmp [SOLVED]

On Thu, 24 May 2018 16:12:35 -0600, Eric Broch wrote: > I think you should update ClamAV on your system. I while back there > was an issue with older ClamAV versions leaving orphaned file handles > on the system in the /tmp directory. The newer versions will resolve > this issue. That's a good

Re: [qmailtoaster] Too many /tmp/clamav-*.tmp

On Thu, 24 May 2018 08:33:40 -0600, Eric Broch wrote: > Is this issue resolved if you remove the call to the wrapper script? Ok, I tried this, and it the number of tmp dirs is still increasing. I'll let it run like this for awhile to see if it improves. > Also, can you enable 'SIMSCAN_DEBUG=3'

[qmailtoaster] wiki spam

I found this at http://wiki.qmailtoaster.com/index.php?title=FAQs (see attached). Q - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail:

[qmailtoaster] email addresses beginning with a hyphen

the problem: http://goo.gl/6vq6ps -- Quinn Comendant Strangecode, LLC http://www.strangecode.com/ +1 530 636 2633 office @com and @strangecode

[qmailtoaster] forwarding submission mail to alternate host

We have a customer who wants to use a Barracuda encryption service so they can be HIPAA compliant. They have requested that outgoing mail their office submits to our server on port 587 be forwarded to a barracuda network. I know qmail's `smtproutes` allows incoming mail for a domain to be

[qmailtoaster] sslv3_alert_handshake_failure due to limited cipher-set in tlsserverciphers

I've been using a limited (hardened) set of SSL ciphers in tlsserverciphers, but have noticed today that there have been 13 delivery failures from our server in the past twenty days:

Re: [qmailtoaster] Re: shellshock and qmail

On Thu, 30 Oct 2014 19:09:44 -0700, Eric Shubert wrote: Not surprised that you missed it Quinn, but there was a post here on 9/25 about it. ;) Pretty serious vulnerability, but easily remedied. Ok, glad it was brought up. I didn't see a match for shellshock in the QMT list archives. Q

[qmailtoaster] shellshock and qmail

It hasn't been mentioned on this list yet so I thought I would bring it up: qmail exposes environment variables in a way that a vulnerable bash is susceptible to CVE-2014-6271 (aka shellshock). If you have a patched bash, don't worry. If you haven't patched for this, do. This post includes a

[qmailtoaster] Is spamdyke 5 production ready?

Is spamdyke 5 production ready? I notice the qtp-install-spamdyke script uses the 4.x branch. BTW, in that script, I noticed these lines are wrapped, causing the comments to be left out of the generated conf files: echo # These are words which will reject the sender

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Wed, 22 Oct 2014 20:01:54 +0300, Catalin Leanca wrote: For me , that command works. I also modified IMAPDSSLSTART=NO and IMAP_TLS_REQUIRED=1 Ok, so I've set those variable too, and still not working. Sorry to bother, but would you mind comparing your /etc/courier/imapd-ssl file with mine:

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Fri, 24 Oct 2014 13:53:24 +0545, Quinn Comendant wrote: On Wed, 22 Oct 2014 20:01:54 +0300, Catalin Leanca wrote: For me , that command works. I also modified IMAPDSSLSTART=NO and IMAP_TLS_REQUIRED=1 Also, isn't it a little confusing that courier is accepting connections on port 993 at all

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Fri, 24 Oct 2014 14:09:46 +0545, Quinn Comendant wrote: On Fri, 24 Oct 2014 13:53:24 +0545, Quinn Comendant wrote: On Wed, 22 Oct 2014 20:01:54 +0300, Catalin Leanca wrote: For me , that command works. I also modified IMAPDSSLSTART=NO and IMAP_TLS_REQUIRED=1 Also, isn't it a little

Re: [qmailtoaster] Re: How to fix DNS for Received: from unknown

On Tue, 21 Oct 2014 18:50:11 -0700, Eric Shubert wrote: Personally, I think that's information that doesn't need to be in the message header (along with the authenticated user's account id, but that's another matter). Apparently, that info is important for SA. Here's my discussion on the SA

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Tue, 21 Oct 2014 19:02:09 -0700, Eric Shubert wrote: In order to disable SSL in dovecot, you could either block the SSL ports (993, 995) in the firewall, or change /etc/dovecot/toaster.conf file by adding :!SSLv3 to the list of ciphers: ssl_cipher_list =

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Fri, 17 Oct 2014 10:52:12 +0300, Catalin Leanca wrote: I managed to disable SSLv3 in /etc/courier/imapd-ssl and /etc/courier/pop3-ssl Changed TLS_PROTOCOL=SSLv3 to TLS_PROTOCOL=TLS1 Catalin (and others): have you succeeded in disabling SSLv3 in courier? When I try this configuration, I am

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Fri, 17 Oct 2014 10:52:12 +0300, Catalin Leanca wrote: But how about SMTP ? How to disable SSLv3 over 587 submission port ? I couldn't find the answer with 10 minutes of googling, but I did find this (UNTESTED!): How to take down SSLv3 in your network using iptables firewall:

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

On Tue, 21 Oct 2014 23:27:35 +0545, Quinn Comendant wrote: On Fri, 17 Oct 2014 10:52:12 +0300, Catalin Leanca wrote: But how about SMTP ? How to disable SSLv3 over 587 submission port ? Here's a comprehensive list of how to disable SSLv3 in everything *except* qmail: http://askubuntu.com

[qmailtoaster] How to fix DNS for Received: from unknown

Hi Guys I've been discussing on the us...@spamassassin.apache.org list about a minor issue I'm having with SA, and it was noted by a couple people that the headers of incoming mail indicates qmail is not doing DNS lookups correctly. Specifically, it seems qmail is not recording the reverse dns

Re: [qmailtoaster] Re: user and group for vpopmail

Hi Eric On Sat, 11 Oct 2014 08:41:43 -0700, Eric Shubert wrote: Recommended solution? I'd simply chgrp -R /home/vpopmail/domains/* vchkpw after the rsync. That's what I did. I also had to change the group IDs in `/var/qmail/users/assign` and rehash the cdb: sudo perl -pi.bak -e

Re: [qmailtoaster] Re: user and group for vpopmail

On Sat, 11 Oct 2014 23:35:35 -0700, Eric Shubert wrote: Did you use the --numeric-ids flag on rsync? Without it, user and group ids can get changed from one host to another, depend on what number is assigned to which name(s). No, because I wanted files to retain same username ownership,

[qmailtoaster] user and group for vpopmail

I'm migrating a qmailtoaster installed in 2006 to a new server. I've come to an issue where the vpopmail-toaster package creates user vpopmail with group vchkpw: {q@oak2/0 bin} groups vpopmail vpopmail : vchkpw However, on the old server, the vpopmail user was setup with group

Re: [qmailtoaster] Re: IRC

On Sun, 20 Jun 2010 18:49:04 -0700 Scott Hughes wrote: So far no luck. I can find bots, but none yet that log. I'm sure I'd have to find a way to transfer the logs to some type of searchable format, but one step at a time. FWIW, there are plenty of free logging bot services, e.g.,

Re: [qmailtoaster] Migration of qmail

On Fri, 31 Jan 2014 08:13:01 -0700, Dave M wrote: remionder Centos 6, not 100% yet Is there a list of things that don't work on centos 6? If it's not 100%, is it 90%? 95%? -- Quinn Comendant Strangecode, LLC http://www.strangecode.com/ +1 530 624 4410 mobile +1 530 636 2633 office @qc

[qmailtoaster] Disabling Domain Keys

to `qmail-dk` by default; I thought by default it would go to `qmail-queue.orig` (the page above writes, This will be disabled in future releases anyway). Thanks, -- Quinn Comendant Strangecode, LLC http://www.strangecode.com/ +1 530 624 4410 mobile +1 530 636 2633 office @qc and @strangecode

[qmailtoaster] valias vs aliases in .qmail

After 7 years using qmailtoaster I only just realized some unexpected behavior with `valias` versus aliases in .qmail files. I thought I'd mention this here in case others also weren't aware of this, or if I'm wrong y'all can call me crazy. I discovered if you use `valias` to create a virtual

Re: [qmailtoaster] Re: valias vs aliases in .qmail

On Wed, 08 Jan 2014 11:17:11 -0700, Eric Shubert wrote: Instead, if you modify a .qmail file to add `destinat...@addre.ss` in addition to the local mail delivery rule (preferably through vqadmin, which modifies the .qmail file for you) Whoops I meant preferably through qmailadmin. Quinn

Re: [qmailtoaster] Re: valias vs aliases in .qmail

On Wed, 08 Jan 2014 11:17:11 -0700, Eric Shubert wrote: Instead, if you modify a .qmail file to add `destinat...@addre.ss` in addition to the local mail delivery rule (preferably through vqadmin, which modifies the .qmail file for you) Whoops I meant preferably through qmailadmin. Quinn

Re: [qmailtoaster] Re: valias vs aliases in .qmail

On Wed, 08 Jan 2014 11:17:11 -0700, Eric Shubert wrote: I'm not positive about this. My understanding is that forwards are now stored in the database instead of using .qmail files. Are you sure that vqadmin modifies the .qmail file for the account? It does create them. I just tested: 1.

Re: [qmailtoaster] Re: Can I disable CRAM-MD5 authentication for submission service?

on this? Thanks! -- Quinn Comendant Strangecode, LLC http://www.strangecode.com/ +1 530 624 4410 mobile +1 530 636 2633 office @qc and @strangecode - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

Re: [qmailtoaster] Re: Can I disable CRAM-MD5 authentication for submission service?

On Wed, 11 Sep 2013 15:07:31 +0200, Johannes Weberhofer wrote: this line in the spec will remove CRAM-MD5 completely: %{__perl} -pi -e s|\#define CRAM_MD5||g qmail-smtpd.c I'd like to do this as well to remove the dependence on pw_clear_passwd. It's really this easy? And the clients that

Re: [qmailtoaster] a dns patch maybe

This may be related to the DNS 'ANY' query canonicalization issue I reported a few weeks ago: http://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg35790.html Quinn - To unsubscribe, e-mail:

Re: [qmailtoaster] DNS Best Practices for QMT

This is great Dan. Is this up on the wiki yet? Thanks! Quinn - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] QMT and the DNS 'ANY' query canonicalization issue

Rackspace has corroborated our findings with the va.gov DNS misconfiguration (their response pasted below). Which brings me back to my question: is there a way to make qmail more resilient to these kind of DNS issues? Quinn - Forwarded message from supp...@rackspace.com, 21 Jul 2013

[qmailtoaster] QMT and the DNS 'ANY' query canonicalization issue

Hi all, We've been experiencing CNAME_lookup_failed_temporarily._(#4.4.3)/I'm_not_going_to_try_again errors when sending mail to @va.gov addresses. Since QMT includes the Big DNS Patch, a DNS packet buffer overrun isn't the issue. I wonder if we might be experiencing the other DNS issue

[qmailtoaster] QMT and the DNS 'ANY' query canonicalization issue

Hi all, We've been experiencing CNAME_lookup_failed_temporarily._(#4.4.3)/I'm_not_going_to_try_again errors when sending mail to @va.gov addresses. Since QMT includes the Big DNS Patch, a DNS packet buffer overrun isn't the issue. I wonder if we might be experiencing the other DNS issue

Re: [qmailtoaster] QMT and the DNS 'ANY' query canonicalization issue

Thanks Alex I can confirm the ANY query failure now; it was working earlier today – it must be an intermittent problem with their DNS. I've emailed the address listed in the SOA. It it still useful for qmail to make DNS ANY queries, or can they be disabled as recommended at

[qmailtoaster] Re: Mail Certificates

Natalio Gatti ngatti at gmail.com writes: I need to buy a digital certificate for my qmail server. In the wiki there is a link to DiscountWebCerts.  Do you still recomend them? Is there any other server? And one more question: Those cheap RapidSSL certificates are fully compatible with

[qmailtoaster] commercial ESP for forwarded SMTP?

We'll be deploying a mail server on a Rackspace cloud server, and they suggested that because their offering is 'utility computing' the IP addresses included are dirty (in a blacklist kind of way) and we should use a commercial ESP such as SendGrid, PostMark, CritSend, CloudSMTP, or the like.

Re: [qmailtoaster] Re: spamc -h received in message body

Eric I've posted the raw email here: http://pastie.textmate.org/private/68bokw2tmauf2soczq I agree: the catch-all is not the problem; it is something to do with the way simscan is passing the message to clamc that an email addressed to --local@domain is interpreted as an invalid argument. This

Re: [qmailtoaster] spamc -h received in message body

On Sat, 21 May 2011 19:37:19 -0700, Quinn Comendant wrote: We have a client on our mail server who occasionally and randomly receives emails which contain nothing other than the output from `spamc --help` I found the cause of this problem. The client was using a catch-all address

[qmailtoaster] spamc -h received in message body

Anybody seen this before? We have a client on our mail server who occasionally and randomly receives emails which contain nothing other than the output from `spamc --help` (see output at http://pastie.textmate.org/private/6gb0ymmqpyw7mee39sespg). Nothing* in our log files match up with the

Re: [qmailtoaster] Mirror

Here's a copy of all the latest QMT rpms on our CDN. Jake, feel free to link to these for a few days if you need to relieve www.qmailtoster.com of its burden. http://cdn.one.strangecode.com/qmt/autorespond-toaster-2.0.4-1.3.6.src.rpm

[qmailtoaster] clamav 0.94 end-of-life today

Just a reminder to everybody that ClamAV 0.94.x is no longer supported by signature file updates after 15 Apr 2010. http://www.clamav.net/lang/en/2009/10/05/eol-clamav-094/ If you haven't yet upgraded to 0.95.x you need to do so now to process signature updates provided through freshclam.

[qmailtoaster] vpopmail persistant mysql connections

Does vpopmail use persistent mysql connections? To reduce mysql memory usage, I'd like there to be fewer sleeping vpopmail db connections: | Id | User | Host | db | Command | Time | State | Info | | 394 | vpopmail | localhost | vpopmail | Sleep | 10

Re: [qmailtoaster] bypassing virtualdomains

On Fri, 12 Sep 2008 10:26:13 -0400, Dan McAllister wrote: I've had to deal with this... and if you have control of BOTH ends (old server and new) it's much easier... I almost never have access to the old server. Any other ideas? Quinn

[qmailtoaster] bypassing virtualdomains

Hi all, Is there a way to have qmail-send check actual MX records for a domain before deciding if it is local or not (instead of by (more)rcpthosts and virtualdomains)? An issue comes up occasionally when a domain is added on our server which is currently hosted somewhere else (i.e. it's a

[qmailtoaster] ezmlm lists and valias

Hmmm. This should work but it doesn't. I have a ezmlm list at [EMAIL PROTECTED] I wanted to create an alias to this address so incoming messages are forwarded to a mailbox that is posted to a blog. Adding the alias using valias doesn't work: vpopmailselect * from valias where domain =

Re: [qmailtoaster] Communication Error: Cannot read data from socket

On Mon, 3 Mar 2008 21:34:01 -0800, Quinn Comendant wrote: Communication Error: Cannot read data from socket (Resource temporarily unavailable) Two more bits of information: 1. Often the message *does* go through, even through my mail client says sending failed. 2. If I restart qmail

Re: [qmailtoaster] Communication Error: Cannot read data from socket

On Tue, 04 Mar 2008 16:37:15 -0700, Eric Shubert wrote: I used to see this problem (at least I think it's the same one) too. I haven't seen it since I upgrade to the current packages, most notably clamav. I'd upgrade all of them and see if the problem doesn't go away. I'll try that and report

[qmailtoaster] vpopmail over-quota phantoms

This week we've received a flood of clients complaining about vpopmail's Your mailbox on the server is now more than 90% full messages, when they were nowhere near over quota. There have been about 3-people-a-day for the past week noting this, and each time I check the `vuserinfo` command and

[qmailtoaster] Communication Error: Cannot read data from socket

I've started getting this error when sending mail to my QT over port 587: Communication Error: Cannot read data from socket (Resource temporarily unavailable) Message sending just stalls for 60 seconds or so. It happens to me a few times a week, and sometimes I can't send mail at all,

[qmailtoaster] Communication Error: Cannot read data from socket

I've started getting this error when sending mail to my QT over port 587: Communication Error: Cannot read data from socket (Resource temporarily unavailable) Message sending just stalls for 60 seconds or so. It happens to me a few times a week, and sometimes I can't send mail at all,

RE: [qmailtoaster] DSpam

On Thu, 15 Nov 2007 11:54:11 -0500, Kyle Quillen wrote: I would love to be able to have users forward spam messages. This can be done using SA too, via sa-learn injection. Just create two aliases: sudo valias -i '|sa-learn --spam --no-sync /var/log/sa-learn-spam.log 21' [EMAIL PROTECTED];

[qmailtoaster] Fwd: smtp port 587

I wonder if anybody can comment on a client's request (below). Is there a setting for MSP 587 timeout? Quinn - Begin forwarded message - Subject: smtp port 587 Date: Wed, 18 Jul 2007 14:22:08 -0700 I am having problems using thunderbird, port 587, tls. It works on most connections, but

Re: [qmailtoaster] Fwd: QmailToaster: Update patches included in qmail toaster page : Task closed

On Wed, 4 Apr 2007 12:36:13 -0700, Erik A. Espinoza wrote: rpm -q --changelog qmail-toaster So far only bigdns and linefeed have been added. I know, but... http://www.google.com/search?q=qmail-smtpd-linefeed.patch No matches. What is this patch? Q

[qmailtoaster] Fwd: QmailToaster: Update patches included in qmail toaster page : Task closed

- Begin forwarded message - FS#23 - Update patches included in qmail toaster page User who did this - Erik A. Espinoza (espinoza) Reason for closing: Won't fix Additional comments about closing: Wiki's can be edited by anyone. Feel free to take care of this. I would but I have no

Re: [qmailtoaster] UPDATED PACKAGES: simscan-toaster, isoqlog-toaster, clamav-toaster, spamassassin-toaster, qmail-toaster

On Wed, 7 Mar 2007 12:05:19 -0800, Erik A. Espinoza wrote: qmail-toaster (added bigdns patch, linefeed patch) Which is the linefeed patch? Add details to: http://wiki.qmailtoaster.com/index.php/Patches_included_with_QmailToaster spamassassin-toaster (Upgraded to 3.1.8, Marked

[qmailtoaster] Apache-writable file executed as root (isoqlog cron.sh)

All I found a possibly severe permissions issue. I've added this as a bug to the bug tracker as ticket #6 but should be corrected asap on existing QT installations. The isoqlog cron script is installed writable by apache: -rwxr-xr-x 1 apache apache 467 Jan 28 23:26

[qmailtoaster] Fwd: [qmailadmin] Patch for autorespond

FYI: a patch for autorespond to prevent spam from getting a reply. I would recommend adding this to the toaster. Quinn - Strangecode :: Internet Consultancy http://www.strangecode.com/ +1 530 624 4410 - Begin forwarded

Re: [qmailtoaster] Heavy qmail queue pls help !!!

On Tue, 30 Jan 2007 02:33:24 +0300, Alexey Loukianov wrote: AFAIK, it chooses the LAST available interface on the system (the last one ifconfig shows). This behavior is something I dislike and I'm thinking about implementing a patch allowing manual selection of outgoing IP/port pair to send

Re: [qmailtoaster] Spamassassin has problem in scanning

On Tue, 30 Jan 2007 13:31:43 -0800, Erik Espinoza wrote: Updated rules, catches more of the stock spam and what not. It's nice. Read up at http://saupdates.openprotect.com/ I think ashok means he installed OpenProtect's software package (a collection of programs that replaces

Re: [qmailtoaster] UPDATE qmail-toaster-1.03-1.3.13.src.rpm URGENT

On Wed, 31 Jan 2007 15:13:46 +0100, Jean-Paul van de Plasse wrote: Or to manualy change the run script by changing the line REQUIRE_AUTH=1 to export REQUIRE_AUTH=1 The smtp/run script maybe also has this but as it only has: REQUIRE_AUTH=0 Quinn

Re: [qmailtoaster] setting noreplace more in *-toaster.specs

On Mon, 29 Jan 2007 10:07:08 -0700, Eric Shubes wrote: Erik Espinoza wrote: I put all of my custom conifg in myconfig.cf. It's easier that way, just a thought. This can be trouble if the other .cf and .pre files happen to appear (from upgrading, etc) and your config values are supersceeded by

[qmailtoaster] overquota.msg typo again

Typo in /home/vpopmail/domains/.overquota.msg: This user has exceeded there mail quota. there = their I've reported this before...but? It seems we could use a system for managing bugs tasks and issues. It could be as easy as adding an ISSUES page to the wiki, although it could become

Re: [qmailtoaster] Re: Development Package: qmail-toaster-1.03-1.3.8.src.rpm

On Wed, 8 Nov 2006 22:37:45 -0800, Erik Espinoza wrote: I will add support for qmailmrtg to monitor the submission logs once this feature makes it to stable. Thanks, Erik Just a reminder... ;P Quinn - Strangecode ::

Re: [qmailtoaster] setting noreplace more in *-toaster.specs

On Thu, 25 Jan 2007 19:22:30 -0700, Eric Shubes wrote: %{qdir}/supervise/spamd/run I don't think of this as a configuration file. [...] It's not really a configuration file but because it is something that might be fine-tuned there is a strong advantage to adding the %config(noreplace) flag

Re: [qmailtoaster] Fwd: [simscan] attachment filename scanning bug report

On Wed, 24 Jan 2007 11:43:30 +0200, Peter Peltonen wrote: On 1/22/07, Quinn Comendant [EMAIL PROTECTED] wrote: FYI: I found an issue with simscan this morning that y'all should be aware of. Read below... Has this bug been confirmed? I don't know. I emailed my bug report to the simscan

Re: [qmailtoaster] couriertls couriersslcache error

On Sat, 20 Jan 2007 13:27:14 +0200, Peter Peltonen wrote: On 1/6/07, Quinn Comendant [EMAIL PROTECTED] wrote: I discovered I could solve the issue by changing the TLS_CACHEFILE value in /etc/courier/{pop3d-ssl,imap4-ssl} from: In your experience, what is the impact of using Courier's TLS

[qmailtoaster] setting noreplace more in *-toaster.specs

Can we set the %config(noreplace) specification for a few more files? Specifically, I found after upgrading spamassassin that my local.cf and run files were hosed: %{qdir}/supervise/spamd/run %{_sysconfdir}/mail/spamassassin/local.cf %{_sysconfdir}/mail/spamassassin/v310.pre

Re: [qmailtoaster] recent changes and changelogs

On Mon, 22 Jan 2007 15:31:18 -0500, Jake Vickers wrote: Not sure how to do this on the wiki I guess I could write a script that would download the qmail-toaster package and grab the release notes (out of the SPEC file I imagine would be the best) then (for simplicity) spit that back

Re: [qmailtoaster] recent changes and changelogs

On Mon, 22 Jan 2007 13:25:05 -0700, Eric Shubes wrote: The main site (1.3.10) contains the latest DomainKey patches (more than just logging). Yes, but what ARE the patches? ;P That's exactly my point. And Alexey mentioned once he would add a feature to disable DomainKeys in the right way --

Re: [qmailtoaster] recent changes and changelogs

On Tue, 23 Jan 2007 00:40:08 +0300, Alexey Loukianov wrote: Jake, hang on for a minute. Changelogs are basically the product of development process itself, so they must be kept in track accordingly. That's why I think that first we should discuss it with Erik and Nick, and only then made any

[qmailtoaster] Fwd: [simscan] attachment filename scanning bug report

: [simscan] attachment filename scanning bug report Date: Mon, 22 Jan 2007 13:38:16 -0800 From: Quinn Comendant [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] I found a problem with simscan's attachment scanning: the filename matching is overly sensitive. I'm using version 1.2

Re: [qmailtoaster] Consolodating emails on multiple lists

On Tue, 23 Jan 2007 00:08:27 +0300, Alexey Loukianov wrote: AFAIK, that's it. Qmail will not sort/uniq the recipients of the message, it will simply forward it, resulting in dupes. If you need another behavior, you will have either to write a custom patch for ezmlm, implementing sublists

[qmailtoaster] POP3 password scanning

I found 8000+ entries in my logs like this: 2007-01-21 09:51:25.570281500 tcpserver: status: 200/200 2007-01-21 09:51:25.570410500 tcpserver: pid 28241 from 24.220.50.36 2007-01-21 09:51:25.571261500 tcpserver: ok 28241 two.strangecode.com:72.3.142.43:110

Re: [qmailtoaster] Consolodating emails on multiple lists

On Tue, 23 Jan 2007 02:30:34 +0300, Alexey Loukianov wrote: I'm not sure procmail will be able to filter out such almost dupes, but in any case James will be forced to modify each user separately to filter out dupes, which is not the easiest thing to deploy and administer. The formail -D

Re: [qmailtoaster] Consolodating emails on multiple lists

On Tue, 23 Jan 2007 04:15:00 +0300, Alexey Loukianov wrote: [...] The only trouble for this method I see then is the relatively difficult deployment and administration (i.e. we are adding another point for possible failures, and it will be harder for us to check up why the hell user

  1   2   3   >