[qmailtoaster] spambox
Hi list, The spambox option is active on my qmailtoaster server. Some emails that are not spam are marked as spam and are moved in the spam folder and other emails that obiously are spam remain in my inbox folder. Its there a solution without whitelist the sender domain to unmark the sender that are not spam ? ... and to manually mark the spam from my inbox ? Thx Toni - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Fwd: Cron r...@mailserv /usr/sbin/clamav-unofficial-sigs.sh -c /etc/clamav-unofficial-sigs.conf
Hi, after upgrading my toaster via qtp-newmodel i'm receiving again (remember last thread? :-D ) this message hourly. In my clamav-unofficial-sigs.conf i have set: curl_silence=yes# Default is no to report curl statistics rsync_silence=yes # Default is no to report rsync statistics gpg_silence=yes # Default is no to report gpg signature status comment_silence=yes # Default is no to report script comments Is there any way to avoid this message ? Thanks! Inizio messaggio inoltrato: Da: r...@kartonet.info (Cron Daemon) Data: 06 ottobre 2009 09.28.57 GMT+02.00 A: r...@kartonet.info Oggetto: Cron r...@mailserv /usr/sbin/clamav-unofficial-sigs.sh - c /etc/clamav-unofficial-sigs.conf Restarting clamd /var/qmail/supervise/clamd: up (pid 11860) 21452 seconds /var/qmail/supervise/clamd/log: up (pid 22163) 1 seconds
[qmailtoaster] qtp-newmodel on Fedora 11
running qtp-newmodel on Fedora11, im running into problems with the new FUSE chroot [..] Would you like a unionfs/overlay sandbox? (recommended) [y]/n: y Using FUSE union filesystem ... qtp-mount-sandbox v0.3.3 qtp-mount-sandbox - installing fuse-unionfs ... qtp-mount-sandbox - this could take a few moments - please be patient Loaded plugins: dellsysidplugin2, refresh-packagekit qtp-Fedora qtp-Fedora/primary qtp-Fedora Setting up Install Process Resolving Dependencies -- Running transaction check --- Package fuse-unionfs.i586 0:0.23-1.qtp set to be updated -- Processing Dependency: libfuse.so.2(FUSE_2.8) for package: fuse-unionfs-0.23-1.qtp.i586 -- Running transaction check --- Package fuse.i586 0:2.8.0-1.qtp set to be updated -- Finished Dependency Resolution Dependencies Resolved === Package Arch Version === Installing: fuse i586 2.8.0-1.qtp replacing fuse-libs.i586 2.7.4-3.fc11 fuse-unionfs i586 0.23-1.qtp Transaction Summary === Install 2 Package(s) Upgrade 0 Package(s) Total download size: 165 k Downloading Packages: (1/2): fuse-2.8.0-1.qtp.fc11.i586.rpm (2/2): fuse-unionfs-0.23-1.qtp.fc11.i586.rpm --- Total Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : fuse-2.8.0-1.qtp.i586 MAKEDEV: no such group: fuse warning: group fuse does not exist - using root Installing : fuse-unionfs-0.23-1.qtp.i586 service fuse does not support chkconfig Error in PREUN scriptlet in rpm package fuse Erasing: fuse-libs-2.7.4-3.fc11.i586 error: %preun(fuse-2.7.4-3.fc11.i586) scriptlet failed, exit status 1 fuse-2.7.4-3.fc11.i586 was supposed to be removed but is not! Installed: fuse.i586 0:2.8.0-1.qtp fuse-union Replaced: fuse-libs.i586 0:2.7.4-3.fc11 Complete! qtp-mount-sandbox - installation of dependent packages failed qtp-mount-sandbox - is your qmailtoaster-plus.repo package up to date? qtp-newmodel - qtp-mount-sandbox failed, exiting So did i forget to update the repo? r...@fury:~ yum update qmailtoaster-plus.repo Loaded plugins: dellsysidplugin2, refresh-packagekit qtp-nodist | 951 B 00:00 updates/metalink| 24 kB 00:00 Setting up Update Process No Packages marked for Update nope
Re: [qmailtoaster] Fully qualified hostname with multiple domain names
Eric Shubert wrote: Jake Vickers wrote: Eric Shubert wrote: Interesting. I don't buy that using an IP address is necessarily the best practice though. Here are my thoughts on this. It does not matter so much these days, but it used to be best practice for multi-domain machines that accept mail. The reason being that when a connection is coming in the recipient server has no idea (initially) what domain the message is destined for, so it should answer with an IP address since this IP address *should always* be the answer when checking a domain's MX record versus the domain name which may not be related to the recipient domain. For diagnosing purposes when the sending admin checks the logs and sees the IP address for the server he can then check the MX record and verify the IP address. These days it's a given that a mail server is accepting mail for multiple domains and this does not matter as much, but I have seen it used for a lot of older email shops. Thanks for the explanation Jake. To be honest though, I don't really follow your logic. This has nothing to do with MX records that I've seen in the RFCs. BL, I agree it doesn't matter much, at least until a server refuses mail from you because of it. I still think that the best value here is a hostname that has a type A record matching the IP address that is used to connect to the host. If this is the case and a receiving server has a problem with the name, then I think the problem lies with the receiving server. The MX record is a side item and really means nothing. I was throwing that in there to show some diagnostic uses. I deliver a message to you at mail.shubes.net. Your server response that it's [192.168.0.1] since it does not know what domain the incoming message is for. This can sometimes give you less problems than mailers that expect to connect to mail.shubes.net when your server responds that it's incoming.ejs.net or something. It also can cause less problems in the corporate world if some brighter-than-normal person performs a telnet session and finds that you're not only running their email, but a competitor's as well or other similar situation. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] spambox
Toni Cosma wrote: Hi list, The spambox option is active on my qmailtoaster server. Some emails that are not spam are marked as spam and are moved in the spam folder and other emails that obiously are spam remain in my inbox folder. Its there a solution without whitelist the sender domain to unmark the sender that are not spam ? ... and to manually mark the spam from my inbox ? Thx Toni Not an easy way, no. At the CLI you need to feed the real message to sa-learn and tell it that it's ham, and the other message needs to be fed to sa-learn and told it's spam.
Re: [qmailtoaster] qtp-newmodel on Fedora 11
petrus wrote: running qtp-newmodel on Fedora11, im running into problems with the new FUSE chroot [..] Would you like a unionfs/overlay sandbox? (recommended) [y]/n: y Using FUSE union filesystem ... qtp-mount-sandbox v0.3.3 qtp-mount-sandbox - installing fuse-unionfs ... qtp-mount-sandbox - this could take a few moments - please be patient Loaded plugins: dellsysidplugin2, refresh-packagekit qtp-Fedora qtp-Fedora/primary qtp-Fedora Setting up Install Process Resolving Dependencies -- Running transaction check --- Package fuse-unionfs.i586 0:0.23-1.qtp set to be updated -- Processing Dependency: libfuse.so.2(FUSE_2.8) for package: fuse-unionfs-0.23-1.qtp.i586 -- Running transaction check --- Package fuse.i586 0:2.8.0-1.qtp set to be updated -- Finished Dependency Resolution Dependencies Resolved === Package Arch Version === Installing: fuse i586 2.8.0-1.qtp replacing fuse-libs.i586 2.7.4-3.fc11 fuse-unionfs i586 0.23-1.qtp Transaction Summary === Install 2 Package(s) Upgrade 0 Package(s) Total download size: 165 k Downloading Packages: (1/2): fuse-2.8.0-1.qtp.fc11.i586.rpm (2/2): fuse-unionfs-0.23-1.qtp.fc11.i586.rpm --- Total Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : fuse-2.8.0-1.qtp.i586 MAKEDEV: no such group: fuse warning: group fuse does not exist - using root Installing : fuse-unionfs-0.23-1.qtp.i586 service fuse does not support chkconfig Error in PREUN scriptlet in rpm package fuse Erasing: fuse-libs-2.7.4-3.fc11.i586 error: %preun(fuse-2.7.4-3.fc11.i586) scriptlet failed, exit status 1 fuse-2.7.4-3.fc11.i586 was supposed to be removed but is not! Installed: fuse.i586 0:2.8.0-1.qtp fuse-union Replaced: fuse-libs.i586 0:2.7.4-3.fc11 Complete! qtp-mount-sandbox - installation of dependent packages failed qtp-mount-sandbox - is your qmailtoaster-plus.repo package up to date? qtp-newmodel - qtp-mount-sandbox failed, exiting So did i forget to update the repo? r...@fury:~ yum update qmailtoaster-plus.repo Loaded plugins: dellsysidplugin2, refresh-packagekit qtp-nodist | 951 B 00:00 updates/metalink| 24 kB 00:00 Setting up Update Process No Packages marked for Update nope The package installation is failing on your system for some reason. I'll have to look at the %prerun in the package to see why. Give me a few days on this since I've got a few things to do this week. Thanks. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] spambox
Jake Vickers wrote: Toni Cosma wrote: Hi list, The spambox option is active on my qmailtoaster server. Some emails that are not spam are marked as spam and are moved in the spam folder and other emails that obiously are spam remain in my inbox folder. Its there a solution without whitelist the sender domain to unmark the sender that are not spam ? ... and to manually mark the spam from my inbox ? Thx Toni Not an easy way, no. At the CLI you need to feed the real message to sa-learn and tell it that it's ham, and the other message needs to be fed to sa-learn and told it's spam. Hi Jake, You are so right, Not and easy way. :)) And if I whitelist the ok domains what to do with the spam or emails that I consider to be spam ? - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] spambox
Toni Cosma wrote: Jake Vickers wrote: Toni Cosma wrote: Hi list, The spambox option is active on my qmailtoaster server. Some emails that are not spam are marked as spam and are moved in the spam folder and other emails that obiously are spam remain in my inbox folder. Its there a solution without whitelist the sender domain to unmark the sender that are not spam ? ... and to manually mark the spam from my inbox ? Thx Toni Not an easy way, no. At the CLI you need to feed the real message to sa-learn and tell it that it's ham, and the other message needs to be fed to sa-learn and told it's spam. Hi Jake, You are so right, Not and easy way. :)) And if I whitelist the ok domains what to do with the spam or emails that I consider to be spam ? On a domain level, you can blacklist them or add them to your badmailfrom file, or block their IPs at the firewall (my favorite).
Re: [qmailtoaster] Fully qualified hostname with multiple domain names
quote It also can cause less problems in the corporate world if some brighter-than-normal person performs a telnet session and finds that you're not only running their email, but a competitor's as well or other similar situation. I liked this answer so much because I have a situation like this :) Regards Lucian Jake Vickers wrote: Eric Shubert wrote: Jake Vickers wrote: Eric Shubert wrote: Interesting. I don't buy that using an IP address is necessarily the best practice though. Here are my thoughts on this. It does not matter so much these days, but it used to be best practice for multi-domain machines that accept mail. The reason being that when a connection is coming in the recipient server has no idea (initially) what domain the message is destined for, so it should answer with an IP address since this IP address *should always* be the answer when checking a domain's MX record versus the domain name which may not be related to the recipient domain. For diagnosing purposes when the sending admin checks the logs and sees the IP address for the server he can then check the MX record and verify the IP address. These days it's a given that a mail server is accepting mail for multiple domains and this does not matter as much, but I have seen it used for a lot of older email shops. Thanks for the explanation Jake. To be honest though, I don't really follow your logic. This has nothing to do with MX records that I've seen in the RFCs. BL, I agree it doesn't matter much, at least until a server refuses mail from you because of it. I still think that the best value here is a hostname that has a type A record matching the IP address that is used to connect to the host. If this is the case and a receiving server has a problem with the name, then I think the problem lies with the receiving server. The MX record is a side item and really means nothing. I was throwing that in there to show some diagnostic uses. I deliver a message to you at mail.shubes.net. Your server response that it's [192.168.0.1] since it does not know what domain the incoming message is for. This can sometimes give you less problems than mailers that expect to connect to mail.shubes.net when your server responds that it's incoming.ejs.net or something. It also can cause less problems in the corporate world if some brighter-than-normal person performs a telnet session and finds that you're not only running their email, but a competitor's as well or other similar situation. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Fully qualified hostname with multiple domain names
Lucian Cristian wrote: quote It also can cause less problems in the corporate world if some brighter-than-normal person performs a telnet session and finds that you're not only running their email, but a competitor's as well or other similar situation. I liked this answer so much because I have a situation like this :) Regards Lucian I have the same dog-bite in my rear as well ;) - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
RE: [qmailtoaster] RE: Mails not being scanned / filtered by SA server
Here is the tcp.smtp file: [r...@mail ~]# cat /etc/tcprules.d/tcp.smtp 127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private :allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONG RCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan,NOP0FCHECK=1,DKSIGN=/v ar/qmail/control/domainkeys/%/private -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: Saturday, October 03, 2009 8:51 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] RE: Mails not being scanned / filtered by SA server Please post your new tcp.smtp file so we can be sure the format is correct. Atul Paralikar wrote: I have added those lines to tcp.smtp file and run the command qmailctl cdb. But since there is a problem of Perl module of SA, will it still accept emails and forward it to destination mail server? Or since SA is not working, it will reject all mails? I hope you understand my concern. How do I fix the perl + SA issue? -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: Saturday, October 03, 2009 7:42 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] RE: Mails not being scanned / filtered by SA server You are missing: QMAILQUEUE=/var/qmail/bin/simscan,NOP0FCHECK=1 variables in the 2nd line of the tcp.smtp file. Don't forget to qmailctl cdb after this file is changed. You don't really need the first (127.:) line at all in this file either. That's only used for apps running on the same server that might be submitting email via port 25 without authenticating (e.g. Squirrelmail, at least the way it's presently configured on the toaster). -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Dovecot howto
On my office servers I have Dovecot one year but I didn't know how it is
fast.
Yesterday I installed the newest version 1.2.5 on my private server.
It's 2-3 times faster then courier-imap. Source from
http://atrpms.net/dist/el5/dovecot/ a little modification in spec file
(added compile option --with-vpopmail) and voila.
Next stop qmail, remove: courier-authlib-toaster, courier-imap-toaster
and qmail-pop3d-toaster and check /var/qmail/supervise directory. There
should be only: clamd, send, smtp, spamd and submission.
Then migration: http://www.dovecot.org/tools/courier-dovecot-migrate.pl
described on http://wiki.dovecot.org/Migration/Courier
Next edit /etc/dovecot.conf:
8-- patch
--- dovecot.conf.org2009-10-05 14:57:16.0 +0200
+++ dovecot.conf2009-10-05 16:42:06.0 +0200
@@ -238,15 +238,17 @@
# explicitly, ie. mail_location does nothing unless you have a namespace
# without a location setting. Default namespace is simply done by having a
# namespace with empty prefix.
-#namespace private {
+namespace private {
# Hierarchy separator to use. You should use the same separator for all
# namespaces or some clients get confused. '/' is usually a good one.
# The default however depends on the underlying mail storage format.
#separator =
+ separator = .
# Prefix required to access this namespace. This needs to be
different for
# all namespaces. For example Public/.
#prefix =
+ prefix = INBOX.
# Physical location of the mailbox. This is in same format as
# mail_location, which is also the default for it.
@@ -255,6 +257,7 @@
# There can be only one INBOX, and this setting defines which namespace
# has it.
#inbox = no
+ inbox = yes
# If namespace is hidden, it's not advertised to clients via NAMESPACE
# extension. You'll most likely also want to set list=no. This is
mostly
@@ -271,7 +274,7 @@
# Namespace handles its own subscriptions. If set to no, the parent
# namespace handles them (empty prefix should always have this as
yes)
#subscriptions = yes
-#}
+}
# Example shared namespace configuration
#namespace shared {
@@ -298,6 +301,8 @@
# or names. doc/wiki/UserIds.txt
#mail_uid =
#mail_gid =
+mail_uid = 89
+mail_gid = 89
# Group to enable temporarily for privileged operations. Currently this is
# used only with INBOX when either its initial creation or dotlocking
fails.
@@ -377,6 +382,8 @@
# be done even if first_valid_uid is set to 0.
#first_valid_uid = 500
#last_valid_uid = 0
+first_valid_uid = 89
+last_valid_uid = 89
# Valid GID range for users, defaults to non-root/wheel. Users having
# non-valid GID as primary group ID aren't allowed to log in. If user
@@ -384,6 +391,8 @@
# not set.
#first_valid_gid = 1
#last_valid_gid = 0
+first_valid_gid = 89
+last_valid_gid = 89
# Maximum number of running mail processes. When this limit is reached,
# new users aren't allowed to log in.
@@ -908,7 +917,7 @@
# database (passwd usually), you can use static userdb.
# REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM
# authentication to actually work. doc/wiki/PasswordDatabase.PAM.txt
- passdb pam {
+ #passdb pam {
# [session=yes] [setcred=yes] [failure_show_msg=yes]
[max_requests=n]
# [cache_key=key] [service name]
#
@@ -941,7 +950,7 @@
# args = session=yes %Ls
# args = cache_key=%u dovecot
#args = dovecot
- }
+ #}
# System users (NSS, /etc/passwd, or similiar)
# In many systems nowadays this uses Name Service Switch, which is
@@ -995,12 +1004,12 @@
#}
# vpopmail authentication doc/wiki/AuthDatabase.VPopMail.txt
- #passdb vpopmail {
+ passdb vpopmail {
# [cache_key=key] - See cache_key in PAM for explanation.
# [quota_template=template] - %q expands to Maildir++ quota
# (eg. quota_template=quota_rule=*:backend=%q)
-#args =
- #}
+args = webmail=127.0.0.1
+ }
#
# User database specifies where mails are located and what
user/group IDs
@@ -1073,8 +1082,9 @@
#}
# vpopmail doc/wiki/AuthDatabase.VPopMail.txt
- #userdb vpopmail {
- #}
+ userdb vpopmail {
+args = quota_template=quota_rule=*:backend=%q
+ }
# User to use for the process. This user needs access to only user and
# password databases, nothing else. Only shadow and pam authentication
@@ -1091,6 +1101,7 @@
# Number of authentication processes to create
#count = 1
+ count = 1
# Require a valid SSL client certificate or the authentication fails.
#ssl_require_client_cert = no
@@ -1191,6 +1202,7 @@
# quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
# quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80
#quota = maildir
+ quota = maildir:ignore=Trash
# ACL plugin. vfile backend reads ACLs from dovecot-acl file from
maildir
# directory. You can also optionally give a global ACL directory
path where
8-- EOT patch
Start services qmail and
Re: [qmailtoaster] Fwd: Cron r...@mailserv /usr/sbin/clamav-unofficial-sigs.sh -c /etc/clamav-unofficial-sigs.conf
See response below; Kartone wrote: Hi, after upgrading my toaster via qtp-newmodel i'm receiving again (remember last thread? :-D ) this message hourly. In my clamav-unofficial-sigs.conf i have set: curl_silence=yes# Default is no to report curl statistics rsync_silence=yes # Default is no to report rsync statistics gpg_silence=yes # Default is no to report gpg signature status comment_silence=yes # Default is no to report script comments Is there any way to avoid this message ? Thanks! Inizio messaggio inoltrato: Da: r...@kartonet.info (Cron Daemon) Data: 06 ottobre 2009 09.28.57 GMT+02.00 A: r...@kartonet.info Oggetto: Cron r...@mailserv /usr/sbin/clamav-unofficial-sigs.sh - c /etc/clamav-unofficial-sigs.conf Restarting clamd /var/qmail/supervise/clamd: up (pid 11860) 21452 seconds /var/qmail/supervise/clamd/log: up (pid 22163) 1 seconds The easiest fix for me has been changing the mailto=wh...@youwantit.tld in the conf file. Hourly would be from /etc/crontab. Sidenote, if you have any crons runing from the comand cron -l you will have to edit it with the command cron -e and I suggest adding the line at the top: mailto=wh...@youwantit.tld It worked for me. Kent Busbee Director of Technology Northlake Christian School - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] Multiple domain names in header
Hi all, Thanks again for the help resolving the fully qualified hostname question. Here's another (and hopefully the last): When we send e-mail to someone with an @msn.com address it is immediately rejected. The message hints that it may be spam-related, but that is definitely not true. Our hosting provider is extremely careful about that, our businesses do not send mass e-mails, and I just double-checked our IP address on Spamhaus and it is clean. This might have to do with my QMT configuration for our two domains. Here are the headers from a rejected message (I obscured the recipient's username but nothing else is changed): Hi. This is the qmail-send program at pmcawab.parkermerrick.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. recipi...@msn.com cjccat...@msn.com: Connected to 65.55.37.120 but sender was rejected. Remote host said: 550 OU-001 Mail rejected by Windows Live Hotmail for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation problems. If you are not an email/network admin please contact your E-mail/Internet Service Provider for help. Email/network admins, please visit http://postmaster.live.com for email delivery information and support --- Below this line is a copy of the message. Return-Path: a...@awabllc.com a...@awabllc.com Received: (qmail 3540 invoked by uid 89); 6 Oct 2009 20:56:51 - Received: by simscan 1.3.1 ppid: 3533, pid: 3536, t: 0.0729s scanners: attach: 1.3.1 clamav: 0.95.1 /m:50/d:9332 Received: from unknown (HELO ?137.52.23.46?) (a...@parkermerrick.com@137.52.23.46) by pmcawab with ESMTPA; 6 Oct 2009 20:56:51 - Message-ID: 4acbaf11.3080...@awabllc.com 4acbaf11.3080...@awabllc.com Date: Tue, 06 Oct 2009 16:56:49 -0400 From: Adam Glass a...@awabllc.com a...@awabllc.com User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: recipi...@msn.com cjccat...@msn.com Subject: Hose clamps Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I tried changing our me and smtpgreeting files two different ways, but with the same result. In one case I put [137.52.23.46] into the me file. In the other case I changed me and smtpgreeting to use the awabllc name instead of parkermerrick. QMT was restarted after each change, but no joy. Any suggestions or advice would be most appreciated. Thank you! --Adam
Re: [qmailtoaster] Multiple domain names in header
An e-mail address with two @ symbols is ALWAYS illegal... since SMTP was introduced in RFC 821 in 1982! Your me file should contain your FQDN -- independent of which domains you're hosting! Just my thoughts... Dan IT4SOHO --- IT4SOHO, LLC 224 13th Ave N St. Petersburg, FL 33701-1122 877-IT4SOHO: Toll Free 727-647-7646 In Pinellas 813-464-2093 In Hillsborough 727-507-9435 Fax Only We make IT work for small business! Adam Glass wrote: Hi all, Thanks again for the help resolving the fully qualified hostname question. Here's another (and hopefully the last): When we send e-mail to someone with an @msn.com http://msn.com address it is immediately rejected. The message hints that it may be spam-related, but that is definitely not true. Our hosting provider is extremely careful about that, our businesses do not send mass e-mails, and I just double-checked our IP address on Spamhaus and it is clean. This might have to do with my QMT configuration for our two domains. Here are the headers from a rejected message (I obscured the recipient's username but nothing else is changed): Hi. This is the qmail-send program at pmcawab.parkermerrick.com http://pmcawab.parkermerrick.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. recipi...@msn.com: Connected to 65.55.37.120 but sender was rejected. Remote host said: 550 OU-001 Mail rejected by Windows Live Hotmail for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation problems. If you are not an email/network admin please contact your E-mail/Internet Service Provider for help. Email/network admins, please visit http://postmaster.live.com for email delivery information and support --- Below this line is a copy of the message. Return-Path: a...@awabllc.com Received: (qmail 3540 invoked by uid 89); 6 Oct 2009 20:56:51 - Received: by simscan 1.3.1 ppid: 3533, pid: 3536, t: 0.0729s scanners: attach: 1.3.1 clamav: 0.95.1 /m:50/d:9332 Received: from unknown (HELO ?137.52.23.46?) (a...@parkermerrick.com@137.52.23.46) by pmcawab with ESMTPA; 6 Oct 2009 20:56:51 - Message-ID: 4acbaf11.3080...@awabllc.com Date: Tue, 06 Oct 2009 16:56:49 -0400 From: Adam Glass a...@awabllc.com User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: recipi...@msn.com Subject: Hose clamps Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I tried changing our me and smtpgreeting files two different ways, but with the same result. In one case I put [137.52.23.46] into the me file. In the other case I changed me and smtpgreeting to use the awabllc name instead of parkermerrick. QMT was restarted after each change, but no joy. Any suggestions or advice would be most appreciated. Thank you! --Adam
RE: [qmailtoaster] Multiple domain names in header
If you join there Junk Mail Sender group you can get yourself removed very fast. https://support.msn.com/eform.aspx?productKey=edfsjmrpp https://support.msn.com/eform.aspx?productKey=edfsjmrpppage=support_home_o ptions_form_byemailct=eformtsscrx=1 page=support_home_options_form_byemailct=eformtsscrx=1 This is similar to Return Path with there feedback loop, The biggest thing with MSN is having a Reverse DNS, and have a decent sender score. I would signup with there Sender group first and get yourself removed, it harder when you email them they don't seem to check there support queues very much. _ From: Adam Glass [mailto:adamgl...@gmail.com] Sent: Tuesday, October 06, 2009 2:21 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Multiple domain names in header Hi all, Thanks again for the help resolving the fully qualified hostname question. Here's another (and hopefully the last): When we send e-mail to someone with an @msn.com address it is immediately rejected. The message hints that it may be spam-related, but that is definitely not true. Our hosting provider is extremely careful about that, our businesses do not send mass e-mails, and I just double-checked our IP address on Spamhaus and it is clean. This might have to do with my QMT configuration for our two domains. Here are the headers from a rejected message (I obscured the recipient's username but nothing else is changed): Hi. This is the qmail-send program at pmcawab.parkermerrick.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. mailto:cjccat...@msn.com recipi...@msn.com: Connected to 65.55.37.120 but sender was rejected. Remote host said: 550 OU-001 Mail rejected by Windows Live Hotmail for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation problems. If you are not an email/network admin please contact your E-mail/Internet Service Provider for help. Email/network admins, please visit http://postmaster.live.com http://postmaster.live.com/ for email delivery information and support --- Below this line is a copy of the message. Return-Path: mailto:a...@awabllc.com a...@awabllc.com Received: (qmail 3540 invoked by uid 89); 6 Oct 2009 20:56:51 - Received: by simscan 1.3.1 ppid: 3533, pid: 3536, t: 0.0729s scanners: attach: 1.3.1 clamav: 0.95.1 /m:50/d:9332 Received: from unknown (HELO ?137.52.23.46?) (a...@parkermerrick.com@137.52.23.46) by pmcawab with ESMTPA; 6 Oct 2009 20:56:51 - Message-ID: mailto:4acbaf11.3080...@awabllc.com 4acbaf11.3080...@awabllc.com Date: Tue, 06 Oct 2009 16:56:49 -0400 From: Adam Glass mailto:a...@awabllc.com a...@awabllc.com User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: recipi...@msn.com mailto:cjccat...@msn.com Subject: Hose clamps Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I tried changing our me and smtpgreeting files two different ways, but with the same result. In one case I put [137.52.23.46] into the me file. In the other case I changed me and smtpgreeting to use the awabllc name instead of parkermerrick. QMT was restarted after each change, but no joy. Any suggestions or advice would be most appreciated. Thank you! --Adam
Re: [qmailtoaster] Multiple domain names in header
Hmm ... then maybe there is a more basic question. When creating users for QMT, I made usernames with an @ symbol because it seemed things got confused otherwise. That is, I have the following usernames: a...@parkermerrick.com - for the parkermerrick.com virtual domain a...@awabllc.com - for the awabllc.com virtual domain This has not been a problem in the 3 or 4 months we've been using the server, but should it be changed? Can I have the username as just adam for both virtual domains, or will that confuse things? Thanks, --Adam On Tue, Oct 6, 2009 at 5:31 PM, Dan McAllister d...@it4soho.com wrote: An e-mail address with two @ symbols is ALWAYS illegal... since SMTP was introduced in RFC 821 in 1982! Your me file should contain your FQDN -- independent of which domains you're hosting! Just my thoughts... Dan IT4SOHO --- IT4SOHO, LLC 224 13th Ave N St. Petersburg, FL 33701-1122 877-IT4SOHO: Toll Free 727-647-7646 In Pinellas 813-464-2093 In Hillsborough 727-507-9435 Fax Only We make IT work for small business! Adam Glass wrote: Hi all, Thanks again for the help resolving the fully qualified hostname question. Here's another (and hopefully the last): When we send e-mail to someone with an @msn.com address it is immediately rejected. The message hints that it may be spam-related, but that is definitely not true. Our hosting provider is extremely careful about that, our businesses do not send mass e-mails, and I just double-checked our IP address on Spamhaus and it is clean. This might have to do with my QMT configuration for our two domains. Here are the headers from a rejected message (I obscured the recipient's username but nothing else is changed): Hi. This is the qmail-send program at pmcawab.parkermerrick.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. recipi...@msn.com cjccat...@msn.com: Connected to 65.55.37.120 but sender was rejected. Remote host said: 550 OU-001 Mail rejected by Windows Live Hotmail for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation problems. If you are not an email/network admin please contact your E-mail/Internet Service Provider for help. Email/network admins, please visit http://postmaster.live.com for email delivery information and support --- Below this line is a copy of the message. Return-Path: a...@awabllc.com a...@awabllc.com Received: (qmail 3540 invoked by uid 89); 6 Oct 2009 20:56:51 - Received: by simscan 1.3.1 ppid: 3533, pid: 3536, t: 0.0729s scanners: attach: 1.3.1 clamav: 0.95.1 /m:50/d:9332 Received: from unknown (HELO ?137.52.23.46?) (a...@parkermerrick.com@137.52.23.46) by pmcawab with ESMTPA; 6 Oct 2009 20:56:51 - Message-ID: 4acbaf11.3080...@awabllc.com 4acbaf11.3080...@awabllc.com Date: Tue, 06 Oct 2009 16:56:49 -0400 From: Adam Glass a...@awabllc.com a...@awabllc.com User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: recipi...@msn.com cjccat...@msn.com Subject: Hose clamps Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I tried changing our me and smtpgreeting files two different ways, but with the same result. In one case I put [137.52.23.46] into the me file. In the other case I changed me and smtpgreeting to use the awabllc name instead of parkermerrick. QMT was restarted after each change, but no joy. Any suggestions or advice would be most appreciated. Thank you! --Adam
Re: [qmailtoaster] From_failed problem
Hi again, after multiple test, i think i know what's the problem When the phpmailer script tries to send to an email with bad dns resolve (for example, an email for an expired domain), the mail server can't continue and every email send attempt from that script may fail. If reconnect to the server and continues with next email, the mail server works again. In resume, when open a session (smtp keep alive) in the mail server, and get a dns resolve problem, qmailtoaster returns problems and no send email until reconnect and continue with an email that resolver well its domain Eric Shubert escribió: Aleksander Podsiadly wrote: W dniu 04.10.2009 18:49, Fernando Ortega pisze: But the same script is working with another mail server fine, without problems. The Language string problem it's only a warning because the lang directory isn't installed, but isn't important. [...] Check the log files (Apache, QMT, system), IMO there should be an answer. I agree. The smtp log is the first thing I'd check, since that's where they'd be coming in. The send log should show them going out. qmlog is a good tool for checking QMT logs. See http://qtp.qmailtoaster.com - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
[qmailtoaster] create 'New Forward' from command line
Dear List, Can i create new forward account from command line? Is there any utility in /home/vpopmail/bin can do this? where will be the man pages for the utilities in /home/vpopmail/bin located? Please suggest me... Thanks and Regards, S.Senthilvel,
Re: [qmailtoaster] create 'New Forward' from command line
W dniu 07.10.2009 06:47, senthil vel pisze: Dear List, Can i create new forward account from command line? Is there any utility in /home/vpopmail/bin can do this? where will be the man pages for the utilities in /home/vpopmail/bin located? Please suggest me... Thanks and Regards, S.Senthilvel, As root: su -s /bin/bash - vpopmail and as vpopmail: valias -i u...@domain ali...@domain valias -i u...@domain ali...@domain -- Pozdrawiam / Regards, Aleksander Podsiad?y mail: a...@westside.kielce.pl jid: a...@jabber.westside.kielce.pl ICQ: 201121279 gg: 9150578
