Anybody using this? It does look promising but i dont wanna get my machine reset again :P.

I've asked on the cobalt mailing list one person answered saying it works good and no problems with it.

we used to have the older version, if you have the older one installed, please uninstall it first.I just updated our raq3's pop before smtp to the newwer version and so far nothing broke ;)

elijaH

I'm running it and its working fine for me.

Hi everybody,
duh...I installed the new POP-before-SMTP 4.0.7 before removing the old one.

Is there any way reinstalling the new version as I can't uninstall it? The GUI only gives me the standard error "Package already exists". Moving, renaming and deleting didn't work either.

Man, I'm getting old. :-((

Thanx for any help!

Chris

I've got the same problem I tried everything. But still no succes. Who could help me?

I've got my smtp to work again thanx to the cobalt-users list. :):)

http://list.cobalt.com/pipermail/cobalt-users/2001-March/035965.html

Succes with it

Try this url ...http://pkg.nl.cobalt.com/howto/cobalt_uninstall_howto.html

Well done Starhost! Good job!
I got mine back to work as well!

Now I can get older again. <g>

Chris

Thanx :):)

But why did you install the old version again? The new one is working fine for me at the moment.

OK...here's what I did:

- old version was installed
- installed new version
- uninstalled the old version afterwards
- realized that I messed something up
- bit my a**
- sent a message to this forum (and also to Cobalt Support)
- you enlightened us with the link
- I renamed the md5lst to "nicetry"
- installed the new version again (with a little error I can't recall - something with "...patch")
- renamed "nicetry" back to the original name

...and then it worked.

BTW: That's what I like in forums...replies are much faster than from support departments. Anyway, Cobalt support seems to redirect every user with a problem directly to their expensive Pro Support. Due to their sometimes massive changes in the installed Linux you are more or less stuck with them and can't simply use third party stuff w/o messing everything up. Just cool hardware doesn't justify their prices (my RaQ3i really made a whole in my earnings) - a decent support should be included as well.

Chris

what is the advantage of the new one over the old one: POP Authenticated SMTP Relaying Release 1.3pre1 ?

The new one is an official release, the old one isn't. I don't know what's different

The new one allows you to enable and disable the pop b4 smtp relay and you can specify the timeout value.

elijaH :)

I've got RaQ4 and installed RaQ4-en-System-1.0.7-9229.pkg (POP-before-SMTP 1.0.7).

According to the manual I had the impression that
- everyone who's matching the "Relay for the following Hosts/Domains" entries, OR
- everyone who's doing pop-before-smtp
is allowed to send mail, but it seems to me that
both restrictions apply: you can only send mail when you pop AND match the relay domains...

So when I've installed the POP-before patch can I say like everyone who's popping can use the SMTP by placing somthing like '*' into the relay host lists?

a.) how can I accomplish something like '*'
b.) if I do this do I open a big door to spammers?

Originally posted by elijah
The new one allows you to enable and disable the pop b4 smtp relay and you can specify the timeout value.

elijaH :)

POP Authenticated SMTP Relaying Release 1.3pre1 does that as well.

iplexx-
The point is, that you *want* people to check their pop before sending mail. Anyway, that's the point of the scipt...

(preface: ppl should use their ISP SMTP whenever possible)
Ofcourse I want ppl to pop-before but I just don't get the relation to the domain/host relay list....

On a test account i did "check my pop" but still got "relaying denied" when trying to send mail. So I entered the sender IP in the relay list, and it worked fine.
(yes, pop-before-smtp is enabled ;))

Confused I read Cobalt's manual for pop-before again, and I understood it like "with pop-before the IP of the pop-checker is temporarly added to the relay list". But according to my tests this is not correct.

(Q1) So, if I allow everyone in the relay list to send mail, everyone should be able to when using pop-before, right?

(Q2) Just leaves open how I want to accomplish "allow everyone"... entering all TLD in the list? Adding all IP A-class networks?

(Q3) Is it sure if I do this that I don't open my server for spammers?

Thx!

Originally posted by iplexx
On a test account i did "check my pop" but still got "relaying denied" when trying to send mail. So I entered the sender IP in the relay list, and it worked fine.
(yes, pop-before-smtp is enabled ;))

Ok, I just read back into the thread and am trying to figure out what the problem might be. One, realize that I have the POP Authenticated SMTP Relaying Release 1.3pre1, not the RaQ4-en-System-1.0.7-9229.pkg installed.

On my machine, it works fine. No problems.

Assuming yours works fine (which it may or may not), you are checking the pop account, *then* clicking send on the message right? Even when I do this, every now and then it fails and I have to 'send' again and the message goes.

Now, this is without any modification to the relay list, etc.

If this does not happen, then I suggest you uninstall the pkg and install the one I have (only because it works on my machine).

As it still doesn't work I finally take some time to check this pop-b4-thing indeep...

I did some manual POP's and SMTPs and never could send mail; then checked sendmail ruleset which seems to be okay, the poprelayd is running, but I found out that if you check mail with POP3 the IP is not entered in the popip-database (/etc/mail/popip.db).

I made the DB world-writeable, nothing. I deleted it and created one from scratch. Nothing.

I really need to fix this because I definitly will not open a lot of class B networks just for sum dial up users.


Chicken, are you still running the 1.3pre1 or did you install the RaQ4-en-System-1.0.7-9229.pkg? Is the 1.3pre1 still avaible somewhere?

I'm still running 1.3pre2 and if you can't find it, I can email you a copy.

okay, finally I found the reason why pop-b4-smtp is not working for me:

all my users (not email aliases) are like <domainname>.<nr>,
ie. if hans.com has 10 users they're named hans.01, hans.02, ..., hans.10

if I create a user just called hans01 (without dot!) the pop-b4-thing works fine, if hans.01 tries to send email he gets 'relaying denied... check mail first' even if he did.

I found a posting describing the problem at the cobalt's mailing list http://list.cobalt.com/pipermail/cobalt-users/2001-April/039903.html but no solution for it....

Is this a general bug in pop-b4-smtp; or just a cobalt one; and is there a fix for it?

And I really don't want to delete and recreate all hans-dot-something users....


Chicken,
can you verify if this bug is at the pre-version too? thanks!

username jim.bob worked fine with sending.