Array
(
[startpos] => 1
[where] => AND i.iblog = 1 AND i.inumber IN (3,18,22,27)
[total_pages] => 1
[total_items] => 4
[page_amount] => 5
[current_page] => 1
[offset] => 0
[prev_page] => 1
[next_page] => 1
[first_link] => http://ebullientworks.com/tag/mail/page_1
[last_link] => http://ebullientworks.com/tag/mail/page_1
[prev_link] => http://ebullientworks.com/tag/mail/page_1
[next_link] => http://ebullientworks.com/tag/mail/page_1
)
SELECT i.inumber as itemid, i.ititle as title, i.ibody as body, m.mname as author, m.mrealname as authorname, i.itime, i.imore as more, m.mnumber as authorid, m.memail as authormail, m.murl as authorurl, c.cname as category, i.icat as catid, i.iclosed as closed FROM nucleus_item as i, nucleus_member as m, nucleus_category as c WHERE i.iblog=1 and i.iauthor=m.mnumber and i.icat=c.catid and i.idraft=0 and i.itime<="2008-12-05 03:50:00" AND i.iblog = 1 AND i.inumber IN (3,18,22,27) ORDER BY i.itime DESC LIMIT 1,5
stdClass Object
(
[itemid] => 22
[title] => Courier-IMAP, Postfix, Amavis, Maildrop, SpamAssassin
[body] => I got my previous mail install (Courier-IMAP, Postfix, MySQL, SquirrelMail, Amavis, Clam-AV), working with Maildrop and SpamAssassin this weekend.
I’m using a sitewide install (there are only two of us, and we’re both virtual users – it made more sense to share the SpamAssassin config than to rig up the separate prefs, etc.).
[author] => erin
[authorname] => Erin Schnabel
[itime] => 2004-02-29 05:22:00
[more] =>
References:
- Postfix w/ SASL Courier IMAP w/ SSL Maildrop MySQL SpamAssassin HOWTO
- SpamAssassin: Using SpamAssassin for an entire site
- HOWTO: Bayesian filtering with SpamAssassin, courier-imap and maildrop
- [imp] [sam] SA + Maildrop + IMP spam reporting
[authorid] => 1
[authormail] => erinschnabel@gmail.com
[authorurl] => http://ebullientworks.com/
[category] => General
[catid] => 1
[closed] => 0
)
Sunday, 29 February 2004
I got my previous mail install (Courier-IMAP, Postfix, MySQL, SquirrelMail, Amavis, Clam-AV), working with Maildrop and SpamAssassin this weekend.
I’m using a sitewide install (there are only two of us, and we’re both virtual users – it made more sense to share the SpamAssassin config than to rig up the separate prefs, etc.).
»
Read More
posted by
erin at 05:22 AM
in
General
tags:
mail
stdClass Object
(
[itemid] => 18
[title] => Got It!
[body] => Finally, a lucid explanation about how to set up Postfix to use SMTP AUTH as a client.
Of course, I found this after making changes to SquirrelMail for sitewide auth, but I think those changes will still be useful for someone…
[author] => erin
[authorname] => Erin Schnabel
[itime] => 2004-01-04 02:01:00
[more] =>
Just in case the text mysteriously vanishes:
Relay Set Up (postfix)
In following examples * should be substituted with your second level domain (sbcglobal, ameritech, pacbell, swbell, etc.)
You need to either set up your designated smtp.*.yahoo.com server as either relayhost (to relay all mail), or /etc/postfix/transport (man 5 transport) to only relay for specific destination domains. For either relayhost or transport you may have to enclose the relay in square brackets like relayhost = [smtp.*.yahoo.com] so the bogus MX record will be ignored.
transport file example:
ameritech.net smtp:[smtp.*.yahoo.com]
.ameritech.net smtp:[smtp.*.yahoo.com]
Do likewise for other SBC related domains on the left like pacbell.net, prodigy.net, prodigy.com, sbcglobal.net, snet.net, swbell.net, yahoo.com. Then do postmap /etc/postfix/transport to update transport.db.
Postfix as SMTP AUTH Client
Things you need to enable or add to /etc/postfix/main.cf:
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
- above blank to clear default noplaintext since SBC auth is plain text
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
With smtp.*.yahoo.com now as CNAME for smtp-sbc.mail.yahoo.com, this works in sasl_passwd file:
# this worked before
smtp-sbc.mail.yahoo.comuser@yourSBC.domain:passwd
- this may be needed now (Dec 10, 2003):
smtp-sbc-v1.mail.vip.sc5.yahoo.comuser@yourSBC.domain:passwd
Then you need to postmap /etc/postfix/sasl_passwd to update sasl_passwd.db (or just run SuSEconfig in SuSE). Since I am new to postfix I do not know how to get verbose output of what it is doing, but either your mail logs should tell you if it sent successfully, or the bounce error will tell you why not, if your return address is valid.
This worked grand for me. I have my transport table in MySQL, and added what I needed to use my ISPs SMTP server.
Be careful with the sasl settings, there is a matching set starting with smtpd_ that are for Postfix SMTP acting as a server. Make sure you use the ones without the _d_ to effect client behavior..
[authorid] => 1
[authormail] => erinschnabel@gmail.com
[authorurl] => http://ebullientworks.com/
[category] => General
[catid] => 1
[closed] => 0
)
Sunday, 04 January 2004
Finally, a lucid explanation about how to set up Postfix to use SMTP AUTH as a client.
Of course, I found this after making changes to SquirrelMail for sitewide auth, but I think those changes will still be useful for someone…
»
Read More
posted by
erin at 02:01 AM
in
General
tags:
mail
Friday, 05 September 2003
posted by
erin at 12:25 AM
in
General
tags:
mail